Article summary

        For a Bancontact transaction the merchant starts by sending the request to a BPE transaction gateway. The gateway processes the request and sends a response to the merchant. If the request is sent to a gateway without a customer redirect, the response will contain a redirect URL to which the customer must be redirected. If in the original request the customer was already redirected to the public gateway, the customer is automatically redirected to this page by the transaction gateway. Once the customer reaches this page, he can enter his card details. Once these have been entered and verified and the card is not secured with a 3D Secure code, the payment is processed immediately and the customer will be redirected back to the merchant website, along with the result. If the card is secured with a 3D Secure code, the customer is redirected to the 3D Secure page for its specific card. After completing the process at this page, the customer returns to the BPE transaction gateway and the Payment Engine will process the credit card payment, after which the customer is also redirected back to the merchant website, along with the payment result. Additionally, the Payment Engine will also perform a Transaction Push, with the status of the payment.

        Servicecodes and actions

        The servicecode for Bancontact is: bancontactmrcash

        The Bancontact service supports the following actions: Pay, Refund, Authenticate, PayOneClick and PayRecurrent. All actions can be used with channel 'Web'.

        Wallet Initiated Payments

        When you are eligible for Wallet Initiated Payments, it is possible to use the PayOneClick and PayRecurrent actions. This is possible after an initial successful Bancontact transaction, where the Bancontact token is saved. For this the optional service parameter "savetoken" needs to be set to true on the original Bancontact transaction.

        Recurring Direct Debits

        It is also possible to use a Bancontact transaction as a reference transaction for recurring SEPA Direct Debit transactions. To do this, add the basic parameter "StartRecurrent" with value "True" to your Bancontact API request. Once successful, you can perform a recurring SEPA direct debit transaction. Please see the SEPA Direct Debit section for an explanation of the "PayRecurrent" request.

        Bancontact app

        When Buckaroo is your Bancontact acquirer, it is possible for the customer to finish a Bancontact transaction with the Bancontact app. The "pay with Bancontact app"-button will appear automatically when the customer is redirected to the Buckaroo checkout, below the fields where the customer can enter its card data. When a customer clicks on this button, it will either see a QR-code which the customer can scan with its Bancontact app, or, when a customer is on a mobile device, it will be redirected directly to the Bancontact app, and the customer can finish the transaction.

        It is also possible to show this button (and show the QR-code, or redirect to the Bancontact app) on your own webshop checkout. To be able to do this you have to implement our Client SDK. And initiate a server side Pay request. With the "Key" given in the Pay response, you can call the Client SDK like this:

        $(document).ready(function() { BuckarooSdk.BancontactMobile.initiate("#bancontactMobileButton", "TransactionKey"); });

        Where "#bancontactMobileButton" is the id of the location where you want to show the button.

        Click here for more information about our Client SDK.

        App or Card on your own webshop checkout

        It is also possible to let the consumer choose between paying with the Bancontact App or Bancontact Card on your own webshop checkout. Al you have to do is send a Pay request to our Transaction API. And send a GET request to where TRANSACTIONKEY is the retrieved transaction key from the Pay request. The response contains the data you have to use to show the QR-Code. When the consumer pays with the Bancontact App, you don't have to do anything. When the consumer pays with its Bancontact Card, you have to send the encrypted card data in a CompletePayment request to our DataRequest API to complete the payment.

        New URL feature for Bancontact App2App payments

        A new feature for BC App2App payments makes it possible that Merchants can send an IntentURL as the return URL.

        This way the Merchant IntentURL will be passed through to Bancontact instead of to our own return URL. The URL enables the Merchant to return the consumer to the Merchant App after the consumer has made its payment through the Bancontact App.

        The feature does not conflict with Merchants using both App2App and Browser based transactions. For this, Buckaroo will basically provide 2 URLs at the same time: One URL is referring to the Bancontact App and the other URL can be used for a browser based payment (like for instance a QR code which can be displayed in the browser). The Merchant implementation can pick and choose the right URL per transaction channel.

        The feature will have to be activated by Buckaroo in the Merchant Account.

        How to test Bancontact

        You can find everything on test transaction in this article: Test transaction

        Was this article helpful?

        What's Next