PayPay via Stripe
This feature is a Private Beta release. Contact Chargebee Support to enable PayPay via Stripe for your live and test sites.
Chargebee now supports PayPay through the Stripe payment gateway, letting you offer your Japanese customers a familiar local payment experience at checkout.
When a customer selects PayPay during checkout:
- They're redirected to a local processing partner (NICEPAY) to authenticate and authorize the payment.
- After authorization, Stripe redirects the customer back to your Chargebee site.
This integration adds checkout flexibility and helps improve conversion for businesses on the Chargebee platform.
Key features
- Supports one-time payments (one-time charges) only.
- Supports JPY (Japanese Yen) as the payment currency.
- Compatible with:
Prerequisites
Before you set up PayPay in Chargebee:
- Stripe is configured as a payment gateway in Chargebee.
- PayPay is enabled in your Stripe account.
Configure PayPay via Stripe in Chargebee
To enable PayPay payments through Stripe in Chargebee:
- Log in to your Chargebee Billing site.
- Go to Settings > Configure Chargebee > Payment Gateway.
- Select Stripe from the list of configured gateways.
- On the Configure Stripe page, enable PayPay.
- Click Apply to save your changes.
Configuring webhooks
To keep your Chargebee–Stripe integration in sync, configure webhooks in Stripe. Webhooks let Chargebee receive real-time updates from Stripe when important events, such as refunds, occur.
For this integration to work correctly, enable the following event:
This event notifies Chargebee when a refund transaction is created, fails, or is updated in Stripe, so refunds are reflected accurately in your Chargebee account.
Payment workflow
Your customer completes the following steps at checkout when paying with PayPay via Stripe:
- The customer reviews the order details on the Your order page and selects Proceed To Checkout.
- The customer enters the billing address on the Add your billing address page and selects Next.
- On the Add your payment details page, the customer selects PayPay and selects Continue with PayPay. The transaction is processed through the local partner, NICEPAY.
- The customer reviews the order summary on the Complete your order page and selects Pay.
- On the PayPay payment page, the customer authorizes the payment.
- The customer is redirected back to Chargebee, where the transaction is processed.
Note
The screenshots above show the PayPay authorization flow in Stripe's test environment. In production, customers complete the payment in the actual PayPay app or by scanning the live QR code.
Payment features
The following features are supported for PayPay via Stripe.
| Feature | Description | Supported | Default state | Configuration or behavior |
|---|---|---|---|---|
| Integration sync mode | Defines how payment requests are processed and statuses are communicated between Chargebee and Stripe. | Yes (asynchronous) | Asynchronous | Stripe processes PayPay payments asynchronously. Chargebee receives the final payment status through Stripe webhooks. Webhook configuration is mandatory and is used to receive refund updates through the charge.refund.updated event. |
| 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 Stripe. No additional configuration is required. |
| Verification modes | Defines how payment methods are verified before processing. | Yes | Enabled | The customer authorizes the payment in the PayPay app or by scanning the QR code on the redirect page. 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 | Not applicable | PayPay doesn't support chargebacks for this integration. Issue refunds manually if needed. |
| Fraud management | Uses gateway fraud signals to identify and flag high-risk transactions. | No | Not applicable | 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 | Not applicable | PayPay supports customer-initiated, one-time payments only. Merchant-initiated recurring charges aren't supported. |
| Error intelligence | Provides standardized categorization of payment failures. | Yes | Enabled | Available through Stripe payment 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. |
| Adding payment methods in the Chargebee dashboard | Allows a payment method to be added in Chargebee when details are collected outside checkout. | No | Not applicable | Customers must complete the PayPay checkout flow. PayPay can't be added from the Chargebee dashboard. |
Supported token formats
This section is relevant if you're building a custom checkout or migrating payment methods from another provider to Stripe.
| 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 | Not applicable |
| Gateway permanent token | Permanent reference provided by the gateway. Not applicable to PayPay because it doesn't support stored credentials. | No | payment_method[reference_id] | Not applicable |
| Gateway temporary token | Short-lived token format that can be converted to a permanent token. | No | Not applicable | Not applicable |
Testing
Sandbox testing
Refer to Stripe's PayPay documentation for instructions on testing PayPay in the Stripe test environment. Make sure webhooks are configured to receive the charge.refund.updated event for refund settlement updates.
Production testing
Before you go live:
- Make sure PayPay is enabled in your Stripe live account.
- Verify that webhook configuration is complete (required for refund settlement updates).
- Run 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 Stripe, use the Chargebee transaction field id_at_gateway, which maps to the Stripe PaymentIntent ID.
To reconcile transactions:
- Retrieve the
id_at_gatewayvalue from the Chargebee transaction details. - Locate the corresponding transaction in your Stripe Dashboard or reports.
- Match transactions using this reference to keep your records consistent.
Limitations and important points
- PayPay can't be added as a payment method through the customer portal or the Chargebee app. Customers must complete the PayPay checkout flow.
- PayPay doesn't support storing payment methods for recurring billing. Each transaction requires explicit customer authorization in the PayPay app.
- PayPay isn't suitable for automatic subscription renewals. To collect subscription payments with PayPay, send email notifications with a Pay Now link when a new invoice is generated.
- PayPay doesn't support chargebacks. Issue refunds manually if needed.
- PayPay is available only for JPY (Japanese Yen) transactions.
Was this article helpful?