Payment integrations · Build
Taking payments in markets where Stripe isn’t available
Where Stripe works we use it, and elsewhere we integrate the gateway your market or regulator requires. We have done this for five products in four markets.
EngagementHourly · remote
Hours9–18 CET · 4 h overlap
StackStripe · PayPal · Apple Pay
Proof3 case studies
The service in 4 parts
01 · Who it’s for
Companies that have to take payments in a market the usual tutorials don’t cover, or where a regulator or a license decides which payment partner they can use.
02 · What we’ve built
- Passport and ID card fees paid through a national government gateway in West Africa, with PayPal for applicants who live abroad. Both ways of paying lead into the same application flow.Case study 18 →
- Cross-border remittances on a licensed partner’s infrastructure. The partner verified the payer, and our system verified the payment instruments, including SWIFT and IBAN details.Case study 18 →
- Recurring charges for a marketplace’s advertisers through Stripe, PayPal, Apple Pay and Google Pay. A successful charge, a failed one and an upcoming one each send the customer a different message.Case study 07 →
- Coupons for collecting a remittance, printed at a terminal even when it has no network. A coupon becomes valid only when the system confirms it, so none can be paid out twice.Case study 11 →
We have also integrated a domestic payment gateway in Bosnia and Herzegovina.
03 · How we work
01 · PARTNER FIRSTBefore any code is written, we establish which partner the market, the regulator or the license requires.
02 · FOUR RECURRING PROBLEMSIdempotency, retries, reconciliation and webhook verification come up in every integration. On earlier products we solved them again each time, inside that product. Now we plan all four together at the start.
04 · Stack
StripePayPalApple PayGoogle Paynational gatewayswebhooksNode.js
Proof
Where we’ve done this before
Case study 18 · Business systems4 marketsPassport and ID card fees paid through a national government gateway in West Africa, with PayPal for applicants who live abroad. Both ways of paying lead into the same application flow.Read the case study →Case study 07 · Marketplace6 jobsRecurring charges for a marketplace’s advertisers through Stripe, PayPal, Apple Pay and Google Pay. A successful charge, a failed one and an upcoming one each send the customer a different message.Read the case study →Case study 11 · Identity3 domainsCoupons for collecting a remittance, printed at a terminal even when it has no network. A coupon becomes valid only when the system confirms it, so none can be paid out twice.Read the case study →
FAQ
Questions about this service
Then we integrate the partner your market recognizes. We have done this with a national government gateway in West Africa and with a domestic gateway in the Balkans.
That is common. The gateway a market requires is often the one with the least documentation and the smallest community around it, and we integrate it all the same.
The customer gets a message written for that case, because someone whose payment failed probably still wants the service.
On the remittance product the licensed partner did, through card and bank checks, while our system verified the payment instruments. That split is the usual one, and it is correct: the bank that issued the card or holds the account has already confirmed who owns it.
Next step
Describe the problem and we’ll come back with three options.
The first call takes 30 minutes, and you’re under no obligation.