Developer News

The sandbox environment is currently offline due to a hardware failure. There is no current ETA however, work to restore the environment is in progress. Initial estimates say that there will be no stored data loss.

Update 11:15am PST 8/27/2008: sandbox.usaepay.com has been back online since noon 8/25/2008 PST.

There were several short outages between the times of 11:43pm PST and 1:00am PST. The outage is currently being investigated. All connections are online and running.

The sandbox environment is currently offline due to a hardware failure. There is no current ETA however, work to restore the environment is in progress. Initial estimates say that there will be no stored data loss.

Update 2:28 pm PST 8/15/2008: sandbox.usaepay.com is back online.

At 04:48pm PST Wednesday, July 23rd, the connection to the Global platform in datacenter CA0 failed. Affected traffic was automatically rerouted through to an alternate datacenter.

Update 12:10am PST 7/24: Link remains offline due to a telco DS3 trunk outage. No ETA is available at this time. All Global traffic continues to be routed to alternate datacenter.

Update 10:22am PST 7/24: Repairs to the DS3 have been completed and service has been restored. Connection has been added back to the pool and is now passing traffic.

→ Read more...

Version 1.1 of the Soap API has been released. This version includes minor changes to the TransactionDetail and CreditCardData to support the recent addition of Pin Debit Card and Signature Capture devices.

Two new methods copyCustomer and moveCustomer have been added to facilitate copying data between merchants accounts. These methods are only available to merchants who have multiple location/accounts.

→ Read more...

The virtual terminal, sale form and ePayment form pages in the console have been updated to better prevent web browsers from auto-completing the credit card number, CVV2, check routing and account number fields. USAePay recommends that all users keep the auto-complete features disabled in their browser preferences because the auto-complete data is not stored in a secure manner.

→ Read more...

Vericheck is experienced a network outage that prevented the processing of checks on that platform. Affected merchants who attempt to process a check during the outage window received the error message “Temporarily unable to process transaction. Please try again shortly.”

UPDATE 1:35pm: Vericheck has resolved the issue and check processing is back on line.

→ Read more...

The “Quick Sale” page has been renamed to “Sale Form” to reduce confusion with other features in the gateway. The name change affects only the title of the page and it's link in the console menu, all functionality remain unchanged.

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:

• UMdukpt for pin debit transactions
• UMcomments for extended transaction notes
• UMsignature for signature capture support
• UMresponseHash response variable for transaction response verification

The UMmd5hash and UMmd5key have been superseded by UMhash but will remain supported indefinitely. Applications using UMmd5hash do not need to make any modifications to continue to work with the new release.

The Payment Form now supports custom templates for the transaction response page. To modify the response page template, go to the source key in the merchant console, click the customize payment form button. There are now two tabs. One for the form and one for the response page.

New versions of the Transaction API and Payment Form have been posted to the Sandbox and Staging servers. We encourage all 3rd party developers to test their applications against the new releases. The new versions are scheduled to go in to production on June 9th.

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

• UMdukpt for pin debit transactions
• UMcomments for extended transaction notes
• UMsignature for signature capture support
• UMresponseHash response variable for transaction response verification

The UMmd5hash and UMmd5key have been superseded by UMhash but will remain supported indefinitely. Applications using UMmd5hash do not need to make any modifications to continue to work with the new release.

The Payment Form now supports custom templates for the transaction response page. To modify the response page template, go to the source key in the merchant console, click the customize payment form button. There are now two tabs. One for the form and one for the response page.