Plug in
any
provider
Bring your own acquirers and PSPs. Alderone connects to them with your credentials and gives you one API, one webhook format and one data model on top of all of them.
Pre-built connectors
Ready integrations with acquirers, PSPs and local methods.
Your own contracts
Pricing, settlement and merchant accounts stay between you and the provider.
New ones on request
Need a provider we don't cover yet? We build and certify it.
One data model
Statuses, decline codes and fees mapped to one format.
What you can connect
Everything that touches a payment, from authorization to the fraud check, behind the same API.
Acquirers & PSPs
Global and local card acquiring, with several merchant accounts per provider.
Local payment methods
Pix, BLIK, iDEAL, Bancontact, SEPA and other methods buyers use at home.
Wallets
Apple Pay and Google Pay, routed to whichever acquirer suits the card underneath.
3DS servers
Use your provider's 3D Secure or a standalone 3DS server for every provider.
Fraud tools
Keep an external fraud vendor and call it from the Alderone risk step.
Payout providers
Send refunds and payouts through the provider with the right currency and rail.
Add a provider in minutes
- Enter credentials in the dashboard or via API
- Test mode with a real test payment
- Add it to a routing profile when it passes
await alderone.connections.create({
provider: "acquirer_uk",
credentials: { api_key: "•••", webhook_secret: "•••" },
merchant_accounts: [
{ mid: "4410•••", currencies: ["GBP"] },
{ mid: "4411•••", currencies: ["EUR"] },
],
methods: ["card", "apple_pay"],
mode: "test",
});Every provider speaks the same language
- Normalized statuses and decline codes
- Fees mapped per transaction
- Raw provider response kept for audits
Acquirer EU "05" Do Not Honour
Acquirer UK "card_declined/generic"
LatAm PSP "REFUSED-ISSUER"
→ Alderone
{
"decline_code": "do_not_honor",
"category": "soft",
"retryable": true
}Missing a provider? We build it.
Connector requests from customers decide what goes on our roadmap.
Request
Tell us the provider, the methods and the markets you need.
Build and certify
We build the connector against the provider's sandbox and certify it with them.
Go live
The connector appears in your dashboard, ready for test mode and routing.
Know how every provider is doing
Health checks run on live traffic, so a problem at a provider is visible before your support team hears about it.
Status per connector
Approval rate, error rate and latency per provider and merchant account.
Automatic failover
Providers that fail are taken out of rotation and returned after they recover.
Learn moreCredential checks
Alerts when keys expire or a provider rejects your credentials.
Frequently asked questions
Which providers do you support?
Global and regional acquirers, PSPs and local payment methods in the markets our customers sell to. Send us your list and we'll confirm coverage for each provider.
How long does a new connector take?
It depends on the provider's API and certification process, usually a few weeks. Connectors requested by several customers are prioritized.
Can I connect several accounts with the same provider?
Yes. Each merchant account is a separate connection with its own currencies, methods and routing weight.
Do you charge per connector?
Pricing depends on volume and the number of providers you route between. Get in touch for a proposal.
Tell us which providers you use
We'll confirm coverage for each of them and show you what routing between them could look like.
- Coverage check for your provider list
- Sandbox with simulated providers
- A dedicated integration manager