Please note that Online Sales (Custom on the Website Checkout Page and App to App) and Invoice solutions are no longer offered directly by Bancontact Payconiq Company.
If you would you still like to use a similar solution in your business please contact one of the partners listed here.
To request an account on our new pre-Production Environment, please email us at devsupport@payconiq.be with the following information:
- Company Name:
- Merchant ID (MID): (your unique Merchant Identifier. You can retrieve it from your Merchant Portal)
- Point of Contact:
- Name:
- Surname:
- Email:
- Phone Number:
- Type of Integration:
The available types of integration for testing are the following:
On a Display: A one-time usage digital QR code will be generated by your system and shown on a consumer-facing screen. Your consumers scan the QR code with their preferred payment application and confirm the transaction.
On a Receipt: A one-time usage QR code is printed by your ECR system on your receipts. Your consumers scan the QR code with their preferred payment application and confirm the transaction.
Static Sticker:A printed static QR code is linked to your cash register or your point of sale (PoS). Your PoS sends the payment information to the QR code, your consumers scan the QR code with their preferred payment application and confirm the transaction.
Top Up: Closed loop payment system to top up payment cards or wristbands. Ideal for festivals, employee cards, student cards…etc. You print a fixed payment QR code on a top-up medium of your choosing, your consumers scan the QR code with their preferred payment application and confirm the transaction.
Once we receive your email, a member of our Dev Support Team will create your pre-production account and will provide you, for each integration type:
- Product Profile ID (PPID): Unique product identifier
- API Key: Used to secure the request between the Merchant’s backend and Bancontact Payconiq’s backend. Do not share your API keys in public areas such as online sites or client-side code.
Please note that processing your request may take up to 2 weeks.
Once you receive your credentials, you can follow the steps below.
In order to test transactions and validate your integration with the Bancontact Payconiq Acceptance Service end-to-end, you will need to use the Payconiq by Bancontact App (PQbyBC).
To install and activate the app, please follow the instructions below.
If you require any assistance or encounter any issues during the process, please reach out to testappsupport@bancontactpayconiq.com with a description of the encountered issue and the following information:
- Account details: phone number and email address
- App version
Important Note: before proceeding with the steps below, please make sure there are no other Payconiq by Bancontact apps installed on your device. Having multiple versions installed can cause redirection issues. Delete the PRODUCTION app before downloading the PRE-PRODUCTION (EXT) version.
Start by downloading Payconiq by Bancontact (PQbyBC) app and install it on your device.
The PREPROD Build of the app can be downloaded via the following form.
The PROD Build of the app can be downloaded via both the App Store (iOS) and the Google Play Store.
Once done, open it and follow the intructions below:
Select: Continue "I don't have itsme"
Email address:
- Enter your email address
- Enter the code 123456 (no OTP code will be sent by email)
Enter your first name and last name (only applicable if you are a new user)
Phone number
- Enter your phone number (must be an EU phone number)
- Enter the code 123456 (no OTP code will be sent by SMS)
Set a PIN code. It will be used to validate payments and enter some protected sections in the app.
Either activate Biometric or skip the step.
Add a Bancontact card from the list here below
Select the bank of the card.
Input the bank card number and the expiry date.
Switch the toggle “I have read and accepted the terms and conditions of my bank.” and click on "Add card".
Click on “Continue” on the next screen.
Give access to the camera and allow notifications.
You are now all set!
Important Note:if you intend to onboard again with a new email or phone number, you’ll need to reset the app first. You can do this directly within the app (via your profile).
| Issuer | Card Number | Expiry Date | Expected Result |
|---|---|---|---|
| KBC | 5127 8829 9999 9715 | Nov-29 | Always Authorized |
| KBC | 5127 8829 9999 9723 | Nov-29 | Insufficient funds |
| KBC | 5127 8829 9999 9731 | Nov-29 | Card Refused by Issuer |
Once you have dowloaded the PQbyBC PROD build and have created your account, you can update your API endpoints as follows:
| Operation | Legacy EndPoint | New EndPoint |
|---|---|---|
| Create Payment - Static QR | https://api.ext.payconiq.com/v3/payments/pos | https://merchant.api.preprod.bancontact.net/v3/payments/pos |
| Create Payment - Other Integrations | https://api.ext.payconiq.com/v3/payments | https://merchant.api.preprod.bancontact.net/v3/payments |
| Get Payment Details | https://api.ext.payconiq.com/v3/payments/{paymentId} | https://merchant.api.preprod.bancontact.net/v3/payments/{paymentId} |
| Get Payment List | https://api.ext.payconiq.com/v3/payments/search?page={p}&size={s} | https://merchant.api.preprod.bancontact.net/v3/payments/search?page={p}&size={s} |
| Cancel Payment | https://api.ext.payconiq.com/v3/payments/{paymentId} | https://merchant.api.preprod.bancontact.net/v3/payments/{paymentId} |
| Get Refund IBAN | https://api.ext.payconiq.com/v3/payments/{paymentId}/debtor/refundIban | https://merchant.api.preprod.bancontact.net/v3/payments/{paymentId}/debtor/refundIban |
| Callback | https://api.ext.payconiq.com/callback | https://merchant.api.preprod.bancontact.net/callback |
Important Note: The changes mentioned in this section will not impact your existing QR codes. Generating new QR codes is only needed for pre-production testing before migration. Once migration is completed, your current production QR Codes will keep on working like they do today.
Bancontact Payconiq's QR code URLs contain two parts:
| Service URL | Payload URL |
|---|---|
| https://portal.payconiq.com/qrcode | https://payconiq.com/pay/1/5c1b589a296e9a3330aebbe0&s=L&f=PNG |
When put together, these two sections result in a unique QR Code URL like the following:
https://portal.payconiq.com/qrcode?c=https://payconiq.com/pay/1/5c1b589a296e9a3330aebbe0&s=L&f=PNG
In our new Wero and Bancontact solution, only the Service URL changes and is replaced by https://qrcodegenerator.api.bancontact.net/qrcode The "Payload URL" remains unchaged. This results in a full QR Code URL like the following:
https://qrcodegenerator.api.bancontact.net/qrcode?c=https://payconiq.com/pay/1/5c1b589a296e9a3330aebbe0&s=L&f=PNG
As a result, you will have to update your QR Code Generation URL for the following integrations:
Important Note:
Our QR code generator exists both in PRE-PROD and in PROD:
- https://qrcodegenerator.api.preprod.bancontact.net/qrcode?c
- https://qrcodegenerator.api.bancontact.net/qrcode?c
In the table below you'll find a before and after structure for each of the integrations mentionned above:
| Integration Type | Legacy QR Web View | New QR Web View |
|---|---|---|
| Static QR Code | https://portal.payconiq.com/qrcode?f=PNG&s=L&c=https://payconiq.com/l/1/{PaymentProfileId}/{POSId} | https://qrcodegenerator.api.bancontact.net/qrcode?f=PNG&s=L&=c=https://payconiq.com/l/1/{PaymentProfileId}/{POSId} |
| Receipt & Top Up | https://portal.payconiq.com/qrcode?f=PNG&s=L&c=https://payconiq.com/t/1/{productProfileId}?D={Enc_description}&A={Enc_amount}&R={Enc_reference} | https://qrcodegenerator.api.bancontact.net/qrcode?f=PNG&s=L&c=https://payconiq.com/t/1/{productProfileId}?D={Enc_description}&A={Enc_amount}&R={Enc_reference} |
Alternatively, you can simply generate the Payload URL using your pre-production PPID. You will be redirected to the existing Payconiq web view.
Please note that starting migration, Bancontact Payconiq Company will move it's CallBack Certificates to the following links
- Bancontact Payconiq may rotate its certificate without prior notice.
- Merchants who pin certificates must pin only the Common Name (CN) of the certificate, enabling seamless rotation.
- A new JWK will be added for 24 hours before the old one is removed.
- Merchants should cache JWKs for up to 12 hours and re-fetch if verification fails.
For further information, please refer to our Callback Guide