Using Payeezy with Aeon

Follow

Credit card payments made using Payeezy are made on a secure page hosted by this provider. When a researcher chooses transactions to pay for and clicks the Pay Now button on the Aeon Orders to Approve/Pay form (ViewOrderApproval.html), they are taken to the Payeezy-specific CreditCardPayment form. Clicking the Pay Now button on this form takes them to a secure page outside of Aeon to perform the credit card transaction.

After the payment is submitted and the transaction is complete, the researcher is redirected back to the Orders to Approve/Pay page in the Aeon web interface. The form shows an updated balance due and the status line at the top of the form notifies the researcher that the payment was successful and displays the payment confirmation code.

Aeon integrates with Payeezy using the Hosted Checkout method.

Configuring Customization Keys for Payeezy

The payment provider keys used to set up Payeezy are located in the Aeon Customization Manager under System > Billing.  you will need to set the following key values:

PaymentProviderMerchantId

Enter the Payment Page Id provided to you by Payeezy, which can be obtained from the Payment Pages section of the Payeezy website.

PaymentProviderResponseToken

This is the Response Key used to authenticate responses sent from Payeezy to the Aeon system. This value is the response key that displays on the security tab of the payment page within the Payeezy merchant interface.

PaymentProviderToken

This is the Transaction Key used for encryption when sending the initial request from Aeon to Payeezy. This value is the transaction key that displays on the security tab of the payment page within the Payeezy merchant interface.

CreditCardTransactionsDescription

This value is used as a product description on the Payeezy website to describe the researcher's purchase. Payeezy does not display this value to the customer. The default value of this key includes the transaction numbers of the included requests:  Aeon Photoduplication charges for transaction(s) <#PARAM name='TransactionNumbers'>. This key is located under System > General.

Editing the Web Forms for Payeezy

Below are the steps necessary to set up the web forms to work with Payeezy. Specialized ViewOrderApproval and CreditCardPayment forms have been created to work with Payeezy. Your Implementation Coordinator or Customer Service Agent will supply these to you when you are setting up your payment provider information. They are also available as a zip file at Aeon Downloads.

ViewOrderApprovals Form

Replace the default ViewOrderApprovals form in the Web folder with the ViewOrderApprovals form designed to work with credit card payments. This form contains the Pay Now button that takes the researcher to the CreditCardPayment.html form.

CreditCardPayment Form

Replace the default CreditCardPayment form in the Web folder with the Payeezy CreditCardPayment.html form. Make the following changes to these hidden fields on the form:

  • x_relay_url. By default, this field is set to the value of the WebDLL customization key, but in some instances, it may be necessary to change this value to use a specific URL. The most common case is if you have both a protected and unprotected Aeon directory. For instance, if you are Shibboleth, you will want to set the x_relay_url to the unprotected directory.
  • transactionNumbers. This field provides the value that will be used on the Payeezy website to describe the researcher's purchase. The default setting simply pulls the value from the CreditCardTransactionsDescription customization key but can be changed if you wish to differentiate the product's description, and additional values can be added.

Note that the javascript of this page has been changed from previous versions. If a user cancels the page the account is returned to the Main Menu:

$("#cancel").click(function() {

                      window.location.replace("<#DLL queryFields=false>?action=10&form=10"

Aeon Relay Response URL

The Relay Response URL will be necessary when configuring your Payeezy settings. This needs to be formatted very precisely in order for the successful integration of Aeon and Payeezy.

The default URL is the value of the WebURL customization key with “aeon.dll?action=11&type=110” appended to the end

In some systems, such as those using Remote Authentication, the Relay Response URL is the value hardcoded in the CreditCardPayment.html page in the following tag:

<input type="hidden" name="x_relay_url" value="<#CUSTOMIZATION name="WebURL">aeon.dll?action=11&type=110">

Editing Payeezy Settings

Log into your Payeezy account, navigate to Payment Pages.

Create a new payment page to be used for Aeon.

Complete all fields with your site-specific information. The "Return to Your Site" URL should be replaced with your Aeon URL.

The Payment Types page should be configured based on your institution's local needs. If your institution has a finance office they may provide guidelines on how this should be completed if they need to set up another merchant or terminal to be used for Aeon. Aeon does not support level 3 processing.

Aeon does not need the Pay Now/Donate Now button.  That page can be skipped in the setup.

Aeon does not use the receipt page within Payeezy and instead redirects the user back to Aeon after payment is completed. Since the receipt page is not used internally and instead uses the Authorize.Net Protocol, the return link method should be set to “Link”. Be sure to check the “Allow Relay Response” checkbox and enter your Relay Response URL as indicated above. The “Allow HTTP Redirect to Merchant Website” should be enabled which allows Payeezy to redirect to the Aeon web interface after the Relay Response is successfully validated. Atlas Systems also recommends enabling the “Retry Failed Relay Responses” setting so that if there are any networking issues after the payment is completed the transactions can be successfully recorded from Payeezy to Aeon at a future time.

Please note that the Payeezy support staff reviews all relay response URLs for both their demo and production interfaces. The configuration does not need to be completed for the Payeezy staff to review but the Aeon DLL needs to be working. If you view the Payeezy relay response URL you should see a blank white page. This is normal. Please plan accordingly when attempting to test Payeezy or move to a production environment and allow time for Payeezy staff to complete their review. Once their review is complete the URLs will show on the page with a green checkbox.

The configuration of Receipt Emails, the Customize Form, and Appearance is all based on the institution’s local needs. Aeon does not require any specific configurations for these settings. Aeon does not enable recurring billing; the “Enable Recurring Payments” section should be disabled.

The final step is to get the security settings which will be needed for input in the Aeon customization manager. The encryption type should be set to MD5. You can use the transaction key & response key as configured or click the buttons to generate new keys as needed. The Transaction Key from this page should be entered as the value for the PaymentProviderToken customization key. The Response Key from this page should be entered as the value for the PaymentProviderResponseToken customization key.

Be sure to “Create” the payment page when you have finished configuring your Payeezy payment page for Aeon.

Workflow

The user will navigate to the Order Billing page and should select the transactions they want to pay for and then click the "Pay Online" button.

The user is presented with a confirmation screen showing all transactions selected and a total amount. The user will then click the "Pay Now" button to be directed to the Payeezy payment form.

The user will enter their payment information.

After completing the payment the user is redirected back to Aeon and should see a status to indicate payment has been accepted. The transactions that were paid for will no longer appear when clicking the "order Billing" page.

Questions?

If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation:

Feedback