Introduction - QR Code - Mercado Pago Developers
Developers
API Reference
Support
Sign in

    Home

    Getting started

    Online Payments

    Checkout Pro

    Checkout API

    Payment Link

    Marketplace

    Mobile Checkout

    Web Tokenize Checkout

    In person payments

    QR Code

    Plugins and platforms

    WooCommerce

    Prestashop

    Magento 2

    Shopify

    VTEX

    SDKs

    Notifications

    Webhooks

    IPN

    Account Management

    Requirements for production environment

    Get payments

    Reports

    Cashback and Cancellations

    Chargeback Management

    Improves approval

    Resources

    Localization

    Changelog

    Status

IN THIS PAGE

Suggest edit
Help us improve the documentation
Did you see wrong information and would you like us to explain something else or improve our manuals? Please leave your suggestions on GitHub.

QR attended model

What’s QR attended model?

After taking a client’s order, this model allows an operator to connect the order with a Point of Sale to complete the transaction. This system is recommended for retail and restaurants, among others.

Main characteristics

The main characteristics are:

  • Operator always works from its Point of Sale system, that was previously set up with a Mercado Pago charge function. From that option, the order is sent to the associated POS.
  • For a client to make a payment, an order needs to be linked to a POS.
  • Operator can see the completed payment on its system.

Model flow

Here's an explanation of how this model works:

Flujo de pago en punto de venta QR Mercado Pago

Note
pos_id is an unique identifier of a POS inside Mercado Pago. You’ll get it at the same moment you create a POS and it’ll have an associated QR.
  1. (A) Point of Sale (POS) logs the order and sends the data to merchant server.

(B) Merchant server sends order to Mercado Pago server with a pos_id. 2. Order is linked to a QR code and ready for the client to scan. 3. Client scans QR and Mercado Pago looks for the order through pos_id. If the client scans before the start of the order registration, flow is not affected. 4. (A) Then, merchant server gets a notification for the order.
(B) Reception is confirmed.
(C) The client will see the order to complete payment inside the app.
5. Finally, the client pays the order. 6. (A) Client will see a payment confirmation.
(B) merchant server will receive a notification for the order.
(C) And seller will confirm reception. 7. (A) merchant server asks for order status with ID received in the last notification to know if it’s closed or still remains open.
(B) Mercado Pago returns respective data like status and payment information, among others. 8. Once order is closed, receipt can be printed.

Note
On point 4 you’ll have to follow steps 7A and 7B to get order status.

Next steps

REQUIRED

How to Integrate attended model

Learn to integrate this model step by step.

Was this information helpful?

Copyright © 1999-2021 DeRemate.com de Uruguay S.R.L.

Terms and conditionsHow we take care of your privacy
Partners Mercado Pago

Al navegar en este sitio aceptas las cookies que utilizamos para mejorar tu experiencia. Más información.