_Home › Product › On-ramp_ # Money in: the on-ramp your users stay for The Rails on-ramp is about bringing cash to your platform, seamlessly. Users link their bank once (ACH debit) and deposit from inside your app — no redirects, no third-party widget. Instant on-ramps deliver crypto in seconds, wire covers high-limit transfers, and low-cost ACH works for small and large volumes alike. Wire, ACH, SEPA — behind one integration. It's an on-ramp architected as a unified deposit layer: Rails owns your whole deposit function, not a single rail. **Buy crypto** — in your app · your brand - 500 USDC · ≈ $500.00 · Base · buy - Chase Checking ···4821 · Linked bank · ACH debit - Their own wallet · 0x74a2…9f31 · self-custodial · destination [Book a call](https://form.typeform.com/to/lB1zdVfD) · [View docs](https://docs.spritz.finance) ## Deposits belong in your app Every redirect out of your product is a drop-off point and a branding hand-off. With Rails the deposit happens in your flow, on your screens: the user links their bank once, then funds seamlessly from inside your app — the relationship stays with you, and so does the data on what they do next. For a trading or perps product the logic compounds: every purchase that starts and ends in your app is one less chance to abandon at a handoff, and low-cost ACH removes the fee pain that pushes users to batch deposits into rare, large events. **yourapp.com · Deposit** — embedded - Chase Checking ···4821 · linked · ACH debit - $2,500.00 · → USDC · Base · deposit - Deposit from bank · Instant delivery on supported rails One KYC also unlocks [off-ramp](/product/off-ramp) and [bill pay](/product/bill-pay) — no repeated checks. ## Money in: unified deposits An on-ramp's purpose is to convert fiat into crypto. A unified deposit solution's purpose is to drive maximal volume to your app — it takes over the entire deposit function instead of selling you one rail. Rails is an on-ramp, architected as unified deposits — and it works either way: as your whole deposit layer, or as one rail sitting alongside providers you already use. ### A rail you bolt on - **Fragmentation** — Payment methods can't be surfaced intelligently inside your deposit flow — the on-ramp decides, not your product. - **A second sign-in** — Users authenticate again with a third party mid-deposit — the step where conversion rates get crushed. - **One-size risk** — An on-ramp iframe applies the same risk profile to every app, whatever your product actually looks like. ### The deposit layer (Rails) - **One flow, every method** — ACH debit, wire, and SEPA surfaced natively in your own deposit screen — the right rail for each user and amount. - **No second sign-in** — Users link a bank once and never re-authenticate with anyone else — the deposit stays in your app, on your brand. - **Risk tuned to your app** — Fiat rails that understand your product's unique risk profile, instead of treating every app the same. **Plays well with others.** Rails doesn't have to replace anything — keep your existing providers where they're strong. ## Bringing cash to your platform, seamlessly Wire, ACH, SEPA — one linked bank covers everyday deposits, wire covers the high end, and instant rails deliver in seconds. | Method | Speed | Limits | Best for | | --- | --- | --- | --- | | Linked bank (ACH debit) | Instant delivery | High | Seamless in-app deposits — small and large volumes alike | | Wire | Same business day | Highest | Large, high-limit transfers | | Instant SEPA | Seconds | High | Euro deposits a user wants now | | SEPA | Same or next business day | High | Standard euro transfers | ## How the on-ramp works 1. **Your user verifies once** — Rails runs KYC in your flow; the same verification later unlocks off-ramp and bill pay inside your app. 2. **They link a bank and deposit** — One bank link (ACH debit), then deposits happen from inside your app — ACH for everyday volumes, wire for high limits, SEPA in Europe. 3. **Crypto lands in their own wallet** — Settlement on supported networks, reconciled automatically. See coverage for the live list. ## What partners do with it fomo uses Rails to move new members from fiat to crypto inside its app; it went live in two weeks and put 500+ users through in the first weeks. - **2 weeks** kickoff to live - **500+** users in the first weeks - **$350M+** processed on the same stack, June 2026 [Read the fomo case study](/customers/fomo) ## Questions, answered ### What is a crypto on-ramp API? An on-ramp API lets an app offer crypto purchases with fiat inside its own interface. Rails provides the API plus the KYC, AML, banking, and settlement operations behind it. ### What is a unified deposit solution vs an on-ramp? An on-ramp's purpose is to convert fiat into crypto. A unified deposit solution takes over an app's entire deposit function to drive maximal volume: payment methods are surfaced intelligently inside the app's own deposit flow, there is no third-party sign-in, and risk is tuned to the specific app rather than one-size-fits-all. Rails is an on-ramp architected as a unified deposit layer. ### What payment methods can my users fund with? Users link their bank once and fund via ACH debit — good for small and large volumes alike. Wire covers high-limit transfers, and SEPA and Instant SEPA cover euro funding. ### How fast do users receive crypto? Instant on-ramps deliver crypto in seconds on supported rails. Wire settles the same business day. ### Can Rails run alongside other on-ramp providers? Yes. Use Rails as your whole deposit layer, or as one rail next to providers you already have. Rails doesn't offer a card on-ramp today, so many apps pair it with a card provider — users still see a single deposit screen. ### Which networks and tokens are supported? Stablecoins plus a broad range of tokens across 13 blockchain networks. See the product page for the live list. ### What does it cost? Pricing depends on volume and scope. Book a call for a quote. ### Do I need my own money transmitter licenses? Rails operates under Spritz's registered MSB status. ## Put the buy button in your own app One integration, and your users never fund elsewhere again. [Book a call](https://form.typeform.com/to/lB1zdVfD) · [Read the fomo case study](/customers/fomo)