TapTransactions Interface Overview

TapTransactions Interface

First, the developer must develop the SDK interface according to this guide:
Interface for Performing a TAP Transaction via Cardcom Using a Third-Party Application (White-label)

Afterward, the developer must call this API using JSON to register and validate the device, as well as record the transaction.

Interface for registering a physical device with a TAP terminal in Cardcom / checking the registration status of an existing device:

Guide: TAP ON PHONE - Get Device Information (PrepareDevice - Get device information before performing a Tap On Phone transaction)

Function in Swagger:

https://secure.cardcom.solutions/Api/v11/Docs#tag/TapTransactions/operation/TapTransactions_PrepareDevice

Function name:

https://secure.cardcom.solutions/api/v11/TapTransactions/PrepareDevice

Interface for recording a successful TAP transaction in the Cardcom transaction report:

Guide: TAP ON PHONE - Performing a Transaction (ProcessTransaction - Process Tap On Phone transaction)

Function in Swagger:

https://secure.cardcom.solutions/Api/v11/Docs#tag/TapTransactions/operation/TapTransactions_ProcessTransaction

Function name:

https://secure.cardcom.solutions/api/v11/TapTransactions/ProcessTransaction

Additionally, a specification file is attached:

Attachments

• TAP Transaction Process via Cardcom Ltd (1).pdf