User Transaction Lookup API

Why use this API?

The User Transaction Lookup API’s primary function is to identify if the new transaction is similar to one of the user’s recent transactions. The response details can then be used to pre-emptively complete the current transaction details required from the user to complete the new purchase. Using this API enhances the customer experience by reducing the number of interactions on recurring purchases.

Participating parties

See here for definitions.

• Buyer

• Clickatell

• Client

Getting started with the User Transaction Lookup API

To interface with Clickatell, the following needs to be set up, configured, and tested:

1

Integrate with Security Service API

• Follow the instructions in the Security Service API quick-start guide to request a token with your client_secret and client_id.

• Use the API_key and access_token in the following request (Step 2).

2

Call User Transaction Lookup API (this API)

• Add the API_key and access_token to the request header.

• Use the client_id supplied during integration.

• The following fields are required for the User Transaction Lookup:

  • sourceIdentifier

  • clientId

Only the buyer's last transaction will be returned if none of the optional parameters (channelId, productId, productTypeId, limit) are specified in the request. Depending on the optional parameters specified in the API request it may return more than one record in the response. It will always only return the latest transaction per productId.

A high-level view of this interface.