My Oracle Support Banner

Settlement Transactions are Sent to the Payment System Using the Wrong Payment System Account (Doc ID 1406063.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Payments - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.


On : 12.1.3 version, FC Core

When attempting to run "Submit Offline Transactions" request,

BEPName : Verisign New
TangibleId : ONTXXXXXX
Currency : USD
Price : 19.99
PayeeId : pfp
Status : 0005 - BEP returned error
Error Code : 19
Error Msg :


NOTE: In some Payment Systems (ie PPG) the following errors have been reported for the same issue:  

- Error Msg : Auth Record Not Found!

status = 17

- Status 17 (Declined due to Insufficient Funds)

The issue can be reproduced at will with the following steps:
1. Create credit card order in Order Management
2. Generate Invoice for Order
4. Create automatic receipt batch
5. Create automatic remittance
6. Submit Offline Transactions request for capture, which gives error.

The issue occurs for Gateway payment systems, when multiple payment system accounts are defined.
When looking in the IBY_TRXN_SUMMARIES_TABLE, it is observed that the settlement transaction has a different value for the BEPKEY than the authorization.


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.