A cardholder makes a $40 purchase and then returns it shortly afterwards. The merchant sends a reversal for the full amount before the transaction settles. This is similar to the transaction shown in <a href="doc:card-transaction-examples#authorization-reversal-and-expiry" target="_blank">Authorization reversal and expiry</a> in _Card Transaction Examples_.

📘

Note

In <<glossary:Production>>, both an authorization and its reversal remain in the authorization table until they expire. However, <<glossary:CV>> does not have the automated expiry function, and you cannot use the Expire Authorization endpoint to expire reversed authorizations. Instead, the authorization is "completed" by the reversal, and it does not expire.

For examples of authorization and reversal expiries in Production, see <a href="page:scenario-4-reversal-on-authorization-before-clearing-mastercard" target="_blank">Scenario 4: Reversal on Authorization Before Clearing (Mastercard)</a> and <a href="page:scenario-5-reversal-on-preauthorization-before-clearing-visa" target="_blank">Scenario 5: Reversal on Preauthorization Before Clearing (Visa)</a>.

### Authorization

Call <a href="ref:post_createsimulatedcardauth" target="_blank">Create Simulated Card Authorization</a> with these parameters:

Capture the `auth_id` for later use.

### Reversal

Call <a href="ref:post_createsimulatedcardauth" target="_blank">Create Simulated Card Authorization</a> with these parameters, because reversals arrive at Galileo through the authorization stream.

### Transactions created

Call <a href="ref:post_getalltranshistory" target="_blank">Get All Transaction History</a> to see the two ledger entries.