Myvirtual Userguide

MyGate Communication (Pty) Ltd

Reg. No: 2006/018060/07, Vat No: 4020234409 Tel: +27 21 555 3260, Website: www.mygate.co.za

1

Virtual API Version 8.0.0

Merchant User Guide



2

Introduction: ......................................................................................................... 5 Overview: ............................................................................................................. 6 MyGates role in the transaction process: ............................................................. 7 MyGate Payment Solutions:................................................................................. 8 The MyGate Web Console: .................................................................................. 9

Global IP Recognition (GIR) ............................................................................10

Repeated Failure Identification (RFI) ...............................................................10

Repeated Successful Identification (RSI) ........................................................10

Unique Client Index (UCI)................................................................................10

Blacklisting.......................................................................................................10

3D-Secure: ..........................................................................................................11 What is 3D Secure?.........................................................................................11

How does 3D-Secure work with MyGate? .......................................................11

What are the advantages of 3D-Secure?.........................................................12

Credit Card Processing: ......................................................................................13 Variables to Be Posted To MyGate:.................................................................13

Shopping-Cart Variables that can be posted to MyGate:.................................16

MyVirtual HTML Code Example: .....................................................................17

MyVirtual Shopping Cart Code Example: ........................................................18

RCCB Integration: ...............................................................................................20 RCCB Overview: .............................................................................................20

RCCB Variables to Be Posted To MyGate: .....................................................21

RCCB HTML Code Example: ..........................................................................24

Cell Pay Point Integration:...................................................................................26 Variables to be Posted to MyGate: ..................................................................26

HTML example core requirements ..................................................................28



3

HTML example when send through shopping cart details ...............................29

eBucks Integration: .............................................................................................30 Variables to be Posted to MyGate: ..................................................................30

eBucks HTML Example: ..................................................................................32

mimoney Integration:...........................................................................................33 Variables to be Posted to MyGate: ..................................................................33

mimoney HTML Code Example: ......................................................................35

SNAP Integration: ...............................................................................................36 Variables to be Posted to MyGate: ..................................................................36

SNAP HTML Code Example:...........................................................................38

Testing the Payment Gateway: ...........................................................................39 FNB Successful Test Card Details:..................................................................39

FNB Failed Test Card Details: .........................................................................39

Nedbank Successful Test Card Details: ..........................................................39

Nedbank Failed Test Card Details:..................................................................39

mimoney Test Voucher Details:.......................................................................39

Return Variables from MyGate:...........................................................................40 MyGate Encryption:.............................................................................................41

Encryption Webservice: ...................................................................................42

Decryption Webservice:...................................................................................42

Error Codes:........................................................................................................43 1xxx = MyVirtual - Validation Response Codes...............................................43

2xxx = MyVirtual - Initiating Response Codes .................................................48

4xxx = MyVirtual - Security Response Codes..................................................50

5xxx = MyVirtual - Gateways Response Code.................................................51



4

6xxx = MyVirtual - Fraud Module Response Code ..........................................52

8xxx = MyVirtual – Warnings Codes................................................................52

9xxx = MyVirtual - Unexpected Error ...............................................................54

1xx – 2xx mimoney Error Codes......................................................................54



5

Introduction:

Since the inception of MyGate, the MyVirtual Payment Solution has been the most popular in the market. This is largely due to the ease of integration into the solution and the high level of Security that it provides to Merchants. The MyVirtual 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 checkout process. MyGate also pride ourselves on our level of security. The Virtual Payment Page is operating behind a SSL (Secure Socket Layer) Certificate 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. MyGate is also fully PCI-Compliant meaning that our systems have gone through rigorous testing and certification procedures to ensure that your client’s information remains confidential and is not prone to attacks or theft.



6

Overview:

MyVirtual allows the merchant to utilize the MyGate payment webpage. This means that your clients will be directed to MyGate’s Payment page where they will enter their credit card details in order for the transaction to be completed. The payment information which MyGate requires is posted to MyGate via a form POST. This POST can be done in any language that supports this method. The process of the transaction is as follows: One of the main benefits of utilising the MyVirtual Solution is the simplicity in which to integrate it into your online website. It requires less development work than other MyGate Solutions and security measures are already incorporated by MyGate. This is beneficial to you as you do not need to go through the process of becoming PCI-Compliant and/or obtaining a SSL Certificate.



7

MyGates role in the transaction process:

As the Payment Service Provider (Payment Gateway), MyGate’s role in the transaction process is as follows:

- MyGate receives the transaction details from the Website via form POST. - MyGate accepts the details from the buyer. - MyGate does validation ensuring that the buyer entered valid information. - MyGate Processes the transaction by submitting the transaction details to the merchant

bank in a live environment. - The merchant bank processes the transaction and returns to MyGate with a result and/or

error code. - MyGate returns this result and/or error code with error description back ro the Merchant

Website address specified in the form POST. - If the functionality is set up (from the MyGate Web Console) MyGate will notify the card

holder via email of the transaction details and the merchant via email and/or SMS. MyGate will also provide the merchant with access to the MyGate Web Console. Here, the merchant will be able to view the transactions in a live environment along with their transactional status (Authorized, Settled, Refunded, etc). The client will also be able to view the client details along with the items purchased provided they get submitted to MyGate in the form POST from the website. Website Orders Bank Payment Gateway



8

MyGate Payment Solutions:

MyGate offers a variety of payment solutions beyond the scope of credit card processing: Credit Card Processing:

VISA, MasterCard, Diners Club and American Express credit card payments can be accepted from anywhere in the world. They are a global form of payment which creates endless opportunities for both the merchant and the card holder. Any business which does not have a credit card facility can now easily incorporate our payment solution into their existing systems. With MyGate, all card types are processed in real-time. Bank settlement generally occurs the next day. Complete control is maintained over all transaction types such as authorisation, settlement, reversals and refunds.

Cell Pay Point:

Cell Pay Point which is an alternative payment method offered by FNB for ecommerce companies. Cell Pay Point enables merchants to accept payments on their website from registered FNB Mobile Banking users. The solution allows FNB Mobile Banking Users to pay from their debit card account via their mobile phone.

eBucks:

MyGate is an approved eBucks payment processor. eBucks internet partners can integrate into MyGate through a simple web service allowing authorization and settlement of eBucks tokens.

mimoney:

mimoney is a new method of payment for use by people who want to shop online but do not have a credit card - or do not wish to use their credit- card details online. mimoney, is an electronic payment voucher that is simple, easy to use, and truly secure.

SNAP:

SNAP provides the consumer with a comprehensive payment card for all sorts of electronic transactions, including Internet Shopping, Money Transfer and Mobile Payments. For accepting merchant, SNAP is a secure and convenient way to bring cash customers to the web, grow revenues and eliminate charge-backs.



9

The MyGate Web Console:

The MyGate Web Console was developed for use by the Merchant as a means to manage their transactions from a central point. It is the most advanced of its kind and is the leading management and reconciliation tool in the market. The MyGate Web Console enables the merchant to perform the following tasks:

- View Transactions that have gone through the payment gateway. - Settle Transactions that are authorized. - Refund Transactions. - Make use of the MyTerminal System (online swipe machine (MOTO environment)) - Activate and configure the MyGate Fraud Module. - Activate and configure the NotifyMe Service. - Load the Referral URL. - Customize the MyVirtual Payment Page. - Perform Reconciliations on payments on a daily basis. - Manage Chargebacks should they arise. - Settle Transactions with an Authorization number.

Your role (as the developer) will be to notify the merchant of the referral URL (this is the last URL on the website before the client is redirected to MyGate). The merchant will need to load this URL in his Web Console in order for live transactions to be processed. The merchant needs to do the following to load the referral URL:

- Log into the MyGate Web Console (www.mygate.co.za/console) - Click on “Settings”. - Click on “Gateway Settings”. - Click on the configure icon. - Load the referral URL. - Click on “Save”.



10

The MyGate Fraud Module:

MyGate understands the risk of chargeback’s and has developed an extensive range of fraud systems allowing the merchant to manage his business more effectively in real time.

Global IP Recognition (GIR)

GIR compares the purchaser's delivery address to the global geographic location assigned to their IP address. If someone was purchasing on your website and their billing address is in the UK but their IP address is in Germany, it would be likely that the transaction is fraudulent.

Repeated Failure Identification (RFI)

RFI works in conjunction with blacklisting and allows the merchant to set the amount of failed attempts a purchaser can make before they are blocked from making further attempts. If a purchaser makes too many purchase attempts without success, it may mean that they are not the cardholder and the transaction could be fraudulent.

Repeated Successful Identification (RSI)

RSI allows the merchant to set the amount of successful transactions a purchaser can make before they’re flagged as potential fraud or blocked from making further transactions. A purchaser is defined from IP address or credit card number.

Unique Client Index (UCI)

UCI forms a one-to-one relationship between a client and a credit card number. The merchant has the ability to provide MyGate with a unique-client-identifier when processing a transaction. MyGate then stores the card number used by that client, and will flag or fail later transactions used by this client with a different card number. This insures that the credit card being used by the client is the card previously used for transacting.

Blacklisting

Blacklisting allows you to block purchase attempts on the payment gateway. You are able to blacklist fraudulent purchases which may have been picked up from either charge backs or any one of MyGate’s Fraud Detection Tools by blocking one or more of the below from your Merchant Interface:

· Blocking e-mail domains, i.e. any address at gmail.com · Blocking specific credit card numbers · Blocking specific e-mail addresses · Blocking specific countries, cities or regions



11

3D-Secure:

Internet transactions are classed as 'cardholder not present' (CNP) transactions. 3D Secure helps to identify a cardholder and confirm that it was indeed the legitimate cardholder entering the card details. The majority of chargebacks can arise as a result of the cardholder denying that they authorized a transaction, making it difficult for you to successfully dispute this sort of chargeback. The 3D Secure technology is designed to reduce the possibility of fraudulent card use by authenticating the cardholder at the actual time of the transaction and subsequently reducing your exposure to disputed transactions and chargebacks of this type.

What is 3D Secure?

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. 3D Secure authentication requires the cardholder to register their card to take advantage of this service. This is a one time process which takes place on the card issuer's website and involves the cardholder answering several security questions to which only the card issuer and cardholder will know the answer. The cardholder selects a password and agrees on a secret phrase, which will be used by the card issuer during each online transaction. 3D Secure can be thought of as an online version of 'Chip and Pin' technology, whereby the cardholder has a personalized password registered with their card that is entered during the checkout process. 3D Secure is predicted to become the industry standard by the end of 2010 and all online consumers will soon become as familiar with this, as when they enter their 'Pin' number at a cash machine or till in a shop.

How does 3D-Secure work with MyGate?

· Each time a cardholder attempts to make a transaction using MyGate, after entering their personal card details on the MyGate payment page, the MyGate system automatically checks to see if their card is enrolled in the 3D Secure scheme.

· Some schemes are not yet fully enabled for 3D Secure but these are expected to be enabled over the next few months.

· If the cardholders' bank is participating, the cardholder is taken to their card issuers secure website where they enter their 3D Secure password. The payment is then taken as normal and the cardholder is smoothly delivered back to the merchants confirmation page.

· If a cardholder of a bank who is participating in the 3D Secure scheme has not yet enrolled, by default, they are offered the opportunity to register. They can then either sign up for 3D Secure, and proceed with the transaction or decline to sign up and proceed



12

with the transaction as normal. Different card issuers may implement a maximum decline limit before the cardholder is made to sign up to 3D Secure.

· MyGate will attempt a 3D Secure check on each card transaction - if the cardholder's bank are not currently participating in the 3D Secure scheme, the transaction will be processed without a 3D Secure check.

· All MyGate Merchant Accounts are now 3D Secure enabled as standard and each MyGate card transactions is checked to see if the cardholder is registered for 3D Secure. Merchants and Sellers should use the notification of the 3D Secure checks as an additional fraud prevention tool in conjunction with existing fraud checks such as AVS and CV2 to help you minimise your risk of fraud.

What are the advantages of 3D-Secure?

· The key attraction to you as a merchant is that once a cardholder registered with the scheme has input their correct 3D Secure password during a transaction and this has been successfully authenticated (and providing that they are acting legally), the liability of a chargeback arising from the cardholder denying that they authorised the transaction, should shift from you (the merchant) to the cardholder's issuing bank.

· If a customer is not yet registered with the scheme, the fact that the transaction is checked by MyGate for 3D Secure compliance should give similar protection from the customer denying that they processed the transaction (providing the customer's bank is participating in the 3D Secure scheme).

· Increased card holder confidence, leading to increased sales. Currently, around 50% of cardholders have not participated in an electronic transaction.

· Early adoption - 3D Secure looks set to become the leading security system for online credit card transactions. Give your customers peace of mind and show you care about their security.

· No additional fees.



13

Credit Card Processing:

Variables to Be Posted To MyGate: The below variables detail what needs to be submitted to MyGate in the form POST: POST URL: https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm

Variable Name Explanation Required Data Mode Specifies a Live or Test

transaction Yes 0 = Test

1 = Live txtMerchantID Your merchant UID

allocated by MyGate Yes xxxxxxxx-xxxx-xxxx-xxxx-

xxxxxxxxxxxx (where x is a hexadecimal number)

txtApplicationID Your Application UID allocated by MyGate

Yes xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (where x is a hexadecimal number)

txtMerchantReference This is any unique number that you refer to the transaction with. (e.g. Invoice Number, Order Number)

Yes AlphaNumeric. Must be between 4 and 16 characters long.

txtPrice The Price of the transaction

Yes Numeric with 2 decimal places (The decimal places are determined by the currency you specify) E.g. 150.00

txtCurrencyCode The 3 letter currency code.

Yes 3 Letters as specified in ISO4217 (e.g. ZAR)

txtDisplayPrice This is used if you want to display a different currency to your users and the price needs to show differently. The data in txtPrice and the currency in txtCurrencyCode is what will be billed off the user’s account.

No Numeric with 2 decimal places.

txtDisplayCurrencyCode This is used if you want to display a different currency to your users. The data in txtPrice and the currency in txtCurrencyCode is what will be billed off the user’s

No 3 Letters as specified in ISO4217 (e.g. ZAR).



14

account. txtRedirectSuccessfulURL This is the url the system

will redirect to in the event of a completed successful transaction

Yes A fully qualified URL (e.g. http://www.mygate.co.za/successful.htm).

txtRedirectFailedURL This is the url the system will redirect to in the event of a completed failed transaction

Yes A fully qualified URL (e.g. http://www.mygate.co.za/failed.htm).

ShippingCountryCode This represents the 2 letter country code of the country to which the item/s are being shipped. This is part of the MyGate Fraud Module, and is used by the following fraud products: BLS (Blacklisting Service) AND GIR (Global IP Recognition Service).

No 2 Letters as specified in ISO4217 (e.g. ZA, UK, US, DK, MX)

UCI Unique Client Index - is any Alphanumeric combination that uniquely identifies the client. It is part of the MyGate Fraud Module, and is used by the following fraud products: BLS (Blacklisting Service) AND UCI (Unique Client Identifier Service).

No AlphaNumeric (MaxLength: 128)

IPAddress This represents the IP Address of the online purchaser. It is part of the Fraud Module, and is used by the following fraud products: RSI (Repeated Success Identifier Service), RFI (Repeated Failure Identifier Service), BLS (Blacklisting Service), and GIR (Global IP Recognition Service).

No AlphaNumeric, representing the user’s IP Address eg 172.16.32.182

txtQty The Number of line items that were ordered

Yes Numeric (1 or greater)

txtItemRef Item Reference Number – allows you to link the




15

item back to an item reference number in your shopping cart

txtItemDescr Item Description Yes AlphaNumeric (MaxLength: 512) txtItemAmount The Price paid by the

purchaser for the item Yes Numeric with 2 decimal places

txtShippingCost Shipping Costs for the order

No Numeric with 2 decimal places

txtDiscount Discount given on the order

No Numeric with 2 decimal places

txtRecipient The name of the individual who has placed the order on your shopping site


txtShippingAddress1 The Shipping Address Line 1










txtQty The Quantity of the shipped item

No Numeric e.g. 2

txtItemRef (Optional but Required if txtQty is posted) The Reference of the shipped item

No AlphaNumeric (MaxLength: 128) e.g. btv1203

txtItemDescr (Optional but Required if txtQty is posted) The Description of the shipped item

No AlphaNumeric (MaxLength: 128) e.g. Black Plasma

txtItemAmount (Optional but Required if txtQty is posted) The total value of the shipped item

No Numeric with 2 decimal places e.g. 12.300.00

txtShippingCost The shipping cost of the full shipments

No Numeric with 2 decimal places e.g. 250.00

txtDiscount The discount given of the full shipments

No Numeric with 2 decimal places e.g. 1000.00

Variable1, Variable2, Variable3, etc

These are variables we will pass through for you should you need it. They will be posted to the success and failed pages in addition to the Transaction Result.

No Any characters that comply with W3 HTML standards.



16

Shopping-Cart Variables that can be posted to MyGate:

MyGate has added the additional ability for MyVirtual merchants to optionally send through shopping cart details to the payment page. This information is then displayed above the credit-card input fields. In addition, once the order is processed and the credit-card transaction created, this shopping-cart data is then stored in our database and linked to the transaction. At any time, you as the merchant can then log into the MyGate Web Console and go to the ‘Search’ Option under ‘Transactions’ Menu Item, and view the purchased items associated with any transaction (this is particularly useful for reconciliation purposes). The fields required to be populated to make use of this new service are detailed below. Please be sure to view the code example below to see how to correctly pass through shopping cart parameters to the payment page. Please note that you can send any number of line items through to the payment page, but they need to be distinguished by being suffixed with 1,2,3 etc. after each line item. Therefore, if the online purchaser is buying two line items, these would be sent through to MyGate as follows: <input type="hidden" name="txtQty1" value="1"> <input type="hidden" name="txtItemRef1" value="Any Item Ref Here"> <input type="hidden" name="txtItemDescr1"value="Any Item Description Here"> <input type="hidden" name="txtItemAmount1" value="123.45"> <input type="hidden" name="txtQty2" value="1"> <input type="hidden" name="txtItemRef2" value=" Any Item Ref Here "> <input type="hidden" name="txtItemDescr2”value="Any Item Description Here"> <input type="hidden" name="txtItemAmount2" value="456.78">



17

MyVirtual HTML Code Example:

The below HTML example details only the required variables that need to be posted to MyGate. This is simply an example to see how a form POST is done to MyGate: <FORM name="PostTest action="https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm"

method="post"> <input type="hidden" name="Mode" value="0">

<input type="hidden" name="txtMerchantID" value="79958a8d-0c7b-4038-8e2e-8948e1d678e1"> <input type="hidden" name="txtApplicationID" value="d48750f9-1dc0-4290-a94c-9a1c9f7e2fb1">

<input type="hidden" name="txtMerchantReference" value="INV15642"> <input type="hidden" name="txtPrice" value="29.99"> <input type="hidden" name="txtCurrencyCode" value="ZAR"> <input type="hidden" name="txtRedirectSuccessfulURL"

value="http://www.mygate.co.za/successful.htm"> <input type="hidden" name="txtRedirectFailedURL" value="http://www.mygate.co.za/failed.htm">

<input type="submit" value="Send Details"> </FORM> The above 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. Please also note that the Merchant UID and Application UID in the above code are for the MyGate test account. They will work only for testing purposes. You will need to replace these details with the Merchant and Application UID provided to you by MyGate in your integration welcome email.



18

MyVirtual Shopping Cart Code Example:

The Below HTML example shows how your form POST could look when extensive information is getting sent to MyGate: <FORM name="Post" action=https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm method="post"> <input type="hidden" name="Mode" value="0">


<input type="hidden" name="txtMerchantReference" value="INV15642"> <input type="hidden" name="txtPrice" value="15.00"> <input type="hidden" name="txtCurrencyCode" value="ZAR">

<input type="hidden" name="txtRedirectSuccessfulURL" value="http://localhost/success_failure.php"> <input type="hidden" name="txtRedirectFailedURL" value="http://localhost/success_failure.php">

<input type="hidden" name=" ShippingCountryCode " value="ZA"> <input type="hidden" name="UCI" value="14A23B"> <input type="hidden" name=" IPAddress " value="172.16.3.18"> 

<input type="hidden" name="Variable1" value="My security check variable"> <input type="hidden" name="Variable2" value="INV15642">  <input type="hidden" name="txtQty1" value="1"> <input type="hidden" name="txtItemRef1" value="Item Ref 1"> <input type="hidden" name="txtItemDescr1" value="ItemDescription 1"> <input type="hidden" name="txtItemAmount1" value="5">  <input type="hidden" name="txtQty2" value="2"> <input type="hidden" name="txtItemRef2" value="Item Ref 2"> <input type="hidden" name="txtItemDescr2" value="ItemDescription 2"> <input type="hidden" name="txtItemAmount2" value="5">  <input type="hidden" name="txtShippingCost" value="0.00"> <input type="hidden" name="txtDiscount" value="0.00">

 <input type="hidden" name="txtRecipient" value="Joe Soap">

<input type="hidden" name="txtShippingAddress1" value="15 Yorke Street"> <input type="hidden" name="txtShippingAddress2" value="Gardens"> <input type="hidden" name="txtShippingAddress3" value="Cape Town"> <input type="hidden" name="txtShippingAddress4" value="8000"> <input type="hidden" name="txtShippingAddress5" value="South Africa"> <input type="submit" value="Send Details">



19

</FORM> The above 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. Please also note that the Merchant UID and Application UID in the above code are for the MyGate test account. They will work only for testing purposes. You will need to replace these details with the Merchant and Application UID provided to you by MyGate in your integration welcome email.



20

RCCB Integration:

RCCB Overview:

RCCB (Recurring Credit Card Billing) is a solution typically used by subscription websites or any other website that requires the card holder to be debited from their credit card automatically on a monthly basis. The RCCB POST to MyGate is slightly different to the standard MyVirtual POST in that it includes additional variables that need to be sent to MyGate in order for us to process the transaction automatically on a monthly basis. MyGate does not post back to your website on each subsequent rebill that we do. We will only POST back to your site on the initial transaction. Transaction statuses along with RCCB transaction statuses can be viewed in the MyGate Web Console. The MyGate Web Console also plays another important role in the RCCB Solution: It allows the merchant to edit and/or delete clients from the RCCB bill cycle.



21

RCCB Variables to Be Posted To MyGate:

Below is a list of the additional variables that need to be posted to MyGate along with the standard MyVirtual Variables: The URL that you will post to for an RCCB transaction is: https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm

Variable Name Explanation Required Data ACCB_Frequency The Frequency of

how often a transaction should happen. The format should always be in the correct format like below: Weekly(W) | Action Day (DDD) Monthly(M) | Action Day (dd) Bi-Annually(B)

Yes AlphaNumeric (MaxLength: 5) e.g. Weekly – W|Mon Monthly – M|01 The last day of the month is depicted as M|31 - regardless of whether or not the month contains 31 days, if the frequency is set to this value, the debit will go off against the RCCB client on the last day of every month. Bi-Annually – Y

ACCB_StartDate The Start Date of the automatic debits. It must be in the format dd-MMM-yyyy

Yes Date Eg 01-Feb-2008

ACCB_EndDate The End Date of the automatic debits. It must be in the format dd-MMM-yyyy

Yes Date Eg 01-Feb-2009

ACCB_Amount The Amount that will be collected on the specified Frequency. This must be greater

Yes Numeric with 2 decimal places e.g. 150.00



22

than 0 ACCB_ClientName A description of the

client. This will be the name of the company or individual, etc.

Yes AlphaNumeric (MaxLength: 64) e.g Joe Soap

ACCB_ClientAccountNo A unique merchant reference for the collection. This is purely for your reference.

Yes AlphaNumeric (MaxLength: 64) e.g. Acc123043

ACCB_ClientEmailAddress The client email address in the event that the client needs to be notified

No Text e.g. [email protected]

ACCB_ClientSendEmail Enable the facility to notify the client via email when a transaction takes place. This will defaults to “No”

No Boolean e.g.: 0 = No 1 = Yes

ACCB_ClientMobileNo The clients mobile number in the event that the client needs to be notified

No Text e.g. 0830000000

ACCB_ClientSendSMS Enable the facility to notify the client via SMS when a transaction takes place. This will defaults to “No”

No Boolean e.g: 0 = No 1 = Yes

txtACCB_Caption The RCCB header can be changed with this field. It will default to “Repeated-Payment Details”

No Text e.g. Recurring Billing

txtFrequency_Caption The Frequency Label can be changed with this field. It will default to “Payment Frequency”

No Text e.g. Recurring Frequency

txtACCBAmount_Caption The Amount Label can be changed with this field. It will default to “Payment Amount”

No Text e.g. Recurring Amount



23

ShowACCBDetails This display the RCCB details for the client on the payment page. This will defaults to “Yes”

No Boolean e.g. 0 = No 1 = Yes

ShowFrequencyDetails This display the Frequency for the client on the payment page. This will defaults to “Yes”


ShowStartDateDetails This display the Start Date for the client on the payment page. This will defaults to “Yes”


ShowEndDateDetails This display the End Date for the client on the payment page. This will defaults to “Yes”


ShowAmountDetails This display the Collection Amount for the client on the payment page. This will defaults to “Yes”




24

RCCB HTML Code Example:

Below is an HTML code example of what an RCCB POST can look like: <FORM name="Post" action="https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm" method="post"> <input type="hidden" name="Mode" value="0">


<input type="hidden" name="txtMerchantReference" value="INV15642"> <input type="hidden" name="txtPrice" value="15.00"> <input type="hidden" name="txtCurrencyCode" value="ZAR"> <input type="hidden" name="txtDisplayPrice" value="15.00"> <input type="hidden" name="txtDisplayCurrencyCode" value="ZAR">

<input type="hidden" name="txtRedirectSuccessfulURL" value="http://localhost/ success_failure.php"> <input type="hidden" name="txtRedirectFailedURL" value="http://localhost/ success_failure.php">

<input type="hidden" name=" ShippingCountryCode " value="ZA"> <input type="hidden" name="UCI" value="14A23B"> <input type="hidden" name=" IPAddress " value="172.16.3.18">  <input type="hidden" name="Variable1" value="My security check variable"> <input type="hidden" name="Variable2" value="INV15642">  <input type="hidden" name="txtQty1" value="1"> <input type="hidden" name="txtItemRef1" value="Item Ref 1"> <input type="hidden" name="txtItemDescr1" value="ItemDescription 1"> <input type="hidden" name="txtItemAmount1" value="5">  <input type="hidden" name="txtQty2" value="2"> <input type="hidden" name="txtItemRef2" value="Item Ref 2"> <input type="hidden" name="txtItemDescr2" value="ItemDescription 2"> <input type="hidden" name="txtItemAmount2" value="5">  <input type="hidden" name="txtShippingCost" value="0.00"> <input type="hidden" name="txtDiscount" value="0.00">  <input type="hidden" name="txtRecipient" value="Joe Soap"> <input type="hidden" name="txtShippingAddress1" value="15 Yorke Street"> <input type="hidden" name="txtShippingAddress2" value="Gardens"> <input type="hidden" name="txtShippingAddress3" value="Cape Town"> <input type="hidden" name="txtShippingAddress4" value="8000"> <input type="hidden" name="txtShippingAddress5" value="South Africa">



25



<input type="hidden" name="txtFrequency" value="M|1"> <input type="hidden" name="txtStartDate" value="01-DEC-2007"> <input type="hidden" name="txtEndDate" value="01-DEC-2008"> <input type="hidden" name="txtACCBAmount" value="5.00"> <input type="hidden" name="txtACCBClientName" value="David Viljoen"> <input type="hidden" name="txtACCBClientAccountNo" value="Test02"> <input type="hidden" name="txtACCBClientEmailAddress" value="[email protected]"> <input type="hidden" name="txtACCBClientMobileNumber" value="0831234567"> <input type="hidden" name="txtACCBClientSendSMS" value="0"> <input type="hidden" name="txtACCBClientSendEmail" value="0">  <input type="hidden" name="ShowACCBDetails" value="1"> <input type="hidden" name="ShowFrequencyDetails" value="1"> <input type="hidden" name="ShowStartDateDetails" value="1"> <input type="hidden" name="ShowEndDateDetails" value="1"> <input type="hidden" name="ShowAmountDetails" value="1">  <input type="hidden" name="txtACCB_Caption" value="Recurring Billing"> <input type="hidden" name="txtFrequency_Caption" value="Payment Frequency"> <input type="hidden" name="txtACCBAmount_Caption" value="Monthly Billing">

<input type="submit" value="Send Details"> </FORM> The above 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. Please also note that the Merchant UID and Application UID in the above code are for the MyGate test account. They will work only for testing purposes. You will need to replace these details with the Merchant and Application UID provided to you by MyGate in your integration welcome email.



26

Cell Pay Point Integration:

Variables to be Posted to MyGate:

You will do a form POST to the following URL: https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm Variable Name Explanation Data txtMode (Required) The mode determines whether the

transaction is to be done in live mode or test mode.

0 = Test 1 = Live

txtMerchantID (Required) Your merchant ID allocated by MyGate

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (where x is a hexadecimal number)

txtApplicationID (Required) Your Application ID allocated by MyGate (if you are a current MyVirtual merchant, your current MyVirtual Application ID can be used)


txtMerchantReference (Required) This is any unique number that you refer to the transaction with. (e.g. Invoice Number, Order Number)

AlphaNumeric

txtMerchantStatementRef

(Required) This is the reference that will appear on your bank statement when you receive payment for the transaction

AlphaNumeric (20 chars max)

txtCustomerStatementRef

(Required) This is the reference that will appear on the customer’s bank statement when they receive payment for the transaction

AlphaNumeric (20 chars max)

txtPrice (Required) The Price of the transaction Numeric with 2 decimal places (The decimal places are determined by the currency you specify)

txtCurrencyCode (Required) The 3 letter currency code as agreed with FNB

3 Letters as specified in ISO4217 (e.g. ZAR)

txtDisplayPrice (Optional) This is used if you want to display a different currency to your users and the price needs to show differently. The data in txtPrice and the currency in txtCurrencyCode is what will be billed off the user’s account.

Any Numeric Value

txtDisplayCurrencyCode

(Optional) This is used if you want to display a different currency to your users. The data in txtPrice and the currency in txtCurrencyCode is what will be billed off the user’s account.


txtRedirectSuccessfulURL

(Required) This is the url the system will redirect to in the event of a completed

A fully qualified URL (e.g. http://www.mygate.co.za/succe



27

successful transaction ssful.htm) txtRedirectFailedURL (Required) This is the url the system will

redirect to in the event of a completed failed transaction

A fully qualified URL (e.g. http://www.mygate.co.za/failed.htm)

txtRecipient (Optional) The name of the individual who has placed the order on your shopping site

AlphaNumeric (MaxLength: 128)

txtShippingAddress1 (Optional) The Shipping Address Line 1 AlphaNumeric (MaxLength: 128)





txtQty (Optional) The Quantity of the shipped item Numeric e.g. 2 txtItemRef (Optional but Required if txtQty is posted) The

Reference of the shipped item AlphaNumeric (MaxLength: 128) e.g. btv1203


AlphaNumeric (MaxLength: 128) e.g. Black Plasma


Numeric with 2 decimal places e.g. 12,300.00

txtShippingCost (Optional) The shipping cost of the full shipments

Numeric with 2 decimal places e.g. 250.00

txtDiscount (Optional) The discount given of the full shipments



(Optional) These are variables we will pass through for you should you need it. They will be posted to the success and failed pages in addition to the Transaction Result.

Any characters that comply with W3 HTML standards.



28

HTML example core requirements <FORM name="PostTest" action="https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm" method="post"> <input type="hidden" name="txtMode" value="0"> <input type="hidden" name="txtMerchantID" value="79958a8d-0c7b-4038-8e2e- 8948e1d678e1"> <input type="hidden" name="txtApplicationID" value="d48750f9-1dc0-4290-a94c- 9a1c9f7e2fb1"> <input type="hidden" name="txtMerchantReference" value="INV15642">

<input type="hidden" name="txtMerchantStatementRef" value="CPPMerchRef"> <input type="hidden" name="txtCustomerStatementRef" value="CPPClientRef">

<input type="hidden" name="txtPrice" value="29.99"> <input type="hidden" name="txtCurrencyCode" value="ZAR"> <input type="hidden" name="txtDisplayPrice" value="29.99"> <input type="hidden" name="txtDisplayCurrencyCode" value="ZAR"> <input type="hidden" name="txtRedirectSuccessfulURL" value="http://www.mygate.co.za/successful.htm"> <input type="hidden" name="txtRedirectFailedURL" value="http://www.mygate.co.za/failed.htm">

<input type="hidden" name="Variable1" value="My security check variable"> <input type="hidden" name="Variable2" value="INV15642"> <input type="submit" value="Send Details"> </FORM>



29

HTML example when send through shopping cart details <FORM name="PostTest" action="https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm" method="post"> <input type="hidden" name="txtMode" value="0"> <input type="hidden" name="txtMerchantID" value="79958a8d-0c7b-4038-8e2e- 8948e1d678e1"> <input type="hidden" name="txtApplicationID" value="d48750f9-1dc0-4290-a94c- 9a1c9f7e2fb1"> <input type="hidden" name="txtMerchantReference" value="INV15642">

<input type="hidden" name="txtMerchantStatementRef" value="CPPMerchRef"> <input type="hidden" name="txtCustomerStatementRef" value="CPPClientRef">

<input type="hidden" name="txtPrice" value="29.99"> <input type="hidden" name="txtCurrencyCode" value="ZAR"> <input type="hidden" name="txtDisplayPrice" value="29.99"> <input type="hidden" name="txtDisplayCurrencyCode" value="ZAR"> <input type="hidden" name="txtRedirectSuccessfulURL" value="http://www.mygate.co.za/successful.htm"> <input type="hidden" name="txtRedirectFailedURL" value="http://www.mygate.co.za/failed.htm">  <input type="hidden" name="Variable1" value="My security check variable"> <input type="hidden" name="Variable2" value="INV15642">  <input type="hidden" name="txtQty1" value="1"> <input type="hidden" name="txtItemRef1" value="Item Ref 1"> <input type="hidden" name="txtItemDescr1" value="ItemDescription 1"> <input type="hidden" name="txtItemAmount1" value="5">  <input type="hidden" name="txtQty2" value="2"> <input type="hidden" name="txtItemRef2" value="Item Ref 2"> <input type="hidden" name="txtItemDescr2" value="ItemDescription 2"> <input type="hidden" name="txtItemAmount2" value="5">  <input type="hidden" name="txtShippingCost" value="0.00"> <input type="hidden" name="txtDiscount" value="0.00">  <input type="hidden" name="txtRecipient" value="Glenn Ross"> <input type="hidden" name="txtShippingAddress1" value="15 Yorke Street"> <input type="hidden" name="txtShippingAddress2" value="Gardens"> <input type="hidden" name="txtShippingAddress3" value="Cape Town"> <input type="hidden" name="txtShippingAddress4" value="8000"> <input type="hidden" name="txtShippingAddress5" value="South Africa"> <input type="submit" value="Send Details"> </FORM>



30

eBucks Integration:


To process an eBucks transaction, you will do a form POST to the following URL: https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm

Variable Name Explanation Data txtMyGateMerchantID (Required) Your merchant ID allocated by

MyGate xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (where x is a hexadecimal number)

txtEBucksMerchantID (Required) Your eBucks merchant ID allocated by FNB

A numeric value

txtInvoiceNumberItems (Required) The number of items of different item codes (see fields below) that the end-user wishes to purchase with their eBucks

A numeric value

txtApplicationID (Required) Your Application ID allocated by MyGate



AlphaNumeric


txtCurrencyCode (Required) The 3 letter currency code as agreed with FNB



(Required) This is the url the system will redirect to in the event of a completed successful transaction

A fully qualified URL (e.g. http://www.mygate.co.za/successful.htm)

txtRedirectFailedURL (Required) This is the url the system will redirect to in the event of a completed failed transaction


txtItemCode1, txtItemCode2 etc.

(Required) Codes of items being purchased (for item reference & identification). The number of individual items must equal the number specified in the txtInvoiceNumberItems field

AlphaNumeric

txtItemName1, txtItemName2 etc.

(Required) Names of items being purchased. The number of individual items must equal the number specified in the txtInvoiceNumberItems field

AlphaNumeric

txtUnitCount1, txtUnitCount2 etc.

(Required) Numbers of items per each item code being purchased.

A numeric value

txtUnitCost1, txtUnitCost2 etc.

(Required) Cost of items per each item code being purchased.

A numeric value



31

txtItemFlatDiscount1, txtItemFlatDiscount2 etc.

(Required) Flat discount offered per each item code being purchased.

A numeric value (0 for no discount)

txtPercentageDiscount1 txtPercentageDiscount2 etc

(Required) Percentage discount offered per each item code being purchased.

A numeric value (0 for no discount)



txtShippingAddress1 (Optional) The Shipping Address Line 1 AlphaNumeric (MaxLength: 128) txtShippingAddress2 (Optional) The Shipping Address Line 2 AlphaNumeric (MaxLength: 128) txtShippingAddress3 (Optional) The Shipping Address Line 3 AlphaNumeric (MaxLength: 128) txtShippingAddress4 (Optional) The Shipping Address Line 4 AlphaNumeric (MaxLength: 128) txtShippingAddress5 (Optional) The Shipping Address Line 5 AlphaNumeric (MaxLength: 128) Variable1, Variable2, Variable3, etc





32

eBucks HTML Example:

<FORM name="PostTest" action="https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm" method="post">

<input type="hidden" name="txtMyGateMerchantID" value="79958a8d-0c7b-4038-8e2e-8948e1d678e1”> <input type=" hidden " name="txtEBucksMerchantID" value="1895”> <input type=" hidden " name="txtInvoiceNumberItems" value="2"> <input type=" hidden " name="txtApplicationID" value="d48750f9-1dc0-4290-a94c-9a1c9f7e2fb1"> <input type=" hidden " name="txtMerchantReference" value="gs56776"> <input type=" hidden " name="txtPrice" value="0.10"> <input type=" hidden " name="txtDisplayPrice" value="0.10"> <input type=" hidden " name="txtCurrencyCode" value="ZAR"> <input type=" hidden " name="txtDisplayCurrencyCode" value="R"> <input type=" hidden " name="txtRedirectSuccessfulURL" value="http://mysite/eBucksASPTest/Success.aspx"> <input type=" hidden " name="txtRedirectFailedURL" value="http://mysite/eBucksASPTest/Failure.aspx"> <input type=" hidden " name="Variable1" value="this is variable 1"> <input type=" hidden " name="Variable2" value="this is variable 2"> <input type=" hidden " name="txtItemCode1" value="Item Code 1"> <input type=" hidden " name="txtItemName1" value="ItemName 1"> <input type=" hidden " name="txtItemDescr1" value="ItemDescription 1"> <input type=" hidden " name="txtUnitCount1" value="1"> <input type=" hidden " name="txtUnitCost1" value="0.05"> <input type=" hidden " name="txtItemFlatDiscount1" value="0"> <input type="hidden" name="txtPercentageDiscount1" value="0"> <input type=" hidden " name="txtItemCode2" value="Item Code 2"> <input type=" hidden " name="txtItemName2" value="ItemName 2"> <input type=" hidden " name="txtItemDescr2" value="ItemDescription 2"> <input type=" hidden " name="txtUnitCount2" value="1"> <input type=" hidden " name="txtUnitCost2" value="0.05"> <input type=" hidden " name="txtItemFlatDiscount2" value="0"> <input type=" hidden " name="txtPercentageDiscount2" value="0"> <input type=" hidden " name="txtRecipient" value="Joe Williams"> <input type=" hidden " name="txtShippingAddress1" value="27 York Street"> <input type=" hidden " name="txtShippingAddress2" value="Newtown"> <input type=" hidden " name="txtShippingAddress3" value="Cape Town"> <input type=" hidden " name="txtShippingAddress4" value="7706"> <input type=" hidden " name="txtShippingAddress5" value="South Africa">

<input type="submit" value="Send Details">



33

mimoney Integration:


To initiate a mimoney transaction, you will need to POST to the following URL: https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm Variable Name Explanation Data txtMode (Required) The mode determines whether the


0 = Test 1 = Live






AlphaNumeric


txtCurrencyCode (Required) The 3 letter currency code as agreed with mimoney
















34
















35

mimoney HTML Code Example:

<FORM name="PostTest" action="https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm" method="post"> <input type="hidden" name="txtMode" value="0"> <input type="hidden" name="txtMerchantID" value="79958a8d-0c7b-4038-8e2e- 8948e1d678e1"> <input type="hidden" name="txtApplicationID" value="d48750f9-1dc0-4290-a94c- 9a1c9f7e2fb1"> <input type="hidden" name="txtMerchantReference" value="INV15642"> <input type="hidden" name="txtPrice" value="29.99"> <input type="hidden" name="txtCurrencyCode" value="ZAR"> <input type="hidden" name="txtRedirectSuccessfulURL" value="http://www.mygate.co.za/successful.htm"> <input type="hidden" name="txtRedirectFailedURL" value="http://www.mygate.co.za/failed.htm">  <input type="hidden" name="txtQty1" value="1"> <input type="hidden" name="txtItemRef1" value="Item Ref 1"> <input type="hidden" name="txtItemDescr1" value="ItemDescription 1"> <input type="hidden" name="txtItemAmount1" value="5">  <input type="hidden" name="txtQty2" value="2"> <input type="hidden" name="txtItemRef2" value="Item Ref 2"> <input type="hidden" name="txtItemDescr2" value="ItemDescription 2"> <input type="hidden" name="txtItemAmount2" value="5">  <input type="hidden" name="txtShippingCost" value="0.00"> <input type="hidden" name="txtDiscount" value="0.00">  <input type="hidden" name="txtRecipient" value="John Williams"> <input type="hidden" name="txtShippingAddress1" value="15 Yorke Street"> <input type="hidden" name="txtShippingAddress2" value="Gardens"> <input type="hidden" name="txtShippingAddress3" value="Cape Town"> <input type="hidden" name="txtShippingAddress4" value="8000"> <input type="hidden" name="txtShippingAddress5" value="South Africa">




36

SNAP Integration:


To initiate a SNAP transaction, you will need to POST to the following URL: https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm Variable Name Explanation Data txtMode (Required) The mode determines whether the


0 = Test 1 = Live






AlphaNumeric


txtCurrencyCode (Required) The 3 letter currency code as agreed with SNAP
















37
















38

SNAP HTML Code Example:

<FORM name="PostTest" action="https://www.mygate.co.za/virtual/8x0x0/dsp_ecommercepaymentparent.cfm" method="post"> <input type="hidden" name="txtMode" value="0"> <input type="hidden" name="txtMerchantID" value="79958a8d-0c7b-4038-8e2e- 8948e1d678e1"> <input type="hidden" name="txtApplicationID" value=" d5ed8aec-9615-4e64-97eb- d28948b78b7d"> <input type="hidden" name="txtMerchantReference" value="INV15642"> <input type="hidden" name="txtPrice" value="29.99"> <input type="hidden" name="txtCurrencyCode" value="ZAR"> <input type="hidden" name="txtRedirectSuccessfulURL" value="http://www.mygate.co.za/successful.htm"> <input type="hidden" name="txtRedirectFailedURL" value="http://www.mygate.co.za/failed.htm">  <input type="hidden" name="txtQty1" value="1"> <input type="hidden" name="txtItemRef1" value="Item Ref 1"> <input type="hidden" name="txtItemDescr1" value="ItemDescription 1"> <input type="hidden" name="txtItemAmount1" value="5">  <input type="hidden" name="txtQty2" value="2"> <input type="hidden" name="txtItemRef2" value="Item Ref 2"> <input type="hidden" name="txtItemDescr2" value="ItemDescription 2"> <input type="hidden" name="txtItemAmount2" value="5">  <input type="hidden" name="txtShippingCost" value="0.00"> <input type="hidden" name="txtDiscount" value="0.00">  <input type="hidden" name="txtRecipient" value="John Williams"> <input type="hidden" name="txtShippingAddress1" value="15 Yorke Street"> <input type="hidden" name="txtShippingAddress2" value="Gardens"> <input type="hidden" name="txtShippingAddress3" value="Cape Town"> <input type="hidden" name="txtShippingAddress4" value="8000"> <input type="hidden" name="txtShippingAddress5" value="South Africa">




39

Testing the Payment Gateway:

While Testing the Gateway, there are two sets of card details that can be used to simulate both successful and failed responses from MyGate:

FNB Successful Test Card Details:

Card Name Joe Soap Card Number (No spaces) 4111111111111111 Card Type Visa Card Expiry Date Any time in the future CCV Number 123

FNB Failed Test Card Details:


Nedbank Successful Test Card Details:


Nedbank Failed Test Card Details:


mimoney Test Voucher Details:

Voucher Number 111122223333444455 Cell Phone Number Any Number * Voucher Number (for failure) Any 18 digit number * Cell Phone Number (for failure) Any number Once the gateway is enabled for live trading, you should also perform a test withlive details to ensure that the live system is working to your satisfaction.



40

Return Variables from MyGate:

On each Successful and/or failed transaction, MyGate returns a result along with other variables to your Success/Failure page specified in your form POST. These return variables can then be used to do a number of things, namely:

- Display an appropriate message to your client. - Update a database on your system. - Update the order status of an order.

Below are the variables that MyGate return to your website via POST: Variable Name Explanation Data _RESULT This contains the transaction

result code which will indicate if the transaction was successful or failed.

0 = Success > 0 = Successful with Warning < 0 = Failed

_ERROR_CODE This is the error code should one exist

AlphaNumeric

_ERROR_SOURCE This is the source of the error which can be provided to us for tracking purposes

AlphaNumeric

_ERROR_MESSAGE This is the error message AlphaNumeric _ERROR_DETAIL This is the detail of the error

message AlphaNumeric

_BANK_ERROR_CODE This is the error code returned by the bank after authorization

AlphaNumeric

_BANK_ERROR_MESSAGE This is the error message returned by the bank after authorization

AlphaNumeric

_3DSTATUS This is the 3D Secure status of a credit card.

Numeric

_CARDCOUNTRY The county of the issuing credit card bank

AlphaNumeric

VARIABLE1, VARIABLE2, VARIABLE3, etc

These are your variables returned to you if they were specified in the original post page. (See Variables to be posted to MyVirtual)

AlphaNumeric



41

MyGate Encryption:

As an additional security measure, MyGate has implemented an encryption function that allows you to have a security variable sent through to MyGate that is encrypted using DES encryption. The process of how to implement this is as follows:

- The card holder goes through the checkout process on your website and comes to the final checkout page on your website.

- Your website invokes a Coldfusion webservice that takes a variable as a parameter, encrypts it and returns the encrypted value back to your server.

- This encrypted value is then populated as an additional variable in your form POST to MyGate with the name “txtTransactionID” and will have the value of the returned value in its encrypted format.

- MyGate processes your transaction normally and returns the card holder back to your success/failure URL.

- When MyGate redirects the card holder back to your website, an additional return variable is now returned: “_TRANSACTIONID”. This return variable is posted along with the other return variables and contains the following information:

txtMerchantReference || txtTransactionID || txtPrice

- This return variable is in an encrypted format so you will still need to decrypt it. - The decryption can be done by invoking an additional webservice that will take the

encrypted variable as a parameter, decrypts it and returns the unencrypted value. This can then be used to compare the values and ensure that the values are correct.

An example of how to invoke the encryption and decryption webservice is provided below:



42

Encryption Webservice:

<?php $client = new SoapClient ("https://www.mygate.co.za/virtual/6x0x0/mygate_encryption.cfc?wsdl"); $arrResults = $client->dataEncryption( 'D48750F9-1DC0-4290-A94C-9A1C9F7E2FB1', //txtApplicationUID 'Security Variable' //String to be encrypted ); print_r(explode('||', $arrResults)); echo("<br />"); ?>

Decryption Webservice:

<?php $client = new SoapClient ("https://www.mygate.co.za/virtual/6x0x0/mygate_encryption.cfc?wsdl"); $arrResults = $client->dataDecryption ( 'D48750F9-1DC0-4290-A94C-9A1C9F7E2FB1', //txtApplicationUID ‘B37AEAAA386D517DB188BD49EFDBE4FD' //Encrypted value to be decrypted ); print_r(explode('||', $arrResults)); echo("<br />"); ?> The above code examples are written in php. Please note that you can use any server side scripting language to invoke these webservices. Please also note that the encryption and decryption function uses an encryption and decryption key. This key is stored on MyGate’s systems ensuring that they remain secure. You can use the above txtApplicationUID in the example to test the encryption facility, but before you can go live with it, you would need to provide MyGate with the encryption key of your choice. This will then be loaded to your account and used to encrypt and decrypt your values.



43

Error Codes:

Although MyGate returns an error message as a return variable, you may wish to display custom error messages to your clients based on the error code returned by MyGate. For this reason, below is a full list of error codes returned by MyGate in the event of a failed/declined transaction:

1xxx = MyVirtual - Validation Response Codes

Code Message Description 1001 Gateway Required A gateway was not specified. Please check that

you have entered a gateway. If this problem persists, please contact support at [email protected]

1002 MerchantID Required A Merchant ID was not specified. Please check that you have entered a Merchant ID. If this problem persists, please contact support at [email protected]

1003 Invalid Merchant UID An invalid merchant UID was specified. Please check that you have entered the correct merchant id. The Merchant UID can be retrieved from either the integration email or from the MyGate Web Console. If this problem persists, please contact support at [email protected]

1004 ApplicationUID Required An application UID was not specified. Please check that you have entered an application id. The Application UID can be retrieved from either the integration email or from the MyGate Web Console. If this problem persists, please contact support at [email protected]

1005 Invalid ApplicationUID An invalid application ID was specified. Please check that you have entered the correct application id. The Application UID can be retrieved from either the integration email or from the MyGate Web Console. If this problem persists, please contact support at [email protected]

1006 Action Required An Action was not specified. Please check that you have entered an Action. If this problem persists, please contact support at [email protected]

1007 Invalid Action An invalid action was specified. A valid action is one of the following: {1, 2, 3, 4}. If this problem persists, please contact support at [email protected]

1008 Invalid Transaction Index An invalid TransactionIndex was specified. Please check that you have entered the correct TransactionIndex. If this problem persists, please contact support at [email protected]

1009 Terminal Required A Terminal was not specified. Please check that you have entered a Terminal. If this problem



44

persists, please contact support at [email protected]

1010 Invalid Terminal An invalid terminal was specified. A terminal is an alphanumeric string with a minimum of 4 and a maximum of 16 characters. If this problem persists, please contact support at [email protected]

1011 Mode Required A Mode was not specified. Please check that you have entered a Mode. If this problem persists, please contact support at [email protected]

1012 Invalid Mode An invalid mode was specified. A mode is a value specifying either 1=LIVE or 0=TEST mode. If this problem persists, please contact support at [email protected]

1013 MerchantReference Required A MerchantReference was not specified. Please check that you have entered a MerchantReference. The merchant reference is specified by the website and is typically the order number. If this problem persists, please contact support at [email protected]

1014 Invalid MerchantReference An invalid MerchantReference was specified. A MerchantReference is an alphanumeric string with a minimum of 4 and a maximum of 16 characters. If this problem persists, please contact support at [email protected]

1015 Amount Required An Amount was not specified. Please check that you have entered an Amount. If this problem persists, please contact support at [email protected]

1016 Zero Amount A zero amount is not allowed. Check that you have specified the right amount. If this problem persists, please contact support at [email protected]

1017 Invalid Amount An invalid Amount was specified. An amount needs to be in the format: RR.cc (50.00). If this problem persists, please contact support at [email protected]

1018 Currency Required A Currency was not specified. Please check that you have entered a currency (ZAR). If this problem persists, please contact support at [email protected]

1019 TransactionIndex required This transaction requires a TransactionIndex. Please specify a correct transaction index. If this problem persists, please contact support at [email protected]

1020 CardType required This Card Type is required. Please specify a correct Card Type. If this problem persists, please contact support at [email protected]

1021 Invalid CardType An invalid Card Type was specified. A valid Card Type is a number from 1 to 4. If this problem persists, please contact support at [email protected]



45

1022 CardNumber required The Card Number is required. Please specify a correct Card Number. If this problem persists, please contact support at [email protected]

1023 Invalid Currency An invalid Currency was specified. Describe requirements of ISO4217. If this problem persists, please contact support at [email protected]

1024 Invalid CardNumber An invalid Card Number was specified. Please specify a valid Card Number. If this problem persists, please contact support at [email protected]

1025 CCVNumber required This Credit Card Verification Number is required. Please specify a correct Credit Card Verification Number. If this problem persists, please contact support at [email protected]

1026 Invalid CCVNumber An invalid Credit Card Verification Number was specified. Please specify a valid Credit Card Verification Number. If this problem persists, please contact support at [email protected]

1027 ExpiryMonth Required An Expiry Month is required for this transaction. If this problem persists, please contact support at [email protected]

1028 ExpiryYear Required An Expiry Year is required for this transaction. If this problem persists, please contact support at [email protected]

1029 Invalid ExpiryMonth An invalid Expiry Month was specified. If this problem persists, please contact support at [email protected]

1030 Invalid ExpiryYear An invalid Expiry Year was specified. If this problem persists, please contact support at [email protected]

1031 Past Expiry Date The expiry date is in the past. If this problem persists, please contact support at [email protected]

1032 Account Type Required An account type was not specified. Please check that you have entered an account type. If this problem persists, please contact support at [email protected]

1033 Invalid Account Type An invalid Account Type was specified. A valid account type is a number between 1 and 3 inclusive. If this problem persists, please contact support at [email protected]

1034 Card Holder Required A Card Holder was not specified. Please check that you have entered a card holder. If this problem persists, please contact support at [email protected]

1035 Invalid Card Holder An invalid Card Holder was specified. A valid alphanumeric string of max length 255 must be specified. If this problem persists, please contact support at [email protected]

1036 Invalid CCV for this card type An invalid CCV was specified for this card type. A



46

valid CCV Number is…. If this problem persists, please contact support at [email protected]

1037 Invalid Budget An invalid Budget was specified. A valid number 1 or 0 must be specified. If this problem persists, please contact support at [email protected]

1038 Budget Period Required A budget period was not specified. Please check that you have entered a budget period. If this problem persists, please contact support at [email protected]

1039 Invalid Budget Period An invalid budget period was specified. A valid number between… was expected. If this problem persists, please contact support at [email protected]

1040 Amount Required A Cashback Amount was not specified. Please check that you have entered a cashback Amount. If this problem persists, please contact support at [email protected]

1041 Zero Amount A zero cashback amount is not allowed. Check that you have specified the right cashback amount. If this problem persists, please contact support at [email protected]

1042 Invalid Amount An invalid cashback Amount was specified. {Describe requirements of ISO4217}. If this problem persists, please contact support at [email protected]

1043 Invalid Authorisation An invalid authorisation was specified. Please check that you have entered a valid authorisation number. If this problem persists, please contact support at [email protected]

1044 Invalid Budget An invalid budget was specified. Please check that you have entered a valid budget number (0 or 1). If this problem persists, please contact support at [email protected]

1045 AuthorisationNumber Required An authorisation number was not specified. Please check that you have entered an Authorisation Number. If this problem persists, please contact support at [email protected]

1046 PIN Required A PIN was not specified. Please check that you have entered a PIN. If this problem persists, please contact support at [email protected]

1047 Invalid PIN An invalid PIN was specified. A valid PIN was expected. If this problem persists, please contact support at [email protected]

1048 eCommerceIndicator Required An eCommerceIndicator was not specified. Please check that you have entered an eCommerceIndicator. If this problem persists, please contact support at [email protected]

1049 Invalid eCommerceIndicator An invalid eCommerceIndicator was specified. A valid eCommerceIndicator was expected. If this problem persists, please contact support at



47

[email protected] 1050 verifiedByVisaXID Required A verifiedByVisaXID was not specified. Please

check that you have entered a verifiedByVisaXID. If this problem persists, please contact support at [email protected]

1051 Invalid verifiedByVisaXID An invalid verifiedByVisaXID was specified. A valid verifiedByVisaXID was expected. If this problem persists, please contact support at [email protected]

1052 verifiedByVisaCAVV Required A verifiedByVisaCAVV was not specified. Please check that you have entered a verifiedByVisaCAVV. If this problem persists, please contact support at [email protected]

1053 Invalid verifiedByVisaCAVV An invalid verifiedByVisaCAVV was specified. A valid verifiedByVisaCAVV was expected. If this problem persists, please contact support at [email protected]

1054 secureCodeUCAF Required A secureCodeUCAF was not specified. Please

check that you have entered a secureCodeUCAF. If this problem persists, please contact support at [email protected]

1055 Invalid secureCodeUCAF An invalid secureCodeUCAF was specified. A valid secureCodeUCAF was expected. If this problem persists, please contact support at [email protected]

1056 SSL Required This service must be called using SSL (https). If this problem persists, please contact support at [email protected]

1057 UCI Required A UCI was not specified. Please check that you have entered a UCI. If this problem persists, please contact support at [email protected]

1058 Invalid UCI An invalid UCI was specified. A valid UCI was expected containing only a combination of upper and lower case letters, numbers, - (dash) and _ (underscore); having a maximum length of 128 characters. If this problem persists, please contact support at [email protected]

1059 IP Address Required A IP Address was not specified. Please check that you have entered a IP Address. If this problem persists, please contact support at [email protected]

1060 Invalid Public IP Address An invalid Public IP Address was specified. A valid Public IP Address is expected, please note that private IP addresses are excluded and defined as codified in RFC1597, RFC1918, RFC3330, RFC3927. If this problem persists, please contact



48

support at [email protected] 1061 Shipping Country Code

Required A Shipping Country Code was not specified. Please check that you have entered a Shipping Country Code. If this problem persists, please contact support at [email protected]

1062 Invalid Shipping Country Code An invalid Shipping Country Code was specified. A valid Shipping Country Code is expected - 2 alphabetical characters. If this problem persists, please contact support at [email protected]

1063 Invalid PurchaseItemsID An invalid PurchaseItemsID was specified. If this problem persists, please contact support at [email protected]

1064 Invalid GateWayID An invalid GateWayID was specified. If this problem persists, please contact support at [email protected]

1065 3D Secure failed Cardholder enrolled, successful authentication, unsuccessful signature verification. If this problem persists, please contact support at [email protected]

1066 3D Secure failed Cardholder enrolled, unsuccessful authentication, successful signature verification. If this problem persists, please contact support at [email protected]

1067 verifiedByVisaXID Required verifiedByVisaXID required when eCommerceIndicator = 05. If this problem persists, please contact support at [email protected]

1068 verifiedByVisaCAFF Required verifiedByVisaCAFF required when eCommerceIndicator = 05. If this problem persists, please contact support at [email protected]

2xxx = MyVirtual - Initiating Response Codes

Code Message Description 2001 Invalid Gateway The specified gateway is does not exist or is invalid.

Please check that you have entered the correct gateway. If this problem persists, please contact support at [email protected]

2002 MerchantID does not exist The specified merchant ID does not exist. Please check that you have entered the correct merchant id. If this problem persists, please contact support at [email protected]

2003 ApplicationID does not exist The specified Application ID does not exist. Please check that you have entered the correct Application ID. If this problem persists, please contact support at [email protected]

2004 TransactionIndex not found The transaction index you specified does not exist. A valid transaction index must be specified in order to complete this transaction. If this problem



49

persists, please contact support at [email protected]

2005 Duplicate Merchant Reference A duplicate merchant reference was found. Your merchant reference must be unique. If this problem persists, please contact support at [email protected]

2006 Can’t Credit without Debit A credit action cannot be implemented without a debit action on a transaction. If this problem persists, please contact support at [email protected]

2007 ReverseAuthorisation Already Performed

A ReverseAuthorisation action has already been implemented for this transaction. No more actions can be performed on this Transaction. If this problem persists, please contact support at [email protected]

2008 Debit Already Performed A Debit action has already been implemented for this transaction. A ReverseAuthorisation Action can no longer be performed on this transaction. If this problem persists, please contact support at [email protected]

2009 Credit Already Performed A Credit action has already been implemented for this transaction. No more actions can be performed on this Transaction. If this problem persists, please contact support at [email protected]

2010 Authorisation Expected Authorisation Action has not yet been performed. All transactions have to begin with an authorisation action. If this problem persists, please contact support at [email protected]

2011 Debit Already performed A debit action has already been performed on this transaction. An action cannot be performed twice on the same transaction. If this problem persists, please contact support at [email protected]

2012 Authorisation Already performed An authorisation action has already been performed on this transaction. An action cannot be performed twice on the same transaction. If this problem persists, please contact support at [email protected]

2013 Budget must preceed transaction

Only a successful AUTHORISEPURCHASE and BUDGET can preceed a BUDGETREVERSAL. If this problem persists, please contact support at [email protected]

2014 Authorise must preceed transaction

Only a successful AUTHORISEREFUND can preceed a AUTHORISEREFUNDREVERSAL. If this problem persists, please contact support at [email protected]


Only a successful AUTHORISEREFUND can preceed a REFUND. If this problem persists, please contact support at [email protected]

2016 Refund must preceed transaction

Only a successful AUTHORISEREFUND and REFUND can preceed a REFUNDREVERSAL. If



50

2020 Incorrect Relationship An Incorrect Relationship with Gateway, Application

and Merchant. The relationship between the given 3 values doesn't exist. If this problem persists, please contact support at [email protected]

2021 Invalid Shipping Country Code An invalid Shipping Country Code was specified. Please provide a valid shipping country code. If this problem persists, please contact support at [email protected]

2050 Incorrect Decimal Length An incorrect amount of decimal places was passed. If this problem persists, please contact support at [email protected]

4xxx = MyVirtual - Security Response Codes

Code Message Description 4001 Mode Denied This mode was denied. You cannot perform Live

transactions until you have completed the test phase. Please contact support at [email protected]

4002 Invalid Mode / Credit Card You cannot perform this transaction in the current mode. If you wish use test credit card numbers, please switch to test mode. If this problem persists, please contact support at [email protected]

4003 Merchant Inactive This merchant ID has not yet been enabled. If this problem persists, please contact support at [email protected]

4004 Merchant Suspended This merchant ID has been suspended. If this problem persists, please contact support at [email protected]

4005 Merchant Removed This merchant ID has been removed. If this problem persists, please contact support at [email protected]

this problem persists, please contact support at [email protected]


Only a successful AUTHORISECASHADVANCE can preceed an AUTHORISECASHADVANCEREVERSAL. If this problem persists, please contact support at [email protected]


Only a successful AUTHORISECASHADVANCE can preceed a CASHADVANCE. If this problem persists, please contact support at [email protected]

2019 Refund must preceed transaction

Only a successful AUTHORISECASHADVANCE and CASHADVANCE can preceed a CASHADVANCEREVERSAL. If this problem persists, please contact support at [email protected]



51

4006 Application Inactive This Application ID has not yet been enabled. Please contact support at [email protected] to be activated

4007 Application Suspended This application ID has been suspended. If this problem persists, please contact support at [email protected]

4008 Application Removed This application ID has been removed. If this problem persists, please contact support at [email protected]

5xxx = MyVirtual - Gateways Response Code

Code Message Description 5001 Connection error to bank Error occurred because the Gateway haven’t been

4009 Source IP Address Invalid The caller’s IP Address is not in the list of allowed IP Addresses for this Application. If this problem persists, please contact support at [email protected]

4010 Gateway Inactive The gateway that your trying to use, has been set to inactive. If this problem persists, please contact support at [email protected]

4011 Gateway Obsolete The gateway that your trying to use, has been set to obsolete. If this problem persists, please contact support at [email protected]

4012 Currency not allowed The currency you have specified is not listed under the allowed list of currencies for your application. You may only use ZAR as a currency. If this problem persists, please contact support at [email protected]

4013 Invalid Currency The currency you have specified is invalid. If this problem persists, please contact support at [email protected]

4014 Transaction Limit Exceeded This transaction amount exceeds the transaction limit for your application. If this problem persists, please contact support at [email protected]

4015 Cumulative Transaction Limit Exceeded

This transaction amount exceeds the cumulative transaction limit for your application. If this problem persists, please contact support at [email protected]

4016 CardType not allowed The card type you have specified is not listed under the allowed list of card types for your application. If this problem persists, please contact support at [email protected]

4017 AccountType not allowed The account type you have specified is not listed under the allowed list of account types for your application. If this problem persists, please contact support at [email protected]

4018 Budget not allowed Budget transactions are not allowed for your application. If this problem persists, please contact support at [email protected]



52

configured yet for live transactions 5002 Declined from the bank The bank decline the transactions. See Appendix A

– Bank Response Codes 5003 Unexpected Error An unexpected error occurred that was not provided

for. Please notify MyGate immediately

6xxx = MyVirtual - Fraud Module Response Code

Code Message Description 6001 Card Number Blacklisted Your card has been blacklisted on the payment

gateway. If this problem persists, please contact support at [email protected]

6002 Country Code Blacklisted Your country code has been blacklisted on the payment gateway. If this problem persists, please contact support at [email protected]

6003 IP Address Blacklisted Your ip address has been blacklisted on the payment gateway. If this problem persists, please contact support at [email protected]

6004 UCI Blacklisted Your unique client identifier has been blacklisted on the payment gateway. If this problem persists, please contact support at [email protected]

6005 GIR Check Failed The fraud module determined that this transaction was not safe for processing. This was determined by the Global IP Recognition Procedure. If this problem persists, please contact support at [email protected]

6007 RFI Check Failed The fraud module determined that this transaction was not safe for processing. This was determined by the Repeated Failure Identification Procedure. If this problem persists, please contact support at [email protected]

6008 RSI Check Failed The fraud module determined that this transaction was not safe for processing. This was determined by the Repeated Success Identification Procedure. If this problem persists, please contact support at [email protected]

6009 UCI Check Failed The fraud module determined that this transaction was not safe for processing. This was determined by the Unique Client Identifier Service Procedure. If this problem persists, please contact support at [email protected]

8xxx = MyVirtual – Warnings Codes

Code Message Description 8001 Mode was ignored 8002 Amount was ignored 8003 CCType was ignored 8004 CCNumber was ignored 8005 CCVNumber was ignored 8006 ExpiryMonth was ignored



53

8007 ExpiryYear was ignored 8008 Cumulative Transaction Limit

Almost Exceeded

8009 Transaction Limit Exceeded You have exceeded your transaction limit. If this problem persists, please contact support at [email protected]

8010 Cumulative Transaction Limit Exceeded

You have exceeded your cumulative transaction limit. If this problem persists, please contact support at [email protected]

8011 Transaction Index was ignored 8012 Currency was ignored 8013 Account Type was ignored 8014 Card Holder was ignored 8015 Budget was ignored 8016 Budget Period was ignored 8017 Cashback Amount was ignored 8018 Authorisation was ignored 8029 Flagged for Card Number

Blacklist This transaction has been flagged by the Card Number Blacklist Procedure.

8030 Flagged for Country Code Blacklist

This transaction has been flagged by the Country Code Blacklist Procedure.

8031 Flagged for IP Address Blacklist This transaction has been flagged by the IP Address Blacklist Procedure.

8032 Flagged for UCI Blacklist This transaction has been flagged by the Unique Client Identifier Blacklist Procedure.

8033 Flagged for GIR This transaction has been flagged by the GIR Procedure.

8035 Flagged for RFI This transaction has been flagged by the RFI Procedure

8036 Flagged for RSI This transaction has been flagged by the RSI Procedure.

8037 Flagged for UCI This transaction has been flagged by the UCI Procedure.

8038 Card Number Blacklist not performed

Card Number Blacklist procedure was not performed on this transaction

8039 Country Code Blacklist not performed

Country Code Blacklist procedure was not performed on this transaction.

8040 IP Address Blacklist not performed

IP Address Blacklist procedure was not performed on this transaction.

8041 UCI Blacklist not performed Unique Client Identifier Blacklist procedure was not performed on this transaction.

8042 GIR not performed GIR procedure was not performed on this transaction.

8044 RFI not performed RFI procedure was not performed on this transaction.

8045 RSI not performed RSI procedure was not performed on this transaction.

8046 UCI not performed UCI procedure was not performed on this transaction.



54

8047 PurchaseItemsID Was Ignored

9xxx = MyVirtual - Unexpected Error

9001 Unexpected Error An unexpected error has occurred. Please try again later. If this problem persists, please contact support at [email protected]

9002 Request Not Implemented You requested functionality that has not been implemented on this gateway yet. If this problem persists, please contact support at [email protected]

9003 Card Type Not Implemented This card type has not yet been implemented on this gateway. If this problem persists, please contact support at [email protected]

9004 Fraud Status Unknown The fraud module returned an unexpected status. If this problem persists, please contact support at [email protected]

9005 Fraud Result Unknown The fraud module returned an unexpected result. If this problem persists, please contact support at [email protected]

1xx – 2xx mimoney Error Codes

100 Invalid Voucher Number An invalid voucher number was specified. A voucher number needs to be numeric and 18 characters in length.

101 Invalid MSISDN An invalid MSISDN number was specified. Please enter a valid MSISDN (Cell Number).

102 Invalid Account Number An Invalid Account Number was specified. Please supply a valid account number. If this problem persists, please contact Support at [email protected]

103 Invalid Amount An invalid amount was specified. If this problem persists, please contact Support at [email protected]

104 Invalid Card Number An invalid card number was specified. If this problem persists, please contact Support at [email protected]

105 Invalid ID Number An invalid ID number was specified. If this problem persists, please contact Support at [email protected]

106 Invalid MerchantID An Invalid MerchantID was specified. If this problem persists, please contact Support at [email protected]



55

107 Invalid MSISDN An invalid MSISDN number (Cell Phone Number) was specified. If this problem persists, please contact Support at [email protected]

108 Invalid PIN An invalid PIN was specified. If this problem persists, please contact Support at [email protected]

109 Invalid Purchase Data Invalid Purchase Data was specified. If this problem persists, please contact Support at [email protected]

110 Invalid Statement Code An invalid statement code was specified. If this problem persists, please contact Support at [email protected]

111 Invalid TerminalID An invalid TerminalID was specified. If this problem persists, please contact Support at [email protected]

112 Invalid Transaction Reference An invalid transaction reference was specified. If this problem persists, please contact Support at [email protected]

113 Invalid Voucher Action An invalid voucher action was specified. If this problem persists, please contact Support at [email protected]

114 Invalid Voucher Number An invalid voucher number was specified. If this problem persists, please contact Support at [email protected]

115 Invalid Voucher State The specified voucher is not in the correct state. If this problem persists, please contact Support at [email protected]

116 Invalid Voucher Transaction reference

An invalid voucher transaction reference was specified. If this problem persists, please contact Support at [email protected]

117 Invalid Voucher Type An invalid voucher type was specified. If this problem persists, please contact Support at [email protected]

200 Application Error An Application Error occurred. If this problem persists, please contact Support at [email protected]

201 Accounting System Unable to Find Payment

The mimoney accounting system was unable to process your transaction. If this problem persists, please contact Support at [email protected]

202 Account Limit Reached The total value of the transaction exceeds that of your account limit. If this problem persists, please contact Support at [email protected]

203 Channel Deactivated The transactional channel has been deactivated. If this problem persists, please contact Support at [email protected]

204 Channel Password Invalid The transactional channel password is invalid. If this



56

problem persists, please contact Support at [email protected]

205 Could Not Create Voucher The voucher could not be created at this time. If this problem persists, please contact Support at [email protected]

206 Could Not Find Original Transaction

The original transaction could not be found. If this problem persists, please contact Support at [email protected]

207 Could Not Find Voucher The specified voucher could not be found. If this problem persists, please contact Support at [email protected]

208 Could Not Find Voucher Transaction

The specified voucher transaction could not be located. If this problem persists, please contact Support at [email protected]

209 Could Not Load MSISDN Limit The MSISND limit could not be set at this time. If this problem persists, please contact Support at [email protected]

210 Could Not Load Payment The payment could not be loaded. If this problem persists, please contact Support at [email protected]

211 Could Not Load Transaction Steps

The transaction steps could not be loaded. If this problem persists, please contact Support at [email protected]

212 Could Not Lock Transaction for Reversal

The transaction could not be locked for a reversal to occur. If this problem persists, please contact Support at [email protected]

213 Could Not Obtain Voucher Lock

The voucher could not be locked. If this problem persists, please contact Support at [email protected]

214 Could Not Send Notification Notification could not be sent. If this problem persists, please contact Support at [email protected]

215 Could Not Unlock Transaction From Reversal

The transaction could not be unlocked from the reversal. If this problem persists, please contact Support at [email protected]

216 Could Not Update Voucher Action

The voucher action could not be updated. If this problem persists, please contact Support at [email protected]

217 Could Not Update Voucher at Transaction Close

The voucher could not be updated at transaction close. If this problem persists, please contact Support at [email protected]

218 Could Not Update Voucher PIN Data

The voucher PIN data could not be updated. If this problem persists, please contact Support at [email protected]

219 GI Technical Error A GI Technical Error occured. If this problem persists,



57

please contact Support at [email protected]

220 Incorrect Merchant An incorrect merchant was specified. If this problem persists, please contact Support at [email protected]

221 Incorrect Transaction An incorrect transaction was specified. If this problem persists, please contact Support at [email protected]

222 Incorrect Voucher PIN An incorrect voucher PIN was specified. If this problem persists, please contact Support at [email protected]

223 Insufficient Funds in Voucher The voucher has insufficient funds for the transaction. If this problem persists, please contact Support at [email protected]

224 Merchant Inactive The specified merchant is inactive. If this problem persists, please contact Support at [email protected]

225 Merchant Limit Reached The merchant has reached their transactional limit. If this problem persists, please contact Support at [email protected]

226 Merchant No Issuer There is no issuer for the specified merchant. If this problem persists, please contact Support at [email protected]

227 Merchant TerminalID Required A TerminalID was not specified for the transaction. If this problem persists, please contact Support at [email protected]

228 Merchant Terminal Inactive The terminal specified is inactive. If this problem persists, please contact Support at [email protected]

229 Merchant Terminal Limit Reached

The transactional limit for the specified terminal has been reached. If this problem persists, please contact Support at [email protected]

230 Merchant Terminal Unknown An unknown terminal was specified. If this problem persists, please contact Support at [email protected]

231 Merchant Unknown An unknown merchant was specified. If this problem persists, please contact Support at [email protected]

232 Merchant Voucher Action Not Found

The voucher action specified was not found. If this problem persists, please contact Support at [email protected]

233 MSISDN Daily FICA Limit Reached

The daily FICA limit for the specified MSISDN was reached. If this problem persists, please contact Support

234 MSISDN Monthly FICA Limit The monthly FICA limit for the specified MSISDN was



58

Reached reached. If this problem persists, please contact Support at [email protected]

235 Original transaction Not Successful

The original transaction was not successful. If this problem persists, please contact Support at [email protected]

236 Payment Already Reversed The transaction has already been reversed. If this problem persists, please contact Support at [email protected]

237 Payment Error A payment error has occured. If this problem persists, please contact Support at [email protected]

238 PIN Security Requirements Not Met

The PIN security requirements were not met. If this problem persists, please contact Support at [email protected]

239 Unable To End Voucher Transaction

The transaction was unable to be completed. If this problem persists, please contact Support at [email protected]

240 Unable To Move Fee Amount The fee amount could not be moved. If this problem persists, please contact Support at [email protected]

241 Unable To Move Principal Amount

The principal amount could not be moved. If this problem persists, please contact Support at [email protected]

242 Unable To Move Profit Share Amount

The profit share amount could not be moved. If this problem persists, please contact Support at [email protected]

243 Unable To Move Service Fee Amount

The service fee amount could not be moved. If this problem persists, please contact Support at [email protected]

244 Unable To Move TransactionTax Amount

The transaction tax amount could not be moved. If this problem persists, please contact Support at [email protected]

245 Unable To Obtain Merchant Voucher Rate

The merchant voucher rate was unable to be obtained. If this problem persists, please contact Support at [email protected]

246 Unable To Obtain Voucher Details

The voucher details could not be obtained. If this problem persists, please contact Support at [email protected]

247 Unable To Obtain Voucher Quote

The voucher quote could not be obtained. If this problem persists, please contact Support at [email protected]

248 Unable To Start Voucher Activation

Voucher activation could not be started. If this problem persists, please contact Support at [email protected]

249 Unable To Start Voucher Voucher payment reversal could not be started. If this



59

Payment Reversal problem persists, please contact Support at [email protected]

250 Unable To Start Voucher Purchase

Voucher purchase could not be started. If this problem persists, please contact Support at [email protected]

251 Unable To Start Voucher Redemption

Voucher redemption could not be started. If this problem persists, please contact Support at [email protected]

252 Unable To Start Voucher Status Change

The voucher status change could not be started. If this problem persists, please contact Support at [email protected]

253 Unknown Fee Calculation type An unknown fee calculation type was specified. If this problem persists, please contact Support at [email protected]

254 Voucher Amount Below Minimum Limit

The specified amount is below the minimum limit. If this problem persists, please contact Support at [email protected]

255 Voucher Amount Exceeds Maximum Limit

The specified amount exceeds the vouchers maximum limit. If this problem persists, please contact Support at [email protected]

256 Voucher Cost Exceeds Quoted Value

The voucher cost exceeds the quoted value. If this problem persists, please contact Support at [email protected]

257 Voucher Number Generation Failure

The voucher number could not be generated. If this problem persists, please contact Support at [email protected]

258 Voucher PIN Locked The PIN for the specified voucher has been locked. If this problem persists, please contact Support at [email protected]

259 Voucher Status Change Invalid The specified change in voucher is invalid. If this problem persists, please contact Support at [email protected]

260 Voucher Status Is Inactive The voucher specified is inactive. If this problem persists, please contact Support at [email protected]

261 Voucher Status Is Cancelled The voucher specified is cancelled.

262 Voucher Status Is Creating The specified voucher is being created. If this problem persists, please contact Support at [email protected]

263 Voucher Status Is Expired The specified voucher has expired. If this problem persists, please contact Support at [email protected]

264 Voucher Status Is Pending Activation

The specified voucher is pending activation. If this problem persists, please contact Support at



60

[email protected]

265 Voucher Status Is Redeemed Or Depleted

The specified voucher is redeemed or depleted. If this problem persists, please contact Support at [email protected]

266 Voucher Status Is Suspended The specified voucher is suspended. If this problem persists, please contact Support at [email protected]

267 Voucher Status Is Undefined The specified voucher status is undefined. If this problem persists, please contact Support at [email protected]

268 VoucherTransaction In Incorrect State

The specified transaction is in the incorrect state. If this problem persists, please contact Support at [email protected]

269 Voucher Transaction Too Old The specified trnasaction is too old to be re-processed. If this problem persists, please contact Support at [email protected]

270 MSISDN Mismatch There is a mismatch with the MSISDN. If this problem persists, please contact Support at [email protected]

271 Unknown Workflow Version The workflow version is unknown. If this problem persists, please contact Support at [email protected]

272 Unable To Start Voucher Grouping

The voucher could not be grouped. If this problem persists, please contact Support at [email protected]

273 Unable To Start Voucher Grouping Reversal

The voucher could not be grouped for reversal. If this problem persists, please contact Support at [email protected]

274 Voucher Payment Reversal Illegal

A reversal on the specified voucher is not permitted. If this problem persists, please contact Support at [email protected]

275 Merchant does not exist The specified Merchant does not exist on the MiMoney database. If this problem persists, please contact support.

Documents

Myvirtual Userguide