Go-live

Before go-live please make sure that you have read and completed all the steps below.

We recommend printing this page and keeping it for reference after go-live.

Skipping any of the steps outlined below may lead to errors and delayed support cases.

1) General

•We recommend always using a sandbox database for testing of iPayment

•Note: Once you switch from Demo-mode to Live-Mode, all iPayment tables will be cleared, and the action can't be reversed.

•Read "General must read notes on gateways" for the gateway you are implementing

•Read "Handling large authorizations and split shipments" and decided if this applies to the customer or not

•Read "Known limitations in iPayment"

•Read "iPayment and Payment Card Industry Data Security Standard (PCI-DSS)" + "iPayment and Payment Application Data Security Standard (PA-DSS)"

•Read "Data theft"

2) Configure your Payment gateway

Make sure that all the required features are enabled at the gateway and that you insert all the required credentials into the iPayment gateway configuration window.

•Trust Payments (Secure Trading) Requirements

•Authorize.NET Requirements

•CyberSource Requirements

•Eway Requirements

•Moneris Canada Requirements

•Cayan Requirements

•ProPay Requirements

Note: Not getting all gateway features enabled (example ECC) may not give errors immediately but it will give issues later on when doing a refund.

Customers needs to have a specific currency set. You cannot use the "Multi-currency" customer.

3) Provide gateway access to your accounting team

The accounting team should have access the to gateway backend system so that they may reconcile and verify the transactions.
All error handling in regards to rejected transactions are manual and the accounting team should be instructed on how to handle this.

Additionally you may want to setup automatic e-mail notification on rejected settlement if this is supported by the gateway.

4) Instruct your sales team in the new work-flow

The users that are going to use iPayment should receive appropriate training and should all know where to obtain the iPayment manual.
They should  be instructed in how to handle Credit Card details securely and in compliance with PCI-DSS.

5) Testing

We test each iPayment version released with a number of automated and manual test cases but it is your responsibility to test that the product behaves as expected before go-live.

We recommend that you to run a few small value test transactions with real cards before starting to accept customer orders.

•Test your work-flow and create a new order and test authorizations

•Create invoice documents and settle the invoice

•Issue a partial refund

•Issue a full refund

•Test the incoming/outgoing payment functionality

Check using the gateway backend that all transactions are processed as expected and have the correct amounts

6) Make sure to show and instruct the super-users in how the "Action log" window works

The action log is a very important tool as it contains a log of everything done with iPayment and who did it.
This tool is both an audit and a support tool to show you what has happened in the system.

When requesting support we may ask for information from the action log to be included in the ticket.

Post go-live

After go-live it is important that new versions released of iPayment are checked for bugs relating to functionality that the customer are using and that new versions are installed if any corrections have been made.

You can find the version history at: https://ipayment.boyum-it.com

1) Requesting support

Before requesting support please read this article on what information should be included