Error Scenarios

Merchant POS/PMS applications must be able to handle the following error scenarios.

• If a token is not in the enterprise Token Database and the tokenization provider is no longer available (such as Protegrity Universal tokens), an Error of “Token Not Found” will be returned. This can occur if the token provided from Merchant POS/PMS application is incorrect or invalid, applications would need to acquire the card data from the card holder again and request a new token for further processing.

• If a token is generated that is the same value as an existing token, an Error of “No Found – Re-enter” will be returned. Merchant POS/PMS applications would need to resubmit the token request. This would be considered a token collision and is a very rare situation.

Fusebox response codes are populated by the appropriate third party processor interface. For any error that is internal to Fusebox, the response codes that are generated do not originate from the processor.

Response codes for API 1003 and Response API 1010 include:

• previousExample Transactions
• nextRetail