Pin_deposit Issues Command "Auth And Deposit" To Chase PaymentTech
(Doc ID 2161081.1)
Last updated on JANUARY 16, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM), 22.214.171.124.0 version, Paymentech Manager, the 'pin_deposit' utility issues command "auth and deposit" to Chase PaymentTech.
The user have enabled tokenization for CC and DD payment processing. When CC online payment processing is done, PCM_OP_PYMT_COLLECT is submitted with PIN_FLD_COMMAND = 2 (PIN_CHARGE_CMD_AUTH_ONLY) and authorized successfully. Later pin_deposit was executed, to deposit the payments.
Here the 'pin_deposit' executed successfully and payments were received. However, Chase Payment tech confirmed that the transaction file was sent in as below,
Need confirmation if this is the normal behavior of the pin_deposit to send action type as "Validate and deposit" for PIN_CHARGE_CMD_DEPOSIT in BRM. Why re-authorize the transaction during deposit?
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