oracle ipayment “ making the 16-digits flow at riverdeep ” -donald fernandes, riverdeep, inc

Oracle iPaymentOracle iPayment

“ “ Making the 16-digits flow at Making the 16-digits flow at Riverdeep ”Riverdeep ”

-Donald Fernandes, Donald Fernandes, Riverdeep, Inc.Riverdeep, Inc.

About Riverdeep, Inc.About Riverdeep, Inc.

Educational Software CompanyEducational Software Company www.riverdeep.net, www.riverdeep.net,

www.broderbund.comwww.broderbund.com DTC, Schools, OEM, Reseller ChannelsDTC, Schools, OEM, Reseller Channels Oracle Applications 11.5.9Oracle Applications 11.5.9 IBY.O, AR.L, ONT.I, IBE.OIBY.O, AR.L, ONT.I, IBE.O 2000 Credit Card Transactions / Day2000 Credit Card Transactions / Day


iPayment OverviewiPayment Overview Implementation HomeworkImplementation Homework Reporting RequirementsReporting Requirements Implementation ProcessImplementation Process Post-Live MaintenancePost-Live Maintenance Special ScenariosSpecial Scenarios Q & AQ & A

iPayment OverviewiPayment Overview

iPayment Candidacy for BusinessiPayment Candidacy for Business

Low-Dollar-per-Order eCommerce Transactions

Single-Installment Payment Terms

Around 4% Return Orders

Availability of a Credit Card Processing Specialist

Credit Card Revenue Transactions


iPayment Technology SchematiciPayment Technology Schematic

Oracle 11iApplication

Tier

Database Tier / Concurrent

Processing Tier

Payment Gateway / Processor

Bank 1

Bank 2

Bank 3

Router / Dial-up Modem

Riverdeep PaymenTech

Secure Website

ApplicationUser

Cust-omer

Secure Website

iStore


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

Credit Card Business Operations Credit Card Business Operations


Authorize

Void Settle

Refund

Re-Authorize


Credit Card Systematic Transactional Credit Card Systematic Transactional FlowFlow

iStore / Third Party Web

Order Entry

Order Booking

Pick Release

AutoInvoiceReceipts Awaiting

Remittances

Vendor Website

Validation

Receipts/ Remittances/

Clearing

iPayment Batch Scheduler

BATCHCLOSEBATCHQUERY

Oracle iPayment Engine

PaymenTech

O M A R

Implementation Implementation HomeworkHomework

Business Requirements (Business Requirements (▓ =Priority)▓ =Priority)Types of Transactions supportedTypes of Transactions supported ▓ ▓ ▓ ▓ Transactional Volume CapacityTransactional Volume Capacity ▓ ▓ Legacy Data ConversionLegacy Data Conversion ▓ ▓ Reporting RequirementsReporting Requirements ▓ ▓ ▓ ▓ ▓ ▓ Transactional SecurityTransactional Security ▓ ▓ ▓ ▓ Vendor-specific Features / LimitationsVendor-specific Features / Limitations

▓ ▓ Overall Systematic StabilityOverall Systematic Stability ▓ ▓ ▓ ▓


Application / HardwareApplication / Hardware– Dedicated and Redundant Dedicated and Redundant

Communication LinkCommunication Link– Database Sizing for Transactional Database Sizing for Transactional

GrowthGrowth– IBY Patches – Compatibility and IBY Patches – Compatibility and

Relevance ( Note# 296206.1 )Relevance ( Note# 296206.1 )– CustomizationsCustomizations


Project PlayersProject Players

iStore, OM, AR Power Users

Legal

IT-Functional

IT-Technology

Networking

PM

PaymenTech Customer Support


Vendor Selection CriteriaVendor Selection Criteria

Oracle Partner Compatibility

Cost / TransactionTypes of

Transactions Supported

Available Training and Support

Available Reporting Capabilities

Transaction Bandwidth,

Response Time

Corporate Relationship

Implementation Implementation ProcessProcess

System Configuration

Network

Database

Application


NetworkNetworkTwo-way IP Address Handshake Two-way IP Address Handshake

using FTP, Ping, etcusing FTP, Ping, etcBandwidth AvailabilityBandwidth AvailabilityFail-safe mechanismFail-safe mechanism


Database / Concurrent ServerDatabase / Concurrent ServerIBY Patch ApplicationIBY Patch ApplicationApache / JServ Configuration Apache / JServ Configuration

( jserv.properties, zone.properties )( jserv.properties, zone.properties )OS Check for XML Files ( Top Tech OS Check for XML Files ( Top Tech

Docs )Docs )OS Check for ClassPathOS Check for ClassPathTablespace Sizing for IBY table growthTablespace Sizing for IBY table growth


Application LayerApplication LayerSetting up Payment SystemSetting up Payment SystemSystem Profile Options (IBY%, ICX%)System Profile Options (IBY%, ICX%)OM, iStore, AR Setups ( Note# OM, iStore, AR Setups ( Note#

228855.1, 138088.1 )228855.1, 138088.1 )API for Auth Testing ( Note# API for Auth Testing ( Note#

148151.1, 276085.1 )148151.1, 276085.1 )


Reporting RequirementsReporting Requirements

1. Oracle seeded

IBY Reports

2. Custom Reports

based on IBY tables and Vendor-specific Message

Codes

3. PaymenTech Reports

(Daily / Monthly / Summary / Exception)

Data Synchronicity


Communications TestingCommunications Testing– iPayment API iPayment API – iPayment EC Servlet iPayment EC Servlet

(http://machine.port.com/oa_servlets/ibyeca(http://machine.port.com/oa_servlets/ibyecapp)pp)

– IBY Module Tracing and Logging IBY Module Tracing and Logging (Note#265330.1)(Note#265330.1)

– Crash Testing Crash Testing Riverdeep Network downRiverdeep Network down PaymenTech downPaymenTech down


Application Testing

Authentication Settlements

Quoting

Order Booking

Pick Release

Cash Receipts

Refunds

Reports, Vendor-Side Data Reconciliation

ExceptionTesting

Volume Testing

For 1000+

X’actions

Post-Live Post-Live MaintenanceMaintenance

Legacy Data Conversion and Legacy Data Conversion and ReconciliationReconciliation

Data Reconciliation between Data Reconciliation between Oracle, Payment Vendor and Oracle, Payment Vendor and BankBank– Timing DifferencesTiming Differences– Discrepancy ResolutionDiscrepancy Resolution

Vendor Maintenance Schedule Vendor Maintenance Schedule DependencyDependency


Security Compliance

(PCI)

Network Scans

Production Environment

Cloning Policies(Sanitization)

Credit Card Encryption

Methodologies(Note# 338756.1)

Oracle Responsibilities

and Reports


Data Corruption – Common SymptomsData Corruption – Common Symptoms– Refunds Mis-matchRefunds Mis-match– Duplicate Receipt SettlementDuplicate Receipt Settlement

Data Corruption – Common CausesData Corruption – Common Causes– Network FailureNetwork Failure– JServ Max Sessions CrashJServ Max Sessions Crash

Data Corruption – Resolution Data Corruption – Resolution StrategiesStrategies– One-off PatchesOne-off Patches– Credit Card Re-authentication ( Manual / Script)Credit Card Re-authentication ( Manual / Script)– Receivables Write-offsReceivables Write-offs

Project Timeline Project Timeline

Vendor Co-ordination

Patch / Oracle Setups

Testing

Reports Development

Vendor-based Training

Post-Live Maintenance

M0 M1 M2 M3 M4 M5

““Special Scenarios” Special Scenarios” Quadrant Quadrant

Implemented as Standard Functionality

Available as Standard Functionality

Future Upgrade

Riverdeep Customization

X X

X XX

X X X X X

X XX

Special Special Scenarios - IScenarios - I

Multiple Stores / PayeesMultiple Stores / Payees

Non-Major Credit Card TypesNon-Major Credit Card Types

Mandatory Credit Card Information and Mandatory Credit Card Information and Risk Management Risk Management

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

Pre-Authentication ProcessPre-Authentication Process

Voiding/ Modification of Original Order Voiding/ Modification of Original Order AmountAmount

Special Special Scenarios - IIScenarios - II

Transactional Staging Area for System Transactional Staging Area for System Downtime, Archiving, AuditingDowntime, Archiving, Auditing

Split Payments using Credit CardsSplit Payments using Credit Cards

Encryption of Data TransmissionEncryption of Data Transmission

Vendor-side Processing CapabilityVendor-side Processing Capability

Changing Payment VendorsChanging Payment Vendors

Special Special Scenarios - IIIScenarios - III

Order Line-level AuthenticationOrder Line-level Authentication

Multi-CurrencyMulti-Currency

Configuring Authentication Configuring Authentication Expiration PeriodExpiration Period

Refund Transaction Allowance Period Refund Transaction Allowance Period and Purge / Audit Policiesand Purge / Audit Policies

Non-Oracle Integration ( Note# Non-Oracle Integration ( Note# 304220.1 )304220.1 )

Questions?Questions?

iPayment OverviewiPayment Overview Implementation HomeworkImplementation Homework Reporting RequirementsReporting Requirements Implementation ProcessImplementation Process Post-Live MaintenancePost-Live Maintenance Special ScenariosSpecial Scenarios

[email protected]@riverdeep.netIT Manager (Finance)IT Manager (Finance)

Riverdeep, IncRiverdeep, Inc

oracle ipayment “ making the 16-digits flow at riverdeep ” -donald fernandes, riverdeep, inc

Documents

prioritytypes of transactions

properties os check

ar setups

relevance note

riverdeep donald fernandes

auth testing note

classpathtablespace

tech docs os check