Crypto On-Ramp Chargebacks: Who Pays When a Card Payment Is Reversed
- A chargeback reverses a card payment after the crypto has been sent. A blockchain transfer cannot be recalled, so the provider or the partner absorbs the loss.
- With the Paybis On/Off Ramp, Paybis undertakes chargeback liability and holds no rolling reserve. Read 9 Questions to Ask Before You Sign With a Crypto On-Ramp Provider for the full buyer checklist.
- Paybis reports 72 decline codes through webhooks. See Build vs Buy: The Real Cost of Crypto Payment Infrastructure if you are weighing a custom card flow.
A chargeback happens when a cardholder disputes a card payment and the bank takes the money back. On a crypto on-ramp, the crypto has usually been sent by then. A blockchain transfer cannot be recalled, so someone has to absorb the loss.
This guide explains who carries that loss with the Paybis On/Off Ramp, how a chargeback differs from a declined payment, and what you can do to keep disputes low.
What is a chargeback on a crypto on-ramp?
A chargeback is a forced reversal of a card payment. The cardholder, the person who owns the card, asks the issuer, the bank that issued it, to return the money. The bank can then reverse a purchase that was already completed.
| Event | When it happens | Who starts it | Has crypto been sent? |
|---|---|---|---|
| Card decline | At checkout | The cardholder’s bank, called the issuer | No. Payout follows a successful payment |
| Fraud rejection | At checkout or during review | Paybis or its payment processor | No. Payout follows a successful payment |
| Chargeback | After the purchase is complete | The cardholder, through their bank | Usually yes. A sent crypto transfer cannot be recalled |
A decline is a refusal at checkout, so no crypto moves. A chargeback arrives later. That timing is why the two need different handling.
Why are chargebacks a bigger risk on a crypto on-ramp?
The product cannot be taken back. A card payment can be reversed weeks after the purchase, but crypto sent to a customer’s wallet stays there. The provider or the partner is left with the cost.
Two causes stand out. A fraudster may use a stolen card. A genuine cardholder may also dispute a purchase they made, which is often called friendly fraud.
Who carries chargeback liability on the Paybis On/Off Ramp?
With the Paybis On/Off Ramp, Paybis undertakes chargeback liability. Liability means responsibility for the loss when a payment is reversed. In the Paybis flow, Paybis processes the card payment and then sends the crypto to the customer’s wallet.
Check the exact scope in your contract. For a full buyer checklist, read 9 Questions to Ask Before You Sign With a Crypto On-Ramp Provider. If you are weighing a custom card flow instead, Build vs Buy: The Real Cost of Crypto Payment Infrastructure covers what you would take on.
Does the Paybis On/Off Ramp hold a rolling reserve?
No. Paybis has no rolling reserve. A rolling reserve is a share of your revenue that a payment provider holds back for a set period as a buffer against disputes.
There is also no volume cap. For other costs that appear after launch, see 7 Hidden On-Ramp Fees That Show Up After You Integrate.
What do decline codes tell you, and how should you respond?
A decline code says why the issuer or Paybis refused a payment. Paybis lists 72 codes. They fall into a few groups, and each group calls for a different reply to the customer.
| Group | Example codes | Suggested handling |
|---|---|---|
| Fraud and security | SUSPECTED_FRAUD, STOLEN_CARD | Do not push the customer to retry the same card. Offer another payment method |
| Authentication | 3DS_FAILED, PENDING_AUTHENTICATION | Ask the customer to retry and finish the bank’s identity check |
| Funds and limits | INSUFFICIENT_FUNDS, LIMIT_EXCEEDED | Suggest a smaller amount or another payment method |
| Card details | EXPIRED_CARD, SECURITY_CODE_INVALID | Ask the customer to check the card details |
| Bank refusal | DO_NOT_HONOUR, POLICY_REASONS | Suggest the customer contact their bank or use another method |
| Technical | TIMEOUT, ISSUER_UNAVAILABLE | Offer a retry after a short wait |
Paybis reports failures through webhooks. A webhook is a message Paybis sends to your server when a transaction changes status. On a rejected or failed transaction, the payment.errorCode field carries the decline code. A rejected transaction also carries a rejectReason, such as antifraud-failed or security-concerns.
The full list is in the payment decline reasons dictionary. The webhook reference shows the payloads.
Can fallbacks and routing reduce failed card payments?
Yes, they cut lost sales. They do not change who is liable for a later dispute. Paybis documentation describes two features that help a card purchase go through.
- If a card payment fails, Paybis offers a local alternative payment method as a fallback. An alternative payment method is any method other than a card, such as a local bank transfer.
- Paybis can retry a card payment through several payment providers in the background. It calls this Smart Cascade Routing.
For more on payment success, read Boosting Success: Mastering Payment Orchestration.
What can you do to keep disputes low?
Make the purchase clear and keep good records. Clear purchases are less likely to be disputed, and records help you match any dispute to a transaction.
- Show the amount, the fees and the destination wallet before the customer pays.
- Send the same partnerUserId for every request from one customer.
- Pass the wallet address the customer confirmed in your own app.
- Store the requestId from each webhook so you can match any dispute to a purchase.
- Process every webhook, because the same status can arrive more than once.
- Keep a support contact visible and answer customers quickly.
What should you ask a provider about chargebacks?
Ask who carries the loss, whether money is held back and how disputes reach you. Put the same questions to every provider you compare.
| Question to ask | Why it matters | Paybis On/Off Ramp |
|---|---|---|
| Who carries chargeback liability? | If the provider does not, the loss can fall on you | Paybis undertakes chargeback liability |
| Is a rolling reserve held back? | A reserve locks up part of your revenue | No rolling reserve |
| Is there a volume cap? | A cap can limit growth in a strong month | No volume cap |
| Who processes the card payment? | The party that processes it runs the checks | Paybis processes the card payment and sends the crypto |
| How are disputes reported to you? | You need to match a dispute to a purchase | Ask your integration manager |
Bottom line
A chargeback is the hardest cost on a crypto on-ramp because the crypto cannot be recalled. With the Paybis On/Off Ramp, Paybis undertakes chargeback liability and holds no rolling reserve.
To see how it works, visit the Paybis On/Off Ramp page or contact the Paybis sales team.
Related reading
FAQ
What is a chargeback on a crypto on-ramp?
A forced reversal of a card payment. The cardholder asks their bank to return the money, often after the crypto has already been sent.
Who pays for chargebacks with the Paybis On/Off Ramp?
Paybis undertakes chargeback liability. Check the exact scope in your contract.
Does the Paybis On/Off Ramp use a rolling reserve?
No. There is also no volume cap.
What is the difference between a decline and a chargeback?
A decline is a refusal at checkout, so no crypto moves. A chargeback arrives after the purchase is complete.
How do you know why a card payment failed?
Paybis webhooks carry a decline code in payment.errorCode. A rejected transaction also carries a rejectReason.
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
