oracle ipayment implementation summary

Oracle Payments

“ Making the 16-digits flow at Riverdeep ”

-Donald Fernandes 2006

About Riverdeep, Inc.

� Educational Software Company

� www.riverdeep.net, www.broderbund.com

� DTC, Schools, OEM, Reseller Channels

� Oracle Applications 11.5.9

� IBY.O, AR.L, ONT.I, IBE.O

� 2000 Credit Card Transactions / Day

Oracle iPayment

� iPayment Overview

� Implementation Homework

� Reporting Requirements

� Implementation Process

� Post-Live Maintenance

� Special Scenarios

� Q & A

iPayment Overview

� iPayment Candidacy for Business

iPayment Overview

� iPayment Technology Schematic

iPayment Overview

� Technology

� Java Servlet-Based Data Communication

� On-line and Batch Mode of Processing

� Stand-Alone and Integrated with Apps

� Public API

� Credit Card Business Operations

iPayment Overview

iPayment Overview

� Credit Card Systematic Transactional Flow

Oracle iPayment

� iPayment Overview

� Implementation Homework

� Reporting Requirements

� Implementation Process

� Post-Live Maintenance

� Special Scenarios

� Q & A

Implementation Homework

� Business Requirements (▓ =Priority)Types of Transactions supported ▓ ▓

Transactional Volume Capacity ▓

Legacy Data Conversion ▓

Reporting Requirements ▓ ▓ ▓

Transactional Security ▓ ▓

Vendor-specific Features / Limitations ▓

Overall Systematic Stability ▓ ▓

Implementation Homework

� Application / Hardware

– Dedicated and Redundant Communication Link

– Database Sizing for Transactional Growth

– IBY Patches – Compatibility and Relevance ( Note# 296206.1 )

– Customizations

Implementation Homework

� Project Players

Implementation Homework

� Vendor Selection Criteria

Oracle iPayment

� iPayment Overview

� Implementation Homework

� Reporting Requirements

� Implementation Process

� Post-Live Maintenance

� Special Scenarios

� Q & A

Implementation Process

System Configuration

Network

Database

Application

Implementation Process

� Network

�Two-way IP Address Handshake using FTP, Ping, etc

�Bandwidth Availability

�Fail-safe mechanism

Implementation Process

� Database / Concurrent Server

�IBY Patch Application

�Apache / JServ Configuration

( jserv.properties, zone.properties )

�OS Check for XML Files ( Top Tech Docs )

�OS Check for ClassPath

�Tablespace Sizing for IBY table growth

Implementation Process

� Application Layer

�Setting up Payment System

�System Profile Options (IBY%, ICX%)

�OM, iStore, AR Setups ( Note# 228855.1, 138088.1 )

�API for Auth Testing ( Note# 148151.1, 276085.1 )

Implementation Process

� Reporting Requirements

Implementation Process

� Communications Testing– iPayment API

– iPayment EC Servlet (http://machine.port.com/oa_servlets/ibyecapp)

– IBY Module Tracing and Logging (Note#265330.1)

– Crash Testing � Riverdeep Network down

� PaymenTech down

Implementation Process

Oracle iPayment

� iPayment Overview

� Implementation Homework

� Reporting Requirements

� Implementation Process

� Post-Live Maintenance

� Special Scenarios

� Q & A

Post-Live Maintenance

� Legacy Data Conversion and Reconciliation

� Data Reconciliation between Oracle, Payment Vendor and Bank– Timing Differences

– Discrepancy Resolution

� Vendor Maintenance Schedule Dependency

Post-Live Maintenance

Post-Live Maintenance

� Data Corruption – Common Symptoms

– Refunds Mis-match

– Duplicate Receipt Settlement

� Data Corruption – Common Causes

– Network Failure

– JServ Max Sessions Crash

� Data Corruption – Resolution Strategies

– One-off Patches

– Credit Card Re-authentication ( Manual / Script)

– Receivables Write-offs

Project Timeline

Oracle iPayment

� iPayment Overview

� Implementation Homework

� Reporting Requirements

� Implementation Process

� Post-Live Maintenance

� Special Scenarios

� Q & A

“Special Scenarios” Quadrant

Special Scenarios - I

���� Multiple Stores / Payees

� Non-Major Credit Card Types

� Mandatory Credit Card Information and Risk Management

���� Credit Card Storage Encryption (Note# 338756.1, Patch# 4607647 )

���� Pre-Authentication Process

� Voiding/ Modification of Original Order Amount

���� �

Special Scenarios - II

� Transactional Staging Area for System Downtime, Archiving, Auditing

���� Split Payments using Credit Cards

� Encryption of Data Transmission

���� Vendor-side Processing Capability

���� Changing Payment Vendors

���� �

Special Scenarios - III

� Order Line-level Authentication

� Multi-Currency

���� Configuring Authentication Expiration Period

� Refund Transaction Allowance Period and Purge / Audit Policies

� Non-Oracle Integration ( Note# 304220.1 )

���� �

Questions?

� iPayment Overview� Implementation Homework� Reporting Requirements� Implementation Process� Post-Live Maintenance� Special Scenarios

dfernandes@riverdeep.netIT Manager (Finance)

Riverdeep, Inc