Skip to main content

/check response variants

/check always returns the standard JSON response envelope. The data field may be absent while operation is still in progress.

A final unsuccessful transaction may be returned as status: "error" with populated data.

In progress (or not finalized yet)​

{
    "status": "success"
}

Final approved​

{
    "status": "success",
    "data": {
        "txn_id": "TXN123",
        "status": "APPROVED",
        "card_num": "8600********1234",
        "rrn": "123456789012",
        "auth": "123456",
        "data": {},
        "print_data": {}
    }
}

Final error​

{
    "status": "error",
    "data": {
        "txn_id": "TXN123",
        "status": "ERROR",
        "card_num": "8600********1234",
        "rrn": "123456789012",
        "error": "DECLINED",
        "data": {},
        "print_data": {}
    },
    "code": -20,
    "message": "Declined"
}

Returned transaction result statuses in data.status:

  • APPROVED
  • ERROR
  • REVERSED

IN_PROGRESS is not returned as data.status by /check; while an operation is still running, /check returns status: "success"without a transaction payload.