Implementing Credit Card Security Setup
You can ensure credit card security for your employees using the following two methods:
Table and application security.
Data masking.
To secure credit card information for your employees and the table and application level, it is recommended that you use this security protocol:
Set up table security on these tables, which are the only tables that contain credit card information:
The Credit Card Information table (F0075).
The Credit Card Transaction Interface table (F09E150) if your credit card company transfers transactions electronically.
The EDI Payment Order Remittance Advice - Outbound table (F47057) if you process payments using EDI.
Table security prevents access to credit card information for all users.
Set up exclusive application security for each table for these programs:
Secured Table
Exclusive Application Security
Reason for Access
Credit Card Information (F0075)
P09E122: Employee Credit Cards
P09E2011: Expense Entry
R47057: Copy to Outbound EDI Files
To give users access to their own credit card information.
To give the system access to retrieve the credit card address book number.
To retrieve the credit card number to process the payment using EDI.
Credit Card Transaction Interface Table (F09E150)
P09E150: Credit Card Expenses
R09E151: Credit Card Expense Purge
To give the employees access to their credit card transactions.
To give the system access to remove processed credit card transactions.
EDI Payment Order Remittance Advice- Outbound (F47057)
R47057: Copy to Outbound EDI Files
To write the credit card number to the F47057 table
Exclusive application security allows the programs that are necessary for processing reimbursements and EDI payments to have access to the necessary tables.
See JD Edwards EnterpriseOne Tools System Administration Guide.
In addition to table and application security, you can also employ data masking to protect credit card numbers from unauthorized viewers. This type of security is stipulated by PCI (payment card industry) rules.
Data masking is enabled using a display trigger that is associated with the data dictionary item. You can use this functionality to partially hide credit card numbers in web applications and reports. Use the LMASK display trigger to embed leading masks displayed as asterisks (*) in the data, in this case, the credit card number. In the mask parameter, you define how many trailing digits you want the system to display. For example, if you specify the number of trailing digits as four, the system masks all leading digits with asterisks and displays the last four digits. This example illustrates how the credit card number is displayed: **********1234.
When you enter a credit card number, the system applies the mask when you move to another field. Masking occurs at run time when the credit card number is displayed; in the database, the credit card number is not masked.