Parse QR recipient

POST /v1/partner/recipients/parse-qr

Authentication: signed Partner API request.

Request body

Field	Required	Description
`qr_content`	Yes	Raw EMV or provider QR payload, maximum 4096 characters.
`country`	No	ISO alpha-2 constraint, for example `AR`. It must match the country detected from the QR.

{
  "qr_content": "00020101021143540016com.mercadolibre...630456C8"
}

Do not send rail or end_user_id. QR parsing is a merchant-scoped preview, not a user KYC or payment-readiness check.

Response

{
  "country": "AR",
  "payment_instrument": "qr",
  "recipient_fields": {
    "country": "AR",
    "qr_content": "00020101021143540016com.mercadolibre...630456C8",
    "payment_instrument": "qr",
    "account_number": "23316888984",
    "holder_name": "Example Recipient"
  },
  "derived_fields": [
    {"name":"account_number","source":"provider_lookup"},
    {"name":"holder_name","source":"qr_payload"}
  ],
  "verification": "not_supported"
}

Country detection and routing

AgentBank detects the country and validates the complete QR payload. If country is supplied and differs from the detected country, the request fails with 400 RECIPIENT_COUNTRY_MISMATCH. A QR with no detectable supported country also fails instead of guessing a route. The resolved fields vary by country and provider. verification describes whether an account-holder check was available; it is not itself a payment status. This endpoint does not create an address-book record, reserve a route, or verify the merchant end user’s readiness. Send the returned recipient_fields unchanged to Create payment after a successful preview.

Introduction

Getting started

Integration guides

API reference

Parse QR recipient

Request body

Response

Country detection and routing

​Request body

​Response

​Country detection and routing

Request body

Response

Country detection and routing