Background

As you already know, our current credit card software ICVerify is being retired. We are in the process of modifying CCCS in order to outsource the credit card processing and storage to Authorize.Net.

For the CCCS Test environment, we are connecting to the vendor

Modifications

1. The transactions initiated in ICVerify prior to production implementation will be refundable for 30 days. The transactions initiated in Authorize.Net will have a refund cutoff of 120 days. Please note that this is counted from the transaction's settlement date.
2. Authorize.Net's policy is to not display or pass back the expiration date. Therefore, in CCCS, the transactions initiated in Authorize.Net will have have a masked expiration date (e.g. XXXXX).
3. The vendor payment page will include an optional email address field for the customer's address. If one is provided, a receipt of the authorization will be sent to the customer.
4. Upon a successful payment, Authorize.Net will display a receipt page to the customer. There will be a button to take the user back to the CCCS Online Application or department storefront as appropriate.
5. For the Payment Gateway department storefronts:
   1. The storefront css stylesheets will continue to be used. It may need tweaking for the vendor payment page.
   2. The storefront banner will be passed to the vendor for display. However, because the width of the vendor payment page is 580 pixels, you may want to consider adjusting your current banner.
   3. The payment description display will be the screen_header and the non-refundable message (if applicable). If a screen_header is not provided, then the CCCS program profile name will be used.
   4. The error message for code 998 is currently "ICVerify (credit card server) not available." We are proposing to change this to be more general: "Credit card service not available."
   5. There is a Payment Gateway job that performs a department post-back for Gateway sessions that were not posted back (for example, the user has already timed out and may have closed the payment window). This job is scheduled to be run every 10 minutes, and the storefront will receive a post-back between 10-15 minutes of the user initially landing on the payment page. Although the Authorize.Net payment page timeout is 60 minutes, we will maintain this existing job to post back to the departments.

Testing Payments

Credit Cards

Use a non-expired expiration date

Declines

There are two ways to test declines.

Enable Test Mode

1. Authorize.Net admin will need to enable Test Mode
2. Department can simulate declines by passing in an amount of $2 and using the test card number 4222222222222.
   1. Can simulate other vendor responses by making the dollar amount the Response Reason Code found here.
3. If another card number is used, it will be authorized
4. Most flexible, allows department to control declines and authorizations

Enable AVS to force decline

1. Authorize.Net admin will need to enable AVS
2. All payments will be declined while AVS is enabled
3. Less flexible

Testing Schedule

Test Plan

Initial Backend Post

Redirect to Gateway

Vendor Payment Page