> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bachs.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Money is always a decimal string at the currency's precision (for example "29.00"), paired with an ISO 4217 currency field. Never use minor units.
> Build against the sandbox first: base URL https://sandbox-api.bachs.io with sk_sandbox_ keys. Production is https://api.bachs.io with sk_live_ keys; going live is a key swap.
> Treat webhooks (for example collection.succeeded) as the source of truth for fulfilment, never client-side events or redirects.
> Subscriptions are created by completing a checkout for a recurring product. There is no direct create-subscription endpoint.
> IDs carry resource prefixes (cust_, prod_, sub_, chk_, inv_, ref_) and timestamps are ISO 8601 UTC.

# Refunds and disputes

> Who absorbs a reversal when your platform collected the charge, and what happens when your balance cannot cover it.

Your platform is the merchant of record on the shape a marketplace normally uses. A refund or a lost dispute reverses the charge against **your platform's balance**, not the seller's.

This page is written for the reader who is here because something already went wrong.

***

## Where the money comes from

*Image: A refund or lost dispute is taken from your available balance, then from your pending balance if that is not enough, and if that still is not enough your balance goes negative: the debt.*

The reversal draws on your platform's `available_balance` first. If that does not cover it, the draw continues into `pending_balance`.

**A lost dispute can drive the balance negative, deliberately.** Anything still uncovered after both is debited from `available_balance` anyway, taking it negative: that negative balance is the debt, and it heals as your platform's own future settlement credits land. A refund cannot do this; an unfundable refund is refused instead. See [Disputes](https://docs.bachs.io/connect/disputes.md) for what a negative balance blocks in the meantime.

> [!WARNING]
>
> The seller keeps the share it already received. The payout transfer already sent to the seller is not reversed, so your platform bears the full amount, including what the seller was paid.

***

## Why this differs from the account collecting

Liability follows entirely from who was the merchant of record:

| | Who the customer paid | Who a reversal debits |
| - | - | - |
| Your platform collects | You | You |
| [The account collects](https://docs.bachs.io/connect/split-payments/direct.md) | The account | The account |

If the account collected instead, the reversal would be its own, and there would be nothing for you to recover. Here you collected, so you carry it, and recovering the seller's share back is a transfer you send yourself, off Bachs, that only succeeds while the seller still holds it. See [Disputes](https://docs.bachs.io/connect/disputes.md) for that recovery path in detail.

***

## What to do about it

**Watch your own balance, not the seller's.** The debt is your platform's, and it heals only from your own future settlement credits. See [Balances](https://docs.bachs.io/connect/balances.md).

**Do not transfer a seller's share the moment a charge settles, if you might need it back.** A share already transferred and withdrawn cannot be recovered with a transfer, which is refused before it takes the seller's balance below zero. Delaying the transfer gives you a window to reverse it instead. See [Split payments](https://docs.bachs.io/connect/split-payments.md) for the same timing logic applied generally.

**Watch for new disputes rather than waiting on one.** Your platform is notified by email when a dispute is raised, and again on a reminder cadence while it still needs a response, since your platform owns the charge. Poll [List Disputes](https://docs.bachs.io/api-reference/disputes/list-disputes.md) rather than relying on email alone.

***

## Related

* [Disputes](https://docs.bachs.io/connect/disputes.md)
* [Refunds](https://docs.bachs.io/connect/refunds.md)
* [Balances](https://docs.bachs.io/connect/balances.md)
* [Destination charges](https://docs.bachs.io/connect/split-payments/destination.md)
* [Choose your integration](https://docs.bachs.io/connect/choose-your-integration.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.