Wallet Response Codes — ECR Integration Guide

What to read, and what to expect, in the merchant callback and the get wallet status response.

Where to read the transaction status/result

In both scenarios (Merchant callback AND Wallet status) , read the root responseCode — this is the outcome of the wallet transaction.

• root responseCode — the transaction result (see codes below).
• externalResponseCode — the underlying provider code (from Wallet Response codes).

Common responseCode values:

See complete list here: PSP Response codes​.

transactionDetails[] — per‑payment breakdown

Both Merchant callback and Wallet status include transactionDetails[], with one entry per payment leg. A single payment has one entry; a hybrid payment (paid with more than one instrument) has one entry per instrument.

• Use it to see which instruments were used and information about each payment instrument.
• The responseCode / externalResponseCode inside each entry are raw provider codes (from Wallet Response codes ) and are not the same values as the root responseCode. Do not interpret them with the table above — treat them as informational only. The transaction result is always the root responseCode.

Wallet status

The get status response has two separate places that look like reflecting the transaction status. Read the correct one:

{
  "responseInfo": { "responseCode": "0" },   // lookup succeeded
  "responseCode": "2001",      // ← the transaction result (cancelled by consumer)
  "externalResponseCode": "68606",
  "pspReference": "...",
  "merchantReference": "...",
  "transactionDetails": [ ... ]      // informational per-sub-transaction breakdown
...

Merchant callback

Sent from the PSP to the ECR when the transaction is complete (amount(s) authorized or rejected/failed).

• The transaction status/result is the root responseCode (see table above).
• There is no responseInfo — the callback describes the transaction only, so read the root responseCode directly.

{
  "responseCode": "2001",    // ← the transaction result (cancelled by consumer)
  "externalResponseCode": "68606",
  "pspReference": "...",
  "merchantReference": "...",
  "transactionDetails": [ ... ]      // informational per-sub-transaction breakdown
...

In short

1. Transaction status/result = root responseCode. Always, in both responses.
2. The merchant callback has no responseInfo; get status does — and there responseInfo only tells you if the request was served, not the payment outcome.
3. transactionDetails[] are a per‑sub-transaction breakdown (one entry for single‑instrument, more for hybrid); its codes are not PSP codes.
4. 1005 means pending — not final.