For developers

Build global money movement on one API

Open accounts, add recipients, pay out in GBP and EUR with verification of payee, and reconcile every transaction. One REST API, JSON in and out, a webhook for every state change.

Everything you need to move money, in one integration

Each capability is a set of endpoints in the API reference. Build the flow you need without stitching together a bank, an FX provider, and a separate ramp.

01

Multi-currency accounts

Open accounts and dedicated IBANs over the API in GBP and EUR, with sub-accounts to hold balances per end customer.

02

Recipients and payouts

Create recipients, then send payouts in GBP and EUR, choosing the SEPA scheme for euro payments.

03

Verification of payee

Check payee details before you send, so payments reach the right account first time.

04

Webhooks and events

Subscribe to state changes and replay missed events, so your systems stay in sync without polling.

05

Transactions and reversals

List and look up every transaction, and initiate payin reversals, all traceable to source.

06

Statements and reports

Request account statements and reports for reconciliation and finance workflows.

Developer experience

Built for engineers and operations teams

The things that decide whether an integration is quick or painful, made explicit rather than buried in the docs.
A sandbox that mirrors production
Test full flows against the same endpoints and objects as production, and top up test balances in the sandbox before you go live.
Granular webhooks, with replay
Subscribe to the exact events you care about, and replay any you missed, so nothing is lost when a listener is down.
Idempotency and clear status codes
Safe retries through a client nonce, and documented status codes (201, 400, 401, 403, 404, 422, 500) so failures are debuggable rather than opaque.
Choose the payment scheme
Set the scheme per payout, so a euro payment routes through SEPA Instant or SEPA credit transfer exactly as you intend.
Verification of payee, built in
Run a verification of payee check before you send and receive a clear match, close match, or no match, so funds reach the right account.
Granular limits and role controls
Set limits and permissions per user, per account, and per currency, so operations and finance keep control as you scale.

Build on regulated infrastructure

Merge holds its own licences, so the compliance work sits inside the payment flow instead of on your roadmap.

Licensed and registered

Merge holds its own ACPR EMI authorisation and VASP registrations with the AMF and DNB, so you build without market-by-market licences.

Fund segregation and safeguarding

Client funds are held in segregated, safeguarded accounts, kept separate from Merge's own operating money at all times.

Screening in onboarding

KYB and screening run as part of an assisted onboarding, so regulated and higher-risk businesses go live already compliant.

From sandbox to production

Onboarding is assisted. Our team guides you through registration and KYB, then supports you from sandbox testing to live operations.

01
Request access
Reach out to get sandbox access for your team.
02
Onboarding and KYB
Register your business and complete KYB with our onboarding team.
03
Build in the sandbox
Integrate against realistic data, with the same endpoints as production.
04
Go live
Pass the production readiness review and switch to live keys.

Start building today

Read the docs, request sandbox access, and integrate against your existing stack. Our team is here when you want to talk architecture.

FAQ

Does the sandbox mirror production?

Yes. The sandbox uses the same endpoints and objects as production, and lets you top up test balances, so you can build and test a full flow, from opening an account to receiving a webhook, before switching to production keys.

What webhooks does Merge send?

Merge sends an event for every state change across accounts, recipients, payouts, and transactions. You subscribe to the events you need, and you can replay any missed events, so your systems stay in sync without polling the API.

Can I tie payouts to events in my application?

Yes. Payouts are created over the API, so you can trigger them from events in your own application, with limits and role controls applied. This is how teams replace manual bank transfers with automated, event-driven flows.

How does Merge decide which rail a payout uses?

You can set the payment scheme on each payout. For euro payments you choose SEPA Instant or SEPA credit transfer, and when a scheme is set, the payment is routed only through that scheme.

Do my users need a crypto wallet?

No. Stablecoins are used as settlement infrastructure inside Merge. Your users transact in local currency and never need to hold or manage a wallet, while you keep the option to pay in or out in stablecoins where it helps.

How are client funds handled?

Client funds are held in segregated, safeguarded accounts under Merge's own licences, kept separate from Merge's own money. This means you can build regulated flows without acquiring payment or e-money licences yourself.