Multiple PSPs. One integration.
That is the whole point of orchestration. You build against Pleezpay once. When a provider is added behind the platform, your code stays exactly as it is: same endpoints, same status model, same webhooks.
- Add a provider without re-integrating
- One status model across every rail
- Pleezpay manages the provider relationships
One integration. Methods and providers behind it.
You build against Pleezpay once. We manage the provider relationships, the payment methods and the status model underneath, and add connections as they go live.
Payment methods
Live today- iDEAL
PSP connections
Live todayAdditional connections
Rolling out- More on the roadmap
Logos are trademarks of their owners, shown to identify available connections.
How you integrate
Payment-session REST API
Create a payment session from your backend and get one status model back, whichever provider handles it.
Sandbox + live keys · idempotent
Hosted payment page
Send customers to a checkout hosted by Pleezpay on a domain you own, so the flow never leaves your brand.
Your domain · ownership-verified
Signed webhooks
Every state change is pushed to your endpoint, signed so you can verify it and logged so you can replay it.
Replay-protected · retried with backoff
Don’t see your PSP? We add connections based on merchant demand.
What each rail is known for.
These are connections live and rolling out through the orchestration layer, not integrations you wire up yourself. You reach them through the same Pleezpay API, and we manage the relationship behind it.
Wallet with huge consumer reach
A checkout button millions of buyers already trust and are already logged into.
Developer-grade card processing
Deep card coverage and a mature risk stack, widely used across software and e-commerce.
Global accounts & FX
Multi-currency accounts and foreign exchange for merchants selling across borders.
Strong European acquiring reach
Acquiring across a broad set of European markets, with local scheme access.
European methods incl. iDEAL & Bancontact
The local methods Dutch and Belgian shoppers expect at checkout, alongside cards.
UAE payments, regulated by the UAE central bank
Online and in-person acceptance for merchants selling to customers in the United Arab Emirates.
Logos are trademarks of their owners, shown to identify available connections. Availability differs per merchant, market and method, so we confirm your set during onboarding.
Four moving parts. No surprises.
Here is the honest flow, end to end. It is the same whether the payment ends up on one provider or another.
01
Create the session server-side
Your backend calls the versioned REST API at /v1 with the amount, currency and order reference. Every request carries an idempotency key, and we enforce it. Retry the same call and you get the same payment back, never a second charge.
/v1 · idempotency enforced
02
Send the customer to the payment page
Redirect to the hosted payment page, served on a checkout domain you own, with ownership verified, TLS terminated and a strict CSP. The customer picks a method; Pleezpay picks the provider behind it.
Your domain · ownership-verified
03
Trust the webhook and the API, never the redirect
The browser redirect is a UX event, not a source of truth. Fifteen signed, replay-protected event types tell your system what actually happened, with retries, backoff, delivery logs and a circuit breaker. Reconciliation re-verifies every open attempt against the provider, so a late approval is reinstated instead of lost.
15 event types · signed & replay-protected
04
Go from sandbox to live
Build against sandbox keys with the same endpoints, the same status model and the same webhooks. Swap to live keys when you are ready. The integration does not change.
Sandbox + live keys
- OpenAPI-documented
- The /v1 API ships with an OpenAPI description, so you can generate a client in your language today.
- SDKs: on the roadmap
- First-party SDKs are coming. Until then the REST API plus OpenAPI is the supported path.
- One status model
- Providers differ underneath. What your code reads does not change when a new connection goes live.
Don’t see your PSP?
We add connections based on merchant demand. Tell us what you process with today, which markets and methods matter to you, and roughly what you move. It goes straight into how we prioritise the next connections.
No commitment. We will tell you plainly whether a connection is live, rolling out, or not on the map yet.
Route smarter. Get paid more.
One integration, multiple providers behind it, and reconciliation deciding what actually happened. Apply and we will walk you through onboarding.
Or leave your email and we’ll reach out.