Yes, CardConnect is an Oracle Gold Level Partner. Details about our validation are available on our Oracle Partner Network page.

Oracle includes several reports that provide valuable detail regarding transactions. We recommend using the following reports:

• Automatic Receipt and Remittance Execution Report
• Automatic Receipt Batch Management Report
• Remittance Batch Management Report
• Automatic Receipt Awaiting Confirmation Report
• Transaction Awaiting Consolidation Report
• Unapplied and Unresolved Receipt Register
• Receipts Awaiting Remittance Report
• Transaction Summary Report

In addition, as part of the Oracle R12 CardConnect solution, you will receive a report to view the data points from Order Management, Accounts Receivables, and CardConnect specific details.

The CardPointe Web App and CardPointe Gateway API provide additional reporting and transaction management utilities.

A token is the replacement of the sensitive data with a non-sensitive representation of that data point.

We offer customers the option to have persistent tokens. This reuses the same token every time the card is used.

For our SAP customers, we offer one-time use tokens. This generates a new token each time the card is used.

P2PE (point-to-point encryption) is an encryption standard established by the Payment Card Industry (PCI) Security Standards Council. In a P2PE solution, data is encrypted at the point of interaction (for example, a card reader device) and remains encrypted until it reaches the payment processor. Visit the PCI Security Standards Council's Point-to-Point Encryption (P2PE) Solutions page for more information.

Capturing card data using a P2PE validated device like the SREDkey can greatly increase security, as well as potentially reduce your organization's PCI scope.

The steps required to process the Capture for a transaction are:

• Automatic Receipt Master Program
• Automatic Remittance Master Program
• Funds Capture Process (included in the Remittance Master Program for 11i).

This is standard functionality and more details on the flow are available at Oracle's Document Library. We suggest reviewing the following Oracle documents:

• Oracle Receivables User Guide
• Oracle Receivables Implementation Guide

Yes, CardConnect's solution includes a feature that you can implement in your Oracle R12 system to restrict credit card numbers from being entered into the credit card number field, and to only allow tokens to be entered into that field.

The Web Tokenizer can be accessed via a merchant’s web browser by entering a card number into the web application screen and invoking an HTTPS call to the CardSecure server to tokenize the card number and utilizing java code the token value is posted back into the Oracle system.

No, CardConnect’s Validated Integration utilizes the standard credit card column in Oracle and replaces it with a token, and then this value passes over the standard Oracle Gateway Technology.

Please reference Oracle's Document Library and review the following documents:

• Oracle Receivables User Guide

• Oracle Receivables Implementation Guide

When an order begins in Order Management, it authorizes in real-time using Oracle Payments once the order is booked. When an order originates in Receivables, it uses Oracle Payments to capture the required payment details to obtain an authorization. For more details, please refer to Oracle's Payments User Guide.

An authorization will validate that the funds are available to be used and hold the funds for five days. If the funds are not captured in five days, the processor will release them. These are standard credit card processing guidelines.

Authorizations for Visa, Mastercard and Discover cards remain valid for 7 days, while authorizations for American Express cards remain valid for 30 days.

While authorizations remain valid for the periods specified above, transactions are more likely to encounter higher transaction fees as the time between authorization and capture increases. We recommend to capture funds for card-present transactions (cards swiped or inserted into a card reader device) within 24 hours, and capture funds for card-not-present transactions (card data manually entered using Web Tokenizer, iFrame Tokenizer, or SREDkey keypad) within 72 hours to avoid interchange downgrades.

Oracle Payments no longer supports void transactions, so in order to void authorization requests the system will submit a modified authorization request to change the authorization amount to zero dollars to release the funds. This feature is available for customers who run Oracle 12.2 as the feature is not available for Oracle 11i or 12.1.3. Oracle customers on 11i or 12.1.3 these customers can utilize the CardConnect UI to void the authorization or the can utilize the Oracle functionality to cancel the line, which will ensure that the transaction is not captured but it will leave the authorization open until it expires. It's important to note void transactions can take a few days to complete the void on the card holder cards depending on the processor.

As part of the Oracle configuration, the customer creates a new receipt method in Accounts Receivable. This receipt method defines the general ledger accounts that each transaction in the credit card process should use.

CardConnect typically sees the following General Ledger’s used:

• Pending Accounts Receivable (AR)
• Cash In Transit
• Cash on Hand

The following Accounts Receivable steps must be completed to submit a credit card for capture:

• Automatic Receipt Master Program
• Automatic Remittance Master Program
• Submit Offline Transactions
  • Submit Offline Transactions is only required for Oracle R12 Customers. Oracle 11i includes this step as part of the Automatic Remittance Master Program.

Oracle allows you to create a credit memo and apply the necessary invoice(s) to this credit memo. Once the credit memo is created, it will run through the remaining out of the box programs to complete capture steps for receipt, remittance, funds, and capture.

Oracle allows the receipt method to be updated and the credit card payment instrument and details to be applied, once this occurs and the invoice is eligible for capture the receipt will be created and submitted through the remaining steps to capture. Eligible invoices mean that their due date less than or equal to today’s date.

Yes, Oracle will manage this incremental change via a new receipt for that amount. To capture the additional funds, the invoice will only be for the full amount.

Oracle allows the customer to create a credit memo and apply the necessary invoice(s) to this credit memo. Once the credit memo is created, it will run through the remaining out of the box programs to complete capture steps for receipt, remittance, funds, and capture.

Yes. For those who are eligible, CardConnect offers the CardDeposit feature. CardDeposit provides an automatic reconciliation process as a replacement to the time-consuming and error-prone process of manual reconciliation.

Contact your sales representative for more details.

It means that the receipt has not yet been sent for Capture. The following scenarios may apply to the transaction:

• The Automatic Remittance Master Program has not yet processed the receipt.

  -or-

• The receipt is in error and is waiting for a team member to review. These errors can be managed from the Menu function "Correct Funds Transfer Errors" (Oracle R12) or "Correct Credit Card Errors" (Oracle 11i).

  It's a best practice to review errors on a daily basis to align with the concurrent programs running to create new receipt.