Skip to content
qurl.be

Commerce & products

2014: Bancontact brings QR into mobile payments in Belgium

A QR code can open a catalogue or lead into a payment journey: the action after reading differs. Bancontact dates the launch of its QR mobile payments to 2014. This Belgian milestone shows why the symbol, the request processed by the app and payment confirmation need to remain distinct.

Published on 4 min read
A person holds a smartphone at a counter, facing a tablet, illustrative photo.
Photo: Tim Douglas · Pexels

2014: a Belgian milestone, specified to the month by Worldline

In its history, Bancontact dates the launch of QR mobile payments to 2014. Worldline legacy documentation specifies that an updated app, including payments to merchants, launched in May 2014.

These sources serve different purposes: one gives Bancontact’s yearly milestone, while the other describes a stage of the payment solution. The account therefore stays with the documented year and month, without inventing an identical launch day for every user.

The QR code opens a journey that also includes confirmation

Worldline’s historical documentation describes two entry points: reading a QR code with the Bancontact app or moving from the payment page to the app on the same device. It then places payment confirmation in the app.

Reading is therefore not the whole transaction. To understand the journey, distinguish:

The symbol read
It provides entry into the journey intended by the service.
The payment request
It is processed within the payment environment, with its information and conditions.
Confirmation
It belongs to that service; an image decoded by a generic reader alone does not prove a payment succeeded.

The guide to understanding how a QR code works helps separate reading data from the action that follows.

A fictional bookshop: catalogue and payment need different QR codes

Imagine a bookshop called “Les Pages du Canal”. It wants to present new titles on phones and offer a payment journey at the till. The word “QR” alone does not define these two needs.

For the catalogue, the team chooses a public page and a QR code containing its address. For payment, it uses the request and medium supplied by its payment service, under the conditions agreed with that service. A generic QR code containing the shop’s name or an amount written as text does not replace that request.

Captions state the action: “View the catalogue” or the wording intended for payment. The team avoids placing two unexplained codes together. The guide to writing QR captions helps organise these signposts. The bookshop and scenario are fictional; this article provides no payment request.

What Qurl prepares for an information page

The Qurl QR generator can encode the address of your catalogue, opening hours or another information page. It does not create a banking request, confirm a payment or check its status.

For that information link, choose the page the audience actually needs to view. The guide to correcting a QR destination helps distinguish a specific page from an overly general homepage. The guide to providing an alternative to QR explains the value of a readable address for people who do not scan.

Reading historical conditions in context

The cited Worldline page belongs to legacy documentation. Its old screens, product names, limits and conditions do not automatically describe today’s offering. The service used and its current documentation determine the journey available today.

This 2014 milestone mainly shows that the visible square alone does not explain the action. The retrospective on WhatsApp Web in 2015 illustrates a browser-pairing QR code. The retrospective on QR sharing in Chrome describes a web link: three uses that need different instructions.

All News Follow the News via RSS