Payment Orchestration Platform
P26M connects your checkout to the payment service providers (PSPs) you choose — the companies that process online payments for you. You keep your contracts, integrate once, and set the routing rules yourself.
The retry applies to payments your server sends through the API.
The reality today
Companies start with one PSP. Then they add a second as a backup and a third for a new market. Each provider brings its own API, its own reports and its own error codes, and the integration work piles up.
First, a single provider is connected. Simple and predictable, for now.
A second provider joins as a backup. Two integrations, two reconciliation flows.
More providers follow by market, method and vertical. Four integrations, four sets of bugs.
Each declined payment is a customer who wanted to pay. With one provider, there is nowhere else to send it.
When the provider raises fees, changes its API or goes down, you have no second route ready.
Payments live in four dashboards and settlement files in four formats. Finance matches them by hand.
Each new market, currency or method needs another integration, and your engineers are already busy.
How routing works
In the dashboard, you decide where each payment goes. P26M applies your rules to every payment and chooses among the providers that match.
The retry works for API payments only. On the P26M hosted payment page there is no retry yet, and a provider timeout is not retried.
Markets
Each market page lists the providers we checked in that country, with their methods, public rates and status. More countries are on the way. If yours is not listed, tell us on a call.
21 market pages in Europe · more coming
0 market pages in North America · more coming
0 market pages in Latin America · more coming
0 market pages in Asia-Pacific · more coming
0 market pages in Middle East & North Africa · more coming
0 market pages in Sub-Saharan Africa · more coming
No market pages in this region yet.
Book a callNo market pages in this region yet.
Book a callNo market pages in this region yet.
Book a callNo market pages in this region yet.
Book a callNo market pages in this region yet.
Book a callNo countries match your search.
Money and contracts
P26M routes payments. It does not stand between you and your money.
You sign directly with each acquirer or PSP. An acquirer is the bank that accepts card payments on your behalf. Rates and terms are between you and them.
The provider pays out to your account on the schedule in your contract.
We never receive or keep your customers’ money.
Where payments are the product
Six segments where merchants work with more than one provider and need one place to run them.
High volume and thin margins. Rules by card brand, bank and amount send each payment to the provider with the lowest rate.
Cost per paymentMoney moves both ways: payments in and payouts to customers. Both run through the same API and the same dashboard.
Payments and payoutsMerchants here often work with several providers at once. P26M puts them behind one integration and one set of rules.
Several providersCustomers pay with cards from many banks and countries. Rules by card type, BIN and issuing bank decide which provider charges which card.
Rules per cardBookings come in different currencies and payment methods. A rule per currency sends each one to the provider that handles it.
Cross-borderPlatforms accept payments, send payouts and issue invoices. P26M keeps all three in one dashboard.
Payments, payouts, invoicesWhat the platform does
Routing you control, a retry on decline, one integration and a fast start with connected providers.
Send payments to chosen providers or block them by currency, payment method, card brand, card type, country or BIN, issuing bank, amount, operation type or schedule. Test a rule in the simulator before it goes live. Among matching providers, P26M picks the one with the lowest rate.
If a provider declines a payment your server sent through the API, P26M tries once more through another provider on your account. This does not yet cover the hosted payment page or provider timeouts.
Integrate the P26M API once. Each provider you add later is a setting on your account, not new code in your product.
For a provider marked Connected, you sign the contract and we switch it on in 1–3 days. For a provider marked On request, we agree the timeline on the call.
One dashboard
The P26M dashboard is where you see and manage payments from all your providers.
from every provider on your account
send money out from the same place
create and track them next to payments
offered on your checkout
you write them yourself and test them in the simulator
the dashboard walks you through connecting your account
For developers
Your engineers integrate P26M once and test everything before going live.
every request is signed with your RSA key (RSA-PSS), and a replayed request is rejected
PHP is available now (p26m/pay-sdk), more languages are planned. The SDK signs requests for you.
every endpoint with request and response examples
test payments in sandbox, then switch to production
Card orchestration pricing
Two ways to pay. Pay 0.1% of successful payment volume with no subscription, or pick a monthly plan with included transactions and a fee for each transaction above the limit. Every plan includes all supported providers, routing rules and one dashboard.
No subscription. No minimum commitment. Pay only for successful payments.
Book a call (opens in a new tab)Billed monthly after the period: successful payment volume × 0.1%. Failed and declined payments are not counted.
Processing more than $10M monthly? Ask about custom rates starting from 0.05%.
monthly subscription · included transactions · per-transaction overage
Need higher volume or custom routing? Book a call (opens in a new tab) · All prices in USD, billed monthly.
Common questions
P26M is built to work in any country, and markets are added over time. Pages with providers and payment methods exist for Ukraine, Poland, Germany, the United Kingdom, France, Spain, Italy, the Netherlands, Belgium, Austria, Switzerland, Ireland, Portugal, Sweden, Denmark, Norway, Finland, Czechia, Romania, Hungary, and Greece. Need another market? Book a call.
No. P26M sits above your providers. You keep the contracts you already have and add new ones when you need them. Adding a provider is a setting on your P26M account, not new code in your product.
It depends on the status. A Connected provider takes 1–3 days once your contract with it is signed. For an On request provider, P26M first builds the integration, and we agree the timeline on the call.
For payments your server sends through the API, P26M makes one retry through another provider on your account after a decline. On the P26M hosted payment page there is no retry yet. If a provider times out, that payment is not retried. When choosing a provider for new payments, P26M leaves out providers in poor health.
Your provider. Money goes from the provider straight to your account under your contract with it. P26M does not hold your funds.
No. Card data is tokenized and never reaches your systems — you work with tokens, we handle the cardholder data environment.
Not yet. The platform is built to PCI DSS v4.0.1 requirements — cardholder data storage, tokenization, network segmentation and all provider integrations are in scope — and the formal QSA assessment is under way. SOC 2 Type II is in progress, ISO 27001 is planned.
In the EU. All infrastructure runs in AWS eu-central-1 (Frankfurt), with no processing or storage of personal data outside the EEA. P26M is EU-incorporated and GDPR aligned.
Two options. Pay 0.1% of successful payment volume with no subscription, or a monthly plan with included transactions and a fee for each transaction above the limit. Failed and declined payments are not counted. Every plan includes all supported providers, routing rules and one dashboard.
Yes. Your account has a sandbox environment for test payments and a production environment for real ones.
Talk to sales
Thirty minutes on your current providers and the markets you sell in.
or write to sales@p26m.com