Gateway services
One integration. Everything behind it is our problem.
Connectivity to the methods and acquirers you need. Routing that thinks. Fraud decisions in milliseconds. Reconciliation that finishes itself.
Connectivity
Plug in once. Add the rest with a switch.
Methods, acquirers, banks. New ones arrive as configuration, not as a quarter of engineering time. Need a second acquirer? A fifth? Your integration doesn't move.
- Cards, wallets, bank redirects and local schemes behind one API
- Connect acquirers you already work with, alongside ours
- Hosted checkout, embedded fields, or server-to-server
Smart routing
A decline is not a final answer.
Route by market, method, cost or issuer behaviour. When one path fails, the next one is already trying. Your customer sees a single attempt, because that's all they should ever see.
- Cascading retries across acquirers within one authorisation
- Rules by market, currency, card brand, ticket size or BIN
- Automatic failover when a provider degrades
Where cascading stops
- Hard declines — lost or stolen cards, invalid or closed accounts
- Fraud flags — anything stopped by a risk trigger stays stopped
- Authentication — never a route around 3-D Secure
- Retry caps — scheme limits respected, without exception
Risk and fraud
Scored before the page finishes loading.
Every transaction assessed in real time against device, behaviour, velocity and history. Your rules on top of our models. Decisions in milliseconds, and a reason attached to every one of them.
- Real-time scoring with allow, review and block outcomes
- Velocity, device fingerprint, BIN and geolocation signals
- Rules you write yourself, versioned and testable
- Every decision logged with the reason behind it
Reconciliation
Month-end, minus the archaeology.
Transactions, settlements and bank lines matched automatically. What doesn't match gets flagged with a reason. Your finance team reviews exceptions instead of rebuilding the ledger by hand.
- Automatic three-way matching across transaction, settlement and bank
- Exceptions surfaced with a cause, not just a mismatch flag
- Fees itemised per transaction, never netted into a lump sum
- Exports that drop straight into your accounting system
Questions
The ones people actually ask
Can we keep our own acquirer?
Yes. Routing works across acquirers, including ones you already have contracts with. Using our acquiring is an option, not a condition.
What happens when a provider goes down?
Traffic shifts to the next route in your rule set, mid-authorisation. You find out from a dashboard rather than from your support inbox.
Do we have to use your fraud rules?
No. Ours are the starting point. You write, version and test your own on top, and you can see exactly which rule produced which decision.
How long does integration take?
Sandbox access is immediate once onboarding starts. Most teams have a working flow inside a sprint; the long pole is usually your side's release cycle, not ours.
Get started
Take it apart in the sandbox.
Tell us your stack and your markets. You'll get sandbox access, the routing rules written down before you sign anything, and a straight answer on what we support today.
Gateway services are a technical service. They are provided independently of, and do not in themselves constitute, a regulated payment service under our Polish payment institution licence. Availability of individual connections is confirmed during onboarding.