Stablecoin payments, chargebacks, and direct customer refunds

What changes when the payment uses a blockchain?

A card chargeback uses the card-payment system to dispute and potentially reverse a transaction. A direct stablecoin transfer uses a different rail. Once confirmed with the required finality, it does not have a card issuer or card-network chargeback mechanism attached to that transfer.

Circle's USDC terms explain that USDC transfers are not reversible. The practical benefit for a merchant is that a customer cannot use a card-network chargeback to undo that completed onchain payment. This removes that particular reversal process from direct stablecoin acceptance.

It does not make every kind of dispute a thing of the past. Customers can still report a missing delivery, an incorrect service, fraud, or another problem with the purchase. Your team still needs a clear way to hear the complaint and provide any remedy required by your policy and applicable law.

A refund is a new transfer, not an undo button

For a direct wallet payment, an agreed refund generally means sending a new payment to a verified destination. The original transaction stays in the blockchain record. Your business keeps a separate record of the refund and connects it to the original order in its own records.

That lets you work with the customer on a full refund, a partial refund, or another appropriate remedy. The amount, asset, network, and timing should be clear to both sides before funds move. A price adjustment after a partially delivered service, for example, should not depend on guessing how much the customer expects back.

Who handles refunds when you use Ulasend?

Ulasend's terms place responsibility for customer refunds with the merchant. Ulasend does not initiate, facilitate, approve, administer, transmit, or process refunds, and it does not provide a refund-to-sender function or a refund destination.

If you choose, or are legally required, to issue a refund, you must independently obtain and verify the customer's destination and send the funds from your own wallet outside Ulasend's services. Ulasend does not verify, sign, broadcast, track, or reconcile that transfer for you.

Plan for that separation before taking payments. Your payment dashboard can show the original collection, but your own support and accounting records need to document the customer agreement and the separate refund. A merchant payout to an approved business destination is not a customer-refund tool.

A clear process for settling a refund directly

Use a repeatable process so both the customer and your team know what happens next. The following is an operational checklist for a refund your business handles independently:

• Confirm the original order, verified payment, and reason for the request. Check whether any remedy has already been provided.
• Apply your disclosed refund policy and applicable customer rights. Confirm the agreed amount and timing in writing.
• Independently verify the customer's refund destination, supported asset, and network using a trusted communication channel. Do not assume the original sending address is a valid refund destination.
• Confirm how conversion differences and network fees will be handled, consistently with your policy and applicable law.
• Send the agreed refund from your own wallet, outside Ulasend, after reviewing every transfer detail.
• Give the customer a receipt and retain the refund transaction reference alongside the original invoice in your own records.

Where the no-chargeback distinction stops

If a customer buys stablecoins with a card, that earlier purchase is a separate card transaction. ACH-funded activity has its own rules for returns and reversals. A later onchain transfer does not erase the funding provider's terms, any recourse under those terms, or applicable legal rights.

Finality also does not protect against every loss. An incorrect address, a compromised wallet, fraud, issuer restrictions, or a legal claim can still create problems. Circle's terms distinguish irreversible transfers from rights and restrictions that can arise through banks, recipients, and applicable law.

Make your refund policy easy to find before checkout

Publish your contact details, request process, refund conditions, and expected response times where customers can find them before paying. Explain that a confirmed blockchain payment cannot simply be canceled and that an approved refund is handled separately by your business.

Clear communication supports the same benefit you want from the payment itself: fewer surprises. Direct stablecoin payments can remove card-style chargebacks from the collection process while your business remains accountable for resolving legitimate customer concerns.