/
Gateway Storefront Testing for Authorize.Net Outsource

Gateway Storefront Testing for Authorize.Net Outsource

Owned by Cecilia Do
Last updated: Oct 27, 2010Version comment

Credit Card Outsource

The CCCS current credit card software ICVerify is being retired. We will outsource the credit card processing and storage to Authorize.Net.

The modifications include the following:

  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-20 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.

Test Environment

CCCS Test is connected to Authorize.Net's test environment with a dedicated test account. Payments are not sent out to the banks. By default, payments are authorized.

Credit Cards

Use a non-expired expiration date

Credit Card Type

Number

Visa

4007000000027

Visa

4222222222222

Master Card

5555555555554444

Discover

6011000000000012

American Express

370000000000002

Declined Payments

By default, payments are authorized. In order to test declined payments, we will need to do the following:

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

Settlement

Settlement is run every 10 minutes.

Test Schedule

Department

Contact

Schedule

Issues / Bugs

Test Results

Cancer Center

Charles Lowe

10/1/2010-10/7/2010


Successfully completed on 10/7/2010

Center for Educational
Partnerships

Mike Jenkins

10/20/2010

 

Successfully completed on 10/20/2010

Engineering

John Romine

Unavailable for testing

 

 

Graduate Division

David Goenawan
Eric Taggart

9/27/2010-10/26/2010

 

Successfully completed on 10/26/2010

Housing

Jorge Romo
Markus Quon

9/28/2010-10/7/2010

  1. 10/1: Minor change to post-back parameter order. Maintained ordering from old world.

Successfully completed on 10/7/2010

Library

Archana Chaudri

10/5/2010-10/27/2010

 

Successfully completed on 10/27/2010

Paul Merage

Gary Striano

Unavailable for testing

 

 

Student Affairs

Erik Olsson

10/21/2010-10/25/2010

 

Successfully completed on 10/25/2010

Undergrad Admissions

Linda Snyder

9/29/2010

  1. 9/29: Fixed bug for empty department response for post-back

Successfully completed on 9/29/2010

Test Plan

Initial Backend Post

Test Case

Description

Expected Outcome

Comments

Post Data

  1. Multiple programs if applicable
  2. Tax if applicable
  3. Different total amounts if applicable
  4. Different account-fund distribution if applicable
  5. Distribution override and no override if applicable

 

 

CCCS Maintenance

  1. Emergency downtime
  2. Scheduled downtime
  3. Routine maintenance

Response with appropriate error code and message

 

Redirect to Gateway

Test Case

Description

Expected Outcome

Comments

Disabled JavaScript


Display page with instructions on how to enable JavaScript

 

Redirect Timeout

Exceed [department timestamp + duration] window

  1. Post to department
  2. Redirect user back to storefront

 

CCCS Maintenance

  1. Emergency downtime
  2. Scheduled downtime
  3. Routine maintenance
  1. Post to department
  2. Redirect user back to storefront

 

Vendor Payment Page

Test Case

Description

Expected Outcome

Comments

Page Display

  1. Banner
    1. 580 pixels wide
  2. Stylesheet
    1. May need to tweak
  3. Payment description
    1. screen_header
      1. if not supplied, then program profile name
    2. refundable flag

 

 

Authorized Payment

In the vendor's test environment, by default, all payments are authorized.

The vendor transmits post-backs in real time for authorized payments.

  1. Use different card types

Post-Back and Receipt Display Is Asynchronous

The Payment Gateway posts back to the department when it receives the vendor's post. The redirect back to the department will occur after the user presses the button on the vendor receipt page.

  1. Vendor display user receipt
    1. Button for user to go back to the storefront
  2. Gateway post-back to department storefront
  3. If user entered valid email, receive email receipt

 

Canceled Payment

This is a function added by CCCS, since Authorize.Net doesn't offer a cancel option.

  1. Gateway post-back to department storefront
  2. Redirect user back to storefront

 

Declined Payment

The decline procedure is described above.

The vendor does not transmit post-backs for declined payments. As long as a payment is declined, the user will not receive a receipt and the vendor will not transmit a post-back to CCCS.

There is no limit on the number of attempts.

  1. The Gateway department post-back job is scheduled to run every 10 minutes.
    1. If there is no vendor response for an authorization or cancellation for a particular session within 10-20 minutes, then the post-back job will post the record back to the department.
  2. If an authorization is made, see outcome for "Authorized Payment"

 

Close Window

 

See outcome for "Declined Payment"

 

Timeout

The vendor timeout is 1 hour. After this, the next payment attempt will error out.

See outcome for "Declined Payment"

 

Gateway Post-Back

Test Case

Description

Expected Outcome

Comments

Authorization


 

 

Cancellation

 

 

 

Decline / Timeout / Close Window

 

 

 

Redirect Back to Department Storefront

Test Case

Description

Expected Outcome

Comments

Redirect URL

Verify sequence_id, backend_post_id, session_id_key

 

 

Gateway Query

Test Case

Description

Expected Outcome

Comments

Authorization


 

 

Cancellation

 

 

 

Decline / Timeout / Close Window

 

 

 

CCCS Maintenance

  1. Emergency downtime
  2. Scheduled downtime
  3. Routine maintenance

Response with appropriate error code and message

 

Settled Transaction

 

 

 

CCCS Online Application

Test Case

Description

Expected Outcome

Comments

Verify Account-Fund Distribution

  1. Pre-condition
    1. Need to simulate settlement and ledger posting
  2. Login to CCCS Online Application
  3. Go to "Reports"
  4. Go to "Transaction Query"
  5. Pull up transactions
  6. Drill-down
  7. Verify
    1. Transaction status
    2. Account-fund distribution
      1. Expense account is 2% of transaction total