Oracle iPayment

1
Oracle iPayment Making the 16-digits flow at
Riverdeep

• Donald Fernandes, Riverdeep, Inc.

2
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

3
Oracle iPayment

• iPayment Overview
• Implementation Homework
• Reporting Requirements
• Implementation Process
• Post-Live Maintenance
• Special Scenarios
• Q A

4
iPayment Overview

• iPayment Candidacy for Business

5
iPayment Overview

• iPayment Technology Schematic

6
iPayment Overview

• Technology
• Java Servlet-Based Data Communication
• On-line and Batch Mode of Processing
• Stand-Alone and Integrated with Apps
• Public API

7
iPayment Overview

• Credit Card Business Operations

8
iPayment Overview

• Credit Card Systematic Transactional Flow

9
Oracle iPayment

• iPayment Overview
• Implementation Homework
• Reporting Requirements
• Implementation Process
• Post-Live Maintenance
• Special Scenarios
• Q A

10
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

11
Implementation Homework

• Application / Hardware
• Dedicated and Redundant Communication Link
• Database Sizing for Transactional Growth
• IBY Patches Compatibility and Relevance (
  Note 296206.1 )
• Customizations

12
Implementation Homework

• Project Players

13
Implementation Homework

• Vendor Selection Criteria

14
Oracle iPayment

• iPayment Overview
• Implementation Homework
• Reporting Requirements
• Implementation Process
• Post-Live Maintenance
• Special Scenarios
• Q A

15
Implementation Process
16
Implementation Process

• Network
• Two-way IP Address Handshake using FTP, Ping, etc
• Bandwidth Availability
• Fail-safe mechanism

17
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

18
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 )

19
Implementation Process

• Reporting Requirements

20
Implementation Process

• Communications Testing
• iPayment API
• iPayment EC Servlet (http//machine.port.com/oa_se
  rvlets/ibyecapp)
• IBY Module Tracing and Logging (Note265330.1)
• Crash Testing
• Riverdeep Network down
• PaymenTech down

21
Implementation Process
22
Oracle iPayment

• iPayment Overview
• Implementation Homework
• Reporting Requirements
• Implementation Process
• Post-Live Maintenance
• Special Scenarios
• Q A

23
Post-Live Maintenance

• Legacy Data Conversion and Reconciliation
• Data Reconciliation between Oracle, Payment
  Vendor and Bank
• Timing Differences
• Discrepancy Resolution
• Vendor Maintenance Schedule Dependency

24
Post-Live Maintenance
25
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

26
Project Timeline
27
Oracle iPayment

• iPayment Overview
• Implementation Homework
• Reporting Requirements
• Implementation Process
• Post-Live Maintenance
• Special Scenarios
• Q A

28
Special Scenarios Quadrant
29
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

30
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

31
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 )

32
Questions?

• iPayment Overview
• Implementation Homework
• Reporting Requirements
• Implementation Process
• Post-Live Maintenance
• Special Scenarios
• dfernandes_at_riverdeep.net
• IT Manager (Finance)
• Riverdeep, Inc