Fetch Transaction Information

The PayConex Transaction Status API provides an interface to request previous transaction details or a transaction_id value prior to processing a payment.

By fetching a transaction_id value beforehand a developer can send a transaction_id within a PayConex payment request. In this scenario if a communication error, packet loss, or similar issue occurs a developer could use the Transaction Status API to request transaction details in order to determine if the transaction was successful or not.

API URLs

For the certification test environment:

https://cert.payconex.net/api/tsapi/3.8

For the production environment:

https://secure.payconex.net/api/tsapi/3.8

Transaction Status API Functions

There are two main actions that can be completed using the Transaction Status API:

1. GET_TRANSACTION_ID: Returns a transaction_id for use in a PayConex payment request. This value is passed through the transaction_id parameter.
2. GET_TRANSACTION_STATUS: Returns the status of a transaction.

Fetching a Transaction ID

This is an example of a request to fetch a transaction_id value:

curl --request POST \
  --url https://cert.payconex.net/api/tsapi/3.8 \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data account_id=220614966801 \
  --data api_accesskey=32d42f0f0b6c89616d42aed8c96801e6 \
  --data action=GET_TRANSACTION_ID

This is an example of a PayConex API request using a pre-fetched transaction_id. For more PayConex API examples and information please see our Processing Transactions guide.

curl --request POST \
  --url https://cert.payconex.net/api/qsapi/3.8 \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data account_id=220614966801 \
  --data api_accesskey=32d42f0f0b6c89616d42aed8c96801e6 \
  --data tender_type=CARD \
  --data transaction_type=SALE \
  --data transaction_amount=1.00 \
  --data card_number=4124939999999990 \
  --data card_expiration=1230 \
  --data card_verification=456 \
  --data transaction_id=000000101281

Fetching Transaction Details

This is an example of a request to fetch the details of a previous transaction:

curl --request POST \
  --url https://cert.payconex.net/api/tsapi/3.8 \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data account_id=220614966801 \
  --data api_accesskey=32d42f0f0b6c89616d42aed8c96801e6 \
  --data action=GET_TRANSACTION_STATUS \
  --data transaction_id=000000101161

Handling Transaction Status API Responses

The Transaction Status API provides the response_format parameter to allow developers a method to specify a desired data format.

There are three supported data formats at this time:

• FORM: A URL-encoded HTTP form query string.
• JSON: A string in JavaScript Object Notation format.
• DEBUG: A simple, human readable array output. Intended only for use by a developer for testing.

This is an example response where the action is GET_TRANSACTION_ID with the response_format value as JSON.

{
  "transaction_id": "000000101261",
  "error": false,
  "error_code": 0,
  "error_message": null,
  "error_msg": null
}

This is an example response where the action is GET_TRANSACTION_STATUS with the response_format value as JSON.

{
  "transaction_id": "000000101161",
  "transaction_timestamp": "2021-08-12 21:53:13",
  "authorization_message": "APPROVED",
  "transaction_amount": 1,
  "cashier": "QSAPI 3.8",
  "transaction_approved": true,
  "found": true,
  "error": false,
  "error_code": 0,
  "error_message": null,
  "error_msg": null
}

TSAPI Request Format

Indexed in the table below are all the variables that can be posted to TSAPI along with a brief description of each.

TSAPI Response Format

Indexed in the table below are all the variables that can be returned via TSAPI along with a brief description of each.

👍

Note

For your security, transactions older than 18 months may be purged from our system.