Transaction API

API Overview

This API is used to detokenize the debtor and creditor tokens and validate the attributes on the tokens against the transaction data.

Available Endpoints

Endpoint	Usage
/validatetransaction	Used to detokenize and validate token attributes.

Message flows

The diagram below provides an overview of the Transaction API message flow for transaction validation and token processing.

Validate transaction

The Transaction API enables financial institutions and transaction processors to detokenize debtor and creditor account tokens. This API provides comprehensive validation capabilities for tokens through configurable restriction and attribute rules.

Token Restrictions and Validation

Tokens processed through the Transaction API undergo validation according to configurable restriction rules. These restrictions ensure that tokens operate within predefined parameters established during the provisioning process.

The API also validates token attributes that are set during or after provisioning. This validation process uses configurable attribute rules to assess token validity and determine transaction outcomes.

Transaction Decision Process

The validation process results in an advisory outcome that determines whether an invalid transaction should be allowed or rejected. This configurable approach provides flexibility in handling transactions that do not meet standard validation criteria while maintaining security and compliance requirements.

The Transaction API supports both debtor and creditor account token detokenization, making it suitable for various payment processing scenarios where token-based transactions require validation and processing decisions.

Detokenize and validate token attributes

Transaction API response codes

Response Codes

This section includes detailed information about the API Response fields: statusCode, statusMessage, result, reasonCode and message.

Example HTTP 200 Transaction Response Example

{
    "messageId": "b43fe87a-9deb-4086-a03f-ec1f8a603e70", 
    "conversationId" : "1b1685b3-0723-4d30-ba6d-b19ea1d35da3", 
    "statusMessage": "Success.",
    "statusCode": "00000", 
    "transactionIndicator": true, 
    ...
}

Response Message: HTTP Code, statusCode and statusMessage

HTTP Code	statusCode	statusMessage	Applicable Message
200	00000	Success.	/v1/validatetransaction
400	11100	Invalid request. The data field is not in the correct data type format or length or pre-defined values or the required data field is missing.	/v1/validatetransaction
400	11104	Cryptographic error.	/v1/validatetransaction
400	11105	Invalid token requestor id. Only token requestors of RTP domain can proceed the transaction.	/v1/validatetransaction
500	11800	Unknown internal server error. Try again later.	/v1/validatetransaction
500	11801	Unknown error.	/v1/validatetransaction

Payment Account Tokenization