Credit Card Order Management

In this post I will explain in detail about the new changes that Oracle made in R12 about handling of the credit card transaction. Oracle has made significant changes in R12 about handling of Credit Card Transaction.

To begin with now in R12 Order Management “Credit Card Type “ will be refer as “Card Brand”, also we need to enable OM profile OM: Credit Card Privileges, in order to enter credit card information in Sales Order and Payments form.

With R12 onwards OM will not store any of the Credit card/Bank Account related Information in it’s tables, all the credit and Bank related information will be encrypted and stored in a centralized system (i.e. Payments). This would give enhanced security and control over such critical information.

Order Management has to link to these table to retrieve the related information.

NOTE – we can still see the Credit Card related fields in OE_ORDER_HEADERS_ALL in R12, but OM don’t store any of the credit card information in these tables and these are their for Backward compatibility.In orders to protect their customer from Credit frauds (mostly when Credit Card is not Physically Present (Online/Over the Phone) credit card companies has provide the security code to enhance the security. In R12 Order management, Oracle has provide the field to capture the Security Code for the Credit card, value in this field will not be store any where in the system.

Security Code – It is 3 or 4 digit code provide by credit card companies, and we call it CCV/CCV2

As shown below, I have define the Security Code Setup as mandatory in Payments and also in the Masking Rules I have set “Display only last 4 Digits”



Once the Security Code set as mandatory, OM UI’s will mark the security Code filed as required field. But if it is not defined as mandatory in Payment Module, It remains options in Order Management.



Below are examples of the Billing Address is define as mandatory in Payments and user try to process the Orders without providing Billing details.







Security Code mandatory setup
Security Code is not a mandatory field, depending on your requirement you can make it required or option from the Payment Setup, flexibility to make it required or optional is one the best feature in this Area.

Copy Orders with Security Code Set as Mandatory

In R12, if the security Code is set as mandatory in Payments module and user try to Copy a Sales order which as credit card information, System will prompt user to uncheck “Copy payment” information and proceed.

Authorization Hold

Please make a note that Security Code is masked completely once we save the Sales order and ALSO SECURITY CODE is cleared from the UI, once Credit card is Authorized.This some time leads to issue of Order line being put on “Authorization Hold”.

Let me explain it in details, as I have explained that security code will be cleared from the line record as soon as authorization is done. Now if user tries to Reauthorize the card , at the point of time, the security code value is null (authorization process clears the security code value and it is not stored in the system). Since it is an essential attribute for authorization, reauthorization attempt would first put the transaction on CC Auth Hold. The user can then provide the security Code value and proceed with reauthorization