Transactions

The API allows the transaction details to be retrieved.

The main input fields are:

• The issuer ID
• The transaction for which the detail is requested: It is provided by using the transaction Id.

It is also possible to request some additional data relative to addendum (to retrieve lodging information, car rental information, air itinerary information) by using the embedded fields.

In return, the interface provides the generic information (mainly master data) relevant to the transaction.

API links

The API provides possibility to retrieve a list of transactions (original first presentments received from the card schemes), based on certain criteria.

To prevent overly broad searches, at least one of the following conditional search criteria must be provided :

• PAN
• PAN token
• Transaction identifier
• Acquirer reference number
• Virtual Service Card Number
• Card Identifier
• Account Identifier
• Related Transaction

If requested, the API allows also to:

• search from an issuer and optionally with sub-issuers OR search from a list of issuers (by default, the search is performed on all issuers allowed for the user depending on its rights)
• return only certain transactions (disputed transactions, fraudulent transactions)
• request to enrich the response with additional data relative to addendum (to retrieve lodging information, car rental information, air itinerary information) by using embedded fields

The API response contains all matched transactions sorted by descending transaction date.

API links

The API allows an issuer to create a dispute folder in the system for a given transaction. This API enables the issuer to initiate the dispute from its application.

Several actions can be performed :

• Dispute only
• Dispute + refund/redebit (full or partial)
• Dispute + write-off (full or partial)
• Dispute + fraud declaration
• Dispute + event creation
• Dispute + attach documents
• Dispute + combination of above options

Main data in input are :

• the transaction for which the dispute is requested: It is provided by using the transaction Id. The transaction can be retrieved using the API Search transactions
• in option, several fields in the case additional actions have to be done besides the dispute folder creation (e.g. operation(s) posting, event(s) creation, add document(s)).

In response, the created dispute folder identifier is provided back systematically; then depending on the additional requests, the response includes also the posting, event creation and documents add response.

Idempotency is managed by the API; that is, if the request with the same WL-Correlation-ID is sent multiple times, it will be executed only once. The response will be retrieved directly from our system.

API links