Transaction Status Check API

Version History

FieldDescriptionEnd Points
05/08/25 Initial release of Transaction Status Check API (v1)iposTransactStatus v1

Prerequisites

  • For Sandbox (UAT)

Users should be onboarded on the iPOSpays sandbox (UAT) environment as a merchant and have a valid TPN.

  • For Production (Live)

Users should be onboarded on the iPOSpays production environment as a merchant and have a valid TPN.

If you do not have a TPN, contact your ISO or support@dejavoo.io


Generate an Authentication Token

To authenticate your API requests, you must include a valid token in the request header. This token is generated directly from the merchant portal.

Steps to Generate a Token:

Step 1: Log in to your merchant account via the iPOSpays Portal and go to the Settings section.

Step 2: Under the Generate Ecom/TOP Merchant Keys section:

  • Select the appropriate TPN (Terminal Profile Number) from the dropdown list.

  • Click Generate Token to create a new authentication token.

  • The generated token will be displayed and must be used in your API request headers.

Need help? Watch this video tutorial for a guided walkthrough of the token generation process.


Endpoints and Request Method

Request Method: POST

Endpoints

EnvironmentURL
Sandbox https://payment.ipospays.tech/api/v1/iposTransactStatus
Production https://payment.ipospays.com/api/v1/iposTransactStatus

Request Parameters

Header

FieldTypeDescription
token * StringThe authentication token required for all API requests. This token is generated from the iPOSpays Merchant Portal under the Settings > Generate Ecom/TOP Merchant Keys section. It authorizes the request and links it to a specific TPN (Terminal Profile Number).

Body

FieldTypeDescription
merchantId * StringUnique ID of the merchant
transactionReferenceId * StringUnique reference ID of the original transaction for which the status inquiry is being made. This value must match the one used in the original payment request.

Response Parameters

FieldTypeDescription
respCode StringResponse code returned by the processor (e.g., “00” for Approved).
appCode StringApproval code assigned by the acquirer or gateway.
respMsg StringHuman-readable message describing the result of the transaction.
txRefNo StringUnique transaction reference ID originally sent in the request.
dTxId StringUnique transaction ID generated by the system.
hTxId StringHost transaction ID, used for backend reconciliation.
batchNo IntegerBatch number where the transaction is grouped.
invoiceNo IntegerInvoice number associated with the transaction.
rrn StringRetrieval reference number provided by the processor.
processingCode StringCode indicating the type of transaction being processed.
hrc StringHost Response Code.
respStatus StringTransaction status (e.g., Approved, Declined).
amount StringBase transaction amount.
tips StringTip amount included in the transaction, if any.
customFee StringCustom fee amount applied, if applicable.
feeLabel StringLabel describing the custom fee.
localTax StringAmount of local tax applied.
stateTax StringAmount of state tax applied.
lTaxLabel StringLabel describing the local tax.
gTaxLabel StringLabel describing the state tax.
totalAmount StringTotal transaction amount including tax, tip, and fees.
txnSettleStatus StringIndicates if the transaction is settled or pending (e.g., “Yet to Settle”).
transactionType StringType of transaction (e.g., SALE, REFUND, CHECK).
cardType StringType of card or wallet used.
achToken String(For ACH/Wallet) Encrypted token for ACH or wallet transaction.

Nested Objects

TxDetail

FieldTypeDescription
DateNTime StringDate and time when the transaction occurred. Format: YYYYMMDDHHMMSS.
Tpn StringTerminal Profile Number associated with the transaction.

Card

FieldTypeDescription
ChdToken StringEncrypted token representing the cardholder data.
Label StringCard brand (e.g., VISA, AMEX, MASTERCARD).
MaskedPan StringMasked Primary Account Number (e.g., **** **** **** 1234).

Sample Request – Standard Card Transaction

Checks the status of a card-based transaction using the merchantId (TPN) and the unique transactionReferenceId generated at the time of payment.

Request Header
{
  "token": "" 
};
Request Body
{
  "merchantAuthentication": {
    "merchantId": "962923571839",
    "transactionReferenceId": "3245623463254631"
  }
}

Sample Response – Standard Card Transaction

Returns the transaction status and details such as approval code, transaction ID, batch number, amount breakdown (tip, tax, fees), and settlement status for a card-based transaction.

{
  "iposhpresponse": {
    "Response": {
      "RespCode": "00",
      "AppCode": "AXS009",
      "RespMsg": "Approved",
      "TxRefNo": "3245623463254631",
      "DTxId": "99454496548357183920250626112804",
      "HTxId": "000000321000010",
      "BatchNo": 993,
      "InvoiceNo": 9,
      "Rrn": "517705501432",
      "ProcessingCode": "000000",
      "HRC": "00",
      "RespStatus": "Approved",
      "Amount": "150",
      "Tips": "00",
      "CustomFee": "8",
      "FeeLabel": "Custom Fee",
      "LocalTax": "30",
      "StateTax": "15",
      "LTaxLabel": "Local Tax",
      "GTaxLabel": "State Tax",
      "TotalAmount": "203",
      "TxnSettleStatus": "Yet to Settle",
      "TransactionType": "SALE"
    },
    "TxDetail": {
      "DateNTime": "20250626112804",
      "Tpn": "962923571839"
    },
    "Card": {
      "ChdToken": "5502127CC0140E22C6E30808D971BB9113E760DC3F3C2366",
      "Label": "AMEX",
      "MaskedPan": "3796056666"
    }
  }
}

Sample Request – Alternate Payment (Wallet/ACH)

Used to check the status of non-card transactions like ACH or digital wallets, by passing the same merchantId and transactionReferenceId.

Request Header
{
  "token": "" 
};
Request Body
{
  "merchantAuthentication": {
    "merchantId": "962923571839",
    "transactionReferenceId": "9298395654Testing024122"
  }
}

Sample Response – Alternate Payment

Provides status and transaction details for ACH or wallet payments, including approval message, ACH token, amount, type (e.g., CHECK), and whether the transaction is settled.

{
  "iposhpresponse": {
    "Response": {
      "RespCode": "00",
      "RespMsg": "APPROVAL - AUTH NUM 272-172",
      "TxRefNo": "9298395654Testing024122",
      "DTxId": "28118655670253241411750855554528",
      "BatchNo": "607",
      "Rrn": "-rosY2zcUJilI0i2-_uVcDAYaJdZWMItJmrq",
      "TotalAmount": "1231",
      "Amount": "1231",
      "Tip": "0",
      "CardType": "Wallet",
      "TransactionType": "CHECK",
      "Status": "Approved",
      "AchToken": "05944FB3E1DA4663868455AF630F45BE",
      "TxnSettleStatus": "Yet to Settle"
    },
    "TxDetail": {
      "DateNTime": "11750855554528",
      "Tpn": "567025324141"
    }
  }
}

Sample Error Response – Invalid Transaction Reference

Returned when the transactionReferenceId is invalid or not found. Includes an error message indicating no transaction was registered with the provided reference ID.

Request

Request Header
{
  "token": "" 
};
Request Body
{
  "merchantAuthentication": {
    "merchantId": "962923571839",
    "transactionReferenceId": "3245623463254631S2343W12345354356"
  }
}

Response

{
  "errors": [
    {
      "field": "IPOSTRANCT_001",
      "message": "No Transaction Registered with This TransactionRefId. Please try with valid details.",
      "bulbIconRequired": false
    }
  ]
}

Notes

  • The field TxnSettleStatus indicates whether the transaction has been settled or is still pending.

  • The response structure varies slightly based on whether it is a card or an alternate payment method.

  • Ensure that the transactionReferenceId used is the same one provided at the time of initiating the transaction.