# PayPay
> PayPay is the leading mobile payment app in Japan.
**Tab: For One-time Payments**
Launched in 2018, PayPay has emerged as the leading mobile payment app in Japan, boasting a user base of over 62 million. The app's success can be attributed to its strategic marketing campaigns, user-friendly payment experience, diverse range of services, and seamless integration across online and offline platforms. Since its inception, PayPay has effectively steered local consumers away from traditional cash transactions towards the convenience of digital payments, making it an indispensable tool in the daily lives of Japanese individuals.
PayPay is integrated with bank accounts, credit cards, and debit cards, simplifying the process of topping up the PayPay wallet. Whether making online or in-store purchases, buyers can effortlessly complete transactions by scanning QR codes, barcodes, or entering the account information. With widespread acceptance throughout Japan, PayPay boasts a payment ratio exceeding 45%, surpassing other prominent digital wallets in the country.
PayPay offers a new addition of front-end-based integration methods in 2025, which allows merchants to invoke various PayPay features without transitioning to PayPay.
## Properties {#3fZhB}
The properties of the PayPay payment method are shown in the following table:
| **Payment type** | Digital wallet | | |
| --- | --- | --- | --- |
| **Funding source** | Wallet balance, Points, PayPay credit cards [1] | | |
| **Acquirer** | AntomSG, AntomJP, AntomEU, AntomUK, AntomUS, AntomHK | **Merchant entity location** | SG, JP, EEA, UK, US, HK |
| **Payment flow** | Redirect | **Refund** | ✔️ |
| **Buyer country/region** | Japan | **Partial refund** | ✔️ |
| **Time to return payment result** | Real-time | **Chargeback/Dispute** | ❌ |
| **Processing currency** | JPY | **Refund period** | 365 days |
| **Minimum payment amount** | 1 JPY | **Default timeout** | 14 minutes |
| **Maximum payment amount** | Balance [2] : - Last 24 hours: 1,000,000 yen - Last 30 days: 2,000,000 yen | | |
[1] PayPay credit cards: PayPay does not allow other credit cards as a separate funding source, only allowing to top up balance for payments.
[2] Balance: Using of PayPay gift voucher and PayPay points is included in the balance limit.
## User experience {#eTt2B}
> **[INFO]** **Note** : The following payment flows on different terminals are reference only, and represent this payment method's flow on different terminal types. For supported merchants' terminal types, consult Antom Technical Support.
The following screenshots show the journey of paying with PayPay in different scenarios:
### One Time payment {#mkEeC}
**Tab: Mobile**
**Tab: App**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the PayPay app.
3. The buyer selects the preferred payment funding source.
4. Upon completion of payment, the buyer can return to the service page or view the purchase details.
> **[INFO]** **Note** : PayPay's *Deeplink* does not support the ability to downgrade to the *normalUrl* .
**Tab: WAP Login**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the PayPay wap page.
3. The buyer enters the account and password to proceed. Alternatively, the buyer can opt to pay via the PayPay app (refer to the section **WAP Front-end** ).
4. The buyer must enter a 4-digit verification code received via SMS.
5. The buyer reviews the order and selects the preferred funding source.
6. The buyer confirms the payment.
7. Upon completion of payment, the buyer can return to the service page or view the purchase details.
**Tab: WAP Front-end**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the PayPay wap page. (The buyer can also choose to pay via the app).
3. The buyer will be directed to the PayPay app.
4. The buyer checks the balance and selects the preferred funding source.
5. The buyer confirms the payment.
6. Upon completion of payment in the app, the buyer stays on the current page and needs to manually switch to the browser page.
7. PayPay will redirect the buyer return to the service page or view the purchase details.
**Tab: PC**
**Tab: Scan QR code**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the PayPay web page.
3. The buyer chooses to pay by scanning the PayPay QR code.
4. The buyer scans the QR code displayed on the web page using the PayPay app.
5. The buyer selects the preferred funding source and confirms the payment.
6. Upon completion of payment, the buyer can return to the app or view the purchase details.
**Tab: Login**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the PayPay web page and enters the mobile number and password associated with the PayPay account.
3. The buyer must enter a 4-digit verification code received via SMS.
4. The buyer selects the preferred funding source.
5. Upon completion of payment, the buyer can return to the app or view the purchase details.
### Smart Payment {#FuzUP}
**Tab: Mobile**
**Tab: App**
**Tab: First-time payment**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the PayPay app to check the authorization information.
3. The buyer completes the authorization.
4. The buyer is redirected to the Antom page, where Antom triggers PayPay's half-screen checkout. The buyer confirms the order amount and selects a funding source to pay.
5. The buyer completes the payment.
6. The buyer checks the payment result.
7. The buyer is redirected back to the merchant result page.
> **[INFO]** **Note** : When making subsequent payments, the Smart Payment experience relies on the cookie of the buyer's browser. If the cookie expires or the buyer manually clears it, the transaction will be regarded as the first-time payment, and the buyer needs to restart the authorization process.
**Tab: Subsequent payments**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the Antom page, where Antom triggers PayPay's half-screen checkout. The buyer confirms the order amount and selects a funding source to pay.
3. The buyer completes the payment.
4. The buyer is redirected back to the merchant result page.
> **[INFO]** **Note** : When making subsequent payments, the Smart Payment experience relies on the cookie of the buyer's browser. If the cookie expires or the buyer manually clears it, the transaction will be regarded as the first-time payment, and the buyer needs to restart the authorization process.
**Tab: WAP**
**Tab: PayPay app not installed**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the Antom page to open PayPay.
3. The buyer is redirected to the PayPay browser page and enters the mobile number and password to log in.
4. The buyer completes the authorization.
5. The buyer is redirected back to the Antom page, where Antom triggers PayPay's half-screen checkout. The buyer confirms the order amount and selects a funding source to pay.
6. The buyer completes the payment.
7. The buyer checks the payment result.
8. The buyer is redirected back to the merchant result page.
> **[INFO]** **Note** : When making subsequent payments, the Smart Payment experience relies on the cookie of the buyer's browser. If the cookie expires or the buyer manually clears it, the transaction will be regarded as the first-time payment, and the buyer needs to restart the authorization process.
**Tab: PayPay app installed**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the Antom page to open PayPay.
3. The buyer is redirected to the PayPay page to check the authorization information.
4. The buyer completes the authorization.
5. The buyer is redirected back to the Antom page, where Antom triggers PayPay's half-screen checkout. The buyer confirms the order amount and selects a funding source to pay.
6. The buyer completes the payment.
7. The buyer checks the payment result.
8. The buyer is redirected back to the merchant result page.
> **[INFO]** **Note** : When making subsequent payments, the Smart Payment experience relies on the cookie of the buyer's browser. If the cookie expires or the buyer manually clears it, the transaction will be regarded as the first-time payment, and the buyer needs to restart the authorization process.
**Tab: Subsequent payments**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the Antom page, where Antom triggers PayPay's half-screen checkout. The buyer confirms the order amount and selects a funding source to pay.
3. The buyer completes the payment.
4. The buyer is redirected back to the merchant result page.
> **[INFO]** **Note** : When making subsequent payments, the Smart Payment experience relies on the cookie of the buyer's browser. If the cookie expires or the buyer manually clears it, the transaction will be regarded as the first-time payment, and the buyer needs to restart the authorization process.
**Tab: PC**
**Tab: First-time payment**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the PayPay page and enters the mobile number and password to log in.
3. The buyer completes the authorization.
4. The buyer is redirected to the Antom page, where Antom triggers PayPay checkout. The buyer confirms the order amount and selects a funding source to pay.
5. The buyer completes the payment.
6. The buyer checks the payment result.
7. The buyer is redirected back to the merchant result page.
> **[INFO]** **Note** : When making subsequent payments, the Smart Payment experience relies on the cookie of the buyer's browser. If the cookie expires or the buyer manually clears it, the transaction will be regarded as the first-time payment, and the buyer needs to restart the authorization process.
**Tab: Subsequent payments**
1. The buyer selects PayPay to pay.
2. The buyer is redirected to the Antom page, where Antom triggers PayPay checkout. The buyer confirms the order amount and selects a funding source to pay.
3. The buyer completes the payment.
4. The buyer checks the payment result.
5. The buyer is redirected back to the merchant result page.
> **[INFO]** **Note** : When making subsequent payments, the Smart Payment experience relies on the cookie of the buyer's browser. If the cookie expires or the buyer manually clears it, the transaction will be regarded as the first-time payment, and the buyer needs to restart the authorization process.
## Supported online payment integrations {#rRkYR}
Antom offers a range of integration options tailored to each payment method. Each payment method may support different online payment integration options, allowing for flexibility based on your business requirements. The table below provides detailed information about the specific integrations available for each payment method:
| **Supported online payments** | **Supported integrations** |
| --- | --- |
| One-time Payments | ✔️ [API-only (One Time payment)](https://docs.antom.com/ac/cashierpay/apm_api.md) ✔️ [API-only (Smart Payment)](https://docs.antom.com/ac/cashierpay/paypay_passwordfree.md) ✔️ [Hosted Checkout Page](https://docs.antom.com/ac/cashierpay/HOSTEDCKP.md) ❌ Embedded Checkout Page ✔️ [Web Element](https://docs.antom.com/ac/cashierpay/element.md) ✔️ [Mobile Element](https://docs.antom.com/ac/cashierpay/element.md) ❌ Payment links |
| Tokenized Payment | ✔️ [API-only](https://docs.antom.com/ac/auto_debit/integration_guide.md) |
| Subscription Payment | ❌ |
| EasySafePay | ❌ |
| Scan to Link | ❌ |
## Not a customer yet?
Speak to our payment experts for product demos, personalised solutions, pricing, and fast integration support. Contact us now to discover a tailored payment experience for your business!
[Contact Us](https://www.antom.com/contact-us?secondary=Antom_Docs)
**Tab: For Tokenized Payment**
Launched in 2018, PayPay has emerged as the leading mobile payment app in Japan, boasting a user base of over 62 million. The app's success can be attributed to its strategic marketing campaigns, user-friendly payment experience, diverse range of services, and seamless integration across online and offline platforms. Since its inception, PayPay has effectively steered local consumers away from traditional cash transactions towards the convenience of digital payments, making it an indispensable tool in the daily lives of Japanese individuals.
PayPay is integrated with Wallet Balance and Points. With widespread acceptance throughout Japan, it boasts a payment ratio exceeding 45%, surpassing other prominent digital wallets in the country.
## Properties {#yVjuW}
The properties of PayPay are shown in the following table:
| **Payment type** | Digital wallet | | |
| --- | --- | --- | --- |
| **Funding source** | Wallet balance, Points | | |
| **Acquirer** | AntomSG, AntomJP, AntomEU, AntomUK, AntomUS, AntomHK | **Refund** | ✔️ |
| **Merchant entity location** | SG, JP, EEA, UK, US, HK | **Partial refund** | ✔️ |
| **Buyer country/region** | Japan | **Refund period** | 365 days |
| **Processing currency** | JPY | **Chargeback/Dispute** | ❌ |
| **Minimum payment amount** | 1 JPY | **Revoke from wallet** | ✔️ |
| **Maximum payment amount** | Balance [1] : - Last 24 hours: 1,000,000 yen - Last 30 days: 2,000,000 yen | **Revoke from** **merchant** | ✔️ |
| **Time to return payment result** | Real-time | **Token refresh** | ❌ |
| **Auth URL expiration time** | 15 minutes | **Token** **expiration** **time** | 1 year |
[1] Balance: Using of PayPay gift voucher and PayPay points is included in the balance limit.
## User experience {#avQ7c}
The following graphics show the PayPay authorization process, together with theauthorization revocation process from the wallet side:
### Authorization (mobile) {#OT3tX}
**Tab: WAP login**
1. The buyer chooses to sign up with PayPay.
2. The buyer is redirected to the PayPay page and selects a login method.
3. The buyer enters the OTP.
4. The buyer reviews the authorization information and confirms it.
5. The buyer checks the authorization result.
6. The buyer is redirected to the merchant result page.
**Tab: WAP front-end**
1. The buyer chooses to sign up with PayPay.
2. The buyer is redirected to the PayPay page. If the PayPay app is installed, the buyer clicks **開く** to launch the app (after making the initial selection, PayPay supports default automatic launch).
3. The buyer reviews the authorization information and confirms it.
4. The buyer checks the authorization result.
5. The buyer is redirected to the merchant result page.
### Authorization (PC) {#Ok2nf}
**Tab: Login**
1. The buyer chooses to sign up with PayPay.
2. The buyer is redirected to the PayPay page and selects a login method.
3. The buyer enters the OTP.
4. The buyer reviews the authorization information and confirms it.
5. The buyer checks the authorization result.
6. The buyer is redirected to the merchant result page. (the buyer can click to redirect back or wait for PayPay to automatically redirect.)
**Tab: Code scanning**
1. The buyer chooses to sign up with PayPay.
2. The buyer is redirected to the PayPay web page and selects the QR code scanning method.
3. The buyer opens the PayPay app.
4. The buyer completes the QR code scan using the PayPay app.
5. The buyer reviews the authorization information and confirms it.
6. The buyer checks the authorization result.
7. The PayPay web page automatically refreshes the authorization completion results.
8. The buyer is redirected to the merchant result page. (the buyer can click to redirect back or wait for PayPay to automatically redirect.)
### Authorization revocation (wallet) {#B9XVr}
1. The buyer selects the merchant to revoke in the “External Cooperation Service” of the PayPay app.
2. The buyer confirms the authorization revocation.
3. After successful revocation, the buyer returns directly to the "External Cooperation Service" page.
### Authorization information page {#JpCkf}
The following figures show the difference in the authorization information page between recurring payment and one-time payment:
**Tab: Authorization**
**Tab: Revocation**
## Supported online payment integrations {#rJ22K}
Antom offers a range of integration options tailored to each payment method. Each payment method may support different online payment integration options, allowing for flexibility based on your business requirements. The table below provides detailed information about the specific integrations available for each payment method:
| **Supported online payments** | **Supported integrations** |
| --- | --- |
| One-time Payments | ✔️ [API-only](https://docs.antom.com/ac/cashierpay/apm_api.md) ✔️ [Hosted Checkout Page](https://docs.antom.com/ac/cashierpay/HOSTEDCKP.md) ❌ Embedded Checkout Page ✔️ [Web Element](https://docs.antom.com/ac/cashierpay/element.md) ✔️ [Mobile Element](https://docs.antom.com/ac/cashierpay/element.md) ❌ Payment links |
| Tokenized Payment | ✔️ [API-only](https://docs.antom.com/ac/auto_debit/integration_guide.md) |
| Subscription Payment | ❌ |
| EasySafePay | ❌ |
| Scan to Link | ❌ |
## Integration considerations {#ELnwj}
The following section outlines integration considerations for various payment types, detailing customized integration solutions and payment method features.
### Specify *recurringPayment* {#uCF5x}
When calling the [**consult**](https://docs.antom.com/ac/ams/authconsult.md#Requestparameters-recurringPayment) API, the *recurringPayment* field i ndicates whether the auto debit is used for recurring payments . Valid values are :
- `true` : indicates the auto debit is for recurring payments.
- `false` : indicates the auto debit is not for recurring payments.
> **[INFO]** **Note** : Specify this parameter when the value of *customerBelongsTo* is `PAYPAY` . PayPay will continuously monitors the transaction. If the specified value does not align with the merchant's actual business, it may trigger a subsequent investigation by PayPay, potentially leading to the suspension of the transaction.
### About *normalUrl* {#qUSG4}
PayPay only supports the return of *normalUrl* . If this URL is opened on a mobile device, the buyer can click the **開く** button in the upper right corner of the PayPay page to redirect to the app for authorization. After the initial selection, PayPay will remember the buyer's choice for default automatic redirection.
> **[INFO]** **Note** : PayPay Tokenized Payment supports one-time payments, contact Antom Technical Support for more information.