Changelog

All notable changes to the current API will be documented here. To learn about API versioning, see API Lifecycle.

May 2024

• A Category field was added to the merchant callback QR code Create or update callback QR endpoint, to allow merchants to control what will be shown on the waiting screen after the code is scanned.

April 2024

• The QR API signing key was upgraded to accommodate .NET security requirements. Unfortunately, the qrImageUrl URLs for Merchant redirect QR codes created before this time have stopped working. To resolve this, call Get callback QR by ID to get a new qrImageUrl link to the QR code.

March 2024

• A new endpoint for personal QR code exchange allows you to exchange the token or string that you get by scanning a user's personal QR code for the user's information (e.g., phone number (MSISDN)).

January 2023

• The user.checked-in.v1 webhook parameter MerchantSerialNumber has been renamed to msn. See the webhook description.

December 2023

• The merchant callback QR feature has new functionality for how to query QR codes. The new query parameters qrImageFormat and qrImageSize are replacing the Accept header and the Size header respectively when calling [GET:/qr/v1/merchant-callback] and [GET:/qr/v1/merchant-callback/{merchantQrId}]. For more details, see the merchant callback QR section.

November 2023

• Merchant callback QR endpoints are ready for testing in the MT environment. Please note: In the flow when the integrator initiates the payment, the app user will have to go back to the home screen before the payment request arrives. This is temporary and only in the test environment. In the production environment the payment request will come immediately.

May 2022

• Added redirectUrl to all responses, so merchants can see where a QR is pointing.

April 2022

• Path changed from /merchantRedirect to /merchant-redirect.

September 2021

• An early version of the QR API is available.