Docs

Log into read the version of docs relevant to your site.

EPS via Mollie

This feature is a Private Beta release. Contact Chargebee Support to enable EPS via Mollie for your live and test sites.

EPS (Electronic Payment Standard) is a widely used online banking payment method that allows customers to complete transactions online directly from their bank accounts. It is the most popular online payment method in Austria.

This document explains how to configure Mollie EPS. Chargebee allows you to configure and process EPS payments with Mollie seamlessly, enhancing your business opportunity in the Austrian market.

To configure Mollie EPS, you must have an account with Mollie and should have configured Mollie SEPA. This is because Mollie EPS is generally used to make one-time payments. In a subscription business, you will be charging your customers on a recurring basis. Therefore, Chargebee handles recurring scenarios by converting all recurring transactions after the first payment to Direct Debit SEPA payments.

Key Features

Prerequisites

Follow these prerequisites before configuring EPS via Mollie in your Chargebee account:

Configure EPS via Mollie

Complete the steps below to configure your Chargebee account to accept EPS payments via the Mollie gateway:

  1. Log in to your Chargebee Billing site.
  2. Go to Settings > Configure Chargebee > Payment Gateway.
  3. Select Mollie from the list of configured gateways.
  4. On the Configure Mollie page, enable EPS to configure EPS payments for customers in Austria.
  5. Click Apply to save your changes.

Configuring Webhooks

To ensure your Chargebee–Mollie integration works seamlessly, webhooks are automatically handled by Chargebee. Unlike other payment gateways, you do not need to manually configure webhooks in your Mollie account.

Chargebee automatically sends the webhook URL as part of the request object to Mollie. This allows Chargebee to receive real-time updates from Mollie whenever certain actions (such as payment status changes or transaction updates) occur.

No additional webhook configuration is required from your end, ensuring a seamless integration experience.

Was this article helpful?