E-commerce acquiring, Apple Pay and Google Pay in Azerbaijan
Card payments on your website and in your app.
We set up card payments through local acquirers: integration, 3-D Secure, wallets and testing — through to the first live payment.
Illustration: what a typical integration checklist looks like. Real project plans are shared after the NDA.
First — the right setup
Where the user enters card details determines not only the interface but also how much of PCI DSS applies to you.
Acquirer's payment page
An iframe or a redirect. Card data never passes through your server — PCI DSS requirements are minimal, often SAQ A.
Direct API integration
Full control over the interface, but you handle card data — and the PCI DSS requirements grow considerably. Not always worth it.
More on the requirements on the PCI DSS page →
What's included
Integration with the acquirer's e-commerce API
Payment, cancellation, refund, recurring payments by token, status notifications.
EMV 3DS 2.x
3-D Secure working correctly through the acquirer — fewer declines and disputed payments.
Apple Pay
Via your acquirer or PSP: Merchant ID, certificates, domain verification.
Google Pay
Setting up the integration, token modes and 3-D Secure to meet the acquirer's requirements.
Testing and go-live
The acquirer's test scenarios, reconciliation, switching to live mode.
Multiple acquirers
Connecting a second acquirer and routing — so you don't depend on a single bank.
We've worked with the e-commerce APIs of
- Azericard
- Kapital Bank
- Unibank
- ATB
- PASHA Bank
- Yapı Kredi
Technical integrations. Does not imply a partnership or a client relationship.