triPOS^®

OmniToken

triPOS continues to support OmniToken creation using the POST /api/v1/token/omni , POST /api/v1/token/omni/{transactionId} Endpoint. Now, OmniToken can also be created using the POST /api/v1/sale , POST /api/v1/refund , POST /api/v1/authorization and POST /api/v1/authorization/{transactionId}/incremental endpoints. 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.

• To complete a Sale, Authorization, or Refund using an OmniToken the tokenId, tokenProvider, and cardLogo need to be provided as a replacement for the card data that would normally be acquired through the PIN pad.
• To create the OmniToken directly using the POST /api/v1/sale, POST /api/v1/refund, POST /api/v1/authorization and POST /api/v1/authorization/{transactionId}/incremental the getToken value need to be provided.
• The expirationMonth and expirationYear fields are optional but are recommended to prevent fraud.
• Currently a request made to POST /api/v1/refund/token will always approve no matter the tokenId provided. This is because a refund is considered an offline transaction on Express and there is no validation of the tokenId. It is very important that the tokenId is known to be valid to avoid the transaction failing during settlement.
• Currently POST /api/v1/reversal/{transactionId}/{paymentType} may return the same OmniToken if the OmniToken was previously generated in using the original transaction with respect to the transactionId.

---