Overview

AIMStorefront supports numerous payment gateways during the checkout process which can simplify receiving payments from your shoppers. These Checkout Payment Gateways can be set up in the Site Setup Wizard through the yoursite.com/aesys admin console.

For more information on how to set up the specific payment gateways for checkout, please refer to the Payment Gateways section in the AspDotNetStorefront manual, here:

https://help.aspdotnetstorefront.com/manual/1000/default.aspx?pageid=payment_gateways

Checkout Payment Gateway Pages

The following two pages on AIMStorefront are able to accept payments using Checkout Payment Gateways:

  • aepostpayment.aspx*
  • checkout.aspx

* - Aepostpayment.aspx is special in that it is able to accept credit card payments using Checkout Payment Gateways. This only applies to shoppers who have already had their credit card information entered into AIM Desktop via payment tokenization.

Tokenized Gateway for Rentals AND Checkout Gateways for Cart Checkout

It is possible to setup the cart to use the tokenized gateway for the Rental pages while using a checkout gateway for cart checkouts

  • Setup the cart checkout payment gateway where the Payment Processing Solutions selection in the Site Setup Wizard reflects that configuration. The Configuration - Settings - PaymentGateway value will reflect that selection.
  • Setup the tokenized gateway for rentals, but leave the payment gateway set to the cart gateway.
  • In order for the cart to switch over to the tokenized gateway for Rentals, the MANUAL Payment Gateway is set in the Configuration - Settings - PaymentGatewayBackup

Payment Tokenization

In AIMStorefront there are also specialized payment pages which require a different setup. These special pages work in tandem with AIM Desktop to process shoppers' credit card payments. Credit card payments are tokenized, a process which substitutes credit card information with a token which represents it.

The AIM Desktop application does not store credit card numbers. Instead, it uses payment tokens to represent the credit card and performs charges with the tokens. 

Tokenization transforms the payment information into a form where it is usable by AIM Desktop to make charges in a way that is both repeatable and secure.

Using Tokenization for Checkout Payments

It is possible to use tokenization to process checkout payments. This is treated as a Manual Credit Card payment in AIMStorefront.

To use this option:

  • In the Site Setup Wizard in the Admin console, select Credit Card for the Payment Method (or the Configuration - Settings - PaymentMethods value).
  • Select Manual for the Payment Processing Solution (or the Configuration - Settings - PaymentGateway value).
  • Configure a Payment Tokenization Gateway using the instructions below:


Credit Card Tokenization Pages

The following pages on AIMStorefront also prepare credit cards for charges using tokenization:

  • aeapgfinalize.aspx
  • aemanagecc.aspx
  • aepostpayment.aspx
  • aerntfinalize.aspx
  • aeserviceticket.aspx
  • aeteefinalize.aspx
  • aeupdatecc.aspx

When payments are accepted on these pages, the captured credit card token is used to charge the card. Please see the Sample Payment Flow section below for an example of how the payment process works for rentals.

Configuring Payment Tokenization Gateways

The credit card number is tokenized by sending it to a payment gateway. Four tokenization payment gateways are implemented in AIMStorefront.

Generic Settings

There are two generic settings which must be configured in order to enable payment tokenization.

  • aeCCType- This must be set to M, L, O, or T. This setting selects the gateway.
    • M - Mercury
    • L - Open Edge Legacy
    • O - Open Edge
    • T - TSYS
  • aeCCMID - The Merchant ID. This value is provided by the payment processor and must be set in order for payment tokenization to take place.

Worldpay (Formerly Mercury/Vantiv)

Worldpay is run by Worldpay Integrated Payments.

  • https://www.worldpay.com/
  • https://portal.mercurypay.com/
  • Settings for Worldpay are:
    • aeCCType - Must be set to M.
    • aeCCLane - This must be configured and needs to be set to your LaneID. If you were not provided a LaneID, please use 1.
    • AeCCPassword - This needs to be the password configured for your Webservice.

Open Edge

Open Edge is a division of Global Payments and operates through Wells Fargo Bank.

  • https://www.openedgepayment.com/
  • This newer version of Open Edge uses XML in its requests for tokenization.
  • Settings for Open Edge are:
    • aeCCType - Must be set to O.
    • AeCCDeviceID - This needs to be set to your Terminal ID.
    • aeCCTransactionKey - This must be your Authorization Key.

Open Edge Legacy

An older version of Open Edge.

  • https://www.openedgepayment.com/
  • This version of Open Edge uses the x-www-form-urlencoded HTTP request content type for tokenization requests.
  • Settings for Open Edge Legacy are very similar to Open Edge:
    • aeCCType - Must be set to L.
    • AeCCDeviceID - This needs to be set to your Terminal ID.
    • aeCCTransactionKey - This must be your Authorization Key.

TSYS

TSYS is a division of Total System Services LLC and an ISO of Wells Fargo Bank.

  • https://www.tsys.com/
  • Settings for TSYS are:
    • aeCCType - Must be set to T.
    • AeCCDeviceID - The Device ID for TSYS.
    • AeCCPassword - This needs to be the password configured for your TSYS Webservice.
    • AeCCTransactionKey - This value will be automatically set for you on first using TSYS. Once set, it can be viewed from Settings.
    • AeCCUserName - This must be the username associated with your TSYS account.


Sample Payment Flows

The following sample describes tokenized gateway configuration of payment processing in AIMStorefront.

Setup for single tokenized gateway

  • Site administrator Dave has configured his site (cellofellows.com) to use the TSYS Tokenization Payment Gateway when processing rental payments, and as the Checkout Payment Gateway (Manual).

Shopper Engagement Part 1

  • Sally the shopper creates an account. 
  • She browses to the rental page (in this example, cellofellows.com/aerntschoolselect.aspx).
  • She chooses her district and school and decides to rent a cello for $100.
  • After entering her billing information and credit card, she submits the page.

Payment Tokenization and Processing - Rentals

  • The TSYS Tokenization Payment Gateway takes Sally's credit card number and tokenizes it into a form which AIM Desktop can accept and charge.
  • AIM Desktop receives Sally's payment token along with the charge request. Sally is charged for $100.
  • Sally receives a receipt and confirmation.

Shopper Engagement Part 2

  • A few months later, Sally visits the site to update her rental credit card information.
  • While she's on the site, she decides to buy several books of sheet music. She is prompted in checkout to enter her payment information, which is directed to send the charge to AIM through the tokenized gateway.
  • CelloFellows admins process the charge through their AIM Desktop for the order.
  • She receives her receipt.

Payment Processing - Rentals and Checkout

  • AIM Desktop is able to charge her for her rental extension using the same payment token that was generated from TSYS. That information has already been collected and her card hasn't expired, so it can continue to be charged.
  • The admins process Sally's payment using the information she entered during checkout through TSYS

The following sample describes tokenized gateway configuration of payment processing for Rentals while using a Checkout Payment Gateway for cart Checkout in AIMStorefront.

Setup for tokenized gateway for Rentals, cart checkout gateway for product Checkout

  • Site administrator Dave has configured his site (cellofellows.com) to use the TSYS Tokenization Payment Gateway when processing rental payments, but the Checkout Payment Gateway value has been set to a Checkout Gateway. The Configuration - Settings - PaymentGateway will reflect this value, such as AuthorizeNet or PayPal
  • In order for the cart to switch over to the tokenized gateway for Rentals, the MANUAL Payment Gateway is set in the Configuration - Settings - PaymentGatewayBackup

Shopper Engagement Part 1

  • Sally the shopper creates an account. 
  • She browses to the rental page (in this example, cellofellows.com/aerntschoolselect.aspx).
  • She chooses her district and school and decides to rent a cello for $100.
  • After entering her billing information and credit card, she submits the page.

Payment Tokenization and Processing - Rentals

  • The cart attempts to first use the Checkout Payment Gateway set in the PaymentGateway setting. This will fail a few times (per setting value), then switch over to the MANUAL method, which then uses the tokenized gateway, such as TSYS in this case.
  • The TSYS Tokenization Payment Gateway takes Sally's credit card number and tokenizes it into a form which AIM Desktop can accept and charge.
  • AIM Desktop receives Sally's payment token along with the charge request. Sally is charged for $100.

Shopper Engagement Part 2

  • Sally receives a receipt and confirmation.
  • A few months later, Sally visits the site to update her rental credit card information.
  • While she's on the site, she decides to buy several books of sheet music. She is prompted in checkout to enter her payment information, which is directed to use the Checkout Payment Gateway.
  • The gateway charges Sally for the sheet music order, processed through the cart rather than AIM.
  • She receives her receipt.

Payment Processing - Rentals and Checkout

  • AIM Desktop is able to charge her for her rental extension using the same payment token that was generated from TSYS. That information has already been collected and her card hasn't expired, so it can continue to be charged.
  • The admins process Sally's payment using the order data in the cart.