Unable To Encrypt And Then Decrypt The Bank No Field In The /payinfo/cc
(Doc ID 2083660.1)
Last updated on AUGUST 17, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
The user needs to encrypt the Bank No and Debit Num field in the /payinfo/cc for data security purpose. The user is able to encrypt the Debit Num field but not the Bank No.
Steps followed are as below:
- Updated the table dd_objects_fields_t:
set field encryptable to 1 for field_name: PIN_FLD_BANK_NO, PIN_FLD_DEBIT_NUM
modify the length of Bank No. from 30 to 255
- Restarted CM and DM
- Created account and error occurs when executing pin_deploy replace for the payinfo/dd object
Error thrown is as below:
The requirement is to encrypt values for the field (DEBIT_NUM , BANK_NO) in the database by setting ENCRYPTED flag as 1. But the values need to be decrypted for sending to the 3rd party/Bank.
The current implementation exports the card details (which also has DEBIT_NUM , BANK_NO) to the 3rd party/BANK using a report, which queries the database directly using SQL, and the report is fetching encrypted values.
Can DBMS_CRYPTO be used to decrypt these fields?
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