> 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/archived-tokenization-api-2.0/faq.md).

# FAQ

### <mark style="color:purple;">How long does the token expire?</mark>

As long as the customer's credit card is not expired, the token won't expire and still be usable.

### <mark style="color:purple;">How many tokens can a user create?</mark>

One card will be linked to one token. A customer can generate multiple tokens. Coda will have rules to avoid risk patterns of the same user creating too many tokens in a short period of time.

### <mark style="color:purple;">Once a user has activated a token, within the validity period, can the user initiate payment directly?</mark>

Once the user has the token, the charge can be initiated. There is no delay between tokenization and charge actions.

### <mark style="color:purple;">In the case of failed notification, does Coda have a retry mechanism? What is the retry strategy?</mark>

Currently we don't have a retry feature for webhooks sending, but partners can use the "Retrieve Charges" feature to check the latest status of an entity.&#x20;

We may have retry functionality in the future, which is why we encourage partners to check webhook idempotency (mentioned in the documentation).

### <mark style="color:purple;">Is it required to install an SSL server certificate in order to use Tokenization API 2.0?</mark>

It is not required to install a custom SSL certificate.

### <mark style="color:purple;">Is USD supported in Tokenization API 2.0?</mark>

Currently, we only support local currency.

### <mark style="color:purple;">For the "charges" interface, will Codapay return a Success / Failed response and redirect customer to the merchant page?</mark>

At the moment we have no ability to manage return URLs.&#x20;

### <mark style="color:purple;">In fraud cases, are there instances of payment rejection occurring directly with the bank or channel without the merchant's authorization? (Malicious refunds, refusals to pay)</mark>

Succeeded charges are always coming from authorized charges.

### <mark style="color:purple;">How to check the token status?</mark>

Call the [Retrieve Token](/codapay/archived-tokenization-api-2.0/integration-guide/token.md)

### <mark style="color:purple;">How does Coda handle chargeback for Tokenization API in the future?</mark>

There will be no changes to the current process for Tokenization 2.0. Coda Risk Operations will contact the publisher for proof of delivery when disputes are received from payment channels, and Coda will contest the dispute on behalf of the publisher.&#x20;

One-click payments do pose a greater risk as they allow users to conduct recurring transactions without having to re-enter their card details. Any additional authentication, the control measure are managed by the payment channels (Gopay, Mada, Dana) risk systems.

### <mark style="color:purple;">What is the definition of a valid token?</mark>&#x20;

token with status code = authorised

### <mark style="color:purple;">Does Coda Mada support removing the bound card information?</mark>

No, we do not support the cancellation of token/payment info functionality for Card- Mada at the moment.


---

# 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/archived-tokenization-api-2.0/faq.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.