Common Elements Used to Process Credit Cards

Field or Control

Definition

Authorization

Funds are reserved against a specified credit card. An authorization number is obtained for the current amount being authorized. No actual charges take place against the credit card.

Auth Date/Time, Authorization Date/Time, and CrCardAuth Dt (credit card authorization date)

Reflects the date and time the transaction was authorized plus the expiration days. If a transaction is denied, then no date appears. The authorization is only valid for the number of days you entered on the Credit Card Type page. The Return Code is a reason code defining why a transaction is denied. These fields are populated automatically after a successful processing call to the credit card authorization and payment application.

Bill

Funds are charged to the credit card. All bill transactions must be preceded by an authorization. Both an authorization and a bill can be issued at the same time.

Credit

Funds are credited back to a specified credit card.

Credit Card Address
Credit Card Auth Status (credit card authorization status)

The current state of authorization for the credit card transaction.

Credit Card Auth Codeand CrCdAuthCd (credit card authorization code)

The approval code assigned to this transaction upon authorization or billing.

Credit Card First Name

If the name on the card includes a middle initial, include the middle initial after the first name in this field.

Credit Card Group

Supports multiple credit card types associated with multiple payment processors saved in a group. The grouping can be utilized by the FSCM modules to limit or control which credit card types and payment processors are available for transactions.

Credit Card Number

The system validates credit card numbers as you enter them. If you enter a number that does not match the parameters set up for the card type on the Credit Card Type page, then you receive an error message and will not be able to save the page until you correct the error. The validation is:

  • The number of digits. You cannot save a card number of 17 digits for a card type that requires 16.

  • The prefix of the credit card number. You cannot save a card number with a prefix of 1234 for a card type that requires a prefix of 5678.

  • The card number is valid. You cannot save a card number that is not a valid credit card number. The system does a check digit algorithm on the number you enter to ensure that it is valid for the credit card type you are entering.

Credit Card Profile

Provides support for the hosted payment and storage model in the PeopleSoft system. PeopleSoft uses two types of profiles: permanent and temporary.

  • A permanent profile refers to credit card data that will be stored in the hosted system for a contact and remains on file until the contact or CSR chooses to remove the card information.

  • A temporary profile refers to credit card data that remain in the system and are saved in a table. Temporary profiles are purged based on the settings selected on theCredit Card Options Page

    See Setting Up Credit Card Options and Groups.

Profiles are represented by a token ID (or subscription ID) that is assigned by the hosted system. The PeopleSoft system stores this token ID to represent the card data. See also Tokenization.

Credit Card Types

Oracle delivers data for most popular credit card types. You can define the types of credit cards that you accept for credit card processing by modifying existing definitions or adding new ones on the Card Type page (Enterprise Components > Component Configurations > Credit Card Interface > Credit Card Types). See Card Type Page.

Email Address

Third-party credit card authorization and payment applications often require an email address and telephone number. If the customer does not have an email address or does not want to supply this information, then you must enter a dummy email address.

Last Four Digits

This field displays the last four digits of a credit card number and is used as part of the Credit Card Profile for a token ID that helps identify transactions processed in a hosted credit card implementation.

Message 1, Message 2, and Message 3

Display the processing history for the transaction. The prefix ICS denotes a message originating from the third-party credit card authorization and payment application. These messages appear automatically after an attempt to process this transaction by the third-party application. This information is written to the Credit Card History table.

If you make a change to payment terms, Oracle recommends that you clear the messages and enter comments to maintain an audit trail for the transaction.

Request ID

A number assigned by the third-party credit card authorization and payment application to identify this processing transaction.

Sequence or Seq. Nbr (sequence number)

A unique identifier assigned to each line charge in these tables: INTFC_CRCARD for PeopleSoft Order Management and Billing transactions; CRCARD_AR_HST for PeopleSoft Receivables transactions.

Tokenization

Supports the collection and storage of credit card information on PeopleSoft Order to Cash systems that use a hosted credit card implementation. See also Credit Card Profile.