1 / 16

Oracle iPayment Configuration Integrated v/s Third Party Vendors February 22, 2008 8:30 PM – 9:10 AM

Presented By Gouri Borkar gborkar@astcorporation.com Srinivas Chundu schundu@astcorporation.com. Oracle iPayment Configuration Integrated v/s Third Party Vendors February 22, 2008 8:30 PM – 9:10 AM. Agenda. iPayment Overview. Oracle’s answer to automated credit card processing

ardelle
Download Presentation

Oracle iPayment Configuration Integrated v/s Third Party Vendors February 22, 2008 8:30 PM – 9:10 AM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Presented By Gouri Borkar gborkar@astcorporation.com Srinivas Chundu schundu@astcorporation.com Oracle iPayment Configuration Integrated v/s Third Party Vendors February 22, 2008 8:30 PM – 9:10 AM

  2. Agenda

  3. iPayment Overview • Oracle’s answer to automated credit card processing • Provides an interface to financial institutions and payment processors • Published API that other applications can use to enable payment processing

  4. Benefits of iPayment • Integrates with many modules with the applications • Ability to interface to several different payment processors • Accepts Inbound as well as Outbound Payments • Supports multiple payment methods • Provides Security through SSL (Secure Socket Layer) • Provides encryption for credit card data

  5. Integration with other Oracle Application modules Cyber Cash Paymentech iStore Customer Purchases Product iPayment First Data North Creates Order Request Order Capture Concord Authorization Request Fullfill Order Request Field Installable Order Payment System Management Capture or Auth / Capture Request Accounts Collect Overdue Oracle Collections Payment Info . Receviables Order Information for Invoicing

  6. Vendors Integrated Vendors • Paymentech • First Data North (FDC) • Citibank • Cybercash • Concord EFSnet Quasi Integrated Vendors • Verisign (Paypal) Non Integrated • Third Party Payment Processing Vendors

  7. iPayment Architecture Interacts directly with banks and credit card institutions such as Visa, Mastercard and American Express to process financial transactions Acts as an intermediary between the merchant and a payment processor

  8. iPayment Servlet Flow for Integrated Vendor EC Application JAVA API iPayment Engine XML Processor API’s Apache Http Req. Paymentech Servlet Paymentech Server Http Req. EC Servlet Gateway API’s CyberCash Servlet CyberCash Server Http Req. Http Req. Integrated Vendors

  9. iPayment Servlet Flow for Quasi Integrated Vendor EC Application JAVA API iPayment Engine XML Processor API’s Apache Http Req. Verisign Servlet Verisign Server Http Req. EC Servlet Gateway API’s Note: Verisign Servlet to be installed on the Apache Server Quasi Integrated Vendors

  10. iPayment Servlet Flow for Non Integrated Vendor EC Application JAVA API iPayment Engine XML Processor API’s Apache Non Integrated Servlet Non Integrated Server EC Servlet Gateway API’s Custom Code Non Integrated Vendors Custom code provides formatting/ syntax mapping between the requests going into the Payment Server from Oracle and the standards coming from Oracle

  11. Considerations • Available Support • Available Reporting Capabilities • Types of payment methods supported • Corporate Relationship • Cost/Transaction

  12. Why Integrated? • Pre-built solutions • Shorter Implementation duration • Available Support • Available Reporting capabilities • Types of payment methods supported • Lower Cost of Ownership and Maintenance

  13. Why Quasi Integrated Vendors? • Partially Pre-Built Solutions • Available Support • Available Reporting Capabilities • Types of payment methods supported

  14. Why Non- Integrated? • Existing Corporate Relationship • Lower Costs per transactions • Personalized Solutions

  15. Summary

  16. Questions and Answers Questions and Open Discussions Contact Information Gouri Borkar and Srinivas Chundu Email: gborkar@astcorporation.com, schundu@astcorporation.com Phone: 630-778-1180 Presentation Copy www.astcorporation.com/papers/ncoaug

More Related