Update Transaction Status API

The Update Transaction Status API offers the calling application/client to confirm Trident's suggestion and to update the end status of a completed transaction.

Endpoint

Endpoint URL Format: <domainname>/analyse/POS/updateTxnStatus

Example Endpoint URL:

http://localhost:8443/analyse/POS/updateTxnStatus

Method: POST
Content-Type: application/json

Request parameters

Parameter	Description	Example
clientId `mandatory`	`String (36 characters)` - Unique transaction ID generated by Trident for tracking purposes.	201809_86642221-1801-49aa-ad12-c409c0317451.
finalStatus `mandatory`	`String (3 digits)` - Final status of the transaction.	100 - Transaction Success
Custom parameters
action `optional`	`String (3 digits)` - Action taken by client.	001 - Default action
reason `optional`	`String (3 digits)` - Reason for failed transaction.	004 - User Decline
challengeType `optional`	`String (3 digits)` - Response of the challenge sent to the user.	000

📘
Custom parameters:
Trident supports any number of custom fields to be configured basis the use case.

Sample request

curl -X POST "http://127.0.1:8443/analyse/POS/updateTxnStatus" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "clientId": "201809_12345TXN",
    "finalStatus": "100",
    "action": "001",
    "reason": "004"
    "challengeType": "000"
  }'

Response parameters

Parameter	Description	Example
clientId	`String (UUID)` - Unique transaction ID generated by Trident for tracking purposes.	20240112103024_8172_3DS_8d77153d-5bd0-4e89-b0d7-86024adbc13e
NodeId	`String` - Server node identifier that processed the request.	172.31.2.145::8443
error	`String` - Error message indicating reason for failure scenarios	Unrecognised instanceId

Sample response


{
    "nodeId": "192.168.108.139::8085",
    "clientId": "20240112103024_8172_3DS_8d77153d-5bd0-4e89-b0d7-86024adbc13e",
    "error": "Unrecognised instanceId"
}