Required settings page for uc_chase_paymentech module

This project is not covered by Drupal’s security advisory policy.

This module adds Chase Paymentech hosted checkout as a payment method to Ubercart. This module is complete in its ability to function as a payment interface between Ubercart and Chase Paymentech. Upon checkout the user is sent to Chase's payment site for payment completion. When the customer completes their payment, or their payment is declined, a response is sent back to the user's site and their order is updated accordingly.

Multilingual

This module now has multilingual support. The hosted checkout service is not itself translatable, but you can create multiple pay pages using your Chase account. So for the example of having a french and english website you would follow these instructions:

  1. create 2 payment pages within your Chase Paymentech hosted checkout account, one for the french version of your payment page and the other english.
  2. each payment page has separate login ids, transaction and response keys. Record these separately.
  3. on the ubercart payment method settings page for chase paymentech payment method click on the payment pages tab.
  4. If you site is multilingual then you will see options for your default language and extra configuration options for each language that is enabled.
  5. Fill in the respective login, transaction and response keys for each language.
  6. click save.
  7. done

Notes:

  1. This module works for Chase's Canadian implementation of Hosted Checkout. I am not sure if the American site offers this same integration.
  2. Debit transactions can be used through this interface, however, at the moment there is no completion page to display to the user their debit transaction response as required by debit companies.
  3. This module supports POST, LINK and REDI response methods, but does not currently support a RELAY response. REDI can be used to automatically redirect the customer back to your site once their transaction is completed. The POST and LINK methods require the customer to click the link to return to your site. In this case if the user does not click the link and instead chooses to browse elsewhere, the order will not be updated with the transaction information. This issue will be resolved once the RELAY response is implemented. For the time being choose REDI response to avoid this issue.

There isn't currently a module that integrates Ubercart with Chase Paymentech. Although Chase uses e-xact, which bases their hosted checkout on Authorize.net's framework, their specific implementation and methods of response verification are different in functionality. There is not a sensible way to go about modifying the Authorize.net module that ships with Ubercart to incorporate Chase Paymentech without rewriting the entire Authorize.net module to make it more generic and adaptable to other Payment Companies and their implementations of the authorize.net framework. This may be an option for the future. However, at the moment, a properly maintained and secure module to integrate Chase Paymentech with Ubercart is certainly needed.

Here it is... enjoy.

 
 

Sponsored by:

OpenConcept Inc.
http://openconcept.ca

Project information

Releases