9 Questions to Ask Before You Sign With a Crypto On-Ramp Provider
The nine questions at glance:
- Is the provider actually licensed, and where?
- What are the real approval rates?
- How long does integration take, and how much engineering?
- Can you leave, and on what terms?
- Who covers chargebacks?
- Which countries and payment methods are supported?
- What support will you get, and how fast?
- Are all the fees disclosed up front?
- How do you get your data and users out?
Most teams pick a crypto on-ramp by reading the API docs and checking the headline fee. The real problems show up months later: a card failure rate that spikes in one region, a licence that does not cover your market, or an exit clause that traps your funds. The questions below surface those problems before you sign, not after.
New here? Start with our guide to adding a crypto on-ramp: widget, SDK, or API, or go straight to the Paybis On/Off-Ramp for business.
1. Is the provider actually licensed, and where?
This is the question you can verify yourself, so start here. Ask which regulator authorises the provider, in which countries, and under which licence. Then look it up on the regulator’s public register rather than taking the website’s word for it.
Watch for one common trick. An anti-money-laundering registration and a service licence are different things. Many crypto firms hold a legacy AML registration and describe themselves as “compliant” or “regulated” without holding a licence to provide the actual service. In the EU, the licence that matters for crypto services is a MiCA CASP authorisation, and for handling payments it is a Payment Institution licence under PSD2. Ask for both by name.
Paybis holds a MiCA CASP licence and a PSD2 Payment Institution licence, issued by the Bank of Latvia (Latvijas Banka) in May 2026. A single MiCA authorisation passports across all 27 EU countries and the wider EEA, so one licence covers the whole bloc. You can confirm the listing on the independent CASP register and on the official ESMA register of crypto-asset service providers. If a provider cannot point you to a register entry, treat that as your answer.
2. What are the real approval rates?
Coverage tells you where a provider operates. The approval rate tells you how often a payment actually completes. A provider can support 180 countries and still decline a large share of cards in some of them.
Ask for authorisation rates broken down by region and payment method, not a single global average. Ask what the provider does when a card is declined. Good providers route a payment through more than one path and retry intelligently, which recovers payments that a single-path setup would lose. Paybis uses higher-approval card routing for this reason. Request the current figures for your main markets and hold the provider to them after launch.
3. How long does integration take, and how much engineering?
Ask for a real timeline and a written list of what your team has to build. Some providers need weeks of engineering. Others give you a hosted widget you can add in a day.
With Paybis, you can go live in under 48 hours using a widget, an SDK, or the API. PSPs and acquirers that only want a crypto settlement option can use, which runs on a standard bank transfer with no API or widget to build. Match the integration method to how much control you need and how much engineering time you can spare.
4. Can you leave, and on what terms?
Read the exit terms before you sign, because they are hardest to negotiate once you depend on the provider. Check the notice period, any minimum monthly commitment, and whether the provider holds back a share of your funds.
Two clauses matter most here. A rolling reserve keeps a percentage of your money for months. A volume cap limits how much you can process. Both raise your costs and make leaving harder. Paybis runs with no rolling reserve and no volume cap.
5. Who covers chargebacks?
When a customer disputes a card payment, someone absorbs the cost. Ask plainly whether that sits with you or the provider, and get the answer in the contract.
Paybis covers chargeback liability, so a disputed card payment does not land on your books. That shifts a real and unpredictable cost off your business and onto the provider that processed the payment.
6. Which countries and payment methods are supported?
Match the coverage to where your users are and how they actually pay. A provider that is strong in Europe can be weak in Latin America or Southeast Asia, where many users pay with local methods rather than international cards. Ask for the supported list that applies to your specific markets, including local payment methods.
Paybis supports more than 25 payment methods and over 54 fiat currencies across more than 180 countries. Ask any provider to confirm the same detail for your regions before you commit.
7. What support will you get, and how fast?
Support quality shows up when a payment flow breaks in production and you need an answer quickly. Ask for the support hours, the channels, and whether you get a named account contact who understands your setup rather than a general queue.
Paybis provides 24/7 technical support and a personal account manager. For a payments integration that runs around the clock, support that also runs around the clock is worth confirming in writing.
8. Are all the fees disclosed up front?
Ask for the full fee schedule, including any charge that only appears after you integrate. Some providers publish a low headline rate and only reveal the rest at checkout.
Look at the net amount of crypto your user receives after every fee, since that is what actually affects conversion. Compare providers on that net figure rather than the advertised rate. If a provider will not give you a complete written breakdown, keep asking until they do.
9. How do you get your data and users out?
Offboarding is easy to ignore during a signing and painful to sort out during a migration. Ask how it works before you need it. Check who owns the user and transaction data and how you export it. Find out what happens to pending payments if you move mid-flow. A provider confident in its product will have a clear, documented answer ready.
Bottom Line
Choosing a crypto on-ramp is about more than fees and API documentation. Check the licence, approval rates, coverage, support, fees, and exit terms before you commit. The right provider should fit your markets, reduce payment risk, and make it easy to scale or leave when your needs change. Do the due diligence upfront, and you avoid expensive surprises later.
FAQ
What is the most important question to ask a crypto on-ramp provider?
Licensing, because you can verify it independently and it affects your own compliance exposure. Ask which regulator authorises the provider and check the licence on that regulator’s public register.
How do I check if a crypto on-ramp provider is really licensed?
Ask for the regulator and the licence type, then look it up on the public register. In the EU, check for a MiCA CASP authorisation on the ESMA register. An anti-money-laundering registration is not the same as a service licence, so confirm which one the provider holds.
Do I have to build an integration to add crypto payments?
Not always. A widget can go live in under 48 hours. PSPs and acquirers can use Auto Ramp with no integration, because it runs on a standard bank transfer.
Who pays when a card payment is disputed?
It depends on the provider. Some pass chargeback costs to you. Paybis covers chargeback liability itself.
Disclaimer: Don’t invest unless you’re prepared to lose all the money you invest. This is a high‑risk investment and you should not expect to be protected if something goes wrong. Take 2 mins to learn more at: https://go.payb.is/FCA-Info
