Skip to main content

Choose your integration

Choose the integration protocol best suited for your solution. Each protocol differs in where payment data is collected, what PCI compliance level is required, and how much control the merchant has over the payment experience.

Merchant integration protocols​

Checkout integration​

The payer is redirected to Payment Platform's checkout page, which can also be embedded as an iframe on the merchant's website. The key advantage is that any additional parameters required during the payment flow are collected directly by Payment Platform. The trade-off is that the payment process is handled by Payment Platform, giving merchants less direct control over the experience.

Checkout overview

S2S Card​

All merchants that collect and process sensitive data (e.g., card details) must be PCI DSS compliant. With S2S Card, card details are collected by the merchant and transmitted to Payment Platform via API. There is no redirection to Payment Platform's checkout page. The payer is only redirected to the 3DS page when required. This protocol is applicable exclusively to card payments.

S2S Card overview

S2S APM​

S2S APM is used for actual APMs or any connector that requires redirection, including card payments where Payment Platform is not permitted to collect card details. The advantage is that merchants use their own pages, bypassing Payment Platform's checkout intermediary. The disadvantage is that merchants may need to continuously develop and maintain their pages to accommodate the specific parameters required by individual APMs.

S2S APM overview

Which protocol can a merchant use?​

When Payment Platform's connector (acquirer, provider) integration type is Direct Server-to-Server for cards, the available merchant protocols are:

  • S2S Card
  • Checkout

When the integration type is APM, or payment details are collected on the connector's payment page, the available merchant protocols are:

  • Checkout
  • S2S APM

More integration options​