> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/digital-river-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/digital-river-api/payments/supported-payment-methods/afterpay.md).

# Afterpay

This payment method boasts a strong existing user base providing you direct access to their 19 million users worldwide. Afterpay also offers an opportunity to increase your shopper frequency by up to 50% and average order values by up to 40%.

Contact your Customer Success Manager and sign an Afterpay addendum if you want to use Afterpay.

## How to configure

Afterpay is primarily used for purchasing physical goods. It has a review process to assess whether your customers can use it to buy digital goods. If you want to sell digital goods, Afterpay will need the following information to conduct the review: company name, website, and Merchant Classification Code (MCC). The MCC is a code that identifies your sales vertical. Provide this information to your Digital River representative.

How you configure Afterpay depends on whether you're using [DigitalRiver.js with Elements](/digital-river-api/payments/payment-integrations-1/digitalriver.js.md) or [Drop-in payments](/digital-river-api/payments/payment-integrations-1/drop-in.md).

| DigitalRiver.js with Elements                                                                                                      | Drop-in payments                                                                                        |
| ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| [Configuring Afterpay](/digital-river-api/payments/payment-integrations-1/digitalriver.js/payment-methods/configuring-afterpay.md) | [Payment methods in Dashboard](/digital-river-api/administration/dashboard/settings/payment-methods.md) |

## How it works

Afterpay uses a [submit then redirect (STR) payment flow](/digital-river-api/integration-options/checkouts/building-you-workflows/handling-redirect-payment-methods.md).

## Supported markets

For information on supported markets and currencies for Drop-in and DigitalRiver.js, go to:

* **Payment Method Guide:** digitalriver.com/payment-method-guide
* **Country Guide:** digitalriver.com/country-guide/


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/digital-river-api/payments/supported-payment-methods/afterpay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.