Submit Offline Transactions Request Finishes with Communication Error Even After Getting an Approval from the Gateway (Doc ID 3048976.1)

Last updated on SEPTEMBER 23, 2024

Applies to:

Symptoms

"Submit Offline Transaction" request logs (i.e. iby_af.log) show that the capture request is successfully approved by the Gateway Payment System Servlet with a message like "oapfstatus: 0000".

However the process finishes with a Communication Error and the capture transaction status (from table iby_trxn_summaries_all) is set to 1.

Relevant information from the log file:

STATEMENT:[iby.payment.VendorAdapter.oraDispatch]:
contacting BEP servlet using URL:
https://xxxx.xxx.com/oramipp_xxx
?OapfAction=oracapture&
OapfVoiceAuthFlag=Y&
OapfRetry=yes&
OapfCurr=USD&
OapfPrice=7.59&
OapfStoreId=xxxx&
OapfTransactionId=8379916&
OapfOriginalPrice=19.14&
OapfTrxnmid=11592543&
OapfNlsLang=&
OapfAuthCode=tst704&
OapfTrxnRef=&
OapfVoiceAuthDate=2024-09-05&
OapfOrderId=ONT1391365
[...]
STATEMENT:[iby.net.NetUtils.writeHttpPost]:phase 4: reading HTTP response
[...]
STATEMENT:[iby.net.NetUtils.parseHttpResponse]:raw header content:
HTTP/1.0 200 OK
oapfstatus: 0000  <<< This indicates that the transaction was approved by the Payment System
oapftrxntype: 8
oapftrxndate: 20240906071683
oapferrlocation: 0
oapfvenderrcode:
oapfvenderrmsg:
oapfrefcode: xxxx
Content-Type: application/java; charset=UTF-8
Content-Length: 0
Date: Fri, 06 Sep 2024 12:16:02 GMT
Connection: close
[...]
STATEMENT:[iby.net.NetUtils.parseHttpResponse]:header not well-formatted: HTTP/1.0 200 OK
[...]
EXCEPTION:[iby.scheduler.SchedCoreCC.schedPmt]:oracle.apps.iby.exception.CreditCardProcessorException: Communication error. The payment system, the processor, or iPayment electronic commerce servlet is not available/accessible. Please make sure you have the correct system set up and resubmit the request at a later time.
at oracle.apps.iby.payment.CreditCardProcessor.processTrxn(CreditCardProcessor.java:1165)
at oracle.apps.iby.payment.CreditCardProcessor.captureCC(CreditCardProcessor.java:2448)
at oracle.apps.iby.payment.CreditCardProcessor.perform(CreditCardProcessor.java:148)
at oracle.apps.iby.payment.OnlineCreditCardPayment.captureZero(OnlineCreditCardPayment.java:636)
at oracle.apps.iby.payment.OnlineCreditCardPayment.capture(OnlineCreditCardPayment.java:651)
at oracle.apps.iby.scheduler.SchedCoreCC.schedPmt(SchedCoreCC.java:343)
at oracle.apps.iby.scheduler.Scheduler.doProcess(Scheduler.java:307)
at oracle.apps.iby.scheduler.Scheduler.init(Scheduler.java:406)
at oracle.apps.iby.scheduler.SubmitOfflineTransactionsWkr.runProgram(SubmitOfflineTransactionsWkr.java:68)
at oracle.apps.fnd.cp.request.Run.main(Run.java:159)
[...]

Steps to reproduce

The issue can be reproduced at will with the following steps:

1. Enable the logs following instructions from Note 1635161.1, Section B.
2. Login with responsibility: Funds Capture Process Manager
3. Run request: Submit Offline Transactions.
4. Open the iby_af.log file (as per Note 1635161.1, Section B, Step 9.c).

Cause

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