Oracle Retail Order Management uses payment methods that are identified with unique integers. For integration, Commerce Cloud Payment Methods are mapped to Oracle Retail Order Management numeric payment methods.
You can obtain a list of the payment methods available by calling the following endpoint:
GET /ccadmin/v1/merchant/paymentGatewaysThis returns a list of available payment methods. The response also includes the ID of the merchant, whether the method has been enabled, and the repository ID of the payment method. The repository ID identifies the payment method code to use. The following example displays a partial response that identifies a CyberSource payment method:
{
"paymentGateways": [
{
"sopCredentials": {
"storefront": {
"sopURL": "http://10.101.101.101:8080/ccstoreui/v1/PM/cybersourceSOP",
"expirationDate": "2019-01-28T11:54:30.207Z",
"profileId": "Admin",
"applicationName": "storefront",
"hasSecretKey": true,
"hasAccessKey": true,
"repositoryId": "SOP-A"
},Once you have obtained the repository ID, use it to map the payment method:
As orders are created in Commerce Cloud and passed to Oracle Retail Order Management, the payment mappings are passed to Oracle Retail Order Management for fulfillment and settlement with the required payment gateways.
Note: To ensure PCI compliance, no credit card or gift card numbers are sent to Oracle Retail Order Management. The transaction reference and the authorization ID are sent with the order.
Payment Gateways
Commerce Cloud has preconfigured integration with Chase and CyberSource payment gateways. By default, the CyberSource payment gateway is selected for the integration. The Oracle Retail Order Management System requires credit card or gift cart numbers to be provided when using the Chase gateway, however, Commerce Cloud does not store credit cards and cannot provide them. As such, Chase credit cards and gift cards are not supported with this integration. Oracle Retail Order Management supports CyberSource and PayPal gateways by default.
Note: When using the CyberSource payment gateway, you must provide the AuthNumber for reauthorization and settlement. Because Commerce Cloud does not store the AuthNumber, the field is set to NA by default. You must update this field with the AuthNumber values for the CyberSource gateway.
To configure integrations with other order processing systems, use the Generic Payment Framework, as described in Extending Oracle Commerce Cloud Service. Generic payment is not supported by default; however, Oracle Retail Order Management APIs can support sending payment details separately for an order. Whenever a generic payment is used in Commerce Cloud, payment details are not sent and the order is put into an error state. Once you update the payment details for the order, the Oracle Retail Order Management System changes the order to an open state.
External Pricing
Note that this integration does not support external pricing. If you are using a combination of external prices and sale prices from Commerce Cloud, this integration will average the prices of items of the same SKU. For example, a customer qualifies for a promotion in Commerce Cloud that enables him to purchase 5 hats for the sales price of $5 each, instead of the list price of $6. If the customer wants to buy 10 hats, in Commerce Cloud, 5 of the hats would be sold at $5 and 5 of the hats would be sold at $6 for a total of $55. Oracle Retail Order Management does not differentiate between the price lists. Instead, it averages the final price between all of the hats, therefore all 10 hats are priced at $5.50 each for a total of $55. This may impact return processes, as in the above example, the return price of a hat would be $5.50 and not $5 or $6.
Payment Types
Payment Types are set up and configured using the Payment Processing setting and the Payment Types tab, which is described in the Using Oracle Commerce Cloud Service documentation. For information on Oracle Retail Order Management payment types, refer to the Oracle Retail Order Management documentation.
