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

# Held payments

> When a payment doesn't match what was expected.

A payment is **held** when it can't simply be credited, so you decide. The commonest case is a dynamic account receiving the wrong amount, a second payment, or a payment after it expired.

| `hold_reason` | |
| - | - |
| `mismatch` | Not the amount the account expected |
| `late` | Arrived after the account expired |
| `duplicate` | A second payment into a one-payment account |
| `ambiguous`, `unmatched` | The bank couldn't match it to one account |
| `fee_exceeds_amount` | Smaller than the charge on it |

You'll receive `va.payment.held` or `dva.payment.held`, and the payment shows with `status: held` in `GET /v1/virtual-accounts/{accountId}/payments` and `GET /v1/payments/{paymentId}`.

## Decide

* **Accept it:** `POST /v1/payments/{paymentId}/accept`. It's credited, less the account's charge, and you receive `….payment.accepted`.
* **Return it:** returning money to the sender stays with the bank. Contact your bank; you'll receive `….payment.returned` when it's done.

A payment that isn't held answers `409` (code `89`); another business's, `404` (code `88`).


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