Skip to main content
Migo Docs

Normalized payment details (paymentInfo)

When you look up a transaction with GET /transactions, the response includes a paymentInfo field with a standardized summary of the payment, regardless of which processor handled it β€” card, wallet, QR or bank transfer. It's built for support, reconciliation, and reporting: you don't need to know each processor's particular response format to read the card brand, last 4 digits, 3D Secure result, or the authorization event.

When it appears

paymentInfo is null (or the field may be absent) until the transaction has at least one charge attempt. Once it exists, it's filled in progressively: each new processor event (authorization, capture, 3DS result) is merged with what was already there instead of replacing it. A value that was already saved isn't cleared just because a later response doesn't include it.

General shape​

{
"paymentMethodInfo": { "...": "see below" },
"user": { "...": "see below" },
"authentication": { "...": "see below" },
"authorization": { "...": "see below" },
"capture": [{ "...": "see below" }]
}
FieldTypeDescription
paymentMethodInfoobject or nullNon-sensitive payment method data (brand, last 4 digits, expiration, or account/bank data for non-card methods).
userobject or nullPayer data. Only included when at least one real value is available.
authenticationobject or null3D Secure result, when the processor runs it.
authorizationobject or nullThe event where the processor approved, declined, or left the charge pending.
capturearray of objects or nullOne or more confirmed capture events (there can be several with partial captures).

paymentMethodInfo​

Never includes the full card number or CVV β€” only what you need to show the merchant or the customer which payment method was used.

{
"type": "card",
"brand": "VISA",
"last4": "1111",
"bin": "411111",
"holderName": "Juan Perez",
"expirationMonth": "12",
"expirationYear": "2028",
"accountHolder": null,
"accountNumber": null,
"bankCode": null,
"bankName": null
}
FieldDescription
typecard, cardToken, wallet, bankTransfer, cash, credit, or null. If the processor reports a saved-card payment as token, it's normalized to cardToken.
brandCard brand (VISA, MASTERCARD, AMEX, …), always uppercase.
last4Last 4 digits of the card or account.
binFirst 6–8 digits of the card (identifies the issuing bank and network).
holderNameCardholder name, when the processor reports it.
expirationMonth / expirationYearCard expiration (month as MM, year as 4 digits).
accountHolder / accountNumber / bankCode / bankNameAccount data for non-card methods (wallets, transfers).

user​

Payer data, derived mainly from the billTo sent when charging.

{
"name": "Juan Perez",
"email": "juan@example.com",
"phone": "50255555555",
"address": "Ciudad de Guatemala",
"documentType": null,
"documentNumber": null
}

If the processor reports the cardholder name (paymentMethodInfo.holderName), that value takes priority over the name sent in billTo.

authentication​

Present when the payment went through (or attempted) 3D Secure β€” the additional validation the issuing bank may require from the customer before approving the payment.

{
"active": true,
"eci": "05",
"authenticationStatus": "Y",
"cavv": "<cryptogram>",
"xid": null,
"dsTransactionId": "<ds-transaction-id>",
"protocolVersion": "2.2.0"
}
FieldDescription
activeWhether 3DS authentication occurred. Once it's true, it stays true on later updates even if a response doesn't repeat it.
eciElectronic Commerce Indicator reported by the processor.
authenticationStatusAuthentication status reported by the processor or the 3DS system.
cavvCardholder Authentication Verification Value β€” the cryptogram used as technical evidence of authentication.
xidTransaction identifier from 3DS 1.x flows, when applicable.
dsTransactionIdDirectory Server identifier in 3DS 2.x flows.
protocolVersion3DS protocol version (for example 2.1.0, 2.2.0).

authorization and capture​

Both share the same event shape. authorization is a single event and describes a pre-authorization: the processor reserved the funds and the charge is confirmed in a separate call. capture is a list of confirmed charges, because there can be several partial captures against the same authorization.

authorization only applies to pre-authorization

Many payment methods charge in a single step: wallets such as Nequi, QR payments, bank transfers and most card payments. Those processors have no pre-authorization stage, so authorization comes back with every field set to null and the payment result is read from capture.

To tell whether a payment succeeded, use the transaction's status field. paymentInfo is the record of the payment's events, not its current state.

{
"timestamp": "2026-06-26T18:29:00.000Z",
"transactionId": "processor-auth-123",
"reference": "123456789012",
"authorizationCode": "ABC123",
"statusCode": "00",
"statusMessage": "APPROVED",
"approved": true
}
FieldDescription
timestampEvent date/time in ISO 8601.
transactionIdThe identifier the processor gave that event (authorization, charge, or capture).
referenceProcessor reference β€” RRN, order number, or another identifier useful for reconciliation.
authorizationCodeThe processor's authorization code, when present.
statusCode / statusMessageStatus code and message reported by the processor.
approvedtrue = approved, false = declined, null = pending or undetermined.

If the same capture event arrives more than once (retries, reconciliation), it's deduplicated by the combination of transactionId + reference + statusCode + authorizationCode β€” you won't see duplicates in capture.

Full example​

{
"paymentMethodInfo": {
"type": "card",
"brand": "VISA",
"last4": "1111",
"bin": "411111",
"holderName": "Juan Perez",
"expirationMonth": "12",
"expirationYear": "2028",
"accountHolder": null,
"accountNumber": null,
"bankCode": null,
"bankName": null
},
"user": {
"name": "Juan Perez",
"email": "juan@example.com",
"phone": "50255555555",
"address": "Ciudad de Guatemala",
"documentType": null,
"documentNumber": null
},
"authentication": {
"active": true,
"eci": "05",
"authenticationStatus": "Y",
"cavv": "<cryptogram>",
"xid": null,
"dsTransactionId": "<ds-transaction-id>",
"protocolVersion": "2.2.0"
},
"authorization": {
"timestamp": "2026-06-26T18:29:00.000Z",
"transactionId": "processor-auth-123",
"reference": "123456789012",
"authorizationCode": "ABC123",
"statusCode": "00",
"statusMessage": "APPROVED",
"approved": true
},
"capture": [
{
"timestamp": "2026-06-26T18:30:00.000Z",
"transactionId": "processor-capture-123",
"reference": "123456789012",
"authorizationCode": "ABC123",
"statusCode": "00",
"statusMessage": "CAPTURED",
"approved": true
}
]
}

Single-step payment​

The same object for a payment charged in a single call β€” here a confirmed Nequi wallet payment. authorization is present but empty, and the payment result is read from capture:

{
"paymentMethodInfo": {
"type": "wallet",
"brand": null,
"last4": null,
"bin": null,
"holderName": null,
"expirationMonth": null,
"expirationYear": null,
"accountHolder": null,
"accountNumber": "3001234567",
"bankCode": null,
"bankName": null
},
"authentication": {
"active": false,
"eci": null,
"authenticationStatus": null,
"cavv": null,
"xid": null,
"dsTransactionId": null,
"protocolVersion": null
},
"authorization": {
"timestamp": null,
"transactionId": null,
"reference": null,
"authorizationCode": null,
"statusCode": null,
"statusMessage": null,
"approved": null
},
"capture": [
{
"timestamp": "2026-11-17T18:21:38.369Z",
"transactionId": "4HdTqyWzW48lRN5fi29ZQ",
"reference": "4HdTqyWzW48lRN5fi29ZQ",
"authorizationCode": "NEQUI-AUTH",
"statusCode": "00",
"statusMessage": "Payment approved",
"approved": true
}
]
}
The interactive reference doesn't model this field yet

The live spec documents the general shape of the transaction, but doesn't yet describe the internal structure of paymentInfo field by field. This page is the authoritative reference in the meantime β€” it's verified against the endpoint's actual behavior.