🧩 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.
Updated about 2 months ago