QR Code Guide

Overview

QR Codes provide a streamlined mechanism for initiating Payments between parties. A person may generate a QR Code to share payment details, while a Merchant can display one to help a buyer complete a purchase at a Point of Sale (POS).

The Passport PaaS Platform enables the creation of compliant QR Codes that follow the EMV Co Colombian industry specification - current at time of writing with the latest specification from July 2025. These QR Codes can be used in both digital and offline channels, reducing manual errors and enhancing the buyer experience.

Bre-B QR Codes simplify the sale process by embedding essential information (e.g., Bre-B Key, transaction amount, purpose) into a scannable format, reducing friction and improving security - saving the Customer time.

Note

QR Code requirements are defined by institutions including: ACH Colombia, Banco de la República, Credibanco, EMV Co, Mastercard, Redeban, Servibanca, Visa, and Visionamos. Passport provides support to these groups to help further the clarity of the specification for Bre-B payments.

Passport, in partnership with Visionamos, operates a national Bre-B access point to process Bre-B payments and issue QR Codes for use across the ecosystem.

Payment Lifecycle

Bre-B QR Codes can be used across physical and digital channels: including posters, POS terminals, ATMs, websites, and mobile apps.

Example: Coffee Shop Purchase

The image above depicts a simple transaction for a Buyer to purchase a coffee at a Point of Sale where the simple steps are:

Merchant creates a Sale in their POS system.
The POS system generate a Dynamic QR Code that captures the information of the Sale using the Passport PaaS API and displays it to the Buyer.
The Buyer scans the QR code using their mobile banking app's within the Bre-B Zone.
The mobile banking app pre-fills the recipient (Bre-B Key), amount, and transaction purposes.
The Buyer reviews and confirms the transfer to the nominated Bre-B Key.
The payment is sent via the Bre-B network from the Buyer's Bank to Passport's Sponsor Bank.
Passport PaaS receives confirmation from the Bre-B node and identifies the corresponding Merchant.
A Webhook notification is sent to the Merchant's POS system to confirm payment.

Prerequisites

To create QR Codes on the PaaS Platform, there are a number of prerequisities that need to be satisfied. The information for generating the QR Code is pulled from a variety of sources:

Customer: The created Customer contains information such as the Merchant Name and Address which provides data such as the name, city, zip code, and country which are mandatory data fields for the QR Code.
Bre-B Key: A created Key for an Account must be stored in a Static or Dynamic QR Code to route Payments to the Merchant over the Bre-B network.
Configuration: Setting other information such as the Merchant Category Code on the Configuration for the Merchant is required as this is another mandatory data field for a QR Code.
API Request: The majority of the information is provided via the Create QR Codes API request and can include mandatory and optional information depending on the intended use case.

Required Tasks

To satisfy the prerequisites, you must complete the following tasks:

Step	Description
1	Link a Merchant a with legal name, address, city, country, and zip code.
2	Link Account linked to the active customer.
3	Create Key at least one Bre-B Key associated with that account.

Once you finish the steps, you can gather the necessary information for the QR Code from the relevant sources to meet the profile requirements. Use the Create QR Codes API request to get the remaining fields for creating the Static or Dynamic QR Code.

QR Code Creation

To create a QR Code, the Developer needs to consider the main fields and available information for each use case where a QR Code can be presented.

The table below captures the considerations that are needed for the QR Code to have the most impact. Note, the below is not the mandatory fields for each API call, but rather the main fields that can be used to set the contents of the QR Code for the various use cases.

Field	Dynamic	Static
type	A QR Code generated for one time use that is linked to a specific payment amount and activity within the developer ecosystem	A QR Code that can be reused as it doesn't contain any transaction specific information.
channel	Details where and how the QR Code is presented - for example at a Point of Sale, or a Mobile Point of Sale (attached to a phone). The PoS has auto generated the information for the transaction ready for awaiting Payment.	Most likely within a poster or printed mechanism. The Static QR Code is used for sharing information that doesn't change per transaction - such as the Bre-B Key.
qr_code__reference	A unique reference to tie the QR Code to the action the Developer wishes to track	Not required
transaction_purpose	Describes what the QR Code is representing - such as a Purchase	Similar to the Dynamic QR Code, it can also be set for the Static QR Code

These are the main fields that can be changed to suit the Dynamic or Static QR Code implementation - in addition to the Bre-B Key and Amount of course.

The intended use case for the Dynamic QR Code is one that is uniquely tied to a single expected Payment - such as a buyer at the Point of Sale. The QR Code is generated on demand for that particular purchase and is "dynamically" set for that sale.

The Static QR Code can be printed out en masse and left for anyone to find - there is no sale specific information that needs to be generated for each person that scans the QR Code. For example, a charity taking donations could print Static QR Codes in a national newspaper, while the person scanning the code sets the amount of the donation that they wish to send within the mobile banking app.

The examples below show how this can be implemented.

Static QR Code

A Static QR Code contains fixed payment information and does not change once created. It’s typically printed and displayed on a physical medium, such as a sticker, poster, or checkout stand in a merchant's location.

This QR Code type is ideal for environments where the merchant has a direct, in-person interaction with the buyer, such as small vendors or informal retail setups.

The buyer scans the QR Code using their mobile banking app.
The buyer manually enters the amount and submits the payment.
The merchant confirms the payment manually, for example by checking their banking app.

Ease of Use

No integration with a Point of Sale system is required, making this a lightweight solution for Bre-B acceptance.

Passport’s PaaS Platform supports multiple implementation paths: either through dedicated merchant accounts or platform-managed flows where you remain in control of the end-to-end payment lifecycle.

Static QR Code Request Example

The example below could be used for a small street vendor wishing to take Bre-B Payments via a Static QR Code that has been printed out on a sticker that is attached to the side of their cart to help Buyers scan to make a Payment.

Parameter	Description
key_id	The unique identifier for the Bre-B key that was created in a previous step for the pre-requisite.
customer_id	The unique identifier of the merchant (Customer).
type	Set to `STATIC` to indicate this is a static QR Code. (`DYNAMIC` is an option but in this use case `STATIC` is correct).
channel	Set to `MPOS` to indicate this is used via a Mobile Point of Sale.
additional_info.transaction_purpose	Submitted within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to SHOPPING
additional_info.transaction.channel_presentation	Submitted within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel. In this example, it was a Printed Sticker (0), that was not used at the registered location of the business (1) and the cashier was present (0) therefore `010` is submitted.

Static QR Code Request Body

curl --location --request POST 'https://api.paas-sandbox.co.passportfintech.com/qrcodes' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer 17d5cc1adb6f6c90d5aa73f74b38f9fa3336d04aee6cf8121a3cf19f190e6213' \ --data '{ "key_id": "1f2046b7-428d-4682-b6f2-3fe438ae5a3e", "customer_id": "291b10c1-b86a-4741-a49f-ff55c46190d8", "type": "STATIC", "channel": "POS", "additional_info":{ "transaction_purpose": "SHOPPING" } }'

There are additional optional fields that can be added to the additional_info object to augment the information in the QR Code, explore the endpoint Create QR Codes to learn more about them and what they can be used for.

Static QR Code Response Example

Once the request is submitted, the PaaS Platform combines information from the various sources in order to create the compliant QR Code according to the Colombian EASPBV Industry Specification for QR Codes. The response is provided back to the Developer in a similar format as other Resources.

Parameter	Description
id	The unique id for the QR Code that was created from the POST request that can be used for future retrieval and deletion requests.
qr_code data	The formatted string for the QR Code that contains the data which can be presented via a digital channel or converted and printed out.
key	An object to represent the `key_value` and `key_type` that was used for creating the QR Code which is also referenced by the key_id
acquirer_network identifier	QR Codes will always be issued by VISI who are an authorised issuer by Banco de la República for Bre-B keys.
merchant	An object representing the information relating to the Merchant itself - the name, city, zip code, country and category code
status	Indicates successful creation (`ACTIVE`).
created_at	A timestamp capturing when the QR Code was created successfully.
key_id	The unique id for the Bre-B key that was created in a previous step for the pre-requisite.
customer_id	The unique id for the Customer was that was created in a previous step for the pre-requisite.
type	Whether the developer would like to create a STATIC or DYNAMIC QR code - in this example, the Developer would chose STATIC.
channel	States how the QR Code has been presented by the Merchant to the Buyer - in this example, the Developer would chose MPOS for a Mobile Point Of Sale.
transaction_purpose	Returned within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to SHOPPING
channel_presentation	Returned within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel. In this example, it was a Printed Sticker (0), that was not used at the registered location of the business (1) and the cashier was present (0) therefore `010` is submitted.

Static QR Code Response Body

{ "created_at": "2025-05-12T20:30:17.547227Z", "qr_code_data": "00020101021226550015CO.COM.VISI.LLA0332jimmyjohns1111402545255@test.com49270015CO.COM.VISI.RED0104VISI52045782530317054130000100000.005802CO5919Test Business O9F126006Bogota61059827362120808PURCHASE80290017CO.COM.VISI.CANAL0104MPOS81260016CO.COM.VISI.CIVA01020282290015CO.COM.VISI.IVA0106100.0083300016CO.COM.VISI.BASE0106100.0084260016CO.COM.VISI.CINC01020285280015CO.COM.VISI.INC010510.0090610017CO.COM.VISI.TRXID01364A07229A-7B14-4B63-85D5-79572E130E0763040351", "qr_code_image": "iVBORw0KGgoAAAANSUhEUgAAAyoAAAMqAQAAAABFsohqAAAKI0lEQVR4nO2dXYrrRhCFT0WGeZQhC5ilyDvIkoZZUnZgLcULCEiPAxKVh+76aflCmITc2xZHD8PIkv1hQ5fq51S1KH7CMf/2MygAMcQQQwwxxBBDDDHEEEMMMcQQ832M1OMCua0XYL7uInIF5AZAbmu9DqwicsMumMXuu2Ev78WcPsU+8vbzvw0xxBDzrUNVVTGpquoyKIChnALjBmDcoKob9I6hvjYtg9bXRlW9j1rfBgzlU+of/+T7uX40Yog5JWatj229l/Nd9L6+KbBeAKxvWq7q40318wpgljcFVpFyy6RfonezGwCA4h+0mP/5IIYYYr5/XA7ngvEv0VkAmRRQYL9g/qMubMx/bOUCJgVkWq523/q7yvS4bAIAT+XHc/1oxBBzKoxFBAuqp38fVVUXQO8lGFBb0qNqDQaWQcspEG+LAKEGDfDgghEBMcR0jDnmBaoVUMsG+NW62AHUm3VDzh8Aae0zL0AMMS+HKdn9KyAfjwvktr6p/bmgJgcAyMcylFyB3DxrMD3e1AwAgGkBpNYNRH7JtyGGGGK+cZTl3cTxuwDjl+j8vkGx7mJP+10wXyEKfIkClgmc379ssY9folh30WNq4Fw/GjHEnAqT8gJ6B2B1v5oXOLj7JWFQIgf4w784/huAUesFzxUwIiCGmN4xOf9X4321iN5XMkrqr6YJ6n+WJih2Y0oZw8FPaQWIIaZ/jFmB8siPZe8iIs/9qwuLvKBQ/9NaVSifV6oFgDsJtALEENM1JlcB4OWBO4Di5KfyQHH326ABvuzNPyifOrUOBq0AMcT0i3ErsNmatni/igZgnv6kHhG4ljgExVUlYJ9a/osY4lw/GjHEnAqTIoKk/EkGAKEfyobCFAEePpiGICUM4qAVIIaYfjGe8FPT+7SdQ/5aufmQCZzSis+GIrwCWgFiiOkd01QKRysA3Mu1wbN+NS+QBITuPVg0EbrDmkVMDgGtADHE9Itxvz0n9iPhVyUAZhmKUZjSI98MRX34R93ALAOtADHEdI7JCb9JD3n+zVOE8Kd9G/lH8cC9AvcFbA4BrQAxxHSNSXmBqAdELdBCBS8AjM06T1UAZAFS05hEK0AMMV1jki9gjr959S4YskwggJIhAHL4EP2DoR2E+RbUCxBDTO+Ypp7X6ACqV6++sEdPAvoSB6JuAORbXEhAX4AYYjrHZCuQPX2fOaAWDHjDkemLI5rIPkPqN1D6AsQQ8wKYY09htBSVqykdaI/81FOYzENcdSchGYpz/WjEEHMqTErumUNv67wKA7NGODUTaCoSen2hrQ8qIwJiiHkBTHbey2Fq4UOvYCz2lDXwC8mWRDMBqBcghpgXwHhEYJnAWNP5QR9NhFkHkFsHk6oY1lPI+QLEEPNCmHFDHS84bsB89deAdEE+tIoK80DCqCo8LtDPd00DCWuscc4fjRhiToFptYORE6yvmWTYpw+UUysKJF8gXIO4QF+AGGJeAJMqheU8RwQ+OgxAmkGSZEJ+tNlBewetADHEvBbGhUBls9FbHTpsxb9VBLPUvcpEroCVBlX1Uy6Qm6uLis/weNMfYP7HgxhiiPkXh2UHgaduQO8UiOkDVRwUuw+179B2JhF9AWKIeQFM0wMYGYJl8Ne2o0yomSUQbYdNU+IUkkNaAWKI6RuTrEAzKOBZSBA7DrjI2PYz1Gwt1FOE9W20AsQQ0zWm3Y+gmS2ioRhsVQIR+Uf7UIiIgFxkoBUghpjeMU1HUEruhX+fhwqmPoLUKuStiHlMMbKWmFaAGGL6xbQziFUbeXDeoDx6g+pr40FymBMGSXpAK0AMMZ1j2gFBzWtp4pgXBbyMYHNIzeePYQTpqtkDWgFiiOkYk/YsFoxbOZXpzysADCrTn4PriHdRrIBivULn9w0C7KKzDJtJkH/f7OqXAON+0Z/6bYghhph/cUQcj7T3QOT/2tFhGuLh1EnohcPFEoMeOTAiIIaY3jHNJPJR9TiH1HOHNlMsVwWfty5r8gehLKQVIIaYfjG5UhijRV0+kC3DaPYg9jaO3Yu9RmAbGuS+IloBYojpGJN3KPNkf0r9odUS+xHDCI5bHcc2prQCxBDzCphGNdSG+kk1NFoVIG1lGFMFtEkitCNIaQWIIaZ3TCsB8O7g0aL8O+CuARBqAo0sYpIIIjRFbQLxXD8aMcScCuN9BHY+aY7oo9vYWgdz51A9PIuoYS3KBfYUEkNM/5jnvEA848cwAC4vjLctdsEnFEfJIOuHaAWIIeYlMKUMWEYJvqnqw8cGjj6QEIB8WNOQ3EYbLzhfd5GPxwVlEAl8IGGZXvgLvg0xxBDznSNC+OYB7huMLTBfwBoLD23D4T2kIeR+gXkBYojpHfM0dxDwHYma15rcfzNe0C3Iob2YeQFiiHkJTN65POUJR/cPmiFEqslJCN2wzy8OTVEzkYBWgBhiOsakSmF4/3lqWHgK5vPbGELvGViAQ80QsS0RrQAxxHSOaRx/rwxEnt9FgPnhf+wdbrc5H7WdPEIrQAwxXWPankLknGDaZtDXftrQVF1nlCYNbE22cWE3ETHEvApGbv7I/7wCIu8bMOmX1OIfdkExCo8Lco1gGdQKgvWWsoPB53vNEPyKb0MMMcR86zBfYPAJYXmzgdQcCMAEhObzh1eQ5hfnGaasFBJDTP+YpucnVm2z9n9kGVQ1iomeCYwWw8V7EGgFiCGmb0yaMQiv8VV7EDoANXlwGjWcdEZ5c6M0eThtdXKuH40YYk6FyWOB0rTQ0WUBtpzT/CEfMBKtBjaXpNnTzG0ErQAxxHSMabz6BcgzQ0Z7xtf73AOw+7KmKJyEJk3AvAAxxPSOSVYgBEMW9McmhECzUUHOFeTJZBhSTiEmENIKEENMx5gfagdNCtxOIPQl7kNHbAaJdR6U06bLgFaAGGJ6xyQPPkKA0AibV29GwaePWobAcoe+dZldDRkirQAxxLwApsiEsIro5xXWIjxu0M/roHXmgKr9t+yiuux5lgCAMlAgDydZqBoihpj+MXmD8uTLj21ewFqFmr3J3T+w2uJBYUC9ADHEvAQmqYbyToRpiFgeLxg9RHm+QIoX1GyEX6AVIIaYzjFpykis3xgmYqLgZlfig2DINzFTbzhK3YXMDhJDTOeY495EeZOhBbCpAnlmiFUUYZG/VwXv/qnTklsMaQWIIaZ/zHFhY1D9vEYTYfX55YZd9L6KYH735/5DBPO7qnyUTzFbMl+ZHSSGmP4xSUEc2YA8diyifDcPMYmoHr6HEZoaQXkbfQFiiOkbc7QCNlG47Sl8jgjSSCHPLOZEo3sFtALEENM55skK+HSxaANopgwjNRNE72Hcl7c0X6gdJIaY/jF5vkC0EKQRYwgpYW4kst4C1SQ5LCs+hAScMkIMMS+Aea4RAIgOQcReJIf+gDtCXHDY5ywPK2dEQAwxvWNE//me/37M5/rRiCGGGGKIIYYYYoghhhhiiCHmJJi/AZe7huAZpY7zAAAAAElFTkSuQmCC", "acquirer_network_identifier": "VISI", "key_id": "7756cfcb-0d28-4e89-bbc0-d4ebdc5b6ca1", "id": "7aa184b7-c549-467b-917f-460b4224b459", "entity_customer_id": "0d93dea5-00c4-4a9e-b3fa-cbaf5280818b", "merchant": { "merchant_category_code": "1234", "country": "CO", "merchant_name": "Test Business O9F12", "merchant_city": "Bogota", "merchant_zip_code": "98273" }, "status": "ACTIVE", "type": "STATIC", "key": { "key_type": "EMAIL", "key_value": "jimmyjohns1111402545255@test.com" }, "channel": "MPOS", "additional_info": { "transaction_purpose": "SHOPPING" } }

The QR Code has been created successfully and can then use the returned id as a future reference to retrieve and delete as required. The qr_code_data field contains the encoded string that can be printed out as many times as the Merchant wishes, or use the qr_code_image which is in base64 for ease of use.

The Benefits of the Static QR Code are:

Data is fixed - the same key, channel, transaction_purpose and channel_presentation can be printed out and used multiple times over
The sticker can be included in a variety of places on the cart to make it easy for the Buyer to scan and interact with
There is no complicated integration with a Point of Sale system required to generate and receive Payments

Dynamic - Point of Sale

A Dynamic QR Code is generated for each sale and contains all the payment details needed. For example, a Point of Sale (POS) system creates the QR Code at checkout, which the Buyer scans to complete the payment.

This streamlines the process, no manual input is needed, and all required Bre-B payment details are included in the QR.

To use this, the POS system must be integrated with the Passport PaaS Platform to generate, retrieve, and delete QR Codes during the transaction.

Dynamic QR Codes are ideal for high-traffic environments like supermarkets with multiple self-checkouts. Passport provides the tools for Developers to manage these flows and offers Merchant Account options, giving them flexibility and control over the payment lifecycle.

Dynamic QR Code Request Example

The example below is for a Merchant who wants to accept BreB Payment using a Dynamic QR Code generated for a Point of Sale system. This QR Code will include additional information that the Buyer entered on a touchscreen at the checkout.

Parameter	Description
key_id	The unique identifier for the Bre-B key that was created in a previous step for the pre-requisite.
customer_id	The unique identifier of the merchant (Customer).
type	QR Code type: `DYNAMIC` in this case.
qr_code_ reference	A unique identifier that can be set so the sender will include on the inbound payment for the developer to track and identify payments with purchases.
channel	Channel used to present the QR Code. Use `POS` for fixed Point of Sale.
amount.value	The amount to be paid (e.g., `80000.57`).
amount.currency	Currency code (e.g., `COP`).
vat.vat_type	AType of VAT calculation (`FIXED` or `PERCENTAGE`).
vat.vat_value	Indicates the value or the percentage to calculate the VAT depending on what value has been set for the `vat_type` field.
vat.vat_base value	Indicates the VAT base value.
inc.inc_type	An indicator to capture how INC will be calculated for the transaction.
inc.inc_value	Indicates the value or the percentage to calculate the INC depending on what value has been set for the `inc_type` field.
additional_info. transaction_purpose	Submitted within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to SHOPPING.
additional_info. channel_presentation	Submitted within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel. In this example, it was a Merchant Point of Sale (6), that was used at the registered location of the business (0) and used a self attended checkout (1) therefore `601` is submitted.
additional_info. invoice_number	An automatically generated Invoice Number that can be used to track the Payment against the inbound Payment to ensure it can be reconciled by the accounting system.
additional_info. loyalty_label	The Buyer has entered their loyalty number at the Point of Sale, or perhaps it has been extracted after the Buyer has identified themself via Phone Number or Email address.
additional_info. terminal_label	A unique identifier for the terminal that has processed the Sale for the Merchant and Buyer so it can be tracked to the specific checkout point at the supermarket.

Dynamic QR Code Request Body

curl --location --request POST 'https://api.paas-sandbox.co.passportfintech.com/qrcodes' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer 27fb56c030a12d5cb302229531b4cc59d651996d0c3c0bb5933940ef25b42dbd' \ --data '{ "key_id": "e0363dd5-3e0e-4ade-b89a-d743c4bdad59", "customer_id": "19a0ab02-cbaa-4a7f-8ec3-6cc4224d30e7", "type": "DYNAMIC", "channel": "MPOS", "vat": { "vat_type": "FIXED", "vat_value": "11.00", "vat_base_value": "0.00" }, "inc": { "inc_type": "FIXED", "inc_value": "12.00" }, "tip": { "tip_type": "PERCENTAGE", "tip_percentage": "5.00" }, "amount": { "value": "80000.57", "currency": "COP" }, "qr_code_reference": "PAS1234512354520250929", "additional_info":{ "transaction_purpose": "PURCHASE", "channel_presentation": "601" } }'

Dynamic QR Code Response Example

Once the request is submitted, the Passport PaaS Platform combines information from the various sources in order to create the compliant QR Code according to the Colombian EASPBV Industry Specification for QR Codes. The response is provided back in a similar format as other Resources.

Parameter	Description
qr_code_id	Unique identifier of the QR Code. Used to retrieve or delete it later.
qr_code data	The formatted string for the QR Code that contains the data which can be presented via a digital channel or converted and printed out.
qr_code_image	The QR code image encoded in Base64.
key	An object to represent the `key_value` and `key_type` that was used for creating the QR Code which is also referenced by the `key_id.`
acquirer_network identifier	QR Codes will always be issued by VISI who are an authorised issuer by Banco de la República for Bre-B keys.
merchant	An object representing the information relating to the Merchant itself - the name, city, zip code, country and category code.
status	The status of the QR Code to ensure that it has been created successfully.
created_at	A timestamp capturing when the QR Code was created successfully.
key_id	The unique id for the Bre-B Key that was created in a previous step for the pre-requisite.
customer_id	The unique id for the Customer that was created in a previous step for the pre-requisite.
type	Type of QR Code (`DYNAMIC`).
channel	Channel used to present the QR (`POS` for Point of Sale).
amount.value	Payment amount (e.g., `80000.57`).
amount.currency	Currency (e.g., `COP`).
qr_code_ reference	A unique identifier that can be set so the sender will include on the inbound payment for the developer to track and identify payments with purchases.
vat.vat_type	An indicator to capture how VAT will be calculated for the transaction.
vat.vat_value	Indicates the value or the percentage to calculate the VAT depending on what value has been set for the `vat_type` field.
vat.vat_base value	Indicates the VAT base value.
inc.inc_type	An indicator to capture how INC will be calculated for the transaction.
inc.inc_value	Indicates the value or the percentage to calculate the INC depending on what value has been set for the `inc_type` field.
additional_info. transaction_purpose	Submitted within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to SHOPPING.
additional_info. channel_presentation	Submitted within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel. In this example, it was a Merchant Point of Sale (4), that was used at the registered location of the business (0) and the cashier was not present (1) therefore `401` is submitted.
additional_info. invoice_number	An automatically generated Invoice Number that can be used to track the Payment against the inbound Payment to ensure it can be reconciled by the accounting system.
additional_info. loyalty_label	The Buyer has entered their loyalty number at the Point of Sale, or perhaps it has been extracted after the Buyer has identified themself via Phone Number or Email address.
additional_info. terminal_label	A unique identifier for the terminal that has processed the Sale for the Merchant and Buyer so it can be tracked to the specific checkout point at the supermarket.

Dynamic QR Code Response Body

{ "tip": { "tip_type": "PERCENTAGE", "tip_percentage": "5.00" }, "status": "ACTIVE", "channel": "MPOS", "customer_id": "19a0ab02-cbaa-4a7f-8ec3-6cc4224d30e7", "created_at": "2025-05-28T14:20:51.457775Z", "qr_code_id": "52e7fcbc-4527-4e24-a604-a9501ea9bbe9", "inc": { "inc_value": "12.00", "inc_type": "FIXED" }, "additional_info": { "transaction_purpose": "PURCHASE", "channel_presentation": "601" }, "amount": { "value": "80000.57", "currency": "COP" }, "qr_code_reference": "PAS1234512354520250929", "key_id": "e0363dd5-3e0e-4ade-b89a-d743c4bdad59", "acquirer_network_identifier": "VISI", "vat": { "vat_type": "FIXED", "vat_value": "11.00", "vat_base_value": "0.00" }, "key": { "key_type": "ALPHA", "key_value": "@A2IEN44GW553GCN" }, "qr_code_image": "iVBORw0KGgoAAAANSUhEUgAAAwIAAAMCAQAAAADyx0wVAAAJc0lEQVR4nO2dT46jSgzGPz8iZVlIc4AcBW7W6iPNDeAofYCWYNkSyG9RVbaLHmkWbwZeoo9Fq0kgPwXJ8X9bFH/3mP/5ywCABBJIIIEEEkgggQQSSCCBBBKuIUg5bvW/fi+nI3YBsIuMq4hIDwDYBVhvkHEVwSwiwFr+lOtERMZTvwMJJJAQCIOqqi6AqqrW174EQKeY5a5A2oBh2UWk71Sk30XfH6pAUsXcAyIPVZ3QafiUV3pKJJDwBIQixMMCYFiqNA4LoJpfK5eo6gad0pbf0An+7pbvLR+wdAqg0/xDMb3CUyKBhOcliIgIkFRlRKeYH6oAdsHcF1mVManKmDa7qVOd0pcAaYOMvyH8+YMEEkjw43Z8Yfj5YxNgz2+o/YfynwCzAIr1rjL33SZIn7dsaM/SbcfPe4mnRAIJz0Ootnf2p4v9DKDL7nV2lgfdqomd/eQuON/FFE8biivtFjxtbxJIuIowiwe1kf1kGdEpho8bgPWuMq53BdZbeFfG9Vb+e/u4q7zlN3YpFvy534EEEkhAtb1jgWj6kvLaCmB+bFCse5XQtOU/+bW5R3kjX4cvAVJbbvoKT4kEEp6HEGzvEvyuJnaT1Spx73KkYorrlKo9bvfmgHgx2Wl7k0DC2QQcRDenp6Yc1K5u8xTc6+14GuU3lfy0/yhQpkkg4VyCJZ+1hseSapHpVLPSHi3zkNlUryvRsnxvjaWhFp5Qpkkg4VxCkOlgThf5tWj3gmKAW2Qbuapk6YpgFxUNk2m74xWeEgkkPA/B6shqFmpCkct6agoXQBTi/IY71Z7pAkKmizJNAgmnEhAEtlR0IxjWRYizi7xZFKxT191FqQNBpqNmf4WnRAIJz0OoMp226hOjyHQwticAxdEGik72I8fDGh1fq1Qo0ySQcDYh9nAUB1o1dmilWEKWpXYCULVzF0NrWiW5nlKmSSDhbEIjgwsQpREITnVjdjd/AESJL+1c7MsigYRLCIjya02TgP1pgt8lKAbrtfTIWKqRNstPU6ZJIOECgtWRuTgjRMayZw3LVrllboUnQb2XO0r5KGWaBBIuIJR677n/RKnjxn7D3HeQQXfJp8PPe3a5BSjF4fVdQIZpy58iwC4YFqgEwis8JRJIeB6C1YZ2IQvlVWFNEyaC21yta1PHdURCzV6DepoEEq4ghFyWF37mIzrQ3TEDXU121ZDMNg88jDyiTJNAwiWE9QadVglGc9a1ebxgPdWpWNcQ6fc4LfQte+C7ZB/7/aEq48nfgQQSSMCv8tMe4tpq9clSL56ANjTeGOpI3mvJGBkJJFxCaHo4LKmsNgDUDfAyk6i6zeHdOqzIg+SsDSWBhKsIMZeF5H2Vsbb7EPaqmS7PbVs3h/VqsYeDBBIuIlgxqPdluYQCtZYkThEsdraVpQzenGUaOxeTUaZJIOF0QjM3tCrhqLa/l3of2rQAr00BcCwdp0yTQMKpBERJXqzzeYGlptHa4760A3DBjqOM0NaAv8JTIoGE5yE0u3XU7WzzkxcgusheNBqscDSlKkGLU6ZJIOFsQutPw+xsa8ZYAG+drhFwIJriKfZ1KPunSSDhSoIvzhFF2m6KtQcGBYD0KQC6DXmtTlogSJ/APAIYlh8bhqWHDB93BdLnrVy89id/BxJIICEcwZ/OR4rRstA56X6y3+s2+mQfBQC0vUkg4SpCWEQbks9+lClGlnxWT2Y3LZpha237KZRpEki4gjDLDXkZ1vzYkPdgSb+LjKvtywLKJQCguuxSbsMumB82o2xtd2W+0FMigYSnIcjbApQo9iqC+fElPolI3x8bMCy71EvuKiL3ot4tglbW5KUNmPtdZDz1O5BAAgkA4ijBfGTfuVaQlIGitSwl3OflJsVG9xUcAG1vEki4ihAGhcYiTxNOmwfqYbRmFNnWZqVVY26bMk0CCacTbCaCfo9xJ9e/LqbNtN8JMXAeS8Ip0ySQcA3hWx2Zr6oMPdBVQsNKWlur09SAxyA5ZZoEEi4gNKP5Fx8UGhVzncpvDvRyGPINeH4rDhSlTJNAwumEdh6ZN1HHruk47KTG0mo8zEaAL/XzfITwQJkmgYTTCe0ejoPWdRM76u5Qc1I+oNkzb3Uo1NMkkHABoZ1zohbd2qxfw/zkqrvjdvmlWTidD1PvlGkSSLiKoNN611wBNuhXHR663gCkcqrvPYBsbK8ipY6sj2PBm6pxk/PXeUokkPAMhHZ9pdagmMZEVdiZYxq79FmHvo4u6G7ODSWBhKsIzXLaQxN1igVmPkDQM11uo3ta2z1w2t4kkHABIcwCPoS98hET0q67v88os1+Gcht7LUkg4RpCI6s15dxExqxNuq0oO84u8nbMxaaaUaZJIOF0wi8GGcQ67sOcIs95eX6rJq98HpldR5kmgYTTCd/mhobRJSnmqFyVu6FelbVqmO/t2/Boe5NAwvmEY18WUCcRxXH9MB871dB40MSwnswFOC6gp0yTQMKphLaOzH1nO62+s59WYW+LvrXZc8tcFgkkXEQIO+VrWbeZ04gR8No1XfR0XIlXFbOPTYih8Vd4SiSQ8DyEoKfDi1kaUxMy8zYPX2JrbdKuu4PZTdubBBLOJzQzEVKtJXET29qpG6fahL1V1l4mPoG5LBJIuIQQZiLEyHY7jigsonWlnhrtXBLS3p1J25sEEi4hNDP7szpu258BBMvcPOZgntsw/8NyLco0CSRcQGj3cBxKyJp9WVqHndSo2mE31hbTYtxVSwIJFxHa/dO2VcPGHEwAQjFKMNTboJip96qs6U+TQMK1BNu5AQBzD8ibD+kHgOFD8lHOVynvDh8iGJYy+V+kBwB0dXPHSz0lEkj43xNCX1bU2G6Km2I2FzleUqPd+Ga3g/40CSRcRygaWOKmK9U88WSXHArLG7HWGzCLiIxZRd8gY42RifS7lEtsAMoLPSUSSHgiwlCjW/ouIi6cMvqltgzLS0DnvlN97+Ni+XLJYp1cL/SUSCDhCQjNzH7PSi9W5e1DTH7RpmU56zh8sPlk2t4kkHAtQaf0JT5ZEFhvtRjl436cQlbWYa4i8rZ0iuFDxH8jZPwl4c8fJJBAQjgOeromnz3i5eWe36aVhUyXjy3yalLqaRJIOJ/Q5KdrWaiGOYH+2oIg2J6GLmUp9VegeNasOSGBhGsIcXZRcKXbms/Dvsp2FIq3XftQBeaySCDhKoLo76/5T8f8Ck+JBBJIIIEEEkgggQQSSCCBBBLa419DhUlan3DsRwAAAABJRU5ErkJggg==", "type": "DYNAMIC", "merchant": { "country": "CO", "merchant_name": "Passport zqEkYq", "merchant_city": "Bogota", "merchant_zip_code": "98273", "merchant_category_code": "1234" }, "qr_code_data": "00020101021226390015CO.COM.VISI.LLA0416@A2IEN44GW553GCN49270015CO.COM.VISI.RED0104VISI52045782530317054130000640000.0055020357045.005802CO5915Passport zqEkYq6006Bogota61059827362190808PURCHASE110360180290017CO.COM.VISI.CANAL0104MPOS81260016CO.COM.VISI.CIVA01020282280015CO.COM.VISI.IVA010511.0083280016CO.COM.VISI.BASE01040.0084260016CO.COM.VISI.CINC01020285280015CO.COM.VISI.INC010512.0090610017CO.COM.VISI.TRXID0136800F9050-CE3E-4759-90AE-085FAB68107D630485F9" }

Developer Notes

A 200 OK response confirms the QR Code was successfully created.
Use the id to manage the QR Code lifecycle (retrieve, delete).
Use libraries in React, Angular, iOS (Swift), or Android (Kotlin) to convert the qr_code_data qr_code_image (base64) string into an image.
Dynamic QR Codes are flexible and transaction-specific, making them ideal for high-volume environments such as retail, restaurants, and supermarkets.

The Benefits of the Dynamic QR Code are:

Data is flexible - each time a QR Code is generated, a different key, channel, transaction_purpose and channel_presentation can be combined with optional fields provided via the REST APIs
QR Codes are programmable for each transaction and are uniquely generated for each transaction via the integration with the Point of Sale system for the Merchant
The outcome is that they support more scalable volume of transactions and can apply to a wider variety of retailers such as restaurants, sports centers, supermarkets, retailers, or any sophisticated seller

Dynamic - ATM

A Dynamic QR Code contains variable Payment information and is created on demand to suit the specific transaction or sale that is currently being completed at the time.

In this example, an ATM system operator is allowing an Individual to withdraw cash from an ATM by using a QR Code to initiate a Bre-B Payment prior to dispensing the withdrawal. This ensures that all the required information for the ATM is presented to the individual, and simplifies the experience as no reference numbers or location information needs to be manually linked from the ATM.

The downside to this is that it does require integration between the ATM system and the PaaS Platform so that the QR Codes can be created on demand for each withdrawal or deposit, as well as retrieved and deleted as required over the cash lifecycle.

The Dynamic QR Code is suited for this environment as it can be expected that the ATM operator has multiple locations throughout the country, perhaps at dedicated locations, or in shops, and therefore will have multiple transactions happening at any given time of the day.

Passport provides the infrastructure to allow Developers to be in the flow of funds, or provide dedicated Merchant Accounts with oversight of the transactions so Developers can chose each method to implement while maintaining oversight and control to confirm the Payment lifecycle.

Dynamic QR Code Request Example

The example below could be used for an ATM Operator wishing to link Bre-B Payment via a Dynamic QR Code to ensure the transfer is received before dispensing any cash to an individual.

Parameter	Description
key_id	The unique identifier for the Bre-B key that was created in a previous step for the pre-requisite.
customer_id	The unique identifier of the merchant (Customer).
type	QR Code type: `DYNAMIC` in this case.
channel	States how the QR Code has been presented by the Merchant to the Buyer - in this example, the Developer would chose ATM for an Automated Teller Machine.
amount.value	`40000.00`as a string representation to two decimal digits to represent centavos
amount.currency	COP as a string will always be used for the currency
qr_code_reference	A unique identifier that can be set so the sender will include on the inbound payment for the developer to track and identify payments with purchases.
vat.vat_type	An indicator to capture how VAT will be calculated for the transaction.
vat.vat_value	Indicates the value or the percentage to calculate the VAT depending on what value has been set for the `vat_type` field.
vat.vat_base value	Indicates the VAT base value.
inc.inc_type	An indicator to capture how INC will be calculated for the transaction.
inc.inc_value	Indicates the value or the percentage to calculate the INC depending on what value has been set for the `inc_type` field.
additional_info. transaction_purpose	Submitted within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to RETREAT.
additional_info. channel_presentation	Submitted within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel. In this example, it was a Screen - Other (7), that was not used at the registered location of the business (1) and it was at a self attended box (2) therefore `712` is submitted.
additional_info. store_label	A unique identifier that can be set for the location of where the ATM is located if it is in a convenience store or a petrol station for example
additional_info. terminal_label	A unique identifier for the terminal that has processed the Sale for the Merchant and Buyer so it can be tracked to the specific machine in Colombia.

Dynamic QR Code Request Body

curl --location --request POST 'https://api.paas-sandbox.co.passportfintech.com/qrcodes' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer 27fb56c030a12d5cb302229531b4cc59d651996d0c3c0bb5933940ef25b42dbd' \ --data '{ "key_id": "e0363dd5-3e0e-4ade-b89a-d743c4bdad59", "customer_id": "19a0ab02-cbaa-4a7f-8ec3-6cc4224d30e7", "type": "DYNAMIC", "channel": "ATM", "vat": { "vat_type": "FIXED", "vat_value": "0.00", "vat_base_value": "0.00" }, "inc": { "inc_type": "FIXED", "inc_value": "0.00" }, "qr_code_reference": "PAS2025092912345adsf", "amount": { "value": "40000.00", "currency": "COP" }, "additional_info":{ "transaction_purpose": "WITHDRAWAL", "channel_presentation": "712" } }'

Dynamic QR Code Response Example

Parameter	Description
id	The unique id for the QR Code that was created from the POST request that can be used for future retrieval and deletion requests.
qr_code_data	The formatted string for the QR Code that contains the data which can be presented via a digital channel or converted and printed out.
key	An object to represent the `key_value` and `key_type` that was used for creating the QR Code which is also referenced by the key_id
acquirer_network identifier	QR Codes will always be issued by VISI who are an authorised issuer by Banco de la República for Bre-B keys.
merchant	An object representing the information relating to the Merchant itself - the name, city, zip code, country and category code.
status	The status of the QR Code to ensure that it has been created successfully.
created_at	A timestamp capturing when the QR Code was created successfully.
key_id	The unique id for the Bre-B Key that was created in a previous step for the pre-requisite.
customer_id	The unique id for the Customer that was created in a previous step for the pre-requisite.
type	Whether the developer would like to create a STATIC or DYNAMIC QR code - in this example, the Developer would chose DYNAMIC.
channel	States how the QR Code has been presented by the Merchant to the Buyer - in this example, the Developer would chose ATM for an Automated Teller Machine.
amount.value	120000.00 as a string representation to two decimal digits to represent centavos
amount.currency	COP as a string will always be used for the currency
qr_code_reference	A unique identifier that can be set so the sender will include on the inbound payment for the developer to track and identify payments with purchases.
vat.vat_type	An indicator to capture how VAT will be calculated for the transaction.
vat.vat_value	Indicates the value or the percentage to calculate the VAT depending on what value has been set for the `vat_type` field.
vat.vat_base_value	Indicates the VAT base value.
inc.inc_type	An indicator to capture how INC will be calculated for the transaction.
inc.inc_value	Indicates the value or the percentage to calculate the INC depending on what value has been set for the `inc_type` field.
additional_info.transaction_purpose	Submitted within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to `WITHDRAWL`.
additional_info.channel_presentation	Submitted within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel.
additional_info.store_label	A unique identifier that can be set for the location of where the ATM is located if it is in a convenience store or a petrol station for example.
additional_info.terminal_label	A unique identifier for the terminal that has processed the Sale for the Merchant and Buyer so it can be tracked to the specific machine in Colombia.

Dynamic QR Code Response Body

{ "inc": { "inc_type": "FIXED", "inc_value": "0.00" }, "amount": { "value": "40000", "currency": "COP" }, "additional_info": { "transaction_purpose": "WITHDRAWAL", "channel_presentation": "712" }, "status": "ACTIVE", "type": "DYNAMIC", "qr_code_data": "00020101021226390015CO.COM.VISI.LLA0416@A2IEN44GW553GCN49270015CO.COM.VISI.RED0104VISI52045782530317054130000040000.005802CO5915Passport zqEkYq6006Bogota61059827362210810WITHDRAWAL110371280280017CO.COM.VISI.CANAL0103ATM81260016CO.COM.VISI.CIVA01020282270015CO.COM.VISI.IVA01040.0083280016CO.COM.VISI.BASE01040.0084260016CO.COM.VISI.CINC01020285270015CO.COM.VISI.INC01040.0090610017CO.COM.VISI.TRXID013608B7F5FB-22AE-4CE6-BE36-CDE8C674D16263044D66", "acquirer_network_identifier": "VISI", "qr_code_image": "iVBORw0KGgoAAAANSUhEUgAAAwIAAAMCAQAAAADyx0wVAAAJG0lEQVR4nO2dTYrjSBCFX4wEtZRhDtBHkW8wRyrqSH0D6Sh1gIb00iATs8iMn5QbZjHdUpd5WhiXJfmjBOHI+Hspit97rH/9ZgBAAgkkkEACCSSQQAIJJJBAAgnnEKQdI7DKCAAPqe/WC1BP4DZC5PIQueIhIpeHALcRwE1ErgDkehOpLyLts1d6SiSQ8BUIUFVVzKqqWgbFrBsADIq5ALpMG4BJaypNFwztnRZAF8TLoO0o7V390uUVnhIJJHwdgtl0ATCXQauFunEC09YMdgFQrbteN6lWE5/LoADaS7sNA22aBBL+DMK0QeQCYP12F8yfbypXc9bV4j8uj7bEfte7VGOf9S66TBvk+p+EX32QQAIJcYy7vwV4U6nvbyN0/XYXXa8CbWcFmMvfm2D6MWK9FJX5+0OwSr1jeyK8wlMigYSvQ9jH022dPW1Q1a1bmesGzGqRtaq26+KOxdbejKdJIOEsQrPadlh0/P9e7Nto0ySQcDzB8mFxlEFVi52uyW8M2tJj1f9ulu2e2lq7pdbK8PR1tGkSSDiU4Kvr5mY7u9zaituT3/WW8MlAW61buWvIZk+bJoGE4wnJT1tmu0XHqOWpqdl0NtOpWW0Kwz3uToVr2jQJJJxFkOutdYph1rtg/hyRA+MyaO0ju+IhQH1pR+0oWy+AflyGWviS66Qq10P/BxJIIAGAe1OgT2pvuTVssc+a2+5aUJpjnrbmout1oJ8mgYRzCc0TA5OqyKUtu+UK5M+qx57uIlcPr9fLoPJezEWLvLXl+eH/AwkkkND1gc6dx7buT6AF2v7SPLY58AVwF63WIMocGQkknENIa+/c6l1TZpsF1V1DSct7W0Er93v7HXP8RrzCUyKBhK9DQNhvZLvNd3tkPXlXmF1nL3mkI34A4ptp0ySQcCzBe0PDw/rkZAEsCxaeWPP41axelS7eUlryWdo0CSQcS+j9dHbHeaa6oJ2NyNpdedwb3SesT5NAwlkED6A9Oo7weoo+UOvjjsYTTSMdTz1o1kxGmyaBhKMJ2aarX7XFdrLzugDvst3Ni2sXhrfUuCmj0KZJIOF4QleAKkCUrHLeG2g+ebYJj+anC7KzjjEP6pyQQMJJhH2/d5qX9PENq2UBkQqL5vB6ttp5QR7Yok2TQMLxBHTmnJtHIgsWq/DoF633et7s6ffAp7to0ySQcCgh5b2furc1JixDycRuS87aoujU9J1S6K/wlEgg4esQuvHJyF2XrnBdj30zWfusHp7obqlx1qdJIOEcQur3TsnvXorMhMpiZR4eOwsj2G0b42kSSDiNkNxx7SCJZrKW2bYaVT0bg5TeLgYA0QNuo1uc4SCBhFMIXY4s1s/Fq1r1quEnrWbNn8efyeKj1Yw2TQIJhxJSfTp/Zkvx9NkC5IK0V6qRdt+Y3LOzPk0CCecQcn16Duu2pTNiGtpr0dmLW8o7Ws2Slij9NAkkHE/Y93tb2NylvOcu7RXuOMakc7Y7YmzaNAkkHE7o9chyu+dTyRlWuF4A7H1yKoal7DltmgQSjiZ0PSdAVihp7Z4meBCXZE2TCKVj8Y5UrqZNk0DCsYS08VVKeWeN7lD6ziG3/RT0sXi3PKefJoGE0whJ39uHNuS9AHLF4MHyQ9olAOQKIP7EKiMwf77p0yWv85RIIOHrENICfL0MprYPQD9Eqj5/M/vJduT4kBEAmlx/lfpfv93lSQL8dZ4SCSR8BUJeewPwFjJfj5eseNIO6z5R10l42tKSc1kkkHAOIet7J1stLiwW01h+Iu9r6cZuDrx+6cJ4mgQSziHU2Fcw3UVxe1PgJgCmuwC3cZO5PABMP0YFAJm/+51TgWB6jMDtAgCDCgDo+s+PUeZPC7Rf4imRQMLXIez3y0pTkp7P3u+XFfnxdlvsetmp/NNPk0DC8YS0/3Qsp82cbXLS61bw3u4w56hj70asadMkkHACwWctNQXQWYoMyK53sVnpyIx1vwL9thy0aRJIOJzQzXAU+zBETHxbDriM934zjj551q5Trr1JIOEUQlb19i2wctraC9ILvOkbverB1PWR1YN+mgQSziF4jsxD5AKPk30io0SOLGrRIYDSbZDl8TltmgQSTiDkvWrVfO1O/yCJGqWN8KacHuu8vdpPAW2aBBIOJ+x1Q+Hh8G5HnRAqS3F3CqVd9iTPVNOmSSDhaEK39nbBktDiDzkE/zPVolu2rJuuzjNdtGkSSDia4BJFSKH0btmtapYcfdxI85cWT4edU4+MBBLOIvT1aVMGTUG1aqpWhXWbWEJXxwZC8QTULiKBhDMIT7qhSRk0YuKQKPJo2wvX7SjWTBa5NNo0CSQcT+g0+9VrzLvAeNdpolHHtpx5vU6zo6dNk0DCCYSUI0s7UrZkV85nZ43BSXOO2xvMQu7bcmm0aRJIOJqQcmQWLPdbwntCPGXAEbqD9nvgG2PmijZtmgQSDif8NO+dWsh8iQ2386QWmicsbbDL1/K0aRJIOIGwz3snZdDFr/HJja60ldPbsf+l+XP2nJBAwqmE2wjMn2MTAK06JzGIhYegSZc0BUL9uDzaJauI6MfFEufrBZB36pyQQMI5hNzvvStZpeS358L7+a32FR5Ke0WMemQkkHAWIemcIPbXqIcXqvb9YaVLigFWqU7tJgWMp0kg4UxC9at30cVl+OcCyHXaIHIZVBc8RN6LCXr7JaaE8JD2MvUB+Ss9JRJI+PMJXZ46VId8OLovXNtNQzqRfPe8T6HTT5NAwtGEvAWleio7SQlOXYOo17IAK1wn9f5Ig1M3lAQSTiLk+nSuYHmyy0+kxrF9a8mWK2JpY0zaNAkkHE5I1tjNS27ICgcFyNLe7old8sgS3f3umLRpEkg4nOB5b+ydMNLqum9BybInIWVki/d2UN+bBBL+CIIutxG64CGY9V63tGzvrLRVj/XbVhtPdLlJfWk7XBbAmlZ+Rvj1BwkkkJCOJz+Ntqf8fuONHDtvuV90AbrhDthXMe9NAgnHE57j6dLls131IO/NMW2p6ax+i2fF2wLcluK0aRJIOJawz3tHsJx232g7ckS2LFRQttRCll00/TQJJJxDEP3va/7Xsb7CUyKBBBJIIIEEEkgggQQSSCCBhP74F8qn1nvaPhKiAAAAAElFTkSuQmCC", "qr_code_id": "5576c7f0-0761-49dc-b2ae-cf64e6106d07", "key_id": "e0363dd5-3e0e-4ade-b89a-d743c4bdad59", "created_at": "2025-05-28T14:20:46.531062Z", "channel": "ATM", "key": { "key_value": "@A2IEN44GW553GCN", "key_type": "ALPHA" }, "vat": { "vat_base_value": "0.00", "vat_type": "FIXED", "vat_value": "0.00" }, "merchant": { "country": "CO", "merchant_name": "Passport zqEkYq", "merchant_city": "Bogota", "merchant_zip_code": "98273", "merchant_category_code": "1234" }, "qr_code_reference": "PAS2025092912345adsf", "customer_id": "19a0ab02-cbaa-4a7f-8ec3-6cc4224d30e7" }

As with the Static QR Code example, the 201 Created HTTP Status indicates that the QR Code has been created successfully and the Developer can use the returned id as a reference to retrieve and delete as required.

The qr_code_data field contains the encoded string that can be retrieved and presented in the desired format in the ATM. Libraries exist for many frontend programming languages such as Javascript, React, Angular, Android (Kotlin) and iOS (Swift) that convert the text into an image that can then be presented to the individual to scan with their mobile banking application.

To facilitate the endpoint also returns the image in base64 within the qr_image_data parameter.

Benefits of the Dynamic QR Code are:

Data is flexible - each time a QR Code is generated, a different key, channel, transaction_purpose and channel_presentation can be combined with optional fields provided via the REST APIs
QR Codes are programmable for each transaction and are uniquely generated for each transaction via the integration with the ATM infrastructure of the ATM operator
The outcome is that they support more scalable volume of transactions and can then control each withdrawal wherever the machine is in Colombia.

Dynamic - Online Shopping

A Dynamic QR Code contains variable Payment information and is created on demand to suit the specific transaction or sale that is currently being completed at the time.

In this example, an online ecommerce platform can create a QR Code to allow a shopper to scan it from their computer screen to pay for a purchase and complete the checkout process.

The Dynamic QR Code is suited for this environment as it can be expected that the website operator can take multiple orders at any given time at any time of the day and would like 24/7 operations for their payment systems while giving their shoppers the most convenient means to pay for goods.

Dynamic QR Code Request Example

The example below could be used for an ecommerce website wishing to offer shoppers the option to pay for goods online. The website operator will connect to the PaaS Platform to create Dynamic QR Codes for each shopper to scan at the checkout and link to their order.

Parameter	Description
key_id	The unique identifier for the Bre-B key that was created in a previous step for the pre-requisite.
customer_id	The unique identifier of the merchant (Customer).
type	QR Code type: `DYNAMIC` in this case.
channel	States how the QR Code has been presented by the Merchant to the Buyer - in this example, the Developer would chose `ECOMM` for an ecommerce website.
amount.value	The amount to be paid (e.g., `200000.00`).
amount.currency	COP
qr_code_ reference	A unique identifier that can be set so the sender will include on the inbound payment for the developer to track and identify payments with purchases.
vat.vat_type	An indicator to capture how VAT will be calculated for the transaction.
vat.vat_value	Indicates the value or the percentage to calculate the VAT depending on what value has been set for the `vat_type` field.
vat.vat_base value	Indicates the VAT base value.
inc.inc_type	An indicator to capture how INC will be calculated for the transaction.
inc.inc_value	Indicates the value or the percentage to calculate the INC depending on what value has been set for the `inc_type` field.
additional_info. transaction_purpose	Submitted within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to SHOPPING.
additional_info. channel_presentation	Submitted within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel. In this example, it was a Screen - Website (5), that was used as remote commerce (2) and it was at a self attended checkout (1) therefore `521` is submitted.
additional_info. invoice_number	A unique identifier that has been created by the ecommerce website to link the checkout to the QR Code
additional_info. customer_label	A unique identifier that has been created by the ecommerce website for the shopper from their CRM to link to the QR Code

Dynamic QR Code Request Body

curl --location --request POST 'https://api.paas-sandbox.co.passportfintech.com/qrcodes' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer 27fb56c030a12d5cb302229531b4cc59d651996d0c3c0bb5933940ef25b42dbd' \ --data '{ "key_id": "0fb7e5fa-e26f-4195-a94e-ec054e767ac8", "customer_id": "19a0ab02-cbaa-4a7f-8ec3-6cc4224d30e7", "type": "DYNAMIC", "channel": "ECOMM", "vat": { "vat_type": "FIXED", "vat_value": "100.00", "vat_base_value": "100.00" }, "inc": { "inc_type": "FIXED", "inc_value": "10.00" }, "amount": { "value": "200000.00", "currency": "COP" }, "qr_code_reference": "PAS202509291038dn2137d", "additional_info":{ "transaction_purpose": "PURCHASE", "loyalty_label": "124567938", "channel_presentation": "521" } }'

Dynamic QR Code Response Example

Parameter	Description
qr_code_id	The unique id for the QR Code that was created from the POST request that can be used for future retrieval and deletion requests.
qr_code data	The formatted string for the QR Code that contains the data which can be presented via a digital channel or converted and printed out.
key	An object to represent the `key_value` and `key_type` that was used for creating the QR Code which is also referenced by the key_id
acquirer_network_identifier	QR Codes will always be issued by VISI who are an authorised issuer by Banco de la República for Bre-B keys.
merchant	An object representing the information relating to the Merchant itself - the name, city, zip code, country and category code.
status	The status of the QR Code to ensure that it has been created successfully.
created_at	A timestamp capturing when the QR Code was created successfully.
key_id	The unique id for the Bre-B Key that was created in a previous step for the pre-requisite.
customer_id	The unique id for the Customer that was created in a previous step for the pre-requisite.
type	Whether the developer would like to create a STATIC or DYNAMIC QR code - in this example, the Developer would chose DYNAMIC.
channel	States how the QR Code has been presented by the Merchant to the Buyer - in this example, the Developer would chose ATM for an Automated Teller Machine.
amount.value	200000.00
amount.currency	COP
qr_code_reference	A unique identifier that can be set so the sender will include on the inbound payment for the developer to track and identify payments with purchases.
vat.vat_type	An indicator to capture how VAT will be calculated for the transaction.
vat.vat_value	Indicates the value or the percentage to calculate the VAT depending on what value has been set for the `vat_type` field.
vat.vat_base value	Indicates the VAT base value.
inc.inc_type	An indicator to capture how INC will be calculated for the transaction.
inc.inc_value	Indicates the value or the percentage to calculate the INC depending on what value has been set for the `inc_type` field.
additional_info.transaction_purpose	Submitted within the `additional_info` object, but specifies what the transaction purpose is, in this example it will be set to SHOPPING.
additional_info.channel_presentation	Submitted within the `additional_info` object as an optional three digit code that represents the medium used to provide more detail to the channel. In this example, it was a Screen - Website (5), that was used as remote commerce (2) and it was at a self attended checkout (1) therefore `521` is submitted.
additional_info.store_label	A unique identifier that can be set for the location of where the ATM is located if it is in a convenience store or a petrol station for example.
additional_info.terminal_label	A unique identifier for the terminal that has processed the Sale for the Merchant and Buyer so it can be tracked to the specific machine in Colombia.

Dynamic QR Code Response Body

{ "inc": { "inc_type": "FIXED", "inc_value": "10.00" }, "amount": { "value": "200000", "currency": "COP" }, "additional_info": { "transaction_purpose": "PURCHASE", "loyalty_label": "124567938", "channel_presentation": "521" }, "qr_code_reference": "PAS202509291038dn2137d", "status": "ACTIVE", "type": "DYNAMIC", "qr_code_data": "00020101021226330015CO.COM.VISI.LLA0210353250300149270015CO.COM.VISI.RED0104VISI52045782530317054130000200000.005802CO5915Passport zqEkYq6006Bogota61059827362320808PURCHASE0409124567938110352180300017CO.COM.VISI.CANAL0105ECOMM81260016CO.COM.VISI.CIVA01020282290015CO.COM.VISI.IVA0106100.0083300016CO.COM.VISI.BASE0106100.0084260016CO.COM.VISI.CINC01020285280015CO.COM.VISI.INC010510.0090610017CO.COM.VISI.TRXID0136240E0CBF-294B-4C30-9684-9313605D714C63042088", "acquirer_network_identifier": "VISI", "qr_code_image": "iVBORw0KGgoAAAANSUhEUgAAAwIAAAMCAQAAAADyx0wVAAAJAElEQVR4nO2dzY3jSAyFH9cC+ihn4FCkDCakwYS0GUihdAANyEcDMriHKv6UPMAcdkc13ft0MGzL0gcboFkkH1mi+L3H+tdvBgAkkEACCSSQQAIJJJBAAgkkkNCHIPUYgFUGYL0CwF0E6/VZHmS+1xMy3wfIjKeIXJ/lsvpSRGS+293mU78DCSSQAABQVVVMqqq6XbS+t11Ul1EV03ZRYNyhy7jbNX5i0h2qukMXXLQeW31Wbrp8hV+JBBI+D8FsegMwbRfVBSgWCow7qjnjkq27WDwuCviJabO/gvrPcKFNk0DCn0EYVeW7PkR1C+t+CNbbDl0AYL3tkHncoaoPqe9d/cQvCf/1QQIJJMQxHF4LMOxY5aJSXo6AAG8q09/DLsAAmd6HHbgPu2DcVMpV48dQT5z+HUgggYRXwqh12a1azbLG0+8DVLenAHgKJlXFetsB4Cm64Cm24gZs3Z7v8rV+JRJI+DSEVURErjWpjWkD5Pt7deIye+yM+wBM70MJvuX7+5vKDEDmuz+zDPjZ34EEEkgAao7s5Sh5793zZpb7mlS15L09F17iacCvaO/EHBkJJJxK8Lx3TWCrbih+2mwVsJV5rXSVJHl5pjU1Xp5NqYy1gzZNAgkdCEg2WB0zzEJbjw3UGLva6thcBjtRS2AAWMsigYQOBF9717pzqkCrl6s13LEVn1PNurhtq2Nnf06bJoGE0wlp7R3qk+KE0QTL5cPVkut7JjWDiclGtQz4yLU3CSR0IeR4GnBBmGvLAKBmxkwaZtH2pV2y52jbVua0aRJIOJtQ7RchBkX2uvnEWLXdNRc+2pJ9ATwDfkkWTz9NAgkdCCmejrYMoJhkTZRFVtxqWZbohrnj1NcB+yugTZNAQgdC8tOWz7ZsWU1+R8o7N2elvLeGdUcPB+NpEkjoQzCbTuvs3HppnZM7onBta2+zZERmLLQpG/00CST0JEzvA1Jl2SchAOMOkasZ+3rboT+uQFGJVtE3YNb9qLpwAJD53O9AAgkkADnHnTuf3dd6ydkKVfas+uR8WS6LWfBNP00CCecSmhyZ7lkWmuw8piOkYSet3nus92mS5LRpEkg4m5B6OGLOidmlNkdUsDa7OLt34CUNTpsmgYTTCeZNgSTcjrqVaUPzMzN2K2F7yswW6tSckEBCP0LWhnqIHI0c9azmInVcEbFzkpt43ps2TQIJHQi29raSVYwSTPqS0muZ1uPWvxX6klrWzvMJGU+TQEIHgtt0zowBsYh2MYq++uQoV5dbZYEo/TQJJHQhNJoTb7NMzdGmEk3y70lztjs0J436BOy1JIGEHoQ8E6FWm72HA638O4SfiFne+YqYh8IeDhJI6E24DxC5qcpchGNAkpXVoPpRtGVWpH5KGQYutyo106W89xCZi6Ls3O9AAgkkINbeJjdx15szYwj1iWq+LCLrRrTCeJoEEnoRkk1bZtu3wEqDxey9spyOABo4XpEeuPYmgYTzCdlPI0XCe46YF/h4Qc+gAUCUtQ9Dgs1306ZJIOFsQhnLr7i/KYCnaI2TP4B1hsXEuJTNdEpQPW3PQddvH4M1YgEAnoOu3wBd5wG63kwu+iV+JRJI+DyErBQrR8ldI5exUrmrHJdWR1bf+5nym36aBBLOJTQ9HPqiEj2UoetHoj4dihSfeDJ5fM54mgQSzid4AhsuC42YOORieX5JDA+NfXRwnPmt9NMkkNCT4M4V07v46JKHYL1WlajMqGNPsMqAeuIuIiIDdInI2qrX9S5f6FcigYRPQMh+GkBqiQ6v+xJPe8hdJWR+bHEX1qdJIKELoZ3v7Xbpdau0kbTPNJn8Cp/ZH+asaSAhbZoEEk4ntPE0fCioqjVNthtvpKA677BVbuWZ8no/2jQJJJxO8CEmOYGd9tyIAUZVH5bz3odBR81WHWDemwQSehCawUSbPfiutcd5RrEoT51XqWsaaOTftGkSSDibcJxzYstut+7QkviJJQ02aSYmLI3t06ZJIKEDIbVl2DshN2mHEAHI8XRIyCz4PlxGmyaBhA6EJkemmqzRxp7ApCWeGXM/fWixDrdNP00CCb0Iae2NdjdLjfbJVK5Wbbe+dNO1z9kfAOinSSChB6H107G1xmGe4KX9iE0hW+whV6rdlTPvTQIJ5xPSPLJ6NEWpqGCl/XbC4kNHlt9jPE0CCf0IjTbU7TdpPjckx9y0b8TYEy9X+0cYT5NAQidC2ocjRnsjJp74QxSfwzE3jZmti9649iaBhC6Edr8szWlrt+7yOR8xFrMIbYm9J20Ka1kkkNCVkNbeSUHiKS4bBeqbYdl7aaq3J7rVN+fRNJDwK/xKJJDweQjN2lv3/DK8burriH6N0f4KDsvzGEFKP00CCecT2rz3xWWhofQE0ijQ2JFjGcOBZ6mopcdo0ySQ0IWQctdpER2y0NiD1mvRSRLuvjvZebnpBto0CST0IPiYkr3t18i5r7xN7Zaz3elZSqiNrGWRQEI/wrEMbVaL1GvZbLXjjlm1XWeHBq1Nt32FX4kEEj4PIRlndGnkiWO2Ms+7b0RqPP4A/L26AOc8MhJI6EJoejjMzdoJK1mlRsoxD+/OPdWmJg1/TpsmgYQOhKZ4BeAQLKdadNpX2tqv6g02AD5yMCb/06ZJIKEDIe2tE445BgInC/U0uLlje4ieah8vyLw3CST0IuT6dJsZq4cF2rEoz/t1AHliggtJOWOQBBJ6EZqR+xpzfwGkEQlb47ZjY9s0kFCzeoz7ZZFAQi9Cuw9HM9rbM+BIwXJy0VkRGvlxC80ZT5NAQhdCE09v7pgtYo5ld9qCYwrfrTXvHUXq/BHaNAkknE5I7ZOHKb5IG9Fukd5GqkXXG2yA5cdj/2muvUkg4Y8gqG5P0R9XwPawFMF606QXxXq1HS4BAOtth/6QN8V6e0juru70HUgg4f9MePHTXreKRugoaIVKtFy7lHvkPs0Y68+1NwkkdCC8xNML8hYc4XWtem19lQt+UvNSX7fbS9o0CSScSzjmvdOgQW/psIJWTnkfmjYOA0XZl0UCCb0Ior/+zL861q/wK5FAAgkkkEACCSSQQAIJJJBAQnv8A5okD4U9I3hoAAAAAElFTkSuQmCC", "qr_code_id": "45735c23-72fa-4952-b0ba-9a3d6bd01450", "account_key_id": "0fb7e5fa-e26f-4195-a94e-ec054e767ac8", "created_at": "2025-05-28T14:20:22.542258Z", "channel": "ECOMM", "key": { "key_value": "3532503001", "key_type": "MOBILE" }, "vat": { "vat_base_value": "100.00", "vat_type": "FIXED", "vat_value": "100.00" }, "merchant": { "country": "CO", "merchant_name": "Passport zqEkYq", "merchant_city": "Bogota", "merchant_zip_code": "98273", "merchant_category_code": "1234" }, "entity_customer_id": "19a0ab02-cbaa-4a7f-8ec3-6cc4224d30e7" }

As with the Static QR Code example, the 200 OK HTTP Status indicates that the QR Code has been created successfully and the Developer can use the returned id as a reference to retrieve and delete as required.

The qr_code_data field contains the encoded string that can be retrieved and presented in the desired format in ecommerce website. Libraries exist for many frontend programming languages such as Javascript, React, and Angular that convert the text into an image that can then be presented to the individual to scan with their mobile banking application.

For ease of use, in the qr_code_image the image is also returned in base64 format.

Benefits of the Dynamic QR Code are:

Data is flexible - each time a QR Code is generated, a different key, channel, transaction_purpose and channel_presentation can be combined with optional fields provided via the REST APIs
QR Codes are programmable for each transaction and are uniquely generated for each transaction via the integration with the ecommerce website CRM and backoffice system
The outcome is that the ecommerce website can support multiple online orders being submitted at one time in order to successfully receive Bre-B Payments for online order

Warning

PaaS Platform does not verify that the calculated VAT or INC numbers are correct - we do not contain a list of all appropriate added taxes or charges that should be added to every type of transaction in Colombia.

Nor do our Sponsor Bank partners take any liability for ensuring these details are correct - it is up to the Developer to ensure that the appropriate fees and add-ons are calculated as part of the accounting for processing sales.

Last updated on