My Oracle Support Banner

Patch 27584069 for Visa CIT/MIT Incorrectly Handled Storage of Transaction IDs (Doc ID 2419032.1)

Last updated on JULY 22, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.18.0 and later
Information in this document applies to any platform.

Symptoms

After installing patch 27584069-7.5PS18-linux, there is a problem in the following scenario.

1.  When creating a new account with a recurring charge, it resulting in a Customer Initiated Recurring (CREC) transaction.
     A transaction array element is added to the payinfo object with mode 4 (CREC):

op_pymt_charge_cc result flist
# number of field entries allocated 20, used 3
0 PIN_FLD_POID           POID [0] 0.0.0.1 /account 10000102651 0
0 PIN_FLD_CHARGES       ARRAY [0] allocated 20, used 4
1     PIN_FLD_RESULT         ENUM [0] 0
1     PIN_FLD_TRANS_ID        STR [0] "T1,d,0"
1     PIN_FLD_INHERITED_INFO SUBSTRUCT [0] allocated 20, used 1
2         PIN_FLD_CC_INFO       ARRAY [0] allocated 20, used 12
3             PIN_FLD_ADDRESS         STR [0] "Gd1\r\nGD"
3             PIN_FLD_CARD_TYPE      ENUM [0] 0
3             PIN_FLD_CITY            STR [0] "ZAMA CITY"
3             PIN_FLD_COUNTRY         STR [0] "Canada"
3             PIN_FLD_DEBIT_EXP       STR [0] "XXXX"
3             PIN_FLD_DEBIT_NUM       STR [0] "XXXX"
3             PIN_FLD_NAME            STR [0] "test payment"
3             PIN_FLD_STATE           STR [0] "AB"
3             PIN_FLD_ZIP             STR [0] "T0H 4E0"
3             SIR_FLD_CARD_TYPE      ENUM [0] 1
3             SIR_FLD_CC_MONITOR_STATUS   ENUM [0] 0
3             SIR_FLD_DOB_STR         STR [0] ""
1     PIN_FLD_PAYMENT      SUBSTRUCT [0] allocated 20, used 4
2         PIN_FLD_PAYMENT_RESULT   ENUM [0] 0
2         PIN_FLD_DESCR           STR [0] "Credit Card Payment"
2         PIN_FLD_INHERITED_INFO SUBSTRUCT [0] allocated 20, used 1
3             PIN_FLD_CC_INFO       ARRAY [0] allocated 20, used 4
4                 PIN_FLD_RESULT         ENUM [0] 0
4                 PIN_FLD_VENDOR_RESULTS    STR [0] "VC=100   &SR=S&AVS=I3"
4                 PIN_FLD_AUTH_CODE       STR [0] "pinXXX"
4                 PIN_FLD_AUTH_DATE       STR [0] "   180"
2         PIN_FLD_TRANSACTIONS  ARRAY [0] allocated 20, used 3
3             PIN_FLD_TRANS_ID        STR [0] "130121024311123"
3             PIN_FLD_MODE           ENUM [0] 4        ------------> payinfo object with CREC(mode 4)
3             PIN_FLD_FLAGS           INT [0] 1
0 PIN_FLD_BATCH_INFO    ARRAY [0] allocated 20, used 3
1     PIN_FLD_BATCH_ID        STR [0] "T1,d,0"
1     PIN_FLD_POID_VAL       POID [0] 0.0.1.1 /_cc_db -1 0
1     PIN_FLD_RESULT         ENUM [0] 0


2.  When the account cycles for the first time, a Merchant Initiated Recurring (MREC) transaction is sent to PaymenTech, and PaymenTech returns a new transaction ID.
     This transaction ID is now also stored as an array element on the payinfo object with the mode set to 5 MREC transanctions.

op_pymt_charge_cc result flist
# number of field entries allocated 20, used 3
0 PIN_FLD_POID           POID [0] 0.0.0.1 /account 10000102651 0
0 PIN_FLD_CHARGES       ARRAY [0] allocated 20, used 4
1     PIN_FLD_RESULT         ENUM [0] 0
1     PIN_FLD_TRANS_ID        STR [0] "T1,e,0"
1     PIN_FLD_INHERITED_INFO SUBSTRUCT [0] allocated 20, used 1
2         PIN_FLD_CC_INFO       ARRAY [0] allocated 20, used 12
3             PIN_FLD_ADDRESS         STR [0] "Gd1\r\nGD"
3             PIN_FLD_CARD_TYPE      ENUM [0] 0
3             PIN_FLD_CITY            STR [0] "ZAMA CITY"
3             PIN_FLD_COUNTRY         STR [0] "Canada"
3             PIN_FLD_DEBIT_EXP       STR [0] "XXXX"
3             PIN_FLD_DEBIT_NUM       STR [0] "XXXX"
3             PIN_FLD_NAME            STR [0] "test payment"
3             PIN_FLD_STATE           STR [0] "AB"
3             PIN_FLD_ZIP             STR [0] "T0H 4E0"
3             SIR_FLD_CARD_TYPE      ENUM [0] 1
3             SIR_FLD_CC_MONITOR_STATUS   ENUM [0] 0
3             SIR_FLD_DOB_STR         STR [0] ""
1     PIN_FLD_PAYMENT      SUBSTRUCT [0] allocated 20, used 4
2         PIN_FLD_PAYMENT_RESULT   ENUM [0] 0
2         PIN_FLD_DESCR           STR [0] "Credit Card Payment"
2         PIN_FLD_INHERITED_INFO SUBSTRUCT [0] allocated 20, used 1
3             PIN_FLD_CC_INFO       ARRAY [0] allocated 20, used 4
4                 PIN_FLD_RESULT         ENUM [0] 0
4                 PIN_FLD_VENDOR_RESULTS    STR [0] "VC=100   &SR= &AVS=I1"
4                 PIN_FLD_AUTH_CODE       STR [0] "pinXXX"
4                 PIN_FLD_AUTH_DATE       STR [0] "   180"
2         PIN_FLD_TRANSACTIONS  ARRAY [0] allocated 20, used 3
3             PIN_FLD_TRANS_ID        STR [0] "121433213311421"
3             PIN_FLD_MODE           ENUM [0] 5   ---------------------> payinfo object with MREC(mode 5)
3             PIN_FLD_FLAGS           INT [0] 1
0 PIN_FLD_BATCH_INFO    ARRAY [0] allocated 20, used 8
1     PIN_FLD_SUBMITTER_ID    STR [0] "pin_collect"
1     PIN_FLD_STATUS_FLAGS    INT [0] 1
1     PIN_FLD_BATCH_ID        STR [0] "T1,e"
1     PIN_FLD_SEPARATOR       STR [0] ","
1     PIN_FLD_POID_VAL       POID [0] 0.0.1.1 /_cc_db -1 0
1     PIN_FLD_CHANNEL_ID      INT [0] 0
1     PIN_FLD_BATCH_TOTAL  DECIMAL [0] 0
1     PIN_FLD_RESULT         ENUM [0] 0


There should be no redundant transaction ID stored for the corresponding CREC mode.

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.