Create Card Present QR Code Payments (Account-to-Account)

This guide walks you through processing an account-to-account QR Code payment in a Card Present (CP) environment using the Getnet Regional API. In this flow, the merchant’s physical terminal requests a dynamic EMV QR code from the gateway, displays it to the customer, and the customer scans it with their banking app to authorize the payment directly from their bank account.

Requirements

Before initiating a QR code request, ensure the following:

• API Credentials: Obtain your client_id and client_secret from the Integration Support team.
• Authentication: Generate a Bearer token via the Authentication endpoint.
• Terminal Hardware: A physical device (POS/TEF) capable of displaying images or high-resolution text for QR code rendering.
• Serial Number: The physical serial_number of the device must be provided in every request.
• Brand Support: Currently available exclusively for Visa and Mastercard.

How It Works

The Card Present QR Code flow has three stages:

QR Code Payment Process

Step 1: Create the QR Code Request

Send a POST request to the QR Code endpoint to generate the EMV QR payload.

Request Fields

Example Request

curl --location --request POST 'https://api.pre.globalgetnet.com/dpm/payments-gwproxy/v2/payments/qrcode' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'x-transaction-channel-entry: XX' \
--data-raw '{
  "idempotency_key": "cp-qr-visa-001",
  "request_id": "daac03dc-73db-453f-9bea-b1391669d5d3",
  "order_id": "ORDER-101",
  "amount": 10000,
  "currency": "CLP",
  "payment_method": "PURCHASE",
  "transaction_type": "NO_INTEREST",
  "serial_number": "CL00027L"
}'

Step 2: Display the QR Code

A successful request returns HTTP 201 with a JSON body containing the qr_code EMV string inside additional_data. Render this string as a scannable image on the terminal screen.

Response Fields

Example Response (HTTP 201)

{
  "payment_id": "03ec0ede-3bc9-42dd-a71b-1c3a670b2b89",
  "seller_id": "e0ed6f00-fdc5-46d6-9557-6a2cac641b09",
  "request_id": "daac03dc-73db-453f-9bea-b1391669d5d3",
  "idempotency_key": "cp-qr-visa-001",
  "order_id": "ORDER-101",
  "amount": 10000,
  "currency": "CLP",
  "status": "APPROVED",
  "reason_code": "00",
  "reason_message": "TRANSACTION EXECUTED SUCCESSFULLY",
  "additional_data": {
    "transaction_id": "890005df15a2-0b1e-4c6e-8ece",
    "qr_code": "00020101021241260009cl.getnet98097605970315204...",
    "qr_code_emv_type": "dynamic",
    "creation_date_qrcode": "2026-02-19T14:48:00.000Z",
    "expiration_date_qrcode": "2026-02-19T14:49:50.000Z",
    "third_party_qr_code_id": "61260970G",
    "third_party_order_id": "61260970G"
  }
}

To process the response:

1. Extract additional_data.qr_code and render it as a scannable QR image on the POS screen.
2. Start a countdown timer using expiration_date_qrcode to auto-discard expired codes.
3. Store the payment_id to query the final authorization status in Step 3.

Step 3: Verify the Transaction Status

After the customer scans the QR code, verify that the payment was completed using one of these methods:

• Webhooks: Configure your integration to receive asynchronous payment status notifications.
• Polling: Call the Get Transaction endpoint with the payment_id returned in Step 2.

Error Responses

Next Steps

Now that you understand QR Code payments, explore these related Card Present features:

• Single-Step Payments: Process standard chip and magnetic stripe sales.
• Pre-authorized Payments: Manage two-step flows for reservations and delayed captures.
• Cancel a Payment: Reverse a previously captured transaction.
• Terminal Requirements: Verify your device supports QR display capabilities.
• Card Present Workflow: Review the low-level sequence diagrams for all CP flows.