> 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/hosted-payment-page-integration/redirect-urls-for-transaction-status.md).

# Redirect URLs for Transaction Status

These URLs determine which page a customer is redirected to after initiating or completing a transaction in Coda's payment interface.

## How to Configure Redirect URLs

Partners can configure URLs in the Publisher Portal at any time. Refer to [Set up payments](/codapay/getting-started/set-up-payments.md) for instructions. Changes will take effect immediately.

## Types of Redirect URLs

There are three types of redirect URLs that partners must configure. If categorization is not necessary, partners can reuse the same redirect address.

1. **Complete Landing Page URL**: Redirects customers to a page indicating the completion status of their transaction.
2. **Bank Transfer Transaction Pending Redirect URL**: Redirects customers to a page indicating their bank transfer transaction is pending.
3. **Convenience Store Transaction Pending Redirect URL**: Redirects customers to a page indicating their convenience store payment transaction is pending.

## Complete Landing Page URL

When a customer leaves Coda's payment page after completing a carrier billing, e-wallet, or card payment, they are redirected to the Complete Transaction Redirect URL. This URL is accessed using a GET method with the following parameters:

<table><thead><tr><th width="115">Name</th><th width="105">Type</th><th width="99">Length</th><th>Description</th></tr></thead><tbody><tr><td>TxnId</td><td>Numeric</td><td>N/A</td><td>Unique TxnId returned from the <a href="/pages/AwkTokSDoYQMfyLKSEgZ">payment request initiation</a>.</td></tr><tr><td>OrderId</td><td>String</td><td>64</td><td>Unique transaction identifier passed in <a href="/pages/AwkTokSDoYQMfyLKSEgZ">the payment request initiation call</a>.</td></tr></tbody></table>

**Example**

```url
http://new.merchant.com/complete.php?TxnId=XXXXXXXXX&OrderId=YYYYYYYYY
```

**Instructions**

On this page, partners should state the result of the transaction to the customer.

## Bank Transfer Transaction Pending Redirect URL

When a customer leaves Coda's payment page after initiating a bank transfer, they are redirected to the bank transfer transaction pending redirect URL. **This is only for Bank Transfers in Indonesia and Philippines.**

This URL is accessed using GET method with the following parameters:

<table><thead><tr><th width="108">Name</th><th width="101">Type</th><th width="99">Length</th><th>Description</th></tr></thead><tbody><tr><td>TxnId</td><td>Numeric</td><td>N/A</td><td>Unique TxnId returned from the <a href="/pages/AwkTokSDoYQMfyLKSEgZ">payment request initiation</a>.</td></tr><tr><td>OrderId</td><td>String</td><td>64</td><td>Unique transaction identifier passed in <a href="/pages/AwkTokSDoYQMfyLKSEgZ">the payment request initiation call</a>.</td></tr></tbody></table>

**Example**

```url
http://new.merchant.com/atm-pending.php?TxnId=XXXXXXXXX&OrderId=YYYYYYYY
```

**Instructions**

Partners should display a message clarifying the order status, e.g., "Your order is confirmed and pending payment. Please follow the instructions provided to complete your payment at the ATM. Once your payment is completed, we will fulfill your order immediately."

## Convenience Store Transaction Pending Redirect URL

When a customer leaves Coda's payment page after initiating a convenience store payment, they are redirected to the convenience store transaction pending redirect URL. This URL is accessed using GET method with the following parameters:

<table><thead><tr><th width="108">Name</th><th width="105">Type</th><th width="99">Length</th><th>Description</th></tr></thead><tbody><tr><td>TxnId</td><td>Numeric</td><td>N/A</td><td>Unique TxnId returned from the <a href="/pages/AwkTokSDoYQMfyLKSEgZ">payment request initiation</a>.</td></tr><tr><td>OrderId</td><td>String</td><td>64</td><td>Unique transaction identifier passed in <a href="/pages/AwkTokSDoYQMfyLKSEgZ">the payment request initiation call</a>.</td></tr></tbody></table>

**Example**

```url
http://new.merchant.com/otc-pending.php?TxnId=XXXXXXXXX&OrderId=YYYYYYYYY
```

**Instructions**

Partners should display a message clarifying the order status, e.g., "Your order is confirmed and pending payment. Please follow the instructions provided to complete your payment at the convenience store. Once your payment is completed, we will fulfill your order immediately."


---

# 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/hosted-payment-page-integration/redirect-urls-for-transaction-status.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.