Questions About Credit Card Expiration Date Format Supported by BRM
(Doc ID 1624881.1)
Last updated on JULY 23, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
Checked for relevance on 27-Nov-2017.
This note clarifies some questions about the credit card expiration format used by the Billing and Revenue Management (BRM) software related to the Paymentech (Credit Card Processing system) integration.
Other integration elements with BRM usually use the MMYYYY format for credit card expiration as opposed to the current MMYY format.
To avoid having to adapt the precision from MMYY to MMYYYY when BRM requests or notifies other systems, one can customize payinfo_cc_t.debit_exp to store the credit card expiration date as MMYYYY.
The BRM elements related to Paymentech would be impacted by that data format change.
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
|Questions and Answers|
|Will Oracle BRM supports this customization as a better design to store the credit card expiration date as MMYYYY without future patch to cause a problem ?|
Since it is within the customization of policy opcodes, would Customer Center not properly work ?