Oracle Payments Minimum/Dummy Setup For Credit Card/Purchase Card Funds Capture Processing (Doc ID 553614.1)

Last updated on OCTOBER 04, 2023

Applies to:

Purpose

11i Oracle iPayment is replaced with a brand new product called Oracle Payments in Release 12. This new product has extended functionality for funds capture (inbound payments) and funds disbursement (outbound payments) processing. In Release 12, upstream applications such as Order Management, Oracle Receivables and Oracle Payables have mandatory dependency on Oracle Payments implementation. For funds capture processing, minimum implementation of Oracle Payments is required even if real time payment processing functionality is not used. If real time payment processing functionality is used, extensive setups as outlined in Oracle Payments implementation guide are needed. This note will document the setup's needed in Oracle Payments for merchants implementing funds capture without using real time Credit Card processing. If these setups are not performed, receipt and remittance batches will fail with errors. 

Scope

Existing 11i customer had the ability to configure receipt class/method in such a way that realtime payment processsing can be turned off. This was done by setting payment type and merchant_ref to null. In Release 12, merchant_ref was obsoleted and replaced with Payment Method, created in Oracle Payments. This payment method is mandatory. Therefore merchants implementing Release 12 will need to perform following dummy setups in Payments to successfully process receipt and remittance batches using credit card payment method.

Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.