Use Credit Card Tokenization (L18) | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Tokenization IJCT Job (L41) |
Require Credit Card Token (L40)
Purpose: When using Credit Card Tokenization, defines whether the system will accept a credit card number that has not been replaced with a token.
Yes/No field: Select this field to require a token for a credit card number. This ensures that credit card numbers are never stored in the Order Management System database and follows full PCI compliance and maximum security of sensitive data.
If the Credit Card Tokenization Process is unable to replace the card number with a token, the system:
• During interactive Order Entry/Maintenance, Customer Membership, and Change Invoice Payment Method: displays an error message, requiring you to enter a different form of payment.
• During web order processing: replaces the credit card number with the text TOKENIZATION FAILED and places the order in an error status with the reason Invalid Credit Card. You can correct the credit card payment method and resend the card for tokenization in batch order entry.
Unselect or leave this field blank to allow the system to accept a credit card number that has not been replaced with a token.
Note: The system evaluates this system control value only if the Use Credit Card Tokenization (L18) system control value is selected.
Encryption: If you use Use Credit Card Encryption (I97), the system encrypts the number stored in the Credit card number field in the Order Management System database; see the Data Security and Encryption Guide.
For more information: See Credit Card Tokenization in the Data Security and Encryption Guidefor an overview and processing details.
Use Credit Card Tokenization (L18) | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Tokenization IJCT Job (L41) |
IN03_08 OMSCS 18.1 April 2019 OTN