1 Oracle iPayment Configuration Integrated v/s Third Party Vendors February 22, 2008 8:30 PM –...

1

Oracle iPayment Configuration

Integrated v/s Third Party VendorsFebruary 22, 2008 8:30 PM – 9:10 AM

Presented By

Gouri [email protected]

Srinivas [email protected]

2

Agenda

iPayment Overview

Integration with other Oracle applications modules

iPayment Architecture

Integrated Vendors

Quasi Integrated Vendors

Non Integrated Vendors

Considerations

Questions and Answers

3

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

iPayment Overview

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

•iStore

•Order Capture

•Order •Management

•iPayment

•Accounts •Receviables

•Oracle Collections

•Cyber Cash

•Paymentech

•First Data North

•Concord

•Field Installable •Payment System

•Customer Purchases Product•Creates Order Request

•Fullfill Order Request

•Order Information for Invoicing

•Collect Overdue•Payment Info•.

•Capture or Auth •/ •Capture Request

•Authorization•Request

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

Acts as an intermediary between the merchant and a payment processor

Interacts directly with banks and credit card

institutions such as Visa, Mastercard and

American Express to process financial

transactions

8

Integrated Vendors

EC Application

EC Servlet

JAVA APIiPayment Engine

Apache

XML ProcessorAPI’s

Gateway API’s

PaymentechServlet

CyberCashServlet

Paymentech Server

CyberCash Server

Http Req.

Http Req.

Http Req.

Http Req.

iPayment Servlet Flow for Integrated Vendor

9

Quasi Integrated Vendors

EC Application

EC Servlet


Apache


Gateway API’s

VerisignServlet

Verisign Server

Http Req.

Http Req.

Note: Verisign Servlet to be installed on the Apache Server

iPayment Servlet Flow for Quasi Integrated Vendor

10

Non Integrated Vendors

EC Application

EC Servlet


Apache


Gateway API’s

Non Integrated Servlet

Custom Code

Non Integrated Server

iPayment Servlet Flow for Non Integrated Vendor

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


Lower Cost of Ownership and Maintenance

13

Why Quasi Integrated Vendors?

Partially Pre-Built Solutions

Available Support

Available Reporting Capabilities


14

Why Non- Integrated?

Existing Corporate Relationship

Lower Costs per transactions

Personalized Solutions

15

Summary

Integrated Quasi-Integrated Non-Integrated

Pre-Built IntegrationPartially Pre-Built Integration

Fully Custom Integration

Oracle Support Available Limited Support Available Limited or No Support

Reporting Available Some Reporting Available Fully Custom Reporting

Maintenance for Upgrades- Low

Maintenance for Upgrades- Medium

Maintenance for Upgrades- High

Cost of Ownership- Low Cost of Ownership- Medium Cost of Ownership- High

16

Questions and Answers

Questions and Open Discussions

Contact Information

Gouri Borkar and Srinivas ChunduEmail: [email protected],

[email protected]

Phone: 630-778-1180

Presentation Copy

www.astcorporation.com/papers/ncoaug

1 Oracle iPayment Configuration Integrated v/s Third Party Vendors February 22, 2008 8:30 PM –...

Documents

Transcript of 1 Oracle iPayment Configuration Integrated v/s Third Party Vendors February 22, 2008 8:30 PM –...