
What a ramp is, in two lines
An on-ramp receives money through a local transfer (for example, Pix in Brazil or a transfer to a CVU in Argentina) and credits it as stablecoins. An off-ramp does the reverse: it takes stablecoins and pays out local currency to a bank account or wallet.
For a wallet, an exchange or a fintech paying suppliers in several countries, the ramp is the door between crypto and the local financial system. We’ve been running ramps for years, first for our own users and then via API for other companies. These are the questions we learned to ask.
1. Who is the regulated entity in each country?
“We’re regulated” isn’t enough. Ask which entity receives the funds in each country, under which license or registration, and with which authority. If the answer is “a local partner”, ask which one and what happens if that relationship ends.
2. Which rails does the money move on?
A useful ramp uses the payment methods people already use: Pix, instant transfers, CVU, SPEI. Ask which rails are live in each country today, not on the roadmap, and whether both collections and payouts work on each of them.
3. In whose name are payments received?
Does the user transfer to a single pooled account owned by the provider, or to an identified virtual account? Are third-party transfers accepted, or only same-name ones? This determines how much manual matching your team will do.
4. How is pricing structured?
Some providers charge a per-transaction fee, others only charge through the spread, and others combine both, sometimes with monthly minimums. Ask for an end-to-end example: how much comes in as local currency and how much goes out as stablecoins.
5. Is there liquidity outside banking hours?
Users don’t only transact on weekdays during business hours. Ask what happens on a Saturday night: can you convert, at what price, and when do funds arrive?
6. How is each transaction reconciled?
Ask how you find out a payment has arrived (webhooks, API queries), what data each notification includes and how the payer is identified. A ramp without solid reconciliation pushes the problem onto your operations team.
7. How does KYC work, and what are the limits?
Who runs KYC on users: the provider, you, or both? Are limits fixed, or do they adjust to the customer’s profile? How long does it take to approve a new user?
8. How are funds held?
Ask where funds sit while a transaction is being processed, whether they are segregated, and whether the provider publishes any proof of reserves.
9. How long does it take to go live?
A complete sandbox, clear documentation and a responsive team make the difference between weeks and months. Ask whether there’s a widget that lets you launch without coding the entire flow.
10. What happens when something goes wrong?
A transfer that doesn’t land, a delayed bank, a scheme outage. Ask how you’ll be notified, how quickly, and who fixes it. The answer tells you more about a provider than any demo.
One last piece of advice
Get the answers in writing and test them against a real sandbox run and, if possible, a small transaction in production. Many differences between providers only show up when money actually moves: settlement times, the data in each notification, and how the team responds to your first question.
How we handle it at Manteca
We designed our ramp API to answer those ten questions well:
Local rails via bank transfer, with virtual accounts that accept both same-name and third-party transfers.
Liquidity available outside market hours.
Automated reconciliation of every payment, trackable per customer.
Fast KYC and operating limits tailored to each business.
Sandbox, documentation and a widget for a fast integration.
If you’re evaluating ramp providers for your product, tell us what you’re building at manteca.dev and we’ll show you how we’d answer each of these questions for your use case.
M
Written by
Manteca
Considering adding a country, payment method or ramp to your product?
Tell us what you want to build. We’ll be in touch.
