Thales TSH Transaction Notification Passthrough API

Overview

The Thales TSH Transaction Notification Passthrough API defines a set of operations that allows the TSH to retrieve the transaction information to be displayed in the device.

The API follows the HTTP protocol with content type in JSON.

The messages are encoded with the UTF-8 character set which is the default set defined for JSON.

The transport security layer relies on HTTP/TLS mutual authentication.

Download API spec

tsh-transaction-notification-passthrough-api-oas2.yaml

Endpoints

Environment	Endpoint URL
PPROD	api.dbp-stg.thalescloud.io:443/tns-dispatcher/tsh/tnapi/v2.0
PROD	api.dbp.thalescloud.io:443/tns-dispatcher/tsh/tnapi/v2.0

Release Notes

Release	Date	Modifications
1.0	12/2018	Initial version.
1.1	07/2019	Operation 'retrieve-token-transactions' now contains list of 'transactionIds'. Both parameters 'transactionId' and 'transactionIdentifier' are merged into 'transactionId'. No more tag management in the API. Parameter 'IssuerId' removed from the 'POST /retrieve-token-transactions' operation.
1.2	10/2019	Update description of 'transactionResultReason' that is required only for GooglePay solution.
1.3	10/2019	Parameter 'transactionId' is reverted to a simple technical identifier. Parameter 'walletProviderTransactionId' is added to comply with Wallet Providers specific requirements.
1.4	11/2019	Add error code 119 in 'notify-token-transaction'.
1.5	07/2020	Fix wrong description of mCommerce 'walletProviderTransactionId' for Apple Pay.
1.6	05/2022	Parameter 'dpanIdentifier' added in 'retrieve-token-transactions' response. Used to identify auxiliary transaction.
1.7	11/2023	Added new HTTP header on token transaction notification API in order to indicate which wallet type has performed the transaction
1.8	04/2025	Parameter 'linkedTransactionId' added in 'retrieve-token-transactions' response. Applicable to Google Pay solution. Used in the case of refund in order to link the notification to a previous purchase transaction.