How To Decrypt And Unmask Standard Fields Using READ_FLDS Opcode
(Doc ID 1057872.1)
Last updated on MARCH 27, 2018
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 18-Oct-2011***
***Checked for relevance on 17-May-2013***
Checked for relevance on 07-April-2016
We have created a new payment method with 2 fields encrypted (a standard one PIN_FLD_DEBIT_NUM, a custom one MY_FLD_DEBIT_KEY).
When we do a PCM_OP_READ_FIELD from testnap we get:
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID  0.0.0.2 /payinfo/my/dd 98701 0
0 PIN_FLD_DD_INFO ARRAY  allocated 20, used 2
1 PIN_FLD_DEBIT_NUM STR  "XXXX"
1 MY_FLD_DEBIT_KEY STR  "75"
Only the custom field MY_FLD_DEBIT_KEY is decrypted and unmasked, while standard field PIN_FLD_DEBIT_NUM is returned obfuscated.
How to show the content of standard fields via the PCM_OP_READ_FIELD opcode ?
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