VTEX display transactions

Integrate VTEX-DEUNA V2 widget transactions with ERPs, WMS or external services

This section provides a detailed view of how transactions processed by DEUNA V2 widget are visualized in the VTEX Administrator, once they have been completed with credit or debit card. Each transaction and order processed by DEUNA V2 widget will be recorded and properly labeled in VTEX, facilitating their identification and management.

"Method" field detail in transactions processed by DEUNA V2 widget

When implementing DEUNA V2 widget as the new payment connector in VTEX for credit or debit card transactions, processed transactions will be registered under DEUNA at both order and transaction levels. Below is a visualization of how this will appear:

In this visualization, it is highlighted how the "Method" field reflects "DeunaNow" in VTEX, as can be observed in the attached image.

"Acquirer" field detail in transactions

Information regarding the actual gateway that processed the transaction, the card brand and card type, is provided by VTEX in the field called "acquirer". Below is an example:

Visualization and structure of "Acquirer" and "Method" fields in a transaction

Below, the detail of a transaction is shown where both parameters can be appreciated: "acquirer" and "method", reflecting the payment gateway and payment method used, respectively.

The text stored in the "acquirer" field follows a specific structure: "{gateway name}_{card brand / franchise}_{card type}", where each value is delineated by an underscore (_).

The values these fields can take are:

• Gateway name:
  • stripedirect (for Stripe)
  • paypal_acdc (for PayPal ACDC)
  • payu_credit(for PayU Latam)
  • mercadopago(for Mercado Pago)
  • wompi(for Wompi)
  • conekta(for Conekta)
  • paymentez(for Paymentez)
  • openpay(for OpenPay)
  • dlocal(for DLocal)
  • placetopay(for Place To Pay)
  • pagarme (for PagarMe)
• Card brand: Such as visa, amex or american_express, diners_club or diners, mastercard or master, elo or debelo
• Card type: Classified as credit or debit.

Complementary solutions for transmitting payment information to ERP, OMS, BackOffice or custom services

It is common for merchants to extract gateway name, card brand and card type information from the "acquirer" field in the middleware to their ERP, separating the values by the underscore, and then sending them individually to the ERP. However, we provide two additional alternatives to access this information:

📘

Use our API GET /order to retrieve these details.

Configure a webhook from our side, thus allowing the sending of this information to an endpoint specified by you, in the format you require.

📘

To configure the webhook at this time, it is necessary to contact our team, who will assist you in the configuration process.