Release date: November 24, 2009

With release 2.4 developers may now process a previously processed transaction without any need for knowing the credit card or eCheck information. In this release eCheck is also an option. Clients who wish to use eCheck need to apply for an eCheck account separately.

ReferenceTransaction

Every transaction processed through the API will have a response with the following two parameters:
  • OrderNumber
  • VaultGUID

For repeat orders using the same credit card or eCheck the transaction may be duplicated with a new amount through passing the OrderNumber & VaultGUID.

Read more:

eCheck

Transactions may now be processed through eCheck. eCheck accounts are set up separately through our partner. Organizations wishing to use eCheck should contact [email protected] and request an application.

The API manual describes in detail how the eCheck processing may be added to a program.

New Behavior:

Receipts will automatically be sent to the distribution list provided by the CheckOutPageID node. If a checkout page is referenced in the Receipt node the notification list as stated for the checkout page will be used for sending the notifications. node will be in addition to the ones that are already listed for the checkout page.


Questions?


Please post to the PaaS discussion group in this forum.