Why this exists
Building ramp and bank-linking flows from scratch means a separate KYC review per provider, per-region payment rail integrations, and ongoing institution coverage. The ramp surface consolidates those into one place. You call the Sumvin Platform API — ramp sessions, linked accounts, institution discovery — and the user stays inside a single hosted widget for every payment and bank-connect flow. Ramps are powered by our ramp partner, Meld.What’s available today
How it composes
- One identity envelope — the user verifies once with Sumvin. Every ramp flow inherits that state, so the widget does not re-collect KYC.
- One account surface — bank accounts linked through the ramp surface appear on
/v0/accountsalongside any other linked accounts. You read balance, status, and transactions from the same endpoints regardless of provider. - One ramp endpoint family — buy, sell, and off-ramp all run through
/v0/ramp/quotesand/v0/ramp/sessions. You always sendfrom_asset,to_asset, andchain_id; direction is inferred from which side is fiat. See the on-ramp quickstart. - Asynchronous settlement — bank linking and ramp settlement are asynchronous. Poll
/v0/accountsor/v0/ramp/transactionsfor the terminal state.
Where to start
Related
- Atomic Money — the product these ramps belong to
- Ramp sessions — the conceptual model behind sessions and settlement
- KYC and attestation — how the KYC outcome gets reused downstream