Knowledge Base

Get help for payment solutions. Search our articles or browse by category below.

Testing Guide



1 Scope

This document describes the best practice methods to test your integration with the Worldnet payment gateway using our test server accounts and sandbox accounts. It is intended to facilitate thorough testing, resulting in an issue free launch with our live service. You should have chosen your integration method and be familiar with our Integration Guide and have begun integration before reviewing this document.






2 Test environment

All testing should always be done on a test environment, separate from the live web server. Testing on the live server can cause many live problems such as:

    • unnecessary downtime

    • live transaction corruption/loss

    • incorrect/incomplete results of live transactions

    • customer frustration

    • undiscovered issues over time, effecting large numbers of transactions

    • chargebacks

    • PCI DSS implications






3 Setting up the test environment

You should ensure that your test environment is configured as close as possible to your live environment, particularly:

    • Web server (IIS/Apache) version

    • Web server configuration, especially the language interface (PHP/ASP etc.) and session timeout

    • Database connectivity

    • Firewall

    • The identical shopping cart version & configuration to the live environment (if using shopping cart software)






4 Planning your testing

If you are not using a plug-in supplied by Worldnet, then before testing should be attempted at all, you should become familiar with the relevant sections of our Integration Guide document. This is a complete and definitive guide to integrating your systems with the Worldnet gateway no matter what programming language, transaction types or integration method.

Planning your testing depends a lot on your method of implementation. For example if using our Hosted Payment Page (HPP) you should test the situation where a redirect back from our host fails, whereas this is unnecessary if you are using the XML gateway.






5 Background Validation

Also, if using our Hosted Payment Page solution, you should seriously consider implementing Background validation. What Background Validation does is, in the case where for some reason the transaction is authorised but the response fails to get back to your site (customer closes browser/your site is temporarily unavailable/etc.), our host will intermittently send a server side post to a URL with the order ID & transaction result until it receives an “OK” response. This ensures that your order system accurately reflects the transaction result even in the case where the cardholder redirect fails.






6 Security concerns when testing

The PCI DSS states that you should never use live cards in a test environment, otherwise this environment is also subject to PCI audit and DSS rules. For this reason you should only ever use test card numbers, such as those listed in this document. Worldnet cannot be held accountable for live cards being put through our test systems and sandbox accounts.






7 Things to test

7.1 All cases

You should ensure that your test environment is configured as close as possible to your live environment, particularly:

    • Host is unavailable (i.e. Use invalid test host URL)

    • Request details (including hash) are incorrect

    • Response Hash string is incorrect

    • Responses for all possible transaction results (Authorisation/Decline/Referral/Failure) (see “Testing resources” section for details)

    • PCI DSS guidelines are met in all scenarios

    • Refreshing the receipt page does not re-perform the transaction/resend the receipts

    • All required currencies are processed correctly






7.2 Per integration method

7.2.1 Hosted Payment Page/POST Page

    • Customer doesn't complete transaction (e.g. closes browser window)

    • Incorrect Receipt Page URL configured (same as response redirect failure)

    • Customer takes 60 mins to complete entering details

    • Simultaneous transactions do not interfere with each other

    • Background Validation is successful for all transactions and responses (if implemented)






7.2.2 HML gateway

    • Card number/CVV fields can only contain numeric characters (no spaces either)

    • Non-numeric characters (including spaces) are not sent in numeric fields

    • Remote XSD file unavailable (fallback to local cache?)

    • XML fails validation against remote XSD file

    • Host returns a failure due to incorrect content in XML request

    • Host returns a System Error response

    • Host does not return anything

    • Host returns extra response fields






7.2.3 When using shopping cart plug-ins

Testing will be quite specific depending on the shopping cart and plug-in being used. If you have downloaded this guide from within a plug-in zip file as apposed to being sent it directly from Worldnet, please e-mail support@worldnettps.com to confirm that you have the latest version on the plug-in for your solution. Please include the name and version number of the shopping cart software and the name of the plug-in zip file that you downloaded.

You should cover all the relevant test above for your integration method, even though the functionality is obscured by the plug-in you are using. The issues outlined above can still occur. However other shopping cart issues that should be tested are:

    • Card number/CVV fields can only contain numeric characters (no spaces either)

    • Order status is updated correctly in shopping cart

    • Customer e-mails are populated correctly

    • Customers get the right number of e-mails (our host may also send an e-mail to the customer depending on the plug-in)

    • Session timeouts do not cause transactions not to be dropped/lost

    • Transactions over 1,000 and 1,000,000 Euro/Pounds/Dollar etc. are handled correctly






8 Testing resources

8.1 Sandbox

Basic transaction testing can be done through our sandbox accounts. You do not need a dedicated test account for this type of basic proof-of-concept testing,






8.2 Test cards and responses

Test cards that can be used on our host are:

Card Scheme Card Number Requires CVV
American Express 3400000000000000 Y
Debit MasterCard 5100270000000007 Y
Diners 3600000000000008 N
Discover 6011000000000004 Y
JCB 3528000000000007 Y
Maestro 5000330000000000 Y
MasterCard 5001650000000000 Y
Switch 6301144000000009 N
Visa Credit 3779810000000005 Y
Visa Debit 4000060000000006 Y
Visa Electron 4001020000000009 N

All test cards can be used with any expiry date in the future, any CVV (n.b. American Express cards have a 4 digit CVV) and any Issue number where appropriate.

Various different responses can be simulated by using different cent amounts for transactions. The cent values and their respective responses are:

Cent Value Response
0.01 Declined
0.02 Referral
0.03 CVV failure (Decline)
Any other Authorised

Meaning that if you enter 5.01, 99.01 or 1754.01 you will get a decline, for example.






9 Worldnet Testing verification

For large merchants, Worldnet will be happy to coordinate testing with you, provide/review specialised test scripts, and help with any issues raised. If you would like to avail of this service, please feel free to contact support@worldnettps.com




Copyright © 2017 Worldnet Knowledge Base | Powered by DokuWiki
developer/integration_docs/testing-guide.txt · Last modified: 2016/07/26 13:10 (external edit)