Stripe SEPA

From WHMCS Documentation

This page describes a Payment Gateway Module in version 7.9 and above.

Supported Features

Type One Time Recurring Refunds 3D Secure
Token Yes Yes Yes No
Remote Update Card Remote Delete Card
No Yes

Getting Started

To activate and configure the Stripe SEPA module for use, follow the steps below.

  1. Begin by navigating to Setup > Payments > Payment Gateways
  2. Select the All Payment Gateways tab
  3. Locate Stripe SEPA and click to activate it
  4. Stripe SEPA uses API keys for authentication. Upon activation, you will be asked to enter the Secret and Publishable API Keys provided to you by Stripe.
  5. Do not enter a value for the Webhook Endpoint Secret, it will be generated automatically.
  6. Customise the Display Name for the payment gateway as desired
  7. Customise the Statement Descriptor if desired (maximum of 22 characters)
  8. Click Save Changes to complete the setup process.

Stripe SEPA is now activated and ready for use.

Transaction Fees: Stripe returns transaction fees in the default currency of the Stripe account. If you have a different default currency in WHMCS, you must ensure you have configured the currency of your Stripe account in Setup > Payments > Currencies along with a valid exchange rate to allow WHMCS to be able to convert the fee into your other currencies.

Webhook Secret Key

The Stripe SEPA module requires a valid Webhook and Secret Key in order for payments to be recognised and automatically applied to invoices.

Should the Secret Key for the Webhook be modified at Stripe, this must be updated within the WHMCS Stripe SEPA module configuration.

Payment Workflow

  1. Automated recurring and on-demand billing is supported.
  2. SEPA Direct Debit is a pull-based, reusable, and asynchronous payment method. This means that it can take up to 14 business days to confirm the success or failure of a payment after you initiate a debit from the customer’s account, though the average is five business days.. The invoice will be placed in Payment Pending until the payment has cleared.
  3. When making a payment, customers are able to select to use a previously stored bank account or enter a new one.
  4. Customers never leave your WHMCS installation during checkout or adding/removing a new bank account.
  5. Personal bank information is submitted directly to Stripe and is never stored in your local WHMCS installation.
  6. The Stripe API is used for refunds and obtaining transaction information.