Development Notes

Testing Transactions

Below are fields and values you can use to test specific responses:

  • A transaction amount ending in ‘1’ will be declined : AMT=2001
  • A credit card with the expiry month in April will be declined: EXP=0423

For test cards, you can use any valid Visa/MasterCard card number since your test terminal setup does not push any card data to the card networks. Here’s a couple of easy ones that we often use:

4003000123456781

5454545454545454

4111111111111111

5431111111111111

Web-Redirect URL’s in Test Environment

Test Account URL Override

As part of the gateway setup you provide a Return URL that is used to redirect the customer back to your website after the payment is completed. These URL’s are used for all transactions and cannot be customized for each transaction.

To aid with the development of your website a test TERMID can accept fields to override the Return URL value on a per-session basis. This allows for development testing with different landing pages for the redirect back to your website.

RETURNURL= https://localhost/payreturn

s

Ampersands (&) in the URL will be encoded to %38 and must be decoded back to the ampersand (&)

p

For testing purposes, URL may be http instead of https

Test Account Redirect Override

As an aid for development the final redirect back to your Return URL can instead be presented as a web page with a link that is the same as the redirect would have been and additional links showing how to send the GetResult and Ack requests.

To activate this add a flag to the StartSession request:  TESTREDIRECT=Y

p

This flag will be ignored if sent with a 'live' TERMID

Using PaymentsHQ

Utilize your Partner Login to PaymentsHQ to view the Gateway Log. You have complete oversight of all gateway activity.

You will also be given a ‘Test Merchant’ Login to PaymentsHQ. This is useful to view what your user’s experience will be. For example, you will see the benefits of using the INV field as a way to group transactions.