Sign in Get started →
Online acquiringMULTI-RAIL

Accept payments
routed for approval.

One API opens card and bank rails across markets. We generate the hosted checkout, route to the acquirer most likely to approve, reroute the instant a rail degrades, and return a signed result you can reconcile.

Get a proposal → Read the docs
+18pp
approval recovered on tuned routes
100+
methods, cards · bank · local
pay.nomadfinance.org
Amount due
€128.00
Visa / Mastercard ROUTED
Open Banking 16 EU
Local methods 40+
Pay €128.00 →
One request, every rail

Cards, bank transfers
and local methods.

Pass an amount and a method. We mint the invoice on the right acquirer, hand back a short hosted-checkout URL, and send the customer straight to the gateway.

Cards — Visa & Mastercard hosted checkout, 3-D Secure where required.
Open Banking — EUR bank transfers across AT, BE, DE, ES, FR, IT, NL and more.
Local methods & multi-currency — the customer sees your currency on the page.
console · methods
Approval
92.4%
+18pp vs base
Methods
100+
card · bank
Countries
40+
local rails
Visa / Mastercard · EU94.1%
Open Banking · EUR97.8%
Cards · USD88.0%
Payment methods

100+ methods,
one integration.

Connect once and reach the ways your customers actually pay — cards, wallets, bank transfers and local rails across markets. We add new methods behind the same API, so your integration never changes.

Cards

Global card schemes

VisaMastercard3-D Secure
Wallets

One-tap wallets

Apple PayGoogle Pay
Bank transfers

Account-to-account

Open BankingSEPATrustly
Local methods

Where they shop

iDEALBancontactBLIK+ more
Multi-acquirer routing

Routed to approve —
rerouted when a rail fails.

Routing resolves at request time against capability × scope × status × weight — never against who the partner is. When an acquirer degrades or backs out of a sector, traffic shifts to the next live rail with no code change.

A second acquirer on standby — resilience built into the route.
Geo, MCC and amount envelopes enforced at every layer.
router · resolve
BIN 4•• · ES · €128evaluating
acquirer_a · weight 60scope ✓
acquirer_b · weight 40offline
→ routedacquirer_a
# one call, we pick the rail
POST /api/v1/link
{ "amount": 128, "method": "CARD" }
Measured where it matters

Numbers that move
when the routing is right.

+18pp
approval after route tuning on a high-risk portfolio
<3s
from request to a hosted checkout URL, FX fixed at creation
99.98%
signed callbacks delivered and reconciled against the event log
Settlement

Payouts that close on
schedule, not on hope.

Every state change is an immutable event. Settlement and reconciliation derive from that log — a payment calendar you can read, and numbers that reconcile to the cent.

Scheduled payout windows with receivable, payables and margin.
Chargebacks tracked; profit derived, never guessed.
console · settlement
Receivable
€42,180
this window
Margin
€7,420
after payables + fees
Mon · Oct 27 prev wk Mon–Thusettled
Fri · Oct 31 prev wk Fri–Sunupcoming
For developers

Two headers to live.

One POST creates a payment and its hosted checkout. We send the customer to the right rail and notify you, signed, the moment it settles.

Authenticate with one key in the X-API-Key header.
Create a link — POST an amount and method, get back a short hpp_url.
Get the result — a signed webhook to your callback_url on every state change.
Read the API reference →
curl -X POST https://app.nomadfinance.org/api/v1/link \
  -H 'X-API-Key: nf_•••' \
  -d '{"amount":128,"currency":"EUR","method":"CARD",
    "callback_url":"https://you.com/webhook"}'

← { "hpp_url": "https://pay.nomadfinance.org/A1B2",
    "status": "pending" }
FAQ

Questions, answered.

How fast do you settle?
Payouts run on scheduled windows agreed up front — typically twice a week — and every amount reconciles against the event log, so a payment calendar shows receivable, payables and margin to the cent. Timing depends on the acquirer and your risk profile.
How does routing improve approval?
Each transaction resolves at request time to the acquirer most likely to approve it, scored on capability, scope, status and weight — never on who the partner is. When a rail degrades or backs out of a sector, traffic shifts to the next live acquirer with no code change on your side.
Do you work with high-risk sectors?
We are a neutral router across multiple licensed acquirers, each with its own compliance envelope. Where a sector needs redundancy we keep a second acquirer on standby, and geo, MCC and amount rules are enforced at every layer. What we can place depends on the acquirers provisioned to your account.
How much integration effort is it?
One POST with two headers creates a payment and returns a short hosted-checkout URL — the card is entered on our hosted page, so card data never touches your servers and you stay out of PCI scope. You receive a signed webhook on every state change.
How are chargebacks and refunds handled?
Every state change is an immutable event, so chargebacks and refunds are recorded as reversal events referencing the original. Your dashboards and settlement derive profit from that log — it is tracked and reconciled, never guessed.
Which currencies do you support?
Multi-currency across markets — the customer sees your currency on the checkout page, and the FX rate is fixed at the moment the payment is created so the amount never drifts between authorization and settlement.
Get started

Start accepting
in days, not quarters.

Leave an email and a Telegram — we'll map your rails and show you a route.