DI SAP No SSO - Version 1

• Integration Methods

• Token Retrieval Methods

• What You Need to Know to Use Intercept for SAP

• Token Retrieval Procedures

• General Notes About the Intercept WebGUI

This section is ONLY applicable for existing Clients that implemented Intercept SAP WITHOUT single sign-on (SSO) – (Intercept SAP version 1).

The procedure for generating and/or retrieving tokens using Intercept for SAP first requires some knowledge of how the feature is implemented. It is recommended that you review this entire section at least once to gain an understanding of how it works and the information you need from your System Administrator to use Intercept for SAP.

The Data Intercept (Intercept) for SAP solution allows you to integrate SAP with the Intercept-SA WebGUI to obtain tokens so that credit card numbers are never entered in your SAP systems. There are multiple ways to integrate Intercept-SA with SAP and multiple configuration options to affect how the tokens are retrieved.

This section contains the following topics on how to use Intercept for SAP and Intercept-SA. Basic integration information is provided so you will understand the information you need from your System Administrator in order to use this functionality.

Integration Methods

For more information on how Intercept for SAP can be integrated with Intercept-SA WebGUI, see Intercept SAP No SSO - Integration Methods.

Token Retrieval Methods

For the various methods that can be configured to obtain a token and place it in the credit card number field, see Intercept SAP No SSO - Token Retrieval Methods.

What You Need to Know to Use Intercept for SAP

For a summary on the information you need from your System Administrator to use Intercept for SAP without SSO, see Intercept SAP No SSO - What You Need to Know to Use.

Token Retrieval Procedures

For step-by-step procedures on how to obtain a token for each combination of integration and retrieval method available, see Token Retrieval Procedures.

General Notes About the Intercept WebGUI

• Your Organization Administrator may have Card Type enabled in which case you will also see a Card Type drop-down field in addition to the Credit Card Number field.

• A Luhn check is performed when you click the Generate Token button unless it is disabled by your Organization Administrator. If the Luhn check is enabled and you are tokenizing an eCheck account number or non-standard credit card, you will receive an error message that the number is not valid. Contact your Intercept-SA Organization Administrator.