Professional Documents
Culture Documents
Ajaz Ahmed
Royal College of Physicians and Surgeons of Canada aahmed@royalcollege.ca
Objectives:
1. To educate attendees how iReceivables could be a tool of choice to empower internal or external customers 2. To share practical experience in implementing iReceivables and integrating a 3rd party payment system
Topics:
1. 2. 3. 4. 5. 6. 7. 8. Salient Features Product Functionality Security Considerations for iReceivables Integration Nuts and Bolts Integration with 3rd Party Payment Systems Conclusion Other Important Information Q&A
1. Salient Features:
Self-service access to view real-time balance and transaction information. Customers can Pay their invoices online. Customers can Dispute an invoice Customers can Print their invoices using Bills Presentment Architecture (BPA) templates
2. Product Functionality:
iReceivables is a bolt-on module to Oracle Receivables. Transactions or activities in Oracle Receivables can be visible to a customer logged on to iReceivables.
Online Payment Pages iReceivables uses Oracle Payments for payment processing. A 3rd Party Payment System integration with Oracle Payments is required to facilitate online payment functionality in iReceivables.
1. User makes online Payment 2. Payment details passed to Oracle Payments engine 3. Oracle Payments formats the Payment and passes it to Payment Gateway 4. Payment Gateway communicates it to Payment Processor 5. Payment processor contacts CC issuer 6. CC issuer authorizes or rejects a payment request 7. Authorization result is transmitted back to the customer
Start
1
Payment processing is a twostep process. After authorization, Automatic Remittances Master Program needs to be run in Oracle Receivables to settle all authorized funds. 2 3 4
Pass Payment Information to Oracle Payments Servlet Yes
No
Oracle Payment formats the Payment instruction and passes it to Payment Gateway = PayPAL
Payment Authorized?
Yes
Payment Processor communicates it to Credit Card Issuer and transmits response back to Gateway, to Oracle payments and to iReceivables Payment Page
No
End
Dispute Processing
Two types of approval hierarchies primary and non primary Workflow (WF) routes approval requests. Two types of Approvals Workflows
Dispute Processing
Dispute reasons can be set using FND Lookup codes. Registering a dispute results in launching a Credit Memo. Request is routed through the approval hierarchy.
iReceivables - setups ARI_CONFIG package allows modifications to the followings: Account Summary pages information, discount alerts and dispute status section Contact Us global button e-mail address iReceivables transaction search and customer search Dispute pages can also be customized. iReceivables messages can also be edited using look up codes.
iReceivables setups Three setup tabs: Profiles: - to setup OIR profile values Rules: - to setup rules that offer a high degree of flexibility System parameters: - to setup Credit Card Receipt Method and Bank Account Payment Method.
Receivables setups Receipt Class with creation method of Automatic and defining at least one Receipt Method associated with this Receipt Class. Approval limits for Credit Memo and defining a Credit Memo batch source
Oracle Payments setups System Security to setup encryption. Oracle Wallet needs to have been defined beforehand.
Payment Systems to setup 3rd Party Payment Gateway/Processors Payment Methods, Payees and Credit Card Brands
Oracle Bills Presentment Architecture (BPA) setups -Data Sources configuration -Template Management -Template Assignment Template Assignment Rules define criteria to automatically pick desired template for viewing and printing.
Oracle Sysadmin setups Internal and external users Function security for external users Indexing customers database Document Sequence System Profile values
Primary path: based on Approval Limits defined in Oracle Receivables Non-Primary path: based on the Oracle HR resources position hierarchy
6. Conclusion
Implementation setups are spread over a number of EBS modules Integration of Payment System could become a complex task Setting up Oracle Wallet and security certificates are technical tasks Select payment system based on type of payment processing requirements credit card, pin-less debit card or ACH transfers PayPal Payflo Pro Gateway solution is very easy to implement Complying with PCI security standard is a requirement, follow Payment Applications Best Practices document available at Metalink
Conclusioncontd
Consult a network architect to design and configure a DMZ based configuration for making iReceivables accessible to customers while safeguarding rest of the EBS from the possibility of any intrusion attack Plan a phased roll-out Customers can be provided with how to links in Related Information area of home page Like any web application, older browser version used by customers to access iReceivables may often result in support calls
Useful links
https://support.oracle.com/CSP/ui/flash.html https://www.paypal.com/cgi-bin/webscr?cmd=_payflow-gateway-overview-outside http://www.pcisecuritystandards.org http://www.pcicomplianceguide.org
Q&A