This is a popular solution mainly due to the ease of integration into the solution and the high level of Security that it provides to merchants.
The form post URL is the Wirecard URL used to submit the form post to. Wirecard provides the following URL for both Live and Test.
URL : https://virtual.mygateglobal.com/PaymentPage.cfmCopy URL to clipboard
With this URL, mode 0 (test) and mode 1 (live) can be used.
For testing purposes, we have provided a MerchantUID and ApplicationUID's in multiple currencies.
MerchantID: F5785ECF-1EAE-40A0-9D37-93E2E8A4BAB3
When going live, these will need to be replaced in your code by using the Wirecard issued MerchantID and ApplicationID.
Test Cards are used to perform test authorizations to Wirecard. Test Cards will only work when using Test Mode (0) in the live environment. Test Cards transactions will not go to the acquirer.
Test Card Types
Note: Test Cards will not work in Live Mode (Mode 1) in the Live Environment.
Visa Successful | |
Card Name | Joe Soap |
Card Number | 4111111111111111 |
Card Type | Visa |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
Visa Declined | |
Card Name | Joe Soap |
Card Number | 4242424242424242 |
Card Type | Visa |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
MasterCard Successful | |
Card Name | Joe Soap |
Card Number | 5100080000000000 |
Card Type | MasterCard |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
MasterCard Declined | |
Card Name | Joe Soap |
Card Number | 5404000000000001 |
Card Type | MasterCard |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
Amex Successful | |
Card Name | Joe Soap |
Card Number | 370000200000000 |
Card Type | AMEX |
Expiry Date | Any date in future |
CVV Number(last 3 digits on back of card) | any cvv |
Amex Declined | |
Card Name | Joe Soap |
Card Number | 374200000000004 |
Card Type | AMEX |
Expiry Date | Any date in future |
CVV Number(last 3 digits on back of card) | any cvv |
Diners Successful | |
Card Name | Joe Soap |
Card Number | 36135005437019 |
Card Type | Diners |
Expiry Date | Any date in future |
CVV Number(last 3 digits on back of card) | any cvv |
Diners Declined | |
Card Name | Joe Soap |
Card Number | 36135182434011 |
Card Type | Diners |
Expiry Date | Any date in future |
CVV Number(last 3 digits on back of card) | any cvv |
Maestro Successful | |
Card Name | Joe Soap |
Card Number | 5641821111166669 |
Card Type | Maestro |
Expiry Date | Any date in future |
CVV Number(last 3 digits on back of card) | any cvv |
Maestro Declined | |
Card Name | Joe Soap |
Card Number | 6759411100000008 |
Card Type | Maestro |
Expiry Date | Any date in future |
CVV Number(last 3 digits on back of card) | any cvv |
Visa Successful | |
Card Name | Joe Soap |
Card Number | 4000000000000002 |
Card Type | Visa |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
Visa Failed | |
Card Name | Joe Soap |
Card Number | 4000000000000010 |
Card Type | Visa |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
MasterCard Successful | |
Card Name | Joe Soap |
Card Number | 5200000000000007 |
Card Type | MasterCard |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
MasterCard Failed | |
Card Name | Joe Soap |
Card Number | 5200000000000023 |
Card Type | MasterCard |
Expiry Date | Any date in future |
CVV Number (last 3 digits on back of card) | any cvv |
As additional account security, every credit card comes with a special three or four digit code generally known as a CVV2 or CVV number. Cardholders will be requested to enter this when processing an online payment. An identity thief who has come across credit card information illegally will not have access to the CVV number if they do not have physical access of the card.
Enter the full error code below:
View all Response Codes
Use the Go Live Check List to make sure that you have completed all necessary tasks before going live. Please ensure that the following criteria have been met:
Virtual Form Post have been embedded onto your website
Merchant Payment Page have been configured in Wirecard Web Console
Referral URL has been added in Wirecard Web Console
Merchant ID and Application ID of the “Merchant” (NOT test Merchant ID and Application ID) is being used in your message type.
Test a Successful Transaction using our Virtual Test Cards
Test a Decline transaction using our Virtual Test Cards
Test transactions are visible in Wirecard Web Console
Merchant received Go Live email from Wirecard. This email will contain the merchants Customer ID and Merchant ID .
(If not, have merchant contact support.za@wirecard.com)
Ensure that you are using the Live URL.
Ensure that you have added a referral URL.
Form Post Mode have been changed from 0 to 1 (0 test / 1 live)
Perform Live transaction with Live card
If you have in‐depth HTML knowledge or web development skills you can create more variables. The below examples could be applied if you have a web application or shopping cart. The Below HTML example shows how your form POST could look when extensive information is getting sent to Wirecard:
The below code can be copied into your code for testing purposes. Please note however, that before going live, you will need to change the details in the above example.
Select your sample code below:
Solution | View Code |
Virtual | View Code |
Virtual 1Click | View Code |
Visa Checkout | View Code |
If you are a merchant that has signed up with Wirecard's Virtual solution, you will have access to Wirecard's Integration Help Desk for telephonic and email support. Telephonic support is available 8am to 5pm GMT +2. Email support is 8am to 5pm GMT + 2 and connects directly to our help desk through our ticketing system.
If you are a developer that you will have access to Wirecard's Integration Help Desk for email support. Email support is 8am to 5pm GMT + 2 and connects directly to our help desk through our ticketing system.
If you send an email you will immediately be emailed back a reference to track your integration query.
Email: support.za@wirecard.com
The Virtual Payment Solution makes use of Wirecard's hosted payment page. This is a popular solution mainly due to the ease of integration into the solution and the high level of Security that it provides to merchants.
The Virtual Solution also has the ability to be customized to such an extent that your client would feel as though they are on your website while making payment, ensuring peace-of-mind throughout the entire checkout process.
The Virtual solution offers over 25 customizable payment page templates that can be configured. Logo's and details can be presented on that page so that the cardholder does not feel that they are leaving the merchants website. The Virtual Payment Page is operating behind TLS (Transport Layer Security) security protocol and all information that is captured on the payment page is encrypted using 128-bit encryption ensuring that your client's credit card details are kept safe.
One of the main benefits of utilising the Virtual Solution is the simplicity in which to integrate it into your online website. It requires less development work than other Wirecard Solutions and security measures are already incorporated by Wirecard.
Virtual allows the merchant to utilize the Wirecard payment webpage. This means that your clients will be directed to Wirecard's Payment Page where they will enter their credit card details in order for the transaction to be completed. The payment information which Wirecard requires is posted to Wirecard via a form POST. This POST can be done in any language that supports this method.
Illustration: Virtual Payment Process
Step 1 – Cardholder makes purchase from merchant's website.
Step 2 – Merchant creates form post to Virtual payment page.
Step 3 – Wirecard processes the transaction to the merchant Bank.
Step 4 – The merchant bank processes the transaction and returns a successful or declined message.
Step 5 – Wirecard returns this result and/or error code with error description back to the Merchant
Website address specified in the form POST.
Step 6 – If the functionality is set up (from the Wirecard Web Console) Wirecard will notify the card
holder via email of the transaction details and the merchant via email.
An Internet Merchant Account is required to accept credit card transactions over the internet. If you have an Internet Merchant Account you need to supply these details to Wirecard before going Live. If you do not have an Internet Merchant Account, Wirecard can assist you with your application to the acquirer (bank).
Note: An Internet Merchant Account is a different type of merchant account than what is used for card present / POS transactions. You will need to apply for an Internet Merchant Account even if you already accept credit card transactions from your store.
You need to apply security best business practice to ensure that confidential data and card detail are protected while either being stored in the database or while data is being transmitted. It is suggested that you encrypt key information issued to you by Wirecard such as merchantID, applicationID and transaction index.
Note: To reduce fraud or potential incidents it is recommended to encrypt any passwords that give access to your server.
TLS (Transport Layer Security) is a security protocol that ensures that data being captured on Wirecard's payment page cannot be read by encrypting the data using two encryption keys. The Virtual solution does not require a merchant to implement TLS protocol as this is handled by Wirecard.
Merchants can use Virtual to integrate with any of Wirecard's payment methods. The payment methods that Wirecard offer can be found at https://www.wirecard.co.za/payment-solutions/alternative-payments/
Examples of these payment methods are:
Integrating to a Payment Method
A merchant with multiple payment methods can choose to either: ‐
Note: Each payment method is linked to a unique Wirecard application ID.
Process Flow Description for Payment Options Page
Example of Payment Options Page
Payment Option Page Customization
The payment options page is customizable (example: merchant logo) to maintain the look and feel of the merchant system as far as possible. This is done from within the Wirecard Web Console. Click here to see how to upload logo.
1Click payments offers the card holder a simplified checkout experience. The solution caters for customers that repeatedly purchase goods or services from a merchant’s website by simplifying the checkout experience. The solution will tokenize the card holder’s details during the initial transaction. For subsequent transactions, the card holder is only required to enter their CVV to process the payment making the checkout process more simplified. At any point, the card holder can amend card details, which will update the token with the new card information.
One of the main benefits of utilising the 1Click - Virtual Solution is the simplicity in which to integrate it into your online website. It requires less development work than other Wirecard Solutions and security measures are already incorporated by Wirecard.
1Click Process Flow
1) Submit a form POST to the Virtual payment page and include an additional form field in your request <input type = "hidden" name = "ClientToken" value = "CustomerToken123">
2) The payment page reads the ClientToken field and does a lookup to see if the token has been registered before:
3) If card detail is not registered yet (Card holders first time making a payment):
5) If card holder is registered and wants to modify their details:
6) If card holder is registered and the card has expired:
Visa Checkout provides a single sign-in service to pay for online shopping purchases. After a simple setup, Visa Checkout users can skip inputting their payment and shipping information for their orders.
Whether at home or on the go, Visa Checkout works across multiple devices so online shopping stays easy. Visa Checkout enables shoppers to choose their preferred payment method across multiple retailers with a click of a button.
Visa Checkout Transaction Process
Step 1 - The customer selects the Visa Checkout payment option
Step 2 - The customer is prompted to sign in to their Visa Checkout account via the Visa Checkout payment widget
Step 3 - The customer has the option to update any of their payment information before continuing with the payment
Step 4 - Visa Checkout returns the results of the payment to Wirecard
Step 5 - Wirecard returns these results to the merchant. The merchant can then display the results on the payment confirmation page
Example of Visa Checkout Login Page
Configuration is controlled from within the Wirecard Web Console. Certain configuration is mandatory in order to begin trading live. Configuration for the payment gateway can be found under settings within the Wirecard Web Console. (refer to Settings – Gateway below)
NOTE: The Referral URL must be configured in the Wirecard Web Console in order for your form post to be accepted.
Gateway settings are used to configure the Wirecard Virtual Payment and add the referral URL.
Illustration: Settings – Gateway
In this area you will configure specific information relating to page display and page posting.
The Referral URL is the URL that your application is posting from. The URL must be added in order for your form post to be accepted by Wirecard.
Click on the “Save” button at the bottom of the screen.
Illustration: Referral url
Within the configure payment page section of the configure application there are additional payment page features that you can manage.
You can manage:
Illustration: Configure Settings - Payment Page
When a transaction is completed the cardholder can be directed to a page that shows if the transaction was successful or declined. This can either be done by the merchant posting through the results URL in the form post or by configuring the show results page. The show results page is a Wirecard hosted results page that can be configured by the merchant.
Illustration: Show Results Page Configuration Screen
If this box is ticked then a text box will be presented on the payment page allowing a card holder to enter their email address. Once the payment has been processed, the card holder will be emailed a transaction receipt notifying them of confirmation of payment.
If the “email confirmation to user” option has been ticked, you will be required to enter the email address that you want the email confirmation to be sent from. The cardholder will see the email coming from that address.
Fraud within Card Not Present (CNP) is on the rise. Without having the card holder present when a purchase is taking place, it can be difficult to verify that the purchaser is who they say they are. 3D Secure programs such as MasterCard Secure Code and Verified by Visa have helped to reduce the amount of fraudulent transactions. Merchants can further reduce their risk by utilising Wirecard’s Fraud Module.
Wirecard understands the risk of fraud and charge backs and have thus developed a Fraud Module that can aid in the reduction of credit card fraud for merchants. By using IP address locaters, BIN origins and shipping address’s, the Fraud Module helps merchants in identifying potential fraudulent transactions. Within the Wirecard Web Console, merchants can configure the Fraud Module Options to flag or fail transactions based on specific transactional behaviour. Each of the merchants’ web sites can be uniquely configured by the merchant with its own set of processing thresholds.
In this section the various payment instruments supported are listed. These are updated regularly as new payment instruments are integrated to the Wirecard platform.
The below lists the different credit card transaction types that Wirecard supports:
The Wirecard Web Console is used by merchants to manage payment gateway transactions. The console is full of rich features enabling transactional management of any Wirecard’s solution or integration methods. A merchant will be issued with a user name and password for the web console when they sign up with Wirecard.
From within the Wirecard Web Console you can:
The credit card transaction process is defined by mainly an authorization and a capture (settlement). The authorization will reserve the funds for 21 working days on the credit card. During the 21 days you can choose to capture the transaction for settlement. Upon settlement, the bank will pay you the funds.
MasterCard and Visa require that the settlement of a credit card transaction takes place at time of delivery of the purchased product or service. If you are providing a product or service with real time delivery then deferred settlement is not required.
Note: Your account will be defaulted to deferred settlement. In the event that you require deferred settlement to not be activated, please contact support.za@wirecard.com
The transaction result is the transaction response returned from the request form post when sending any message type request to Wirecard. The transaction result informs you whether the transaction was successful or declined. The transaction result is often used to display to the cardholder on the failure / success page. Wirecard provides declined reason codes, error messages and in-depth message descriptions that can be displayed to merchant on the failure / success page.
Note: A full list of transaction result information is listed later in this document.
Wirecard offers the 3D Secure service to all of its merchants. If you are using Virtual, no integration to 3D Secure is required as this is handled by Wirecard.
Wirecard’s payment platform is integrated to 3D Secure enabling transactions to be processed to both the MasterCard Secure Code & Verified by Visa, 3D Secure schemes.
3D Secure stands for Three Domain Secure - the payment industry's internet authentication standard which has been developed by the major card schemes. Visa has called their version of the scheme 'Verified by Visa' and MasterCard have called their equivalent initiative 'MasterCard SecureCode'. These are both collectively referred to as 3D Secure.
Note: In order for a merchant to share the benefits of 3D Secure, they must request that their internet merchant account be 3D Secure enabled.
Note: 3D Secure is mandatory by certain banks.