PayTo via Stripe
This feature is a Private Beta release. Contact Chargebee Support to enable PayTo via Stripe for your live and test sites.
Chargebee supports PayTo through the Stripe payment gateway, letting you offer Australian customers a familiar local payment experience at checkout.
PayTo is Australia's account-to-account payment system built on the New Payments Platform (NPP). Chargebee supports both one-time payments and recurring subscriptions through PayTo mandates.
When a customer selects PayTo during checkout:
- They authenticate and authorize the payment through their Australian bank's digital channels, and save the PayTo payment method during the initial payment.
- After authorization, Stripe redirects the customer back to your Chargebee site.
- Future payments can be initiated by the merchant without requiring the customer to be present.
Supported countries and currencies
| Country | Supported currency |
|---|---|
| Australia | AUD (Australian Dollar) |
Key features
- Supports one-time payments (one-time charges) and recurring payments (subscriptions) through merchant-initiated transactions (MIT).
- Supports AUD (Australian Dollar) as the payment currency.
- Available for customers with participating Australian banks only.
Prerequisites
Before you set up PayTo in Chargebee:
- Stripe is configured as a payment gateway in Chargebee.
- PayTo is enabled in your Stripe account.
- The customer has an Australian bank account with a PayTo-enabled bank.
- The customer has a PayID or a BSB number and account number, one of which is mandatory on the payment details page.
Integration options
You can integrate PayTo via Stripe using the following methods.
| Integration method | Description |
|---|---|
| Chargebee Hosted Pages (in-app checkout) | Accept PayTo payments using Chargebee's in-app hosted checkout with minimal integration effort. |
| Chargebee Hosted Pages (full-page checkout) | Accept PayTo payments using Chargebee's full-page hosted checkout. |
| Chargebee.js | Embed PayTo as a payment method in your custom checkout using Chargebee.js. |
| API (Payment Intent) | Process PayTo payments using Chargebee APIs for a fully custom checkout and payment flow. |
Configure PayTo via Stripe in Chargebee
To enable PayTo 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, turn on PayTo.
- Click Apply to save your changes.
Configure Smart Routing
After you turn on PayTo, follow these steps to configure Smart Routing for it:
- Go to Settings > Configure Chargebee > Payment Gateways.
- Click Manage Rules under Smart Routing.
- Under the For PayTo section, set the rule to route AUD payments to your Stripe account, then click Save.
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 events:
charge.refund.updated— notifies Chargebee when a refund transaction is created, fails, or is updated in Stripe.payment_intent.succeeded— notifies Chargebee when a payment is completed successfully.payment_intent.payment_failed— notifies Chargebee when a payment could not be completed.
These events ensure that payment and refund statuses are reflected accurately in your Chargebee account. Because PayTo payments are asynchronous, Chargebee relies on the payment_intent.succeeded and payment_intent.payment_failed events to receive the final payment status.
Payment workflow
Your customer completes the following steps at checkout when paying with PayTo via Stripe:
- The customer reviews the order details on the Your order page and clicks Proceed To Checkout.
- The customer enters their email address to proceed and clicks Next.
- On the Add your account details page, the customer enters their name, email, and phone number, then clicks Next.
- The customer enters their billing address on the Add your billing address page and clicks Next.
- On the Add your payment details page, the customer selects PayTo and enters either a PayID or a BSB number and account number (one of these is mandatory), then clicks Next.
- The customer reviews the order summary on the Complete your order page and clicks Pay while the transaction is processed.
- Once the payment is authorized, the page automatically closes and the customer is redirected back to Chargebee.
Note
These screenshots show the PayTo checkout flow in Stripe's test environment. In production, customers complete the payment through their Australian bank's digital channels.
Recurring payments (MIT)
PayTo via Stripe supports merchant-initiated transactions (MIT) for recurring billing:
- Customers authorize and save their PayTo payment method during the initial payment.
- Future payments can then be initiated by the merchant without requiring the customer to be present.
- MIT payments are asynchronous and initially move to an In Progress state while the customer's bank processes the payment.
- Processing time is typically 1–3 business days for the bank to process the payment.
- Chargebee relies on webhooks to receive the final payment status:
payment_intent.succeeded— the payment completed successfully.payment_intent.payment_failed— the payment could not be completed.
Payment features
The following features are supported for PayTo 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 PayTo payments asynchronously. A payment initially moves to an In Progress state and can take 1–3 business days to reach a final status. Chargebee receives the final status through the payment_intent.succeeded and payment_intent.payment_failed webhooks, and refund updates through the charge.refund.updated event. Webhook configuration is mandatory. |
| 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 PayTo via Stripe. No additional configuration is required. |
| Verification modes | Defines how payment methods are verified before processing. | Yes | Enabled | The customer authorizes the payment through their bank's digital channels. No separate verification configuration is required in Chargebee. |
| Statement descriptor | Displays the business name on the customer's bank statement, helping them recognize charges and reducing disputes. | No | Not applicable | Not applicable to PayTo via Stripe. |
| Chargeback management | Handles chargeback events and applies configured actions on invoices and subscriptions. | No | Not applicable | Chargebee does not manage PayTo disputes for this integration. Stripe PayTo disputes are final and cannot be appealed. |
| Fraud management | Uses gateway fraud signals to identify and flag high-risk transactions. | No | Not applicable | No PayTo-specific fraud configuration is available in Chargebee. |
| Transaction initiation type | Identifies whether a transaction is customer-initiated (CIT) or merchant-initiated (MIT). | Yes | Supported | The initial payment is customer-initiated when the customer authorizes and saves the PayTo payment method. Subsequent recurring charges are merchant-initiated using the stored Stripe payment method. |
| 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 PayTo checkout flow. PayTo 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 Stripe and used for subsequent merchant-initiated recurring payments. | Yes | payment_method[reference_id] | customer_id/payment_method_id |
| 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 PayTo documentation for instructions on testing PayTo in the Stripe test environment. Make sure webhooks are configured to receive the payment_intent.succeeded, payment_intent.payment_failed, and charge.refund.updated events.
Production testing
Before you go live:
- Make sure PayTo is enabled in your Stripe live account.
- Verify that webhook configuration is complete (required for payment status and refund settlement updates).
- Run end-to-end testing using a real Australian bank account with a PayTo-enabled bank.
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
- PayTo can't be added as a payment method through the customer portal or the Chargebee app. Customers must complete the PayTo checkout flow.
- PayTo supports recurring billing through merchant-initiated transactions (MIT). The customer authorizes and saves the payment method during the initial payment, and subsequent charges are processed without the customer being present.
- Recurring (MIT) payments are asynchronous. A payment stays in an In Progress state and can take 1–3 business days for the customer's bank to process before reaching a final status.
- PayTo is available only to customers with a participating Australian bank. As a relatively new system, bank participation is currently limited.
- The customer must provide a PayID or a BSB number and account number on the payment details page.
- Chargebee does not manage PayTo disputes. Stripe PayTo disputes are final and cannot be appealed.
- Transaction amounts must be between 0.01 AUD and 999,999.99 AUD.
- PayTo is available only for AUD (Australian Dollar) transactions.
Was this article helpful?