Skip to content
_CONNECTIVITY/

Every rail, one model

Connect PSPs and banks behind a single API. Normalize payments, balances, and payouts into one consistent data model.

_AT SCALE/

Ingest millions of payments in real time.

Captures, refunds and payouts from 120+ connectors stream into one normalized feed — reconciled, deduplicated and ledgered as they land. Watch throughput, success rate and latency across every provider, live.

Browse connectors
Payments ingested · last 24h
LIVE
2,847,291▲ 4.2% vs yesterday
120+connectors
99.98%success rate
180msp50 latency
Throughput / hour
Stripe1.24M
Adyen0.86M
Wise0.41M
GoCardless0.34M
_CONNECTORS/

Dozens of connectors, ready to go

Cards, banks, FX and wallets.

Plug into the providers you already use. Each connector maps native events into the same payment, balance and payout primitives.

COINBASE
_CAPABILITIES/

One capability surface, every connector

Accounts, balances, payments, payouts and webhooks.

Every connector — open-source (CE) or licensed (EE) — resolves to the same normalized payments-v3 surface. You know exactly what a PSP exposes before you build, and switching providers never changes your contract.

any connector
CEEE
open-source
Payments v3capability surface
Accountsexposed
Balancesexposed
Paymentsexposed
Payoutsexposed
Webhooksexposed

every connector implements the same surface, ce (open-source) or ee (licensed)

_UNIFIED MODEL/

One model across providers

Stop writing per-provider glue.

Stripe, Adyen, Wise and dozens of banks collapse into a single normalized schema. Write your logic once; switch or add providers without rewrites.

STRIPE
ADYEN
WISE
model
_ONE SCHEMA/

One payment shape, every provider.

Stripe, Adyen, Wise or a bank — every payment comes back in the same normalized shape: id, provider, type, amount, asset, status. Query once, paginate with standard headers, and stop branching on provider-specific quirks.

API reference
GET200/api/payments/v3/payments
Normalized paymentapplication/json
idpay_3Nk92Xa
providerSTRIPE
typePAY-IN
amount2000
assetUSD/2
status
Succeeded
Normalized records2,847,140
Recent
pay_9Qa4f
pay_7Lm2c
pay_3Nk92Xa

one normalized payment model · across connectors

Install
Providerstripe
Polling30m
API key•••• 7F8A3
Install

Pick a provider, set the cadence, drop in a key.

Ingestion
0.0MNormalized records

Payments, balances and payouts stream in continuously.

Normalize
many shapes → one model

Every provider collapses into one consistent model.

Schedules
Accounts2m
Balances5m
Payments1m
every 30m

Each resource stays in sync on its own cadence.

install · ingest · normalize · schedule, one connectivity layer
_SYNC/

Payments & payouts in sync

Internal orders matched to provider refs.

Every internal order is linked to its provider reference and kept in sync as statuses change — so your ledger and your PSPs always agree.

orderssyncexchange
orders:1042EUR 59.00pi_3Qa…7x
SYNCED
orders:1043EUR 120.00ch_2Bd…9k
SYNCED
orders:1044EUR 18.50tr_8Wz…1m
SYNCING
orders:1045EUR 240.00po_5Ny…4p
SYNCED
orders:1046USD 310.00pi_1Kc…3v
SYNCED
orders:1047GBP 42.00ch_9Lm…2w
SYNCED
orders:1048EUR 85.00tr_4Hp…6y
SYNCED
orders:1049EUR 12.75po_7Nx…1z
SYNCED
_NORMALIZED/

One normalized stream

Inbound and outbound, unified.

Captures, refunds, payouts and credits from every provider land as one typed event stream — already mapped onto your ledger accounts.

connectivity · normalized events
LIVE
IN
stripe.payment EUR 59.00 → ledger
IN
adyen.capture EUR 120.00 → ledger
OUT
wise.payout EUR 240.00 ← ledger
IN
modulr.credit EUR 1,000.00 → ledger
OUT
banking-circle.sepa EUR 480.00 ← ledger
IN
checkout.payment EUR 18.50 → ledger
FAQ

Questions, answered

01 / PROVIDER COVERAGE

Cards, banks, FX and wallets map to the same payment, balance and payout primitives. Adding a provider does not change your application logic.

02 / NORMALIZATION

Each connector translates native provider events into one typed schema. You read captures, refunds and payouts the same way regardless of the source.

03 / SYNC GUARANTEES

Every internal order is linked to its provider reference and updated as statuses change, so your ledger and your PSPs never silently disagree.

04 / ADDING A PROVIDER

New connectors plug into the existing model. Switching or adding a provider is a configuration change, not a rewrite.

05 / FAILURE HANDLING

Connector errors surface as typed events with the original provider payload attached, so you can replay or reconcile without guessing.

_GET STARTED/

Connect every rail behind one model

Normalize PSPs and banks into one consistent payment, balance and payout model.