# Refunds

> Refund any confirmed payment in full or in part. Each refund is a new transfer you sign back to the customer, never a reversal, and chargebacks do not exist on Soca.

Part of the Soca documentation (https://soca.finance/docs). Human version: https://soca.finance/docs/business/refunds
When you need to return money, you issue a refund: a new USDC transfer from your wallet back to the customer, in full or in part. Because you sign it yourself, a refund is always a decision you make, never something pulled from your account by a processor or a bank. Every refund gets its own record and receipt.

## How do I issue a refund?

1. **Find the payment**: Open **Dashboard → Refunds** to see every refundable payment, or find the row in [Payments](/docs/business/payments). Any payment with status **confirmed** shows a **Refund** action.
2. **Choose the amount**: Refund the full payment or any partial amount up to what was received. Partial refunds are common for adjustments, prorations, or goodwill credits.
3. **Sign and send**: You approve the transfer and it goes straight back to the wallet the customer paid from. Once confirmed on-chain, the refund is final and visible on the network.

## How is a refund different from a card refund?

A refund is a new merchant-signed USDC transfer back to the customer, never a reversal, always visible on-chain. A card refund is a reversal that winds back through processor and bank and lands days later; a Soca refund is a forward payment in its own right. It confirms in seconds, and the customer can see it on-chain rather than taking anyone's word for it.

- **Signed from the wallet that received the payment.** If the original payment settled to a specific [named wallet](/docs/business/wallets-and-treasury), the refund is sent from that same wallet, so each wallet's ledger stays internally consistent.
- **Back to the original payer.** The refund goes to the wallet the payment came from, which removes "send it to this other account instead" fraud from the flow.
- **Free.** There is no refund fee; the only cost is the amount you return. See [Pricing](/docs/pricing).

## Where do I see my refund history?

The **Refunds** page keeps the full picture: a history table (customer, amount, status, date, and a link to the original payment), running totals for the amount refunded and refunds issued, and the list of confirmed payments still eligible for refund. On the original payment's record, the refund is linked in both directions, and each refund carries its own receipt. Developers can listen for the `refund.succeeded` [webhook](/docs/developers/webhooks).

## What about chargebacks?

There are none. Payments are push-based wallet transfers, so card-style chargebacks (and their fees) do not exist. Money cannot be clawed back out of your wallet by a third party after the fact. The only way funds return to a customer is a refund you choose to sign.

For a business, that removes an entire cost category: no chargeback fees (typically $15–25 per dispute on cards, kept even when you win), no evidence-gathering and dispute deadlines, no rolling reserve held against future disputes, and no risk of a fraudulent buyer keeping both the goods and the money. The trade is symmetry: since no one can reverse your incoming payments, customer trust runs on your refund behavior rather than on a bank's dispute process, which makes a clear refund policy and prompt refunds worth treating as part of the product.

> **Refunds are final too**: A confirmed refund is an on-chain transfer and cannot be un-sent. Double-check the amount before signing. Partial refunds make it easy to return exactly what you intend.