Gateway Integration

Gateway is another interaction mode provided by Unlimit. It allows you to interact with the payment platform and perform payments, payouts, and refunds, as well as request additional information about transactions, for example, retrieve payment status.

Gateway utilizes Unlimit REST API resourses to send and receive requests. When a payment is performed, data about the transaction collected on the Merchant's website is sent in the form of an API request to the Unlimit Payment endpoint. Once the payment is processed, the Customer is redirected back to the Merchant's website and receives a notification with the status of the transaction.

Step 1: Obtain the PCI DSS certificate

PCI DSS is a set of policies and procedures that is intended to protect transactions data against theft and fraud. Any business that processes payments and card data must obtain the PCI DSS certificate.

PCI certification enhances the protection of transactions data through a set of requirements set by the PCI SSC.

To prove the compliance with these requirements, provide Unlimit with the following documents:

• The ASV scan report - for all Merchants

• The Self-Assessment Questionnaire (SAQ) - for Merchants that process up to 6 million operations annually

• The Attestation of Compliance (AOC) - for Merchants that process over 6 million operations annually

For more information on the PCI certification procedure, visit the PCI DSS website.

Once your business is PCI DSS compliant, you can process payments and card data safely.

Step 2: Collect payment data

When Gateway mode is used, the Customer enters credit card data on the Merchant's website and a payment is sent from Merchant to Unlimit server-to-server. Merchant has to collect cardholder data on his site that must be PCI DSS certified, and then send it as a POST request to the Unlimit Payment endpoint.

In response to Merchant's request, the Unlimit server replies with URL the Customer must be redirected to. When the payment is completed, the Customer is redirected back to the shop using one of the predefined URLs. Additionally, callbacks and/or email notifications are sent.