Breb Payment Flow

Breb enables payments via bank transfer using a QR code or transfer key. The buyer scans the QR or enters the key in their banking app to complete the payment.

How it works

Create order

Call POST /v1/orders with the amount and the Breb gateway ID. The shopper object is optional for Breb.

Display QR code and key

The response includes a qr_code (base64-encoded image) and a key (text string). Display both to the buyer — the QR code for scanning, and the key as a fallback for manual entry.

Buyer completes transfer

The buyer opens their banking app, scans the QR code or enters the transfer key, and confirms the payment.

Payment confirmed

Once the transfer is completed, the order status changes to confirmed. You receive a webhook notification, or you can poll for the status.

Shopper data

The shopper object is optional for Breb. The QR code and key are generated from the order, not from the buyer’s data, so you can create a Breb order without any shopper information.

You can omit shopper entirely or send only the fields you have. Fields you do send are validated for format (an invalid email returns 422), but none of them is required.
Shopper fields you did not send arrive as null in webhooks and when reading the order; the whole shopper object can be null.
Nequi and Daviplata are not affected: they still require the full shopper (see Creating orders).

Payer data

Breb reports who actually paid only after the transfer is confirmed, and the data is best-effort:

Name and document (masked, last digits only) of the payer, as reported by the payer’s bank. When present, Wava stores them on the order after confirmation, so shopper.first_name and shopper.last_name may be filled even if you created the order without shopper.
Email and phone number are never guaranteed for Breb payers.
The payer is whoever completed the transfer, which may not be the shopper you sent when creating the order.

Do not depend on these fields to fulfil the order: the order status (confirmed) is what confirms the payment.

Example request

The minimal Breb order, without shopper:

curl -X POST "https://api.wava.co/v1/orders" \
  -H "merchant-key: YOUR_MERCHANT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 100000,
    "description": "Invoice payment",
    "currency": "COP",
    "payment_gateway": {
      "id_payment_gateway": 9
    },
    "order_key": "invoice-11111"
  }'

Example response

{
  "result": {
    "id_order": 12347,
    "status": "processing",
    "payment_gateway": {
      "breb": {
        "qr_code": "iVBORw0KGgoAAAANSUhEUgAAAQAAAAEA...",
        "key": "BREB-TXN-2025-ABCDEF123456"
      }
    }
  }
}

Displaying the QR code

The qr_code field contains a base64-encoded PNG image. To display it in HTML:

<img src="data:image/png;base64,{qr_code_value}" alt="Payment QR Code" />

Display the key value as text alongside the QR code so the buyer can copy and paste it if they prefer not to scan.

Important notes

The buyer completes payment asynchronously (like Nequi), so you must rely on webhooks or polling for confirmation.
Breb does not use any shopper data to generate the QR code or key, so shopper is optional. Payer data arrives after confirmation and is best-effort (see Payer data).
The QR code and key have a limited validity window. If expired, cancel the order and create a new one.

Getting Started

Orders

Payment Flows

Payment Links

Partners

Webhooks

Integrations

Testing

Error Handling

Breb

Breb Payment Flow

How it works

Shopper data

Payer data

Example request

Example response

Displaying the QR code

Important notes

​Breb Payment Flow

​How it works

​Shopper data

​Payer data

​Example request

​Example response

​Displaying the QR code

​Important notes

Breb Payment Flow

How it works

Shopper data

Payer data

Example request

Example response

Displaying the QR code

Important notes