PayPay via Adyen
This feature is currently a Private Beta release. Contact Chargebee Support to enable PayPay via Adyen for your live and test sites.
PayPay is the leading QR-code-based mobile payment method in Japan, enabling customers to authorise payments through the PayPay app. Chargebee supports PayPay as a payment method via the Adyen payment gateway.
When customers select PayPay at checkout, they are redirected to the PayPay app (on mobile) or shown a QR code (on desktop) to authorise the payment. Payment is completed instantly after customer approval and the final status is confirmed via Adyen webhooks.
Supported countries and currencies
PayPay via Adyen supports the following country and currency. Refer to the Adyen PayPay documentation for the latest details.
| Country | Currency |
|---|---|
| Japan | JPY |
Prerequisites
To accept PayPay payments using Chargebee, you must:
- Have an active Adyen account with PayPay enabled as a payment method in your Adyen Customer Area. Learn more
- Ensure JPY (Japanese Yen) currency is enabled for your Chargebee account.
- Ensure the Adyen payment gateway and webhooks are configured in your Chargebee account. Learn more
- Have a Merchant Account configured for PayPay in Adyen, with API credentials and webhooks enabled.
Configure PayPay in Chargebee
Follow these steps to configure PayPay via Adyen in your Chargebee site:
- Log in to the Chargebee app.
- Go to Settings > Configure Chargebee > Payment Gateways.
- Select the relevant Adyen instance from the list.
- On the Configure Adyen page, ensure PayPay is enabled under the list of supported payment methods.
- Click Apply to save changes.
Configure Smart Routing for PayPay
When you configure PayPay through Adyen, smart routing for the JPY currency is automatically enabled. Check the Smart Routing settings, and if another gateway is already designated for the JPY currency, adjust the Smart Routing settings manually to allocate PayPay to it.
Follow these steps to modify Smart Routing settings:
- Log in to the Chargebee app.
- Go to Settings > Configure Chargebee > Payment Gateways.
- Click Manage Rules under Smart Routing.
- Go to the PayPay section and click Add a Gateway for JPY. If you already have a payment gateway assigned to it, click Edit.
- From the Choose a payment gateway drop-down menu, select the relevant Adyen instance with PayPay enabled.
- Click Save.
Enable PayPay to pay for subscriptions
PayPay is a one-time payment method and cannot be used for automatic subscription renewals. To let customers pay the initial subscription checkout invoice using PayPay, configure your Chargebee site to allow one-time payment methods for subscriptions.
Note
While testing, ensure Allow customers to pay for subscriptions with payment methods that only support one-time payments and One-time Payments - Enable button are enabled under Settings > Configure Chargebee > Checkout & Self-Serve Portal.
Follow these steps to enable one-time payment methods for subscriptions:
- In the Chargebee app, go to Settings > Configure Chargebee > Checkout & Self-Serve Portal.
- Select the Configuration tab and enable Allow customers to pay for subscriptions with payment methods that only support one-time payments.
Payment workflow
Your customer performs the following steps during checkout using PayPay via Adyen:
- The customer reviews the order on the Your cart page and selects Proceed to Checkout.
- The customer enters their Account Details and Billing Address, selects PayPay, and selects Pay & Subscribe.
- The customer is redirected to PayPay to authorise the payment — on desktop by scanning the QR code, on mobile via the PayPay app.
- The customer reviews the payment amount and merchant details and selects Pay (支払う).
- PayPay confirms the successful transaction.
- The customer is redirected back to Chargebee, and the order confirmation page appears once the payment is processed.
Note
The screenshots above are from Adyen's test environment. In production, customers authorise the payment in the live PayPay app or by scanning the live QR code, and the screens show merchant branding.
Testing
Sandbox testing
Refer to Adyen's PayPay testing documentation for instructions on testing PayPay in the Adyen test environment.
Ensure webhooks are configured to receive REFUND and CANCEL_OR_REFUND updates for refund settlement.
Production testing
Before going live:
- Ensure PayPay is enabled in your Adyen live account.
- Verify webhook configuration is complete (required for refund settlement updates).
- Perform end-to-end testing using a real PayPay-enabled wallet account and a mobile device with the PayPay app installed.
Reconciliation
For financial reconciliation between Chargebee and Adyen:
- Use the Chargebee transaction field id_at_gateway, which maps to the pspReference in Adyen.
Follow these steps to reconcile transactions:
- Retrieve the id_at_gateway value from the Chargebee transaction details.
- Locate the corresponding pspReference in Adyen reports for PayPay transactions.
- Match transactions using this reference to ensure financial consistency.
Payment features
The following are the features for this integration and details about them:
| Feature | Description | Supported | Default state | Configuration / behavior |
|---|---|---|---|---|
| Integration sync mode | Defines how payment requests are processed and statuses are communicated between Chargebee and Adyen. | Yes (Asynchronous) | Asynchronous | Adyen processes PayPay payments asynchronously. Chargebee receives the final payment status through Adyen webhooks. Webhook configuration is mandatory and is used to receive REFUND and CANCEL_OR_REFUND updates for refund settlement. |
| Capture settings | Payment processing involves two stages: Authorization and Capture. Capture settings determine when funds are collected after authorization. | Yes | Auto capture | Auto capture is the default and only supported capture setting for PayPay via Adyen. No additional configuration is required. |
| Verification modes | Defines how payment methods are verified before processing. | Yes | Enabled | The customer authorizes the payment within the PayPay app or by scanning the QR code. No separate verification configuration is required in Chargebee. |
| Statement descriptor | Displays the business name on the customer's bank or wallet statement, helping them recognize charges and reducing disputes. | Yes | Disabled | Configure this under Settings > Configure Chargebee > Transaction Descriptor. |
| Chargeback management | Handles chargeback events and applies configured actions on invoices and subscriptions. | No | NA | PayPay does not support chargebacks for this integration. Refunds must be issued manually if needed. |
| Fraud management | Uses gateway fraud signals to identify and flag high-risk transactions. | No | NA | No PayPay-specific fraud configuration is available in Chargebee. |
| Transaction initiation type | Identifies whether a transaction is customer-initiated (CIT) or merchant-initiated (MIT). | No | NA | PayPay supports customer-initiated, one-time payments only. Merchant-initiated recurring charges are not supported. |
| Error intelligence | Provides standardized categorization of payment failures. | Yes | Enabled | Available through Adyen payment and refusal responses. No configuration is required. |
| Gateway transaction details | Provides access to raw gateway responses for transactions. | Yes | Enabled | Available on the transaction page under Error details. No configuration is required. |
| Addition of payment methods in Chargebee dashboard | Allows a payment method to be added in Chargebee when details are collected outside checkout. | No | NA | Customers must complete the PayPay checkout flow. PayPay cannot be added from the Chargebee dashboard. |
Supported token formats
This section is relevant if you are building a custom checkout or migrating payment methods from another provider to Adyen.
| Token type | Description | Supported | Token field | Token format |
|---|---|---|---|---|
| Chargebee Payment Intent | Recommended token format when building a custom checkout using Chargebee JS. | Yes | payment_intent[id] | payment_intent_id |
| Chargebee token | Legacy token format supported for selected payment methods and gateways with Chargebee JS. Not recommended for new implementations. | No | token_id | NA |
| Gateway permanent token | Permanent reference provided by the gateway. Not applicable for PayPay as it does not support stored credentials. | No | payment_method[reference_id] | NA |
| Gateway temporary token | Short-lived token format that can be converted to a permanent token. | No | NA | NA |
Limitations and important points
- PayPay cannot be added as a payment method via the customer portal or the Chargebee app. Customers must complete the PayPay checkout flow.
- PayPay does not support storing payment methods for recurring billing. Each transaction requires explicit customer authorization via the PayPay app.
- PayPay is not suitable for automatic subscription renewals. To collect payments for subscriptions using PayPay, send email notifications with a Pay Now link when a new invoice is generated.
- PayPay does not support chargebacks. Refunds must be issued manually if needed.
- PayPay is exclusively available for JPY (Japanese Yen) transactions.
Was this article helpful?