Credit Card Processing in R12 Overview
Recently I have implemented Credit Card Processing in R12. The need was to utilize out of box functionality of Oracle as much as possible. Client has iStore exposed to the retail Customer where s/he can create an account, add credit card information and buy products. Also Client can create Sales Orders in Order Management on behalf of Customer.
If you plan to implement similar process, here is what you need to know/establish:
1. Assumption is that Oracle Payments, OM, AR, iStore and other applications are setup correctly to use Credit Cards (CC for short). Please refer to 'Oracle Payments R12 Implementers Guide' for details. My bet is most settings are already done during implementation of R12. I will touch base on some points further on.
2. Client has a Bank Account to deposit money to. The account setup in Oracle Applications is out of scope of this note. Refer to 'R12 Receivables Implementation Guide' for details.
3. Client has a contract with Payment System Processor or Gateway company. Some of such companies provide ready-made interface, some just a tool set for developing custom interface, and a few are included into out of box Oracle Payments. As the service prices vary by Payment System, business shall consider investing into custom interface vs. out of box solution.
4. Payment System Processor or Gateway has provided vehicle for CC Processing. The type of Payment System (Processor vs. Gateway) will determine business flow of CC processing. My current experience is with Payment System Gateway so I will focus on it here.
If Payment System Gateway provides an interface or you plan to develop your own, it is most likely be a servlet. Follow installation/development instructions/guidelines from the Payment System company. Oracle has a few notes in Knowledge Base on implementing Pay Pal and a few other Payment Systems.
I would not advise to create new Payment Formats and Methods for CC processing if it can be avoided (and it can!)
5. Oracle Apps Setup. You would need to setup some system Profile Options, Oracle Payments Setup, Receivables, and Order Management. I will add some details later on
6. Setup and test out of box Sample Servlet 'lop'. If it works, your custom servlet will work too! I will touch base on details further on.
7. Install your servlet on the Web server (Apache?) I will mention some details later on, including Security considerations
8. Test your solution. Start with basic authorization/capture in the Testing Transactions form. Then test in iStore, Order Management, Receivables. The test cases depend on the business needs. For example: CC authorization, fund capture, authorization and capture (if chose so), void transaction, issue a refund etc.
If you plan to implement similar process, here is what you need to know/establish:
1. Assumption is that Oracle Payments, OM, AR, iStore and other applications are setup correctly to use Credit Cards (CC for short). Please refer to 'Oracle Payments R12 Implementers Guide' for details. My bet is most settings are already done during implementation of R12. I will touch base on some points further on.
2. Client has a Bank Account to deposit money to. The account setup in Oracle Applications is out of scope of this note. Refer to 'R12 Receivables Implementation Guide' for details.
3. Client has a contract with Payment System Processor or Gateway company. Some of such companies provide ready-made interface, some just a tool set for developing custom interface, and a few are included into out of box Oracle Payments. As the service prices vary by Payment System, business shall consider investing into custom interface vs. out of box solution.
4. Payment System Processor or Gateway has provided vehicle for CC Processing. The type of Payment System (Processor vs. Gateway) will determine business flow of CC processing. My current experience is with Payment System Gateway so I will focus on it here.
If Payment System Gateway provides an interface or you plan to develop your own, it is most likely be a servlet. Follow installation/development instructions/guidelines from the Payment System company. Oracle has a few notes in Knowledge Base on implementing Pay Pal and a few other Payment Systems.
I would not advise to create new Payment Formats and Methods for CC processing if it can be avoided (and it can!)
5. Oracle Apps Setup. You would need to setup some system Profile Options, Oracle Payments Setup, Receivables, and Order Management. I will add some details later on
6. Setup and test out of box Sample Servlet 'lop'. If it works, your custom servlet will work too! I will touch base on details further on.
7. Install your servlet on the Web server (Apache?) I will mention some details later on, including Security considerations
8. Test your solution. Start with basic authorization/capture in the Testing Transactions form. Then test in iStore, Order Management, Receivables. The test cases depend on the business needs. For example: CC authorization, fund capture, authorization and capture (if chose so), void transaction, issue a refund etc.
Can you share your contact details?
ReplyDeleteor call at +91 9632266314
I have been absent for some time, but now I remember why I used to love this blog. Thanks , I will try and check back more often. How frequently you update your web site? Slice invitation code
ReplyDelete