Summary / TL:DR: This article will introduce the best practices when placing test orders from order forms in WMC.

11 min read

1 Recommendations
2 Adding Clear Cache Extensions for Chrome or Firefox
3 Using an Incognito Window When Testing
4 Testing in Different Browsers
5 Disable Caching Using Chrome Developer Tools (Advanced)
6 Test Credit Card Numbers
7 Test SEPA Accounts
8 Test Direct Debit Accounts
9 Understanding Browser Sessions in Funnelcake
10 Preview, Line Preview, and Funnel Preview Differences
11 Testing on Internal and External Networks
12 Testing Pre-Auth in Staging
13 Testing Pre-Auth in Production
14 Wrap up

Recommendations

For example, a user may load an order form and discover there is a typo in the copy. They will close the browser tab where the order form was loaded, fix the typo, re-publish the creative, and then load the order form again. At this point they may see that the typo is still visible on the page. This is a result of the browser caching the previous version of that order form - it is not an issue with the application.

Browser Caching can be defined as:
A temporary storage area in memory or on disk that holds the most recently downloaded Web pages. As you jump from Web page to Web page, caching those pages in memory lets you quickly go back to a page without having to download it from the Web again. In order to ensure that the latest page is displayed, the browser compares the dates of the cached page with the current Web page. If the Web page has not changed, the cached page is displayed immediately. If the Web page has changed, it is downloaded, displayed and cached.

Adding Clear Cache Extensions for Chrome or Firefox

Adding Click & Clean for Chrome

From a Chrome browser, open the following link in a new window: Clear Cache for Chrome.
Click
Select
In the new browser tab, select
Close the browser tab to save your settings.

The extension will appear to the right of the address bar.

Adding Click & Clean for Firefox

From a Firefox browser, open the following link in a new window: Clear Cache for Firefox
Click
Click

Once the browser has reopened, the extension will appear to the right of the address bar.

Using an Incognito Window When Testing

For Chrome

Right-click on Chrome in the task bar
Select New incognito window
Paste the order link in the address bar of the incognito window

Note:
Steps one and two can be accomplished in Chrome by using the shortcut ctrl+shift+n

For Firefox

Right-click on Firefox in the task bar
Select New private window
Paste the order link in the address bar of the incognito (private) window

Note:
Steps one and two can be accomplished in Firefox by using the shortcut ctrl+shift+p

Testing in Different Browsers

Since sessions across browsers are completely separate, using multiple browsers will reduce the amount of cache clearing you'll have to do. You may have to clear each browser's cache if your tests require you to open the same link multiple times in each browser.

Disable Caching Using Chrome Developer Tools (Advanced)

Note
This only works in Chrome.

Open Chrome and hit F12 on your keyboard. This will open Chrome DevTools.
Click the ellipse at the top-right corner of the DevTools screen.
Select
Under the Preferences tab, within the Network section, make sure Disable cache is enabled.

Test Credit Card Numbers

This is because we integrate with a Spreedly iFrame to host the CC number. Since this field is an iFrame, we cannot know what the number is and therefore had to divert this functionality into another field (which we chose the Cardholder Name). The following information can be used on the Order Page to submit an order without running Pre-Authorization. This will assist in the testing the Journey works as expected based on the different interactions and validating that an order can be sent to BOSS/OSM/Advantage. This can be used in Production and UAT.

If you need to test Pre-Authorization, see the data further below in this document.

Cardholder Name

Notes

Test without Boss

Will skip pre-auth, Kount, and BOSS. Allows user to navigate Journey without integration dependencies.

This is the Equivalent to the 4111 1111 1111 1111 CC in OPIUM.

Test Boss

Will skip Pre-Auth and Kount, but send the order to BOSS.

This is Equivalent to the 4242 4242 4242 4242 and 4444 3333 2222 1111 CC's in OPIUM.

Test SEPA Accounts

IBAN	BIC/SWIFT	Notes

IBAN	BIC/SWIFT	Notes
GB73RMGE06844057476330	BARCGB22	This account will not be sent to BOSS
CH0515571170854070729	BZBKCH2WXXX	This account will be sent to BOSS

Test Direct Debit Accounts

Account Number	Sort code	Notes

Account Number

Sort code

Notes

10213667

206582

This account will be sent to BOSS

Customer Name: Test Ignore

30060230

306296

This account will not be sent to BOSS

Understanding Browser Sessions in Funnelcake

When a user loads a Funnelcake order page in a web browser, a Funnelcake session is created between the browser and the application. If a new Funnelcake session is needed, for testing purposes for example, it is important to close the previous browser used for a Funnelcake session and open a new browser (preferably in an incognito window) to execute another test.

Preview, Line Preview, and Funnel Preview Differences

The 'Live Preview' option in the code editor will open a new web browser and renders the HTML related information as you are typing; however, it will not display the data for widgets and will instead show the widget text as it is written in the code editor.

To preview the page with all content and data elements, as a customer would experience, you will need to save the creative and use the 'Preview' option at the top of the page. This version of the Preview is a static page and will not allow you to select hyperlinks to place an order or move onto another page via the Yes/No links.

To experience the entire Funnel as a customer would, you will need to utilize the "Funnel Preview" link that exists on the Funnel Page. This link will allow you to navigate through the entire Funnel, place orders, and receive confirmation emails.

Testing on Internal and External Networks

It is possible that certain networks, such as Agora vs non-Agora, will behave differently.

Test on a desktop on the internal network
Test on a desktop on an extneral network
Test on a mobile device on the internal network
Test on a mobile device on an external network
Test the entire process, from IRIS to Funnelcake
Test that the URL is redirected from a non-secure to a secure

Testing Pre-Auth in Staging

Instead, Vantiv has assigned specific Credit Card Numbers to be returned with a specific response code if used in the staging environment to allow for testing of the functionality. Below are the Credit Card Numbers and the response code they will trigger.

Testing Data for Vantiv Processor

Response Code	Credit Card Type	Credit Card Number	Response Message	Order Page Error Message	Pre-Auth Status

Response Code	Credit Card Type	Credit Card Number	Response Message	Order Page Error Message	Pre-Auth Status
000	VI	4457000800000002	Approved	N/A	APPROVED
000	VI	4457000900000001	Approved	N/A	APPROVED
000	VI	4457001000000008	Approved	N/A	APPROVED
000	MC	5112000900000005	Approved	N/A	APPROVED
101	MC	5112001000000002	Issuer Unavailable	N/A	APPROVED
101	VI	4457002700000009	Issuer Unavailable	N/A	APPROVED
101	VI	4457003000000004	Issuer Unavailable	N/A	APPROVED
101	MC	5112002000000000	Issuer Unavailable	N/A	APPROVED
110	VI	4457002100000005	Insufficient Funds	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
120	AX	375000030000001	Call Issuer	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
120	VI	4457001200000006	Call Issuer	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
120	VI	4457001300000005	Call Issuer	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
120	VI	4457001400000004	Call Issuer	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
120	VI	4457002200000004	Call Issuer	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
123	DI	6011000400000000	Call Discover	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
301	MC	5112001600000006	Invalid Account Number	This appears to be an invalid credit card number. Please check your card number and try again.	NOT_APPROVED
301	MC	5112001700000005	Invalid Account Number	This appears to be an invalid credit card number. Please check your card number and try again.	NOT_APPROVED
301	VI	4457000100000000	Invalid Account Number	This appears to be an invalid credit card number. Please check your card number and try again.	NOT_APPROVED
303	VI	4457002000000006	Pick Up Card	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
305	MC	5112001900000003	Expired Card	This appears to be an expired credit card. Please try a different credit card.	NOT_APPROVED
321	VI	4457001900000009	Invalid Merchant	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
321	MC	5112001800000004	Invalid Merchant	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
322	VI	4457002800000008	Invalid Transaction	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
340	VI	4457002500000001	Invalid Amount	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
349	VI	4457002300000003	Do Not Honor	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
350	AX	375000050000006	Generic Decline	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
350	VI	4457002900000007	Generic Decline	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED

Testing Data for World Pay Orders

Response Code	Magic Value	Response Message	Order Page Error Message	Pre-Auth Status

Response Code	Magic Value	Response Message	Order Page Error Message	Pre-Auth Status
0	Authorised	Authorised	N/A	APPROVED
5	Refused	Refused	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
7	Error	Error	N/A	APPROVED
4	Refused4	Hold Card	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
5	Refused5	Refused	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
8	Refused8	Approve after Identification	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
13	Refused13	Invalid Amount	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
15	Refused15	Invalid Card Issuer	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
17	Refused 17	Annulation by Client	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
28	Refused28	Access Denied	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
29	Refused29	Impossible Reference Number	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
33	Refused33	Card Expired	This appears to be an expired credit card. Please try a different credit card.	NOT_APPROVED
34	Refused34	Fraud Suspicion	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
38	Refused38	Security Code Expired	Credit card security code appears to be invalid. Please correct the security code and try again.	NOT_APPROVED
41	Refused41	Lost Card	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
43	Refused43	Stolen Card, Pick Up	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
51	Refused51	Limit Exceeded	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
55	Refused55	Invalid Security Code	Credit card security code appears to be invalid. Please correct the security code and try again.	NOT_APPROVED
56	Refused56	Unknown Card	This appears to be an invalid credit card number. Please check your card number and try again.	NOT_APPROVED
57	Refused57	Illegal Transaction	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
62	Refused62	Restricted Card	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
63	Refused63	Security Rules Violated	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
75	Refused75	Security Code Invalid	Credit card security code appears to be invalid. Please correct the security code and try again.	NOT_APPROVED
76	Refused76	Card Blocked	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
85	Refused85	Rejected by Card Issuer	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
973	RefusedR1	Revocation of Authorization Order	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED
975	RefusedR2	Revocation of All Authorizations Order	We were unable to successfully charge your credit card. Please contact issuing bank for assistance.	NOT_APPROVED

Testing Pre-Auth in Production

The Funnelcake Team does have a few AMEX Gift Cards that have a $0 balance that can be used to validate that Pre-Auth does occur on initial order pages and subsequent up/cross-sells. Additionally, you'll also be able to test that the Default Order Form populates to allow the customer To test this out, please follow these steps:

Steps in Production for US Affiliates

Create an Order Page that has 2 choices; one for $0 and another for a value greater than $0
1. Note that if you don't have a choice with $0, you can create this manually but ensuring that you set the Item Code properly
Create a Page that has an up-sell and Cross-Sell that have a value greater than $0
Create a Funnel that contains only the Order Page and Page created in steps 1 and 2
Open the Funnel Preview Link
Select the Choice that has a value greater than $0
Use the Credit Cards listed below and place the order
Pre-Auth fails and you'll get an error message on the Order Page
Change your choice to the $0 choice
Place your order again
You'll be redirected to the Page
1. Note that since the choice is $0 and the credit card has $0, it is still eligible to purchase the choice
Select the Up-Sell or Cross-Sell
Pre-Auth fails and you'll be redirected to the default order form to enter a new CC

$0 Gift Cards for Production

Type	Card Limit	Number	Expiration Date	CVV

Type	Card Limit	Number	Expiration Date	CVV
AMEX	$0	3790 164832 09184	05/25	9214
AMEX	$0	3790 166422 89317	01/24	3257
AMEX	$0	3790 166483 12303	01/24	1040

Wrap up

You should now have a better understanding of the best practices when placing test orders from order forms in WMC.

Still need help?

We know this can be frustrating. To get further help please open a Support ticket.

Click here to open a ticket

WMC Support

eComm Testing Best Practices

Table of contents