Incorrect Response Codes Returned By Payment Opcode (Doc ID 1401725.1)

Last updated on JUNE 21, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.
Checked for relevance on 18-Oct-2013

Symptoms

During upgrade from BRM 7.3.1 to 7.4 version, payment opcode does not return proper response codes.

Steps to reproduce:

1. Configure answer simulator to return specific response codes like 401 for some cards and 100 for few others.
2. Put together few credit card accounts that use these cards and generate a bill for each with some due amounts.
3. Do pin_collect on them (pin_collect -active -pay_type 10003 -vendor fusa -verbose)
4. The response codes are not mapped appropriately to the corresponding transactions.

cm.pinlog shows that the opcode PCM_OP_PYMT_CHARGE_CC mismaps payment responses returned by the dm_fusa. It alters the VC code to transaction returned by the dm_fusa.

For example the response returned by the dm_fusa (answer) for transaction-ID "U1,U6,7" is
"VC=401" whereas the CHARGES array [10] for the same transaction has a wrong VC code "VC=100".

0 PIN_FLD_RESULTS ARRAY [4] allocated 20, used 5
1 PIN_FLD_TRANS_ID STR [0] "U1,U6,7"
1 PIN_FLD_AUTH_CODE STR [0] "pinXXX"
1 PIN_FLD_AUTH_DATE STR [0] "230127"
1 PIN_FLD_VENDOR_RESULTS STR [0] "VC=401 &SR= &AVS=I1"
1 PIN_FLD_RESULT ENUM [0] 7

0 PIN_FLD_RESULTS ARRAY [10] allocated 20, used 5
1 PIN_FLD_TRANS_ID STR [0] "U1,U6,1"
1 PIN_FLD_AUTH_CODE STR [0] "pinXXX"
1 PIN_FLD_AUTH_DATE STR [0] "230127"
1 PIN_FLD_VENDOR_RESULTS STR [0] "VC=100 &SR= &AVS=I1"
1 PIN_FLD_RESULT ENUM [0] 0

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms