Service · Software development

Custom payment platform development.

A custom payment platform that runs on top of Mollie, Adyen, Stripe or another PSP. Multi-PSP routing, payment cascading on declines, reconciliation and marketplace payouts, all under one API and built around your own workflow.

Multi-PSP orchestrationPayment cascadingPSD2 & SCAPCI-DSS-free architectureMarketplace payouts

We don't replace your PSP, we orchestrate on top of it.

Mollie, Adyen, Stripe, Buckaroo, MultiSafepay, Worldline, Ingenico, Klarna, PayPal, Apple Pay, Google Pay: each of these providers does what it does best, whether that's card processing, local payment methods, settlement with the issuer or fraud screening per network. Building your own payment platform doesn't mean replacing them. It means adding a layer on top that brings multi-PSP routing, cascading on declines, reconciliation and payouts together in one coherent system, built around your business rules, your own data model and your own workflow for your finance and support teams.

We build this layer to your specifications for marketplaces, SaaS companies, platform businesses, growing e-commerce companies, fintech startups, banks and insurers. No white-label from someone else, no off-the-shelf PSP aggregator: your own payment middleware built around your commission engine, your KYC flow and your reporting. What you get is control over transaction costs, over failures, and over data that a standard PSP portal never shows at the right level of aggregation.

You often hear the term "payment orchestration" in the same breath as "payment middleware" or "payments for platforms", and that is no coincidence. It is all the same story seen from a slightly different angle: how do you stay in control of your payment flows while leaving the heavy compliance, licensing and card network work to specialist providers? You build the layer where your business happens, and connect to the layer the market does best.

Three types of payment platform.

It depends on what the platform needs to do and how deep the orchestration goes. In the first conversation, we'll advise which direction suits your business.

Compact project · fixed sprint budget

Payment middleware on a single PSP

One API for your own application, with Mollie, Adyen or Stripe under the hood. A reconciliation engine that matches payments to orders or invoices, a customer portal for self-service payment methods, and your own record of refunds and chargebacks. Suitable if you're currently stitching together separate webhooks and want a grip on your transaction data.

Single APIReconciliationWebhook managementRefund flow
Mid-sized project · fixed sprint budget

Multi-PSP orchestration with cascading

Two or more PSPs under one API, with intelligent routing per transaction (cost, success rate, card type, region). Payment cascading: when a transaction is declined, it is automatically retried via a second PSP. PSP failover during downtime. A dashboard that shows how each provider performs and where you're leaving margin on the table.

Multi-PSP routingPayment cascadingPSP failoverCost optimisation
Larger project · fixed sprint budget

Payments for platforms (marketplace & SaaS)

For marketplaces, platform businesses and SaaS companies with multi-vendor flows. Payment splits per transaction, a commission engine, payouts per seller or partner, and a KYC flow for onboarding. Works on top of Stripe Connect, Adyen for Platforms or Mangopay. We build the custom workflow and reporting layer where those standard products stop.

Payment splitsCommission engineVendor payoutsOnboarding flow

The building blocks of a payment platform.

Which building blocks belong in your platform depends on your business. Below are the components we combine most often, selectively rather than all at once.

Routing

Multi-PSP routing

Automatically choose the right provider for each transaction, based on rules you define: the lowest cost for this card type, the highest historical success rate for this region, a dedicated provider for a specific payment method. The difference between "we use Mollie" and "we use Mollie for Dutch iDEAL and Adyen for cross-border card traffic" then becomes a configuration change rather than a rebuild.

Cascading

Payment cascading on declines

A declined transaction doesn't have to be a lost transaction. On a soft decline, we automatically retry via a second PSP, often with a slightly different risk engine or bank route. This recovers part of the drop-off you're currently losing without noticing, and your end users never see a thing.

Failover

PSP failover during downtime

A PSP has an outage, which is far from unthinkable and happens somewhere in the market every quarter. Health checks detect the outage, and traffic automatically switches to the backup PSP until the primary is available again. For high-volume businesses, this alone is the business case for orchestration.

Reconciliation

Reconciliation engine

Settlement files from each PSP have their own format and their own timing. We match them automatically against your orders or invoices, flag discrepancies, and make sure your books add up at month-end without your finance team digging through spreadsheets.

Refunds

Refund and chargeback management

One workflow in which refunds are requested, approved, routed to the right PSP and reported back to your accounting system. Chargebacks are registered, evidence is gathered, and the dispute flow with the PSP runs from the same dashboard.

Subscriptions

Subscription billing and dunning

Recurring payments, proration on plan changes, trial periods, retry flows for failed payments. What is sometimes limited in a standard PSP becomes business logic that fits your product. For a deeper explanation, see the page on a subscription management platform.

Splits

Marketplace payouts and payment splits

One payment from a customer, multiple recipients: your platform, one or more sellers, and possibly a fee receiver. Stripe Connect, Adyen for Platforms or Mangopay are often the underlying layer, and we build the business rules around commissions, schedules and KYC on top of that.

Self-service

Customer portal for end users

End users want to be able to switch their own payment methods, view their invoice history, pause a subscription or request refunds, without your support team having to get involved at every step.

What you get at the end.

A production-ready payment platform with the building blocks we describe below, plus everything you need to manage and extend it yourself.

  • Your own payment APIOne endpoint for your frontend and backend that talks to the right PSP under the hood. Versioned, documented, with a staging environment.
  • PCI DSS-free architectureCard data never touches your servers. We use tokenisation via the PSPs, so your scope stays limited to SAQ-A wherever possible.
  • Reconciliation engineAutomatic matching of settlement files with your invoices or orders, with a manual resolution flow for discrepancies.
  • Self-service customer portalEnd users see their invoice history, manage payment methods, request refunds and can pause or cancel subscriptions.
  • Admin dashboardFor your finance and operations team: search transactions, process refunds, track chargebacks and export settlement reports to your accounting system.
  • Codebase and architecture overviewFull source code, deployment instructions and documentation. No vendor lock-in.
  • Maintenance contract (optional)Monitoring, PSP updates, SCA flow maintenance, security patches and ongoing development under a fixed monthly agreement.

When a custom payment platform is the right choice.

A few patterns in which we support clients. If you recognise one, we'd be happy to talk further about what it could deliver for you.

Marketplace

Multi-vendor payouts and commission

Customers pay you, you pay sellers, minus commission and any dispute buffers, with an audit trail per transaction. Stripe Connect or Adyen for Platforms do the basic work, but you want to keep the workflow around payouts, onboarding checks and reporting in your own hands.

SaaS & subscription

Recurring and usage-based billing

Trial periods, proration on plan changes, dunning for failed payments, usage-based billing on metering data. Standard tools cover parts of this, but the combination with your product logic almost always ends up custom — see also subscription management platform.

E-commerce growth

Transaction costs become a problem

At volume, a few basis points of difference between PSPs really start to cost money. An orchestration layer that picks the cheapest or best-performing provider per transaction, with cascading on declines, often pays for itself many times over.

Platform business

Paying drivers, sellers or service providers

An Uber-style model: an end user pays your platform, and you settle with the party providing the service. Payment splits, batch payouts, KYC at onboarding: your own orchestration layer keeps this manageable.

Fintech startup

Your own PSP licence or payments MVP

If you are working towards your own PSP licence or payment institution under DNB supervision, you need a platform that supports compliance requirements: AML/KYC screening, fraud monitoring, SCA and settlement administration. See also KYC and AML compliance software.

Bank or insurer

Payment portal for customers

Not a core replacement, but a modern customer portal for premium payments, invoice payments, direct debit or split payments. It works on top of your existing payment infrastructure — compare this with our approach to a core banking platform.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a payment platform project works.

1

Introduction and flow audit

A conversation to understand how money currently flows through your organisation: which PSPs, which costs, which drop-offs, which manual reconciliation steps. We map out the scope and the real pain points before we write a single line of code.

2

Architecture and compliance scope

A workshop with your team — often including finance and compliance — to define the target architecture, the PSP choice and the PCI DSS scope. By the end, you have a plan on the table with a realistic first-release scope.

3

Building in sprints

A working build with an end-to-end payment flow every sprint. You test alongside us in a staging environment with sandbox PSP keys. After a number of sprints, you have an MVP that you can take live in a limited production environment.

4

Rollout, monitoring and further development

A phased rollout to your full transaction volume, setting up monitoring and alerting, and training for your finance and support teams. After that comes a maintenance agreement that leaves room for further development — adding new PSPs, new payment methods, new market rules.

Compliance — what we do and don't cover.

A payment platform touches several compliance regimes at once. We don't claim an audit role; we deliver the technology that makes compliance achievable and work alongside your internal or external specialist.

PSD2 / PSD3

Strong Customer Authentication

SCA flows and 3DS2 are provided by the PSP; we make sure your checkout and backend pass on the right signals and that exemption flows, such as low-value or trusted-beneficiary, are requested correctly wherever that is safe. PSD3 changes are absorbed without a rebuild — the relevant logic lives in one place.

PCI-DSS

Tokenisation and SAQ-A scope

Card data never touches your servers — we use the PSP's hosted fields or redirects and work only with tokens. This keeps your PCI scope almost always within SAQ-A, the lightest compliance level, with a correspondingly lower audit burden.

AML / KYC

Onboarding for marketplaces and fintech

Vendor onboarding for marketplaces, and customer onboarding under DNB supervision for fintech. We integrate with your PSP's KYC tooling or build a custom flow with external verification providers — see also KYC and AML compliance software.

GDPR

PII encryption and data residency

Payment data is sensitive PII. We provide standard encryption at rest and in transit, role-based access to the admin dashboard, an audit log of who viewed or changed what, and data residency in a European region of your choice.

iDIN & eIDAS

Identification for financial services

For flows where you need to identify an end user reliably, such as premium purchases, financial services or age verification, we integrate iDIN or an eIDAS-compliant identity provider into the payment flow without damaging checkout conversion.

Wft / AFM / DNB

For banks, insurers and fintech

For financial institutions, we review Wft requirements and AFM/DNB reporting where relevant. We don't build audit reports, but we do build the logging, retention and export functionality that lets your compliance officer compile them.

Frequently asked questions.

What clients usually want to know before we start on a payment platform.

Do you replace Mollie, Adyen or Stripe?
No. Those providers continue to handle the actual payment processing — they hold the licences, the bank connections and the relationships with the card schemes. We build the layer on top: one API for your application, multi-PSP routing under the hood, your own reconciliation and your own customer portal. Switching or adding PSPs then becomes a configuration choice rather than a rebuild project.
What is the difference between a payment platform and payment orchestration?
Payment orchestration is one component of a payment platform: the routing layer that decides, per transaction, which PSP handles the payment, with cascading on declines and failover during downtime. A full payment platform also covers reconciliation, refund management, subscription billing, marketplace payouts and a customer portal, among other things. Which components you need depends on your business model.
How do you handle PSD2 and SCA (Strong Customer Authentication)?
We leave part of SCA to the PSP: Mollie, Adyen and Stripe provide the SCA flows and 3DS2 integration. We make sure your checkout and backend pass on the right signals (transaction amount, IP, device data) and that exemption flows such as low-value or trusted-beneficiary are requested correctly wherever that is safe. That lets you balance conversion and compliance within the PSD2 rules.
What does your approach mean for PCI DSS?
By default, we build a PCI DSS-free architecture: card data is tokenised directly by the PSP via a hosted field or redirect, and your servers only ever see the token. That keeps your scope within SAQ-A, the lightest compliance level, almost every time. If you have a use case in which you do need to handle card data, we discuss up front how to minimise the scope.
Can you build marketplace payouts with payment splits?
Yes. For multi-vendor marketplaces we usually work with Stripe Connect, Adyen for Platforms or Mangopay as the underlying layer, and build the commission engine, payout scheduling, vendor onboarding and KYC flow on top of it. That way the licensing and compliance burden stays with the PSP, while you keep the business logic and data in your own hands.
How do you handle subscription billing and dunning?
Recurring billing can be done in several ways: directly via the PSP, via an intermediate layer such as Stripe Billing, or entirely in-house. For SaaS platforms with proration, usage-based billing and dunning flows, custom logic is usually the obvious choice. You can find more detail on that approach on the page about subscription management platforms.
Which compliance requirements do you look at?
As standard: PSD2/PSD3, SCA, PCI DSS scope and GDPR. For marketplaces and platforms, often AML/KYC screening during vendor onboarding as well. For financial institutions, we look at Wft requirements (the Dutch Financial Supervision Act) and AFM/DNB reporting where relevant. We do not claim an audit role: we provide the technology and work alongside your compliance officer or external adviser.
What determines the cost of a payment platform?
Mainly the number of PSPs you orchestrate, whether marketplace payouts or subscriptions are added, and how far you want to extend reconciliation and reporting into your accounting. Payment middleware on a single PSP is a fundamentally different project from an orchestration platform with cascading, marketplace splits and custom KYC. After the first conversation, we provide a targeted estimate based on the scope.
How long until we can go live?
A first payment middleware on a single PSP can be up and running in a staging environment within a few sprints. For an orchestration platform with multiple PSPs, cascading and marketplace payouts, we plan for a project of several sprints, with a phased release in which we first route part of the volume through it.

Talk to us about your payment platform.

A no-obligation introductory call of half an hour. We listen to your payment flow, your PSP setup and your goals, and give you direction you can actually use, whether it is about payment middleware, multi-PSP orchestration or marketplace payouts.

Edit content