iverilite Client documentation Version 2.1

Transcription

1 iverilite Client documentation Version 2.1

2 Introduction iverilite will allow the Small and Medium size websites who are running on any type of Operating System (UNIX, LINUX, NT etc) be able to use iveri This means they do not need to use the Microsoft based product to authorise a Credit card. A Web site developer wanting to have the ability to accept credit cards online will merely need to register the required information with iveri and create the HTML pages specified in the following specification. The Broad flow Registering. The Merchant should register their billing details as well as banking details with iveri by phoning Nedbank s Nedlink Merchant helpdesk on and asking for the iveri Technical Division. Once the Merchants web site developer has completed development of the HTML pages in this specification there will first be a test phase to verify the correct implementation of this specification and then a Live phase to verify that the banking details are correct. Flow of events in a transaction. 1) Merchants Website sends a request to the iverilite Server with all the variables listed in Appendix A and B. 2) The iverilite Server takes care of encryption of the data using 128bit SSL. 3) The iverilite Server check the validity of the data 4) The iverilite Server checks if you are a valid merchant 5) If the previous two steps are correct the iverilite Server displays a Please Wait while Authorizing. page to the cardholder. If the details are not correct the iverilite Server passes control back to the Merchants Website by redirecting to the ErrorURL. 6) The iverilite Server performs the authorisation at the appropriate financial institution. 7) The result of an authorisation can be either successful, failed system error or please try again later. In the event of a successful transaction the Client as well as the Merchant can be ed a statement indicating the successful completion of the transaction. All transactions are stored in a database so it is always possible to trace a transaction in the case of an failure. 8) From a financial perspective the Card Holder will be debited and the Merchants account credited at the end of the financial institutions day. 9) iverilite will then return the original form sent to iverilite (as if it had been sent to the Merchants website instead of iverilite) as well as an Error Code, Transaction Index, Invoice number (if appropriate) to the appropriate return URL.

3 Test Phase In the test phase all that is required from you the Merchant is where your URL referrer is (the pages that you hit submit on to go to us).this must be captured by you in Back Office in the Lite Configure Application section. Details regarding access to Back Office will be sent to you after your Billing Details have been captured as well as details to obtain the iveri Lite Back Office User Guide which explains the initial set-up as well as descriptions of all functions within iveri Lite Back Office. Make sure that your Lite_Merchant_ApplicationID is the Test Application ID(without the {} brackets) which was sent to you/your developer by when you were captured on the iveri server and the page you submit your test transactions to is: The test USN number to use for your Test transactions is: If you don t you will receive an error code (255). Note : When performing a test transaction, using your Test Application ID (via the Nedconnect Emulator), the following credit card numbers must be used: Credit Card Result Number returns "Authorised" (acquirer code 0) randomly returns "Hot Card", "Please Call" or "Denied" (acquirer codes 3,4,5) randomly returns "Unable to process" or times out (acquirer code 9 or no reply) All other card numbers the emulator will return "Invalid card number" (acquirer code 14) for instance will produce this error. A real Credit Card Number will also generate this error code in Test. NOTE: Any expiry date in the future can be used for all the above card numbers. Do not make the expiry date more than 2 years in the future. If you want to generate an "Invalid Expiry Date" message, make the expiry date in the past.

4 Live Phase For us to take the Merchant to Live we first need one successful test transaction (mail with the invoice number and your telephone number asking to go live). Notes. Additional tags sent to iverilite will be echoed through to the success/fail etc url's specified in Lite_Website_Successful_Url, Lite_Website_Fail_Url etc. s sent to the Card Holder and the merchant take the following format (see Appendix G). It is possible to turn off iverilite's ability to send s if the merchant would prefer to send them himself. The following extra parameters are sent to the success/fail etc URL's. (Appendix C) Appendix A : Lite Specification General descriptor Name length values Notes Version Lite_Version 5 Set to current Version number ex. 2.0, for Old Version left blank Not available. iveri Status Lite_Payment_Card_Status 10 Status of transaction iveri Application id Lite_Merchant_ApplicationId 36 Allocated to the Merchant by Digital Skies during registration Amount to authorize Lite_Order_Amount 10 The total amount for the order including tax in cents. This must be equal to the sum of the lineamount*linequantity for each line item Terminal on the Lite_Order_Terminal Web 8 Optional Authorisation Optional preauthorisation code Lite_Order_AuthorisationCode 6 Code received from a financial institution Budget Period Optional request to put this order Lite_Order_BudgetPeriod 2 onto a budget plan. The normal options for this are 0, 6, 12, 18, 24 and indicating to budget period. Specifying this field does not guarantee that the request will be granted a budget period. Success End Url Lite_Website_Successful_Url 255 Failed End Url Lite_Website_Fail_Url 255 URL to pass control back to upon successful completion of a transaction URL to pass control back to if the authorisation is refused by the financial institution

5 Network error End Url Lite_Website_TryLater_Url 255 Code error End Url The Authorizing sites background colour The Authorizing sites Text colour LineItem LineQuantity LineAmount Autogenerate Invoice Extension Card Pre-Auth Mode Lite_Website_Error_Url 255 Lite_Website_BgColor 7 Lite_Website_TextColor 7 Lite_Order_LineItems_Product_# 255 Lite_Order_LineItems_Quantity_# 10 Lite_Order_LineItems_Amount_# 10 Lite_ConsumerOrderID_PreFix 5 Lite_Authorisation 5 Error Handling Lite_On_Error_Resume_Next 5 #FFFFF F URL to pass control back to if there is a system error which could be overcome by trying again later URL to pass control back to if the form has not been filled in correctly of there is an inconsistency in the form Optional background colour to use for any intermediary pages #000000Optional Text colour to use for any 0 intermediary pages Line item of what is being ordered. The # indicates a number starting at 1 and incrementing by 1 for every line item. This is essentially a description of the item being ordered. Line item Quantity of what is being ordered. The # indicates a number starting at 1 and incrementing by 1 for every line item. This is the number of units being ordered. Line item cost including tax if any of what is being ordered. The # indicates a number starting at 1 and incrementing by 1 for every line item. This is the unit price for this particular item. E.g. DCT for DCT0001. If the Ecom_ConsumerOrderID is set to "AUTOGENERATE" then this field is used to specify the first few letters that will be used to generate the InvoiceNumber. E.g. if this field is set to "INV" and Ecom_ConsumerOrderID is set to "AUTOGENERATE" then invoice numbers like "INV00001" and "INV00002" etc will be generated. Set to True or False. If True then a Authorisation will be made, if false a Debit will be made. The Authorisation code will be stored for 3 weeks before you need to confirm the transaction in the BackOffice under view orders. Set this to "True" to enable the "Auto Click Through" feature. I.e. the browser will automatically

6 attempt to click through otherwise the customer/card holder will have to manually click on the "click here" Url in order to progress through the transaction. Setting this to false is helpful when debugging. Note: Not all of the fields in this specification are mandatory. Fields which are marked in grey are the only mandatory fields. Appendix B :ECML Version 1 Specification General descriptor Name length values Notes ship to title Ecom_ShipTo_Postal_Name_Prefix 4 e.g., Mr., Mrs., Ms.; field commonly not used ship to first Ecom_ShipTo_Postal_Name_First 15 name ship to middle Ecom_ShipTo_Postal_Name_Middle 15 may also be used for middle initial name ship to last Ecom_ShipTo_Postal_Name_Last 15 name ship to name suffix Ecom_ShipTo_Postal_Name_Suffix 4 e.g., Ph.D., Junior, Esquire; field commonly not used ship to street1 Ecom_ShipTo_Postal_Street_Line1 20 ship to street2 Ecom_ShipTo_Postal_Street_Line2 20 ship to street3 Ecom_ShipTo_Postal_Street_Line3 20 ship to city Ecom_ShipTo_Postal_City 22 ship to state or Ecom_ShipTo_Postal_StateProv 2 2 characters are the minimum for the province US and Canada, other countries may require longer fields; for the US use 2 character US Postal state abbr ship to zip or postal code Ecom_ShipTo_Postal_PostalCode 14 ship to country Ecom_ShipTo_Postal_CountryCode 2 use ISO letter codes for country names ship to phone Ecom_ShipTo_Telecom_Phone_Number digits are the minimum for the US and Canada, other countries may require longer fields, recommend placing on "x" before an extension ship to Ecom_ShipTo_Online_ 40 e.g., jsmith@isp.com bill to title Ecom_BillTo_Postal_Name_Prefix 4 e.g., Mr., Mrs., Ms.; field commonly not used bill to first If this is blank your invoice would read Ecom_BillTo_Postal_Name_First 15 name Dear Customer. bill to middle name Ecom_BillTo_Postal_Name_Middle 15 may also be used for middle initial bill to last name Ecom_BillTo_Postal_Name_Last 15 bill to name Ecom_BillTo_Postal_Name_Suffix 4 e.g., Ph.D., Junior, Esquire; field

7 suffix bill to street1 Ecom_BillTo_Postal_Street_Line1 20 bill to street2 Ecom_BillTo_Postal_Street_Line2 20 bill to street3 Ecom_BillTo_Postal_Street_Line3 20 bill to city Ecom_BillTo_Postal_City 22 bill to state or province Ecom_BillTo_Postal_StateProv 2 commonly not used 2 characters are the minimum for the US and Canada, other countries may require longer fields; for the US use 2 character US Postal state abbr bill to zip or postal code Ecom_BillTo_Postal_PostalCode 14 bill to country Ecom_BillTo_Postal_CountryCode 2 use ISO letter codes for country names bill to phone Ecom_BillTo_Telecom_Phone_Number digits are the minimum for the US and Canada, other countries may require longer fields, recommend placing on "x" before an extension bill to Ecom_BillTo_Online_ 40 This is the address the invoice would be mailed to. e.g., jsmith@isp.com receipt to title Ecom_ReceiptTo_Postal_Name_Prefix 4 e.g., Mr., Mrs., Ms.; field commonly not used receipt to first Ecom_ReceiptTo_Postal_Name_First 15 name receipt to Ecom_ReceiptTo_Postal_Name_Middle 15 may also be used for middle initial middle name receipt to last name Ecom_ReceiptTo_Postal_Name_Last 15 receipt to name Ecom_ReceiptTo_Postal_Name_Suffix 4 e.g., Ph.D., Junior, Esquire; field suffix commonly not used receipt to Ecom_ReceiptTo_Postal_Street_Line1 20 street1 receipt to Ecom_ReceiptTo_Postal_Street_Line2 20 street2 receipt to Ecom_ReceiptTo_Postal_Street_Line3 20 street3 receipt to city Ecom_ReceiptTo_Postal_City 22 receipt to state or province Ecom_ReceiptTo_Postal_StateProv 2 2 characters are the minimum for the US and Canada, other countries may require longer fields; for the US use 2 character US Postal state abbr receipt to zip or Ecom_ReceiptTo_Postal_PostalCode 14 postal code receipt to Ecom_ReceiptTo_Postal_CountryCode 2 use ISO letter codes for country country receipt to phone Ecom_ReceiptTo_Telecom_Phone_Numb er names digits are the minimum for the US and Canada, other countries may require longer fields, recommend placing on "x" before an extension receipt to Ecom_ReceiptTo_Online_ 40 e.g., jsmith@isp.com name on card Ecom_Payment_Card_Name 30 name of cardholder

8 card type Ecom_Payment_Card_Type 4 use the first 4 letters of the association name: American Express=AMER; Diners Club=DINE; Discover=DISC; JCB=JCB; Mastercard=MAST; Visa=VISA; other association names may require more than 4 characters. You can tell card numbers apart from the first digit of a credit card number. 3 - American Express 4 - Visa 5 - MasterCard card number Ecom_Payment_Card_Number 19 cardholder verification value card expiration date day card expiration date month card expiration date year payment protocols available Ecom_Payment_Card_Verification 4 additional cardholder verification number such as American Express' CIV, MasterCard's CVC2, and Visa's CVV2 values Ecom_Payment_Card_ExpDate_Day day of the month Ecom_Payment_Card_ExpDate_Month Jan - 1, Feb - 2, March - 3, etc. Ecom_Payment_Card_ExpDate_Year 4 Value in wallet cell is always 4 digits, e.g., 1999, 2000, Ecom_Payment_Card_Protocols 20 IVERI A space seperated list of protocols available for a specified card. Initial list of case insensitive tokens: "none", "set", or "setcert". "Set" indicates usable with SET Protocol (i.e., is in a SET wallet) without a SET certificate. "Setcert" indicates same but does have a SET certificate. "None" indicates standard is being used but wallet is not SET capable or the card has not been entered into the SET wallet. Usually a hidden field. consumer generated order ID schema version number Ecom_ConsumerOrderID 20 unique order ID generated by the consumer software. If at all possible this should be filled out. If it is impossible iveri will generate one for you but it should preferably be filled out by the merchant. For iveri to create a unique ordered for you please set this to "AUTOGENERATE" and refer to the Lite_ConsumerID_PreFix which enables you to specify the first few letters of the invoice. Ecom_SchemaVersion Identifies the ecom schema version number; format 999_99; digit (3)_digit(2); defined within a URL

9 end transaction flag (e.g. Field should be included on every page with an ECML field on it, and is usually a hidden field. Ecom_TransactionComplete - FALSEA flag to indicate that this web page/aggregate is the final one for this transaction. Usually a hidden field. Note: Not all of the fields in this specification are mandatory. Fields which are marked in grey are the only mandatory fields. ECML Extensions added by iveri General descriptor Name length values notes card expiration Ecom_Payment_Card_StartDate_Day day of the month date day card expiration Ecom_Payment_Card_StartDate_Month Jan - 1, Feb - 2, March - 3, etc. date month card expiration Ecom_Payment_Card_StartDate_Year 4 Value in wallet cell is always 4 digits, date year e.g., 1999, 2000, Note: Not all of the fields in this specification are mandatory. Fields which are marked in grey are the only mandatory fields. Appendix C: Additional Variables Note: These are form variables that are not part of the iveri Lite specification but may be required by the merchant. These form variables (if used) will be returned to the website together with all the iveri Lite form variables. For added security, to prevent possible fraud by someone obtaining the websites return URL and parameters, we highly recommend that you submit an additional form variable of arbitrary name chosen by the merchant and random value which changes from transaction to transaction. This will be returned to the website along with all the iveri Lite form variables and all you need to do is check for the existence of the form variable and that the value thereof is the same as that generated and used during the submission of the iveri Lite page.

10 Appendix D: Variables sent back General descriptor Name length values Notes iveri Status Lite_Payment_Card_Status 10 Status of transaction Result Description Lite_Result_Description 255 Lite Transaction Index Lite_TransactionIndex 36 Status of transaction described, if any error error description. This is a globally unique number generated by the Merchant and is iveri unique number to identify this transaction. consumer generated order ID MerchantReference 20 unique order ID generated by the consumer software. If at all possible this should be filled out. If it is impossible iveri will generate one for you but it should preferably be filled out by the merchant. For iveri to create a unique ordered for you please set Lite_ConsumerID to "AUTOGENERATE" and refer to the Lite_ ConsumerOrderID _PreFix which enables you to specify the first few letters of the invoice. Bank Reference Lite_BankReference 11 Cycle, Trace number eg ,12345 Transaction Date Lite_TransactionDate The date the authorisation took place Referrer Lite_Referrer The Website Referrer where the merchants Transaction started. Appendix E: Error Codes The text description of any error received may be obtained by setting Lite_On_Error_Resume_Next to False. The Source of the Error can be found by querying the value Lite_Payment_Card_Status.

11 Appendix F: Example Code Example of an HTML page requesting the cardholders credit card details <html> <body> <form METHOD="POST" ACTION=" id=aform name=aform> <!-- Lite --> <input type="hidden" id="lite_merchant_applicationid" name="lite_merchant_applicationid" value="use Your Test/Live Application ID ed to you from iveri"> <input type="hidden" id="lite_order_amount" name="lite_order_amount" value="99"> <input type="hidden" id="lite_order_terminal" name="lite_order_terminal" value="web"> <input type="hidden" id="lite_order_authorisationcode" name="lite_order_authorisationcode" value=""> <input type="hidden" id="lite_order_budgetperiod" name="lite_order_budgetperiod" value="0"> <input type="hidden" id="lite_website_textcolor" name="lite_website_textcolor" value="#ffffff"> <input type="hidden" id="lite_website_bgcolor" name="lite_website_bgcolor" value="#86001b"> <input type="hidden" id="lite_consumerorderid_prefix" name="lite_consumerorderid_prefix" value="ppp"> <input type="hidden" id="lite_on_error_resume_next" name="lite_on_error_resume_next" value="true"> <!-- products --> <input type="hidden" id="lite_order_lineitems_product_1" name="lite_order_lineitems_product_1" value="donation product#1"> <input type="hidden" id="lite_order_lineitems_quantity_1" name="lite_order_lineitems_quantity_1" value="1"> <input type="hidden" id="lite_order_lineitems_amount_1" name="lite_order_lineitems_amount_1" value="35"> <input type="hidden" id="lite_order_lineitems_product_2" name="lite_order_lineitems_product_2" value="donation product#2"> <input type="hidden" id="lite_order_lineitems_quantity_2" name="lite_order_lineitems_quantity_2" value="2"> <input type="hidden" id="lite_order_lineitems_amount_2" name="lite_order_lineitems_amount_2" value="32"> <input type="hidden" ID="Lite_Website_Successful_url" NAME="Lite_Website_Successful_url" VALUE=" <input type="hidden" ID="Lite_Website_Fail_url" NAME="Lite_Website_Fail_url" VALUE=" <input type="hidden" ID="Lite_Website_TryLater_url" NAME="Lite_Website_TryLater_url" VALUE=" <input type="hidden" ID="Lite_Website_Error_url" NAME="Lite_Website_Error_url" VALUE=" <!-- Ecml start--> <!-- ShipTo --> <input type="hidden" id="ecom_shipto_postal_name_prefix" name="ecom_shipto_postal_name_prefix" value=""> <input type="hidden" id="ecom_shipto_postal_name_first" name="ecom_shipto_postal_name_first" value=""> <input type="hidden" id="ecom_shipto_postal_name_middle" name="ecom_shipto_postal_name_middle" value=""> <input type="hidden" id="ecom_shipto_postal_name_last" name="ecom_shipto_postal_name_last" value=""> <input type="hidden" id="ecom_shipto_postal_name_suffix" name="ecom_shipto_postal_name_suffix" value=""> <input type="hidden" id="ecom_shipto_postal_street_line1" name="ecom_shipto_postal_street_line1" value=""> <input type="hidden" id="ecom_shipto_postal_street_line2" name="ecom_shipto_postal_street_line2" value=""> <input type="hidden" id="ecom_shipto_postal_street_line3" name="ecom_shipto_postal_street_line3" value=""> <input type="hidden" id="ecom_shipto_postal_city" name="ecom_shipto_postal_city" value=""> <input type="hidden" id="ecom_shipto_postal_stateprov" name="ecom_shipto_postal_stateprov" value=""> <input type="hidden" id="ecom_shipto_postal_postalcode" name="ecom_shipto_postal_postalcode" value=""> <input type="hidden" id="ecom_shipto_postal_countrycode" name="ecom_shipto_postal_countrycode" value=""> <input type="hidden" id="ecom_shipto_telecom_phone_number" name="ecom_shipto_telecom_phone_number" value=""> <input type="hidden" id="ecom_shipto_online_ " name="ecom_shipto_online_ " value=""> <!-- BillTo --> Name: <SELECT id=ecom_billto_postal_name_prefix name=ecom_billto_postal_name_prefix> <option value="mr." >Mr.</option> <option value="mrs." >Mrs.</option> <option value="miss." >Miss.</option> <option value="ms." >Ms.</option> <option value="prof." >Prof.</option> <option value="dr." >Dr.</option> <option value="sir." >Sir.</option> </SELECT> <input type="text" id="ecom_billto_postal_name_first" name="ecom_billto_postal_name_first" value="john" size=8> <input type="hidden" id="ecom_billto_postal_name_middle" name="ecom_billto_postal_name_middle" value=""> <input type="text" id="ecom_billto_postal_name_last" name="ecom_billto_postal_name_last" value="doe" size=10> <input type="hidden" id="ecom_billto_postal_name_suffix" name="ecom_billto_postal_name_suffix" value="iveri"> <input type="hidden" id="ecom_billto_postal_street_line1" name="ecom_billto_postal_street_line1" value=""> <input type="hidden" id="ecom_billto_postal_street_line2" name="ecom_billto_postal_street_line2" value="">

12 <input type="hidden" id="ecom_billto_postal_street_line3" name="ecom_billto_postal_street_line3" value=""> <input type="hidden" id="ecom_billto_postal_city" name="ecom_billto_postal_city" value=""> <input type="hidden" id="ecom_billto_postal_stateprov" name="ecom_billto_postal_stateprov" value=""> <input type="hidden" id="ecom_billto_postal_postalcode" name="ecom_billto_postal_postalcode" value=""> <input type="hidden" id="ecom_billto_postal_countrycode" name="ecom_billto_postal_countrycode" value=""> <input type="hidden" id="ecom_billto_telecom_phone_number" name="ecom_billto_telecom_phone_number" value=" "> <input type="text" id="ecom_billto_online_ " name="ecom_billto_online_ " value="" size=20> <!-- ReceiptTo --> <input type="hidden" id="ecom_receiptto_postal_name_prefix" name="ecom_receiptto_postal_name_prefix" value=""> <input type="hidden" id="ecom_receiptto_postal_name_first" name="ecom_receiptto_postal_name_first" value=""> <input type="hidden" id="ecom_receiptto_postal_name_middle" name="ecom_receiptto_postal_name_middle" value=""> <input type="hidden" id="ecom_receiptto_postal_name_last" name="ecom_receiptto_postal_name_last" value=""> <input type="hidden" id="ecom_receiptto_postal_name_suffix" name="ecom_receiptto_postal_name_suffix" value=""> <input type="hidden" id="ecom_receiptto_postal_street_line1" name="ecom_receiptto_postal_street_line1" value=""> <input type="hidden" id="ecom_receiptto_postal_street_line2" name="ecom_receiptto_postal_street_line2" value=""> <input type="hidden" id="ecom_receiptto_postal_street_line3" name="ecom_receiptto_postal_street_line3" value=""> <input type="hidden" id="ecom_receiptto_postal_city" name="ecom_receiptto_postal_city" value=""> <input type="hidden" id="ecom_receiptto_postal_stateprov" name="ecom_receiptto_postal_stateprov" value=""> <input type="hidden" id="ecom_receiptto_postal_postalcode" name="ecom_receiptto_postal_postalcode" value=""> <input type="hidden" id="ecom_receiptto_postal_countrycode" name="ecom_receiptto_postal_countrycode" value=""> <input type="hidden" id="ecom_receiptto_telecom_phone_number" name="ecom_receiptto_telecom_phone_number" value=""> <input type="hidden" id="ecom_receiptto_online_ " name="ecom_receiptto_online_ " value=""> <!-- Payment --> <input type="hidden" id="ecom_payment_card_name" name="ecom_payment_card_name" value=""> <input type="hidden" id="ecom_payment_card_type" name="ecom_payment_card_type" value=""> Credit Card Number: <input TYPE="text" ID="Ecom_Payment_Card_Number" NAME="Ecom_Payment_Card_Number" VALUE="" size="20"> <small>please type your credit card number without any spaces or hyphens</small> Expiry Date: <input type="hidden" id="ecom_payment_card_startdate_day" name="ecom_payment_card_startdate_day" value="00"> <input type="hidden" id="ecom_payment_card_startdate_month" name="ecom_payment_card_startdate_month" value="07" size=2> <input type="hidden" id="ecom_payment_card_startdate_year" name="ecom_payment_card_startdate_year" value="1999" size=4><br> <input type="hidden" id="ecom_payment_card_expdate_day" name="ecom_payment_card_expdate_day" value="00"> <input type="text" id="ecom_payment_card_expdate_month" name="ecom_payment_card_expdate_month" value="07" size=2> <input type="text" id="ecom_payment_card_expdate_year" name="ecom_payment_card_expdate_year" value="2001" size=4><br> <input type="hidden" id="ecom_payment_card_verification" name="ecom_payment_card_verification" value=""> <input type="hidden" id="ecom_payment_card_protocols" name="ecom_payment_card_protocols" value="iveri"> Invoice: <input TYPE="text" ID="Ecom_ConsumerOrderID" NAME="Ecom_ConsumerOrderID" VALUE="AUTOGENERATE" size="20"> <input type="hidden" id="ecom_schemaversion" name="ecom_schemaversion" value=""> <input type="hidden" id="ecom_transactioncomplete" name="ecom_transactioncomplete" value="false"> <!-- Ecml end--> <! Lite Version--> <input type="hidden" id="lite_version" name="lite_version " value="2.0"> <!-- Version end--> <input TYPE="SUBMIT" NAME="Authorise" VALUE="Authorise"> <input TYPE="RESET" NAME="Clear" VALUE="Clear"> </table> </center> </form> </body> </html>

13 Appendix G: Example URLS All URL s code is the same: <html> <body> <center><h1>success URL</h1></center> <center><h2>form variables</h2></center> <table border=1> Parameter Value <% set Params = Request.Form For Each Pvalue in Params %> <%=Pvalue%> <%=Params(Pvalue)%> <% next %> </table> Your ip : <%=Request.ServerVariables("REMOTE_ADDR")%><br> </body> </html> SuccessfulURL When the transaction was authorised successfully. Lite_Payment_Card_Status = 0 FailURL When the transaction had an unsuccessfully authorised. Eg denied or invalid expiry date. Lite_Payment_Card_Status < 255 other than those below iveri.co.za/examples/iveri/lite/ Fail.asp TryLaterURL If there was a network error. Lite_Payment_Card_Status = 1, 2, 5 or 9 iveri.co.za /Examples/iVeri/Lite/TryLater.asp ErrorURL Any other errors eg. Required variables not set. Lite_Payment_Card_Status = iveri.co.za/examples/iveri/lite/error.asp

14 Appendix H: Example to Client and Merchant to Merchant ClientDetails: Ecom_BillTo_Postal_Name_Prefix+Ecom_BillTo_Postal_Name_First+Ecom_BillTo_Postal_Name_Middle+Ecom_BillTo_Postal_Name_Last Ecom_BillTo_Postal_Street_Line1 Ecom_BillTo_Postal_Street_Line2 Ecom_BillTo_Postal_Street_Line3 Ecom_BillTo_Postal_City Ecom_BillTo_Postal_StateProv Ecom_BillTo_Postal_PostalCode Transaction Index Hash Value DateTime Invoice Number Lite_TransactionRecords_Hash Lite_TransactionIndex : 8/14/99 3:40:38 PM : Ecom_ConsumerOrderID Items Quantity Amount Lite_Order_LineItem_Product_1 Lite_Order_LineItem_Quantity_1 Lite_Order_LineItem_Amount_1 Lite_Order_LineItem_Product_2 Lite_Order_LineItem_Quantity_2 Lite_Order_LineItem_Amount_2 Total Lite_Order_Amount to Client MerchantDetails: Billing details from database DateTime Invoice Number : 8/14/99 3:40:38 PM : Ecom_ConsumerOrderID Items Quantity Amount Lite_Order_LineItem_Product_1 Lite_Order_LineItem_Quantity_1 Lite_Order_LineItem_Amount_1 Lite_Order_LineItem_Product_2 Lite_Order_LineItem_Quantity_2 Lite_Order_LineItem_Amount_2 Total Lite_Order_Amount