API Reference

๐Ÿงฉ Integration Overview Flow

Our API supports three main integration flows depending on your architecture and needs:

๐Ÿ”Œ Integration Options

Choose the integration model that best fits your product and compliance requirements:


1. ๐Ÿง  H2H (Host-to-Host) Integration

Use this backend-to-backend integration when you want full control over the payment process.

You send all required data โ€” including:

  • ๐Ÿ’ณ Card information
  • ๐Ÿ‘ค Customer details
  • ๐Ÿ” 3DS authentication data

โœ… Best for: PCI-compliant merchants who want direct access to the payment flow
โš ๏ธ Note: You are responsible for securely handling card data and 3DS challenge responses.


2. ๐Ÿงฐ SDK Integration (Invisible Frontend)

Embed our JavaScript SDK into your checkout page to handle:

  • ๐Ÿ’ณ Card data collection
  • ๐Ÿ’ธ Payment execution
  • ๐Ÿ” 3DS authentication (frictionless or challenge)

The frontend initializes the SDK and receives the result asynchronously.

โœ… Best for: Merchants who want a native checkout experience with less PCI scope
๐Ÿ›ก๏ธ Benefit: 3DS flow is handled directly by our SDK, simplifying compliance


3. ๐ŸŒ Checkout Page Integration (Redirect Flow)

Redirect the customer to our secure hosted checkout page, where they:

  • ๐Ÿ’ณ Enter card details
  • ๐Ÿ” Complete 3DS authentication
  • โœ… Finalize the payment

Upon success, we redirect the customer back to your site using the configured return_url.

โœ… Best for: Fast integration with minimal compliance effort
๐Ÿš€ Advantage: Full UX and security handled by our platform


๐Ÿ“˜ Want to dive deeper into each model?
Check out our Integration Guides and API Reference for detailed steps and code samples.