Here you can find information about the response received after sending a GET Landing Info call.
If the call is made using a Transaction ID created through a payment method that allows Landing Info, the response will be in JSON format and include the following details:
- The transaction's details;
- Payment instructions;
- QR Codes / Barcodes if applicable;
- Links for redirecting the user when the transaction is successful
- The logo of the payment method to display on your checkout page.
Landing Info Response Fields
The following table contains the definitions for each field included in the response from the GET Landing Info API call.
| Field | Description |
|---|---|
amount | The amount of the transaction. |
currency | The currency used for the transaction. |
expirationDate | The expiration date set for the transaction. |
references | The reference ID from payment processor. |
instructions | Payment instructions for the payment method used in the transaction. |
qrCodes | Link and RAW data for the QR code with which the payment will be made. |
links | Additional links for the payment method used in the transaction. |
logos | Link to the logo associated with the payment method used in the transaction. |
Type values for Bre-B (Colombia)
For a Bre-B transaction, the typed buckets are populated as follows:
| Bucket | Type | Meaning |
|---|---|---|
references | MAIN | The Bre-B key value (e.g., @VUZ8FX8R). Show with copy-to-clipboard. |
qrCodes | RAW | The raw EMV-style QR string for client-side rendering. |
qrCodes | IMG | A pre-rendered QR image (data URL or HTTPS URL). |
bankInfoFields | BENEFICIARY | The beneficiary name (merchant shop name). |
instructions | NORMAL | A step in the payment instructions sequence, already localized. |
links | POLICY | Cookies / privacy policy URL. |
links | SUCCESS | Return / success URL for the customer (if provided at payment creation). |
logos | MAIN | The Bre-B method logo URL. |
Merchants rendering their own checkout should treat both qrCodes entries (RAW and IMG) and the references[type=MAIN] Bre-B key as concurrent surfaces, not alternatives — see the Bre-B integration guide for the rationale.