Solution · Payment gateway
A fast, robust, PCI-compliant gateway with smart routing, retry cascades, tokenisation and local payment methods: payment orchestration you change by configuration instead of a release.
The problem
A soft decline, a missing local method, a currency your acquirer prices badly: each one reads as a lost sale in your dashboard. The gateway’s job is to make those recoverable, and to let your team fix them without shipping code.
01
Recoverable declines that never got a second attempt because retry logic lived in a codebase nobody wanted to touch.
02
Customers in a market where your checkout does not offer the way they normally pay, so they do not pay.
03
Static filters that block good customers and let novel fraud through, because they cannot read the signals in context.
Capability sheet
| No. | Capability | What it means for you |
|---|---|---|
| 01 | Smart routing | Route by method, currency, geography, cost or historic success, set as rules and changed without a release. |
| 02 | Retry cascade | Recoverable declines are re-attempted on an alternative route within the constraints the schemes allow. |
| 03 | Tokenised vault | Card data is tokenised in a PCI-scoped vault and reusable across your channels, keeping card data out of your systems. |
| 04 | Method coverage | Cards, bank rails and local methods chosen per market so checkout matches local habit. |
| 05 | Fraud screening | AI-driven scoring, device and velocity signals and dynamic risk assessment evaluated in the authorisation flow. |
| 06 | Chargeback mitigation | Evidence captured at authorisation and a dispute workflow that does not depend on screenshots. |
| 07 | 3-D Secure and step-up | Authentication applied where the issuer or regulator requires it, and skipped where it only adds friction. |
| 08 | Reporting and settlement | Settlement files, reconciliation exports and webhooks that carry enough detail to close the books. |
Integration
Your engineers learn one request shape and one webhook contract. Adding a method or an acquirer later does not change the code you wrote on day one: it changes a rule.
Developer overviewFAQ
Yes. The gateway is PCI-compliant, and tokenisation keeps card data out of your systems, which reduces your own PCI scope rather than moving it around.
Yes. The gateway can act as an orchestration layer over acquirer relationships you already hold, alongside new ones. Routing rules then decide which one gets each transaction.
Hard declines stop. Soft, recoverable declines can cascade to an alternative route under rules you control, within scheme constraints and subject to risk scoring, so retries do not become a fraud vector.
We build the first set with your team during onboarding, then hand over. Changes after that are configuration, not development work.
Next step
Send a week of declines, methods and regions. We come back with the routing changes we would make and what we would expect them to recover.
