๐งฉ 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 24 hours ago