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

# Handle a Reversal

> When the customer's bank takes a payment transaction back, read the reversal and the payment transaction it reverses

A reversal is money the customer's bank took back from a payment transaction. It's a `transaction` of `type: reversal`, always `completed`, whose `amount` is what the bank took back. Merchant and partner credentials both read it.

| # | Step | Who |
| - | - | - |
| 1 | Receive `transaction.reversal.completed` | Quidkey sends it |
| 2 | Read the reversal | API |
| 3 | Read the payment transaction it reverses | API, optional |

**1. Receive the event**

The event's `result.subject` is the **reversal**, not the payment transaction. It goes to the endpoint the payment transaction's events went to.

**2. Read the reversal**

```bash theme={null}
curl 'https://api.quidkey.com/v1/transactions/tx_3?include=parent_transaction' \
  -H 'Authorization: Bearer ACCESS_TOKEN'
```

The reversal's `parent_transaction` links to the payment transaction, and `?include=parent_transaction` adds it to `entities`, so one read gives you both.

**3. Read the payment transaction**

```bash theme={null}
curl 'https://api.quidkey.com/v1/transactions/tx_1' \
  -H 'Authorization: Bearer ACCESS_TOKEN'
```

The payment transaction stays `completed`, and its `reversals` lists the reversal.

A refund isn't a reversal, and sends no event: see [Refund a payment transaction](https://docs.quidkey.com/api-v1/journeys/refunds.md).


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