In today’s digital landscape, ensuring secure and efficient payment processing is critical for businesses handling online transactions. Oracle Commerce Cloud (OCC) and Oracle E-Business Suite (EBS) offer a robust framework for managing credit card payments through a tokenization-based integration. This blog delves into the OCC to EBS payment processing flow, explaining the key steps, benefits, and technical considerations for handling transactions securely and efficiently.

Understanding Tokenization in OCC and EBS

One of the core aspects of this payment processing flow is credit card tokenization, which ensures that sensitive card details are never stored in raw format. Instead, a token (a unique identifier) replaces the card number, making transactions more secure and compliant with data protection regulations such as PCI DSS.

How Tokenization Works in OCC & EBS

• When a customer enters credit card details in OCC, the system generates a token instead of storing the actual card number.
• This token is then stored in OCC’s profile of the logged in user.
• The tokenized card information is securely transmitted to EBS, where it is used for payment processing and order remittance.
• Chase Paymentech API is used to process payments while ensuring security and fraud prevention.

Payment Flow for New Credit Cards

When a user enters a new credit card in OCC, the following steps ensure a seamless transaction experience:

1. Customer Input: User enters new credit card details at checkout.
2. Decision Point: System checks whether the user wants to save the card for future transactions.
3. OIC Endpoint Call: If saving is chosen, an OIC (Oracle Integration Cloud) call is made to create a credit card order.
4. Tokenization: The card is tokenized and stored securely in EBS TCA (Trading Community Architecture) Module.
5. Transaction Processing: OCC communicates with Chase Paymentech API to initiate payment remittance and receipts.
6. Order Completion: The transaction is completed, and the payment token is stored for reference.

Using Saved Credit Cards for Payments

For customers who have already saved their credit card information, the OCC to EBS payment flow is even more streamlined:

1. Card Selection: Customers choose a saved card during checkout (only the last four digits are displayed for security).
2. Token Retrieval: The token number linked to the saved card is retrieved from the EBS TCA Module.
3. Transaction Processing: OCC uses the token to process payments through Chase Paymentech API.
4. Payment Completion: The system verifies the transaction, processes the remittance, and finalizes the order.

EBS Credit Card Token Storage & Vaulting

How Tokens Are Managed in EBS

• Every new credit card entry creates an entry in EBS’s payment instrument table.
• The system checks if a matching token already exists to prevent duplication.
• A mod-10 algorithm generates a vault number, which is mapped to the token number.
• When a tokenized card is used for payment, the system retrieves the Instrument ID from the vault to process the payment securely.

Technical Considerations & API Integration

To enable smooth communication between OCC and EBS, the following API endpoints play a crucial role:

• Tokenization API: Generates and manages tokenized card details.
• OIC Endpoint Call: Handles secure data transmission between OCC and EBS.
• Chase Paymentech API: Processes payments while ensuring fraud protection.
• EBS Receivables Concurrent Program: Manages recurring payments using stored tokens.

Why This Integration Matters

• Enhanced Security – Tokenization ensures that sensitive card details are never exposed.
• PCI Compliance – Businesses remain compliant with payment security standards.
• Faster Transactions – Saved tokens reduce checkout friction, improving user experience.
• Seamless Data Flow – API-driven integration ensures smooth transaction processing between OCC and EBS.

The OCC to EBS payment processing flow is a well-structured, secure, and efficient approach to handling online payments. By leveraging credit card tokenization, OIC integration, and secure API calls, businesses can enhance security, improve transaction speed, and ensure compliance with global payment regulations.

Implementing this integration ensures that customers enjoy a smooth and secure checkout experience, while businesses benefit from efficient and secure payment processing.

Click here to learn more about this integration.

About Authorize.Net

Authorize.net is a payment gateway enables you to process payments in any way that works for your business, whether it’s through your website, mobile app, or manual transactions.

iBizSoft’s Oracle Commerce Cloud integration with Authorize.Net

Businesses require seamless flow of information and data throughout the organization. iBizSoft team has implemented integration of various Oracle Cloud applications with third party vendor applications. This article discusses one such integration between Oracle Commerce Cloud (OCC) and Authorize.Net Payment Gateway. OCC is a cloud-based e-commerce platform and Authorize.Net is a third party credit-card payment gateway. Shopping cart applications developed on OCC platform make credit card payments through Authorize.NET Gateway

There are two technical features that allow the integration between these two applications, WebHook in OCC and RESTful APIs from Authorize.NET Payment Gateway. When an OCC e-commerce shopping cart order is submitted for payment, the OCC platform calls the Web Service API configured in the WebHook for Payment Gateway. The Authorize.NET Payment Gateway processes this information and returns success or error message back to OCC. If the payment is successful, then OCC will continue completion of OCC order processing and send it for shipping. The order stays in an incomplete state, if there is an error when processing the Credit Cards. Highest level of security is maintained between the two applications. OCC is hosted on Oracle Cloud platform behind a firewall and communicates with third party applications using Secured Socket Layer (SSL) over HTTPS, wherein SSL encrypts data before transmitting the data within the cloud ecosystem. The receiving client decrypts this data with Private-Public key combination.

Click here to learn more about this integration