> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/support/transactions/payment-recovery.md).

# Payment Recovery

Learn how payment recovery options work for your store.

Within the Smartrr app, navigate to **Transaction Settings** under CONFIGURATION in the left-hand menu, then go to the **Payment method recovery** section.

<figure><img src="https://3658670565-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FndNAuxS4koYyI8AQTpS9%2Fuploads%2FHnMNBPjV209aCJIcXN1T%2Fpayment%20method%20recovery%20section.png?alt=media&amp;token=563c0cde-cc8a-4a14-986c-2ad7d97419f7" alt="The &#x22;Retry payments with&#x22; setting allows you to choose if Smartrr should retry failed transactions with other payment methods linked to other subscriptions that are shipping to the same city, or to retry with all available payment methods linked to the customer&#x27;s account."><figcaption></figcaption></figure>

### How this feature works

When a payment fails with a payment method associated with the subscription contract, Smartrr will check whether there are any other payment methods available associated with the customer profile. If there are any Smartrr will try those other payment methods.

### Options Available

<figure><img src="https://3658670565-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FndNAuxS4koYyI8AQTpS9%2Fuploads%2FweylXW5saRTjLm2ey3Hs%2Frecovery%20options.png?alt=media&amp;token=809ee0e9-f0b3-4edb-8ff4-648bcc53b4e7" alt="Dropdown menu of the &#x22;Retry payments with&#x22; setting, showing the two options: 1. Payment methods not used by other active subscriptions to a different city. 2. All payment methods."><figcaption></figcaption></figure>

#### All payment methods

When choosing this option, Smartrr will try all other payment methods that are associated with the customer.

\
Example 1: A Customer with 2 different payment methods has 2 subscriptions, subscription A and subscription B, which are set to ship to 2 different addresses and are associated with 2 different payment methods. If an order from subscription A fails to be paid, Smartrr will automatically try to charge the other available payment method(s), because Smartrr is set to retry all payment methods available.

#### Payments not used by other active subscriptions shipping to a different city

When choosing this option, Smartrr will try all other payment methods that are associated with the customer AND that are not already used by another active subscription that is set to ship to a different location (based on the city).

\
Example 1: A Customer with 2 different payment methods has 2 subscriptions, subscription A and subscription B, which are set to ship to 2 different addresses and are associated with 2 different payment methods. If an order from subscription A fails to be paid, Smartrr will not automatically try to charge the other available payment method, because Smartrr is set to retry all payment methods that are not already associated with another subscription shipping to a different location.

\
Example 2: A Customer with 2 different payment methods has 2 subscriptions, subscription A and subscription B, which are set to ship to the same address and are associated with 2 different payment methods. If an order from subscription A fails to be paid, Smartrr will automatically try to charge the other available payment method, because Smartrr is set to retry all payment methods with the same shipping city.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartrr.com/docs/support/transactions/payment-recovery.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.