Chargebacks versus crypto refunds: why a USDC payment stays paid, and how refunds work.

What is a chargeback?

A chargeback is a card payment reversed by the cardholder's bank. As of 14 October 2026, Stripe's docs describe it this way: the card issuer "creates a formal dispute on the card network, which immediately reverses the payment." The money and the network's dispute fees are pulled from Stripe, and Stripe then debits the merchant's balance for the payment and a dispute fee.

Stripe's documentation sets out the timing:

• Card networks "typically allow cardholders to initiate disputes within 120 days of the original payment", with more time in some cases. For a future event or service, the window usually starts on the event date, not the payment date.
• Once a chargeback is created, the merchant usually has 7 to 21 days to respond, depending on the network. Missing the deadline loses the dispute.
• If the merchant submits evidence, the issuer usually takes 60 to 75 days to decide. Stripe says that review "can take up to 3 months".

And the cost. Stripe's US pricing page lists a dispute received fee of $15.00 for each dispute and a dispute countered fee of $15.00 for each one you answer manually, the second returned only if you win. Outside Mexico, Stripe says the received fee is non-refundable: a merchant who wins still pays it.

Subscriptions add a twist. Stripe notes that when a customer disputes several recurring charges, the bank sometimes files one dispute for the total against a single charge: three 50 USD renewals become one 150 USD chargeback.

Are crypto payments reversible?

A USDC payment on Solana is a transfer the payer signs from their own wallet. There is no bank in the middle and no card network rule that lets the payer claw it back. Circle, which issues USDC, says in its USDC terms that a transfer to another address "is irreversible and Circle does not have the ability to reverse or recall any transaction once initiated."

With Fianto, the payer signs one transaction on the hosted checkout that sends the price straight to the merchant's wallet. Fianto never holds the money: there is no balance and no payout to claw back from. The order counts as paid, and order.paid is sent to the merchant's server, only once Solana has finalized the transaction, so a payment that could still be rolled back is never treated as final.

Stripe says the same of the stablecoin payments it processes: its docs say merchants "won't have disputes that turn into chargebacks" on those payments.

How do refunds work with Fianto?

Fianto has no refund API and cannot refund on your behalf, because it never holds your funds. To refund, send the USDC back from your own receiving wallet to the wallet the payment came from. The payer's wallet address is on the payment in the dashboard.

1. Open the payment in the dashboard and copy the payer's wallet address.
2. From the wallet you get paid to, send the USDC amount you are refunding to that address.
3. Keep a record: the order, the amount, the date and the refund's transaction signature. Fianto cannot see transfers you send from your own wallet.
4. Tell the customer, with the signature, so they can check it on chain.

Because Fianto cannot see your refunds, a row on Needs attention, such as an order paid twice, stays listed after you refund it. That is why your own record matters. The dashboard's reporting and CSV exports cover payments, orders, subscriptions and customers, so you can match refunds against them.

Can a customer dispute a crypto subscription renewal?

Not in the card sense. A Fianto subscription is approved once by the customer, and the Solana Foundation's Subscriptions program then lets Fianto collect each period, within a cap per period fixed on chain when the customer signs. The program refuses any collection above that cap or to a wallet the plan does not name. So a renewal the customer did not agree to cannot be larger than what they approved.

What replaces a dispute is a cancel. The customer signs in at fianto.xyz/my and cancels with one signature; the subscription runs to the end of the paid period and then stops. The customer portal lists every Fianto subscription the wallet pays, across merchants.

A merchant can also cancel, from the dashboard or the API, at once or at the end of the period. A renewal already on its way to Solana can still land after a cancel at once; if it does, refunding it is up to you. Failed renewals and retries explains what happens when a charge cannot be taken.

Does no chargebacks mean no fraud?

No. It removes one kind of loss, the payment clawed back after delivery, and leaves the rest. A thief with someone else's wallet can pay you with it, and that payment cannot be reversed either. Customers can still complain, leave reviews or take a claim to a court or a regulator. A merchant still has to deliver what was paid for.

USDC also has an issuer with powers of its own. Circle's USDC terms say it "reserves the right to block the transfer of USDC to and from an address on chain as permitted under the blocklisting policy". A blocked address cannot send or receive USDC. That is rare, but it means USDC is not beyond anyone's reach, and a merchant should know about it before treating it as cash.

What should a merchant put in place?

Without a bank to settle disputes, the customer's trust rests on what you publish and how you answer. Four things cover most of it:

1. Clear terms. What the customer gets, when, and for how long. For a subscription: the price, the period (monthly is every 30 days, yearly every 365 days) and how to cancel.
2. A refund policy. When you refund, how much, and how fast. Say that refunds are sent in USDC to the paying wallet.
3. A way to reach you. Set a support email in Settings and the checkout page shows it to payers as "Questions:" followed by the address.
4. A record of every refund. The order, the amount and the transaction signature, kept outside Fianto.

The hosted checkout shows the price, the fees and, for a subscription, the most you can charge per period, before the customer signs anything. That helps, but it does not replace your own terms. If you sell with code, the developers page and the orders and payments docs show where each payment's details live.