My Oracle Support Banner

Re-Authorization Is Happening While Payment Capture For Already Authorized Transactions (Doc ID 1323659.1)

Last updated on APRIL 05, 2021

Applies to:

Oracle Order Management - Version and later
Information in this document applies to any platform.
Payment Capture


Customer is using a custom built ECOM shopping cart where the credit card is pre-authorized for the order amount using the existing cybersource setup then the approved transactions are imported in to Oracle.
During the order import we populate the IBY tables( IBY_TANGIBLE, IBY_TRXN_SUMMARIES_ALL, IBY_TRXN_CORE) and the cybersource tables (CYS_RESPONSE, CYS_RESPONSE_ITEM) using the custom wrapper.
When the order is booked and progressed to invoice, we do not see any issues in iPayment server to create bank accounts etc.
When we create a Receipts the iPayment server just ignores the existing approval and tries to re-authorize the transaction.

The same process used to work before with out triggering re-authorization
The profile "OM:Estimated Authorization Validity Period " is set for 21 days, so expiration of auth is not an issue.

Is there any way we could turn-off the re-authorization based on the transaction type and instruct iPayment engine to directly capture the payment when there is a approval code already populated in the system ?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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