Last updated on NOVEMBER 07, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Checked for relevance on 7-Nov-2016.
pin_collect/dm_fusa was sending a batch request to Paymentect. Paymentech was acknowledging the request and successfully processing them. However, pin_collect/dm_fusa was reporting an "unexpected EOF" when trying to get the response file.
Paymentech indicated that the necessary RFR were not sent as part of the 2-call protocol. The 2-call protocol was what the BRM documentation stated should be set up, but pin_collect/dm_fusa was not honoring this protocol.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms