# Reversals

The [checklist items](#integration-checklist) and [standards](#integration-standards) in this section cover performing reverse logistics related to refunds and returns.

## Integration checklist

Click any checklist item to see more detail on how to meet the integration standard.

* [ ] [Using the Refunds API, can you initiate a refund request from the admin portal of your commerce system?](#initiate-refunds-in-your-admin-portal)
* [ ] [Using the Refunds API, can you display details about previous refund requests from the admin portal of your commerce system](#display-refund-information-in-your-admin-portal)?

## Integration standards

These integration standards relate to reversals:

### Initiate refunds in your admin portal

You should build a mechanism for submitting refund requests in your commerce system's admin portal. When you build this feature, you should also ensure you can capture and display any [failure reasons](/digital-river-api/order-management/returns-and-refunds-1/refunds.md#dealing-with-refund-failures) returned by a call to the [Refunds API](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/refunds).

### Display refund information in your admin portal

In your commerce system's admin portal, you should build a mechanism that [searches for previously requested refunds](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/refunds#refunds) and displays that information. This information should be available per order using the [Orders resource](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/orders) and per refund using the [Refunds resource](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/refunds).

## API interfaces

| Documentation                                                                                                                   | Direct API                                                                              | PHP SDK                                                                                                  |
| ------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| [Refunds](/digital-river-api/order-management/returns-and-refunds-1/refunds.md)                                                 | [Refunds](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/refunds) | [Refunds](https://github.com/DigitalRiver/digital-river-php/blob/main/docs/Model/Refund.md)              |
| [Returns](/digital-river-api/order-management/returns-and-refunds-1/returns.md)                                                 | [Returns](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/returns) | [ReturnRequest](https://github.com/DigitalRiver/digital-river-php/blob/main/docs/Model/ReturnRequest.md) |
| [Events](/digital-river-api/order-management/events-and-webhooks-1/events-1.md): refund.created, refund.failed, refund.complete | [Events](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/events)   |                                                                                                          |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/integration-checklists/reversals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.