Bancontact WIP

Bancontact WIP which stands for Wallet Initiated Payments allows Businesses to issue (and process) customer-not-present payment transactions without performing Strong Customer Authentication systematically after first payment.

The service (offered by Bancontact ) enables businesses to initiate recurrent payment flows, unlocking value for use cases like e-commerce, gaming and market places, and enabling subscription models. On first payment, customers are required to complete a Strong Customer Authentication in order to verify their identity and confirm the agreement for subsequent charges with the business.

🚧

Disclaimer

  • Bancontact WIP is currently supported for merchant initiated recurring payments only.
  • This is service is subject to eligibility (cf. set-up requirements)

How it works

First payment (customer present)

During the first payment, the customer grants the rights to the business to initiate subsequent charges (recurring) without their presence. After this first payment a Mandate is created. This object reference needs to be used for processing subsequent merchant initiated transactions.

🚧

You must make it clear to the customer that their payment details will be used to charge subsquent payments.

Recurring payments (customer not present)

For subsequent charges, the merchant initiates a payment of sequenctType=recurring and method=bancontact. You must specify the customerId and mandateId; those references will have been created as a results of the first payment.

More details about how to implement Recurring payments

Key information

Available country codes

BE

Supported merchant locations

European Economic Area (EEA), United Kingdom, Switzerland

Supported currencies

EUR

API method name

bancontact

Supported API

Payments API , Orders API

Minimum transaction amount

EUR 0.02

Maximum transaction amount

EUR 1,500.00

Session timeout

1 hour

Refund

Full refund Partial refund Multiple partial refunds

Refund validity

365 days

Recurring

Yes (Recurring only)

Settlement delay

2 business days

Chargeback risk

No

Chargeback period

n.a.

Charge

Instant charge Full capture

Resource pack

Available here


Bancontact WIP Recurring - Set up and Requirements

Eligibility

Bancontact WIP is subject to eligibility criteria and review by Bancontact. You must follow relevant UX requirements.

UX requirements

Checkout page

In order to accept Bancontact WIP recurring payment your Checkout page must:

  • Display your T&Cs clearly to the customer and the customer must accept T&Cs on checkout.
  • Make it clear to the customer that their credentials will be re-used for subsequent merchant initiated charges as well as the terms and schedule (if applicable) of such charges and that by proceeding with the checkout you accept the storage and reuse of your credentials.

Post checkout page

Post checkout, you must:

  • Provide an easy way for customer to contact you to dispute a charge and request a refund
  • Provider an interface for customers to manage their saved payment details and/or cancel their recurring payments