This section describes the steps that you must complete to process credit card transactions and payments in Receivables.
Prerequisites
Set up Oracle Payments.
Define remittance banks.
If an existing remittance bank allows credit card processing, then you may only need to update an existing bank record.
See: Bank Account Model Overview, Oracle Cash Management User Guide.
Define a receipt class and associated receipt method to determine the processing steps for your credit card transactions.
Note: To use credit card refund functionality, use a receipt class on credit card transactions where the remittance method is Standard and the Require Confirmation option is No.
A transaction can be paid via the Automatic Receipts program, if its assigned receipt method is associated with a receipt class that has an Automatic creation method. See: Receipt Classes.
Alternatively, you can assign an automatic receipt method directly to a manual receipt, manually apply transactions to the receipt, and submit the Automatic Remittances program to authorize and capture the credit card payment. See: Creating Manual Receipts.
When defining your credit card receipt method, select an Oracle Payments credit card payment method. See: Receipt Methods.
Define a document sequence for your credit card transactions, then assign this sequence to your credit card document category. The credit card document category is automatically created when you create the credit card receipt method.
When defining a document sequence for credit cards, be sure to choose a sequence type of Automatic. See: Setting Up Document Sequences.
Define the following profile option.
Sequential Numbering: You must set this profile option to enable document sequencing. Document sequencing is required by the Automatic Receipts program to assign numbers to the credit card receipts. Set this profile option to Always Used or Partially Used.
Define customers who use a credit card as payment for open debit items (if these customers do not already exist in Receivables). See: Entering and Updating Customer Information.
Suggestion: For customers who always use a credit card as payment for open debit items, you should:
mark the credit card receipt method as primary, and
mark the credit card bank account as their primary bank account.
This lets Receivables use credit card bank information as the default when you enter transactions for these customers.
Create one active receivables activity using the Credit Card Refund activity type. You must include information about the Refund Clearing GL account when you define this receivables activity. See: Receivables Activities.
Define Credit Card Refund reversal reason lookups (optional). See: Defining Receivables Lookups.
On the original credit card transactions, use a receipt class with a remittance method of Standard.
If you later refund these payments, the credit card refund (negative miscellaneous receipt) inherits the remittance method from the original receipt.
On the original credit card transactions, use a receipt class whose Require Confirmation option is not selected. If the original credit card receipt requires confirmation, then you will not be able to create a credit card refund against that receipt.