triPOS supports getToken on the following endpoints:
POST /api/v1/sale
, POST /api/v1/refund , POST /api/v1/authorization and POST /api/v1/authorization/{transactionId}/incremental for OmniToken creation. An OmniToken can be
generated using card data and then that OmniToken can be used to complete a Sale POST /api/v1/sale/token, Authorization POST /api/v1/authorization/token, or
Refund POST /api/v1/refund/token transaction.
POST /api/v1/sale, POST /api/v1/refund, POST /api/v1/authorization> and POST /api/v1/authorization/{transactionId}/incremental ,
the getToken : "OmniToken" value need to be provided.
getToken : "omniToken" , using the POST /api/v1/refund, will work only with Swipe entry mode in Debit Aid. getToken : "omniToken" , flag will also work with PR/QC transaction request. getToken : "omniToken" , is sent in the request triPOS would respond with the token details if recievied, inspite of the transaction being approved/declined. getToken : "omniToken" , is sent in the request of the transaction, but omniToken could not be created then triPOS would respond with error message. getToken is used and garbage value is sent in the request of the transaction, triPOS would respond with the exception message.
{
"laneId": "{{laneId}}",
"transactionAmount": "1.99",
"getToken" : "OmniToken",
"configuration":{"marketCode":"Retail", "checkForDuplicateTransactions":"false"}
}