Docs
This feature is a Private Beta release. Contact Chargebee Support to enable SEPA via Twikey for your live and test sites.
To set up the Twikey gateway first, see Configure Twikey in Chargebee. For gateway capabilities and regional support, see Twikey Gateway Overview.
Before enabling SEPA Direct Debit:
Follow these steps to enable Direct Debit (SEPA) via Twikey in your Chargebee site:
Go to Settings > Configure Chargebee > Payment Gateways > Twikey.
On the Configure Twikey page, enable Direct Debit (SEPA).
Enter the following details:
The Creditor Name and Creditor ID are required to create the authorization agreement that allows you to collect funds from the customer’s bank account.
Save changes and click Apply.
SEPA requires that customers receive emails for:
To send these emails from Chargebee, select Send SEPA compliant emails from Chargebee.
Sending these emails from Chargebee lets you customize elements such as your company logo and signature.
Note:
If you enable this option in Chargebee, disable the mandate create email in your Twikey setup to avoid duplicate emails being sent from both systems.
Use the Display Direct Debit as a payment method setting to control who sees SEPA Direct Debit in checkout and the self-serve portal.
Available options:
| Option | Description |
|---|---|
| All your customers | Displays Direct Debit for all customers, including new customers, regardless of the customer-level bank account setting. |
| Customers with Direct Debit payments enabled | Displays Direct Debit only for customers for whom Allow this customer to pay via their bank account is enabled. |
Click Apply to save your changes.
The following are the features for this integration and details about them:
The following are the features for this integration and details about them:
| Feature | Description | Supported | Default state | Configuration / behavior |
|---|---|---|---|---|
| Integration sync mode | Defines the integration mode between Chargebee and Twikey, including how payment requests are processed and statuses are communicated. | Yes (Only Asychronous mode) | Asynchronous | Twikey processes Direct Debit payments asynchronously. Chargebee receives the final payment status through webhook notifications. Webhooks are mandatory, and final status updates can appear with a delay. |
| Capture settings | Payment processing involves two stages: Authorization and Capture. Capture settings in Chargebee and Twikey determine when and how funds are collected post authorization. | Yes | Auto capture | No configuration is required. Auto capture is the only supported capture setting for Twikey. |
| Verification modes | Defines how customer bank accounts are validated before initiating Direct Debit | Yes | Enabled | No configuration is required. Twikey performs background verification and may redirect the user to their bank when applicable. |
| Regulatory requirements support | SEPA scheme rules require mandate text to be displayed at checkout and notifications to be sent on mandate creation and prior to debit (Predebit notification) | Yes | Mandate display in Chargebee Checkout - Enabled by default | In Chargebee's prebuilt checkout interfaces, the mandate text is automatically displayed when SEPA is used. For custom checkouts, you must render the mandate text explicitly. |
| Statement descriptor | A statement descriptor is the business name shown on a customer’s bank or card statement, helping them recognize charges and reducing disputes. | Yes | Disabled | Configure this under Settings > Configure Chargebee > Transaction Descriptor. If set, the site-level descriptor is used; otherwise, Twikey uses the name configured on their end for payment requests. |
| Chargeback management | Processes chargeback events via webhooks and automatically applies configured actions on invoices and subscriptions to streamline handling and prevent repeat disputes. | Yes | Disabled | Configure at Settings > Configure Chargebee > Billing LogIQ > Payments > Chargeback Management. Twikey sends webhook events only when a chargeback is lost. |
| Fraud management | Automatically interprets fraud signals from the payment gateway to identify and flag high-risk transactions for appropriate action. | No | NA | Twikey performs background checks to detect and reject fraudulent payments. As this is handled at Twikey, no additional fraud signals are managed in Chargebee. Contact Twikey to configure specific fraud rules. |
| Transaction initiation type | Classifies transactions as customer-initiated or merchant-initiated | No | NA | Not supported. Direct Debit transactions are merchant-initiated by design. |
| Error intelligence | Provides standardized categorization of payment failures | No | NA | Not supported for Twikey. No configuration required. |
| Gateway transaction details | Provides access to raw gateway responses for transactions | Yes | Enabled | Available on the transaction page under Error details. No configuration required. |
| Addition of payment methods in Chargebee dashboard | Ability to add a payment method in Chargebee when details are collected outside the platform. | No | NA | Not supported. Customers must complete the Twikey verification flow via redirect. |
Was this article helpful?