Developer News

The SSL certificate for the www.usaepay.com website will be expiring on 10/10/2009. In an effort to make the transition to a new certificate as smooth as possible, we will be going through two test windows prior to the final transition. During these test windows (on 9/29 and 10/4), the current certificate will be replaced with the new certificate. Merchants and developers should test their software during these test windows to ensure compatibility with the new certificate.

For the majority of merchants the new certificate should not cause any issues as long as their software is up to date. Out of date software that does not work with the new certificates will need to be upgraded or replaced by October 8th when the old certificate is permanently replaced.

Developers who do encounter issues with the new ssl certificate should contact the integration support department for assistance.

→ Read more...

Version 1.2 of the Soap API has been released. This version includes 9 new methods and dozens of modifications to existing methods and objects. The majority of the changes in this release are aimed at improving speed of the API and its usability for developers. Some of the highlights include:

• Sort parameter added to all search methods
• Count version of all search methods added to allow determination of result size before retrieval
• Added getCustomerPaymentMethods, getCustomerPaymentMethod and updateCustomerPaymentMethod to allow working with payment methods independently of customer objects.

For a complete list of all changes in the 1.2 release please visit the release notes page.

In addition to the modifications to the API, the documentation has also been improved. We are now maintaining independent documentation pages for all soap releases, 1.1 and beyond. To access the documentation for a specific release visit the release notes page. A new navigation index has also been added to all soap documentation page to allow easy navigation within the documentation. Lastly, a new C Sharp howto guide has been posted complete with a sample visual studio project.

→ Read more...

A new version of the payment module for Zen Cart is now available here. New features include Sandbox mode, PIN support for source keys, line item details in the transaction details screen and Card ID (CVC/CVV2) response. Gone is test mode (now use Sandbox) and the module itself is a few files smaller for easier installation. The Zen Cart website will soon be updated with the module as well. In the mean time grab it from the link above.

The new version of the Reseller Console has been released to production servers. There is a new look and and new functionality has been added. Resellers, feel free to log in and look around!

Please report any bugs to: devsupport@usaepay.com

For inquiries on the new features and functionality please contact: resellers@usaepay.com

We will be updating reseller documentation shortly.

A new version of the Transaction API has been posted to the production servers. This release adds support for check scanners and Check 21 transactions.

Two new fields, UMcheckimagefront and UMcheckimageback, have been added to the API. These fields can be used by developers to send in scans of the front and back of checks. Additionally, the UMcheckimageencoding field is used to describe the encoding format of the image data.

Transactions that have image data will have an additional check image icon in the “Check Manager” section of the merchant console. Merchants can view the check images on the transaction details screen.

At approximately 6:40pm PST power was lost in CA1 datacenter. Power was restored at 11:30pm and service was brought back on line 12:00am PST.

During the outage, traffic was automatically re-routed to alternate datacenters.

Currently all processing is online and functioning at CA1.

New versions of the Transaction API and Payment Form have been posted to the production servers. We encourage all 3rd party developers to test their applications against the new releases.

The following fields have been added to both the Transaction API and Payment Form:

• UMcustreceiptname - Specifies the name of a custom receipt template to use
• UMline variables - Adds the ability send line item details for an order
• UMaddcustomer - Replaces the UMrecurring variable to prevent confusion (The UMrecurring variable will continue to be available for backward compatibility)

The following result variables have been added:

• UMprocRefNum - The bankend processor's transaction reference num
• UMcardLevelResult - Indicates the card level result code (for Visa cards). This can be used to determine visa card type (gift card, prepaid card, check card, etc)

In addition, the following changes have been made:

• UMcustom fields now store custom data for both transactions and customers.
• UMschedule now supports “disabled” for adding customer without enabling recurring billing.

USAePay has released an enhancement to the emailed and print receipts. The new system allows merchants to customize all built in receipts using a simple template system. The email receipts now support both text and HTML formats. Merchants can also create custom receipts that are assigned to specific Payment Forms or Source Keys.

A new “Receipts” screen has been added to the “Settings” section of the Merchant Console. This screen allows for the customization of system built in receipts as well as the creation of new receipts.

→ Read more...

A new section, “Pre-Made Customer Reports”, has been added to the Reports section of the merchant console. New reports include: “Pending Billing” which allows merchants to view future recurring billing entries by date or by source/category, “Billing History” which displays the result of recurring billing by date or source/category, “Expired Cards” which allows merchants view customers who have credit cards stored that have already expired, “Expiring before Next Billing” which display customers whose credit cards will expire before their next scheduled billing and “Expiring by Date Range” which allows selection of a custom date range filter on expiring cards.

These new reports are available to all merchants who have access to the Customer Database feature. All reports support Multi-Merchant users.

→ Read more...

A new version of the user login screen has been posted to the production servers. This release gives merchants the ability to reset their passwords online. Initially this feature will be not be available to existing users. Existing users who would like to have the new feature enabled can contact customer support.

→ Read more...