Failure Tokens

If SAP is unable to reach XiSecure On-Demand (e.g. an outage or connectivity problem), merchant's have the option to implement failure tokens. Note that failure tokens are only relevant to SAP.

Failure tokens are unique identifiers that can be generated and saved in your SAP tables should there be a communication issue with XiSecure. Failure tokens contain a 'PMOS' prefix. The PMOS failure token and raw card number are saved in the XiSecure /PMENC/PFAIL table. A background program is scheduled to run daily that executes the tokenization process and updates the raw card number in the /PMENC/PFAIL table with a standard token. This table maintains the reference point between the failure token in the SAP tables and the standard token in the XiSecure database.

If you have the Paymetric Failure token Logic (Processing Option A in the /n/PMENC/BIMG) engaged, then failure (PMOS) tokens will be generated in the SAP tables during a XiSecure outage or RFC connectivity problem. This allows order processing to proceed in the event of a tokenization interruption.

The Resubmit Encryption Failures program (accessed from the BIMG) should be scheduled as a regular batch job to ensure the failure tokens' encrypted strings are tokenized in the PFAIL lookup table.

PMOS tokens will not convert in the SAP tables - they always remain PMOS tokens. The Resubmit Encryption Failures program (tcode /PMENC/FAIL) will convert records only in the /PMENC/PFAIL lookup table.

Check with your system administrator to determine if your organization implemented failure tokens and if not, determine your process should SAP have problems connecting to XiSecure On-Demand.