> 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/changelog/2024-codapay-changelog/new-channel-announcement-japan-paypay.md).

# New Channel Announcement: Japan PayPay

❗We are excited to introduce "PayPay" our payment channel designed exclusively for Codapay users. With the inclusion of "PayPay," we are proud to offer a seamless and convenient payment option with E-wallet support.

Here are some key details about this new payment option: 📱 E-wallet Channel: PayPay is a platform allowing users to purchase their desired items with their familiar bank provider.

💲 Price Limit: Refer [here](broken://pages/qAgapMtGqsCMaFgdvJL5). CONTACT Business Development Team for further details.

🔒 Authentication: When making a payment with PayPay, users are taken to the Pay checkout page. By clicking the "Continue" button, they will be redirected to the PayPay App to complete the payment.

⏰ Transaction Expiry: Please note that transactions made through PayPay, have a validity period of 5 minutes. Users may complete payment within this timeframe to ensure a successful transaction.

💻 Integration Details: For merchants and developers, please be aware that PayPay, integration supports the payment page API. Unfortunately, the Backend API integration is currently not available. We appreciate your understanding and cooperation in this matter.

We encourage all our users to take advantage of this payment channel, leveraging an efficient payment experience. By incorporating "PayPay," into our platform, we aim to provide a tailored and reliable payment solution that meets the specific needs of our users.

**Flow Description**

| <img src="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2FIJI10EqKhANwwanf5ZjM%2Fimage.png?alt=media&amp;token=03d54558-7839-49da-a27e-fd8bd1df170f" alt="" data-size="original">               | <ol><li>User selects PayPay as a payment channel, and clicks the "Continue" button</li></ol>     |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| <img src="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2FyeRrFZWVrHbSYzLwj2B3%2Fimage.png?alt=media&amp;token=c30c3a8a-b442-4e16-8d49-05fc4a32f13f" alt="" data-size="original">               | <ol start="2"><li>Coda displays the pending page, and redirects user to the PayPay App</li></ol> |
| <img src="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2FzV66hyVQioFgIf2Ft01U%2Fimage.png?alt=media&amp;token=e0ed1e9a-ce8d-4bfb-aece-c1565540761a" alt="" data-size="original">               | <ol start="3"><li>The user approves the payment in the PayPay App</li></ol>                      |
| <p></p><p><img src="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2FfwFEWcZyd4Q0xwNf5Qpg%2Fimage.png?alt=media&amp;token=4be45646-3211-435d-8719-66003d5f2a71" alt="" data-size="original"></p> | <ol start="4"><li>Payment completed</li></ol>                                                    |


---

# 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://docs.coda.co/changelog/2024-codapay-changelog/new-channel-announcement-japan-paypay.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.