> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/codapay-integration-faq/payment-retires.md).

# Payment Retires

#### 1. What is changing with the new Payment Retries feature?&#x20;

To reduce user friction and increase conversion rates, users will soon be able to retry failed transactions directly on our fail page, without restarting the purchase flow.&#x20;

#### 2. Do we need to do any development work to support this?&#x20;

No, this feature is automatically available for all Codapay, Codashop, and Coda Webstore users. It requires no development work on your end.&#x20;

#### 3. Will we receive a Notify Callback for every single failed retry attempt?&#x20;

No. Coda will only send a callback in two scenarios to prevent spamming your system:

* Success: If any attempt succeeds, we will share a success status.
* Definitive Failure: If the transaction definitively fails (e.g., the user exceeds their retry limit, the session times out, or fails on all attempts), we will share the latest failed transaction status.

#### 4. What status will the Inquiry API return if the user is actively retrying?&#x20;

If you check the status of a Transaction ID and the user still has retries left and the time limit has not expired, the Inquiry API will return a "Pending" status.

#### 5. How many retries does a user get, and how long do they have?&#x20;

By default, users are allowed a maximum of 5 retries and have 60 minutes after the initial transaction to attempt another retry. The time to complete the transaction remains the same, based on the payment channel selected.

#### 6. What do users see when a payment fails?&#x20;

Users will see a failure page with a contextual error message based on the failure reason (e.g., "Insufficient wallet balance, please top up and retry") and a "Retry payment" button. They can also choose to return to your game or title page. Users who are blocked for fraud or other reasons will not be able to retry their payment.

#### 7. Will users be able to switch payment channels when retrying?&#x20;

Not in the initial phase. Payment channel switching will be introduced in a later phase, with availability targeted before the end of 2026. When we roll out the payment channel switching feature, we will share further details and implications.&#x20;

#### 8. How will this affect our daily transaction reports and settlement?&#x20;

Settlement and Order Accounting will continue using the transaction ID. Your Daily, Weekly, Monthly, and Custom Date Transaction Reports will still use Transaction ID. To enable publishers to track “attempts”, we will add a new report to the publisher portal, accessible via “transactions tab” > “more filters” > “payment details” > “all transaction attempts”.

#### 9. How will conversion rate reporting change?&#x20;

Conversion rate will still be calculated as the: Successful Transactions / Initiations.&#x20;

#### 10. What should we do when we receive a "Pending" status?&#x20;

Do not grant items or mark the order as failed when you receive a Pending status. Wait for the final webhook notification. You can also use the Inquiry API to poll for the latest status.

<br>


---

# 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.coda.co/codapay/codapay-integration-faq/payment-retires.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.