PayHere e-commerce Checkout Page

Transcription

1 PayHere e-commerce Checkout Page Merchant e-solutions October 2012 Version 1.9

2 This publication is for information purposes only and its content does not represent a contract in any form. Furthermore, this publication shall not be deemed to be a warranty of any kind, either express or implied. Merchant e-solutions expressly disclaims, and you expressly waive, any and all warranties, including without limitation those of merchantability and fitness for a particular purpose. Merchant e-solutions reserves the right to alter product specifications without notice. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopy, recording, or any information storage or retrieval system, without Merchant e-solutions permission. Trident Payment Systems Merchant e-solutions 2008 MasterCard is a federally registered trademark of MasterCard International, Inc. Visa is a federally registered trademark of Visa, U.S.A., Inc. ZIP code and ZIP + 4 are federally registered trademarks of the United States Postal Service.

3 Table of Contents Chapter 1 Related Documentation Applicable documents Related documents Document revisions... 2 Chapter 2 Overview Introduction Requirements Back Office Support Transaction Flow... 5 Chapter 3 Integration with the website Request Fields Response Fields Transaction Types Chapter 4 Examples Cascading Style Sheet Fields Cascading Style Sheet Stub HTML Example Extended Example Chapter 5 Web Configuration Overview Hosted Files URLs Security Settings Merchant e-solutions, Inc. 1

4 Chapter 1 Related Documentation 1.1 Applicable documents This document describes in detail the process for configuring Merchant e-solutions MeS Pay Here. 1.2 Related documents All related documents are located at: Most useful to be used with MeS Pay Here are: Name Pay Here HTML Generator MeS Back Office User Guide Definition Template to auto generate HTML code User Guide to Gateway Back Office Functionality 1.3 Document revisions Chapter Action Data 3.2 Update Added response fields. Updated card truncation. 3.3 Update Added Transaction Types DT and AT Merchant e-solutions, Inc. 2

5 Chapter 2 Overview 2.1 Introduction MeS Pay Here is an easy way to add payment processing to any e-commerce web site. MeS Pay Here uses simple HTML to redirect cardholders to the Merchant e-solutions secure payment server. Once on our secure payment page, the cardholder completes the transaction, and is then returned to the merchant s website automatically. The service is simple to deploy, and easy to maintain. It is intended for merchants with low or moderate transaction volume, who need to deploy payment processing quickly and easily. MeS Pay Here enables you to: 1. Deploy payment processing to your website within minutes. 2. Add a logo to our secure checkout form. 3. Customize the feel of the checkout process to match your website with a Cascading Style Sheet. 4. Store cardholder information on Merchant e-solutions PCI compliant servers. 5. Run exception processing through the MeS integrated Back Office. 6. Perform other transaction types, such as Refunds (via transaction ID) and Store Card Tokenization (for use with the Payment Gateway). 2.2 Requirements There are few basic requirements in order to get started: 1. Web Hosting The merchant must have a website which is hosted and publically available. The Cascading Style Sheet and company logo are hosted by the merchant. 2. HTML or Plaintext editor Form elements will need to be added to existing or new HTML, with either a HTML or Plaintext editor. 3. Merchant Account A merchant account is required to begin processing live transactions. 4. Submit Final Amount Only MeS Pay Here will only process the amount sent in the transaction_amount field. Shipping charges, local tax, etc. will need to be accommodated for before the transaction is submitted. 5. SSL Certificate Using your own customized CSS file and/or custom image, it will be necessary to host them on a server with a valid SSL certificate. If they are not stored in this way, some web browsers may display security warnings about mixed content during the checkout process. At this point, MeS does not provide hosting for the merchant s image or CSS file to bypass this requirement Merchant e-solutions, Inc. 3

6 2.3 Back Office Support While the Secure Checkout Page will generally process most of a merchant s transaction volume, it may be necessary to run exception processing or view reports in real time. The Back Office is provided to every user of MeS Pay Here. The website address and login credentials are identical to regular merchant reporting, and are provided upon completion of the merchant application process. The Back Office adds the following functionality to MeS Pay Here: Exception processing: The Back Office offers a wider variety of transaction types. In addition to a sale, a merchant can process Pre-Authorizations, Refunds, Voids, and Offline transactions. View Unsettled Transactions: Merchants can view in real time, transactions which have been processed since the last batch close. View Rejected Transactions: Similar to Unsettled Transactions, a merchant can view rejected or declined transactions, including a description of why the transaction failed. In addition, the administrative section allows for customization of settings such as: Modification of the batch close time. Settings to decline transactions with certain Address Verification results, such as a no ZIP match even if the request receives an authorization code. Settings to decline transactions with certain Card Security Code result, such as P for not processed even if the request receives an authorization code Merchant e-solutions, Inc. 4

7 2.4 Transaction Flow 1. During the first step in the checkout process, a customer is linked from a merchant s e- Commerce website to MeS Pay Here secure checkout page. The link to the Pay Here page can be a text link, image, or both. 2. The transaction amount is displayed and the customer is prompted to enter their card information. Optionally, if the merchant passes all five of these fields to PayHere, a simple processing window is displayed before the customer is directed to the receipt page upon approval. The checkout page is styled by the merchant, giving the appearance to the customer that they are processing on the merchant s website. 3. If there is an error or decline during authorization, the customer is notified but does not leave the Pay Here checkout page. Example decline message. If the sale is approved, the customer is returned to the merchant s website via the specified return_url. Approved transactions have multiple fields posted back to the return_url. See section 3.2 for a full listing. Merchant s hosted return_url page. In the event the cancel button is pressed, they are sent to the cancel_url. At this time, no fields are posted to the cancel_url. Merchant s hosted cancel_url page Merchant e-solutions, Inc. 5

8 Chapter 3 Integration with the website The following are the recommended steps to integrate MeS Pay Here into an e- Commerce website. 1. Obtain a profile ID once the merchant account setup has been completed. 2. Modify or create HTML pages with buy now or checkout links or images. (see section 4.3 for HTML examples). 3. Test the form by processing a sale. Ensure that both return URLs function properly (once tested you can void in the Back Office as this would be a live test). 4. If necessary, run exception processing such as sales, refunds and voids manually in the Back Office. 3.1 Request Fields The following table contains each form field available in the request. Field Name Description Length Required Format Comments profile_id Merchant identifier. 20 Y N Obtained from an MeS VAR form. transaction amount transaction_type The amount of the transaction. Transaction action to perform 12 Y N 1 N A This field contains the final amount the merchant intends to charge the cardholder. D Sale Transaction U Refund Transaction T Store Card Tokenization DT Sale + Tokenization AT Card Verify + Tokenization Default is D (if this field is blank, or not included in the request). css_url cancel_url return_url logo_url URL to a custom style sheet URL to forward upon cancellation URL to forward upon checkout URL for custom logo 64 Y A 64 Y A 64 Y A 64 N A See section 3.3 for details on each transaction type. This is a fully qualified URL to an externally hosted Cascading style sheet. This must be hosted behind a SSL Certificate to avoid mixed content security warnings. This file can be hosted by MeS to avoid this, see section 5.1. This is a fully qualified URL to forward the cardholder when they press the cancel button. This is a fully qualified URL to forward the cardholder when the transaction is successfully approved. This field is a fully qualified URL to a custom logo, which is displayed at the top of our Secure Checkout Form. This must be hosted behind a SSL Certificate to avoid mixed content security warnings. This file can be hosted by MeS to avoid this, see section Merchant e-solutions, Inc. 6

9 footer_url response_url invoice_number currency_code client_reference_number customer_ merchant_ echo_variable cardholder_street_address cardholder_zip cardholder_first_name cardholder_last_name cardholder_phone URL for custom logo URL to POST transaction response details Custom invoice field Used for foreign currencies Custom reference number Cardholder s address Merchant s address Custom echo field Cardholder address Cardholder Zip Code Cardholders first name Cardholders last name Cardholders phone number 64 N 64 N A 21 N A 3 N N 96 N A 32 N A 32 N A 64 N A 32 N A 10 N N 16 N A 16 N A 12 N A This field is a fully qualified URL to a custom logo, which is displayed at the bottom of our Secure Checkout Form. It replaces the Merchant e-solutions logo. This must be hosted behind a SSL Certificate to avoid mixed content security warnings. This file can be hosted by MeS to avoid this, see section 5.1. Once a transaction is approved, the details will be POSTed to the response_url if provided. When used, no data is sent back to the return_url. This is typically used to store transaction responses in a database. If left blank, this field will automatically be filled. Changing the ISO currency code allows acceptance of foreign currencies. Default is 840. This is an extended custom field. Data entered here will show in web reporting. Optionally a receipt to the cardholder. Optionally a copy of the receipt to the merchant. Echo fields are custom fields which are simply passed back via post when the cardholder is returned to the merchant s website. Ex: echo_sessionid The resulting post field would be named: eresp_sessionid Optionally send the cardholders billing address. This field will be auto-populated in the PayHere Billing Address field. Optionally send the cardholders zip code. This field will be autopopulated in the PayHere Billing Zip Code field. Format may be 5 or 9 digit zip. International Zip codes are accepted. This field is only for use on receipts, and the PayHere web report. This field is only for use on receipts, and the PayHere web report. This field is only for use on receipts, and the PayHere web report. ship_to_first_name Recievers first 16 N A This field is only for use on Merchant e-solutions, Inc. 7

10 ship_to_last_name ship_to_address name Recievers last name Recievers address 16 N A 16 N A receipt_header Custom header 128 N A receipt_footer Custom footer 128 N A transaction_id Transaction ID 32 N A card_number card_exp_date cvv2 use_merch_receipt Cardholder account number Cardholder expiry date Cardholder CVV2 code Bypass the receipt page 16 N A 4 N N 4 N N 1 N A transaction_key 32 N A receipts, and the PayHere web report. This field is only for use on receipts, and the PayHere web report. This field is only for use on receipts, and the PayHere web report. Customize the printed and ed receipt headers. Customize the printed and ed receipt footers. Only for use with the refund transaction type. When supplied, the transaction id field is autopopulated. * If supplied, the PayHere Account Number field will be auto-populated with the truncated card number. * If supplied, the PayHere Expiration Date field will be autopopulated. Format: MMYY * If supplied, the PayHere Security Code field will be auto-populated with the masked CVV2. Set to Y in order to skip the hosted receipt page. A 32 character security field used to validate the request. See section 5.4 for more information on security options. * When collecting card data, setting the HTML form action to something other than the MeS PayHere URL may not be PCI Compliant Merchant e-solutions, Inc. 8

11 3.2 Response Fields The following table contains each field available in the response. It is not necessary to use response data, though it can be helpful to store transaction data, or for integration efforts. These fields are sent in an HTTP POST to the merchant s return_url once a transaction has been approved. Note: There are no fields POSTed to the cancel_url. Field Name tran_type tran_amount invoice_number currency_code client_ref_number acct_number exp_date billing_address billing_zip retrieval_ref_number auth_code resp_code resp_text tran_id tran_date eresp_variable card_id cardholder_first_name cardholder_last_name cardholder_street_address cardholder_zip cardholder_phone ship_to_first_name ship_to_last_name ship_to_address Description The transaction type from the original request (see section 3.3 for a full listing). The amount of the transaction. Identical to the request field of the same name. Identical to the request field of the same name (if it was included). Defaults to 840 (USD). Identical to the request field of the same name. Truncated cardholder account number. Cardholder expiration date. Formatting of the date is: mmyy Street address entered by the cardholder during checkout. Zip Code entered by the cardholder during checkout. 12-digit MeS generated reference number Authorization code provided by the issuing bank. At this time, resp_code will always be 000 indicating an approved sale. A textual response for the transaction result. 32-character transaction ID. The transaction ID can be stored and used at a later time to issue refunds or voids in the Back Office without the need to keep sensitive card data. Timestamp of the transaction. Format: MM/DD/YYYY HH:MM:SS AM/PM If you had sent any fields proceeded with echo_, they will be listed in the response with the prefix eresp_. Example request fields: echo_session echo_customer_id Example response fields: eresp_session eresp_customer_id This field is only returned when a transaction type of T is used. The returned value is the token for the card which was stored. Will appear in the response data, if it was passed in the request. Will appear in the response data, if it was passed in the request. Will pass what the cardholder enters for billing information on the hosted page. Will pass what the cardholder enters for billing information on the hosted page. Will appear in the response data, if it was passed in the request. Will appear in the response data, if it was passed in the request. Will appear in the response data, if it was passed in the request. Will appear in the response data, if it was passed in the request Merchant e-solutions, Inc. 9

12 3.3 Transaction Types By modifying the transaction type field, you can alter the functionality of PayHere. Transaction Type Code Description This is the default functionality. The cardholder is presented with a page to enter all relevant card data. Once the user submits, the transaction is authorized. Sale D Optionally, the merchant may elect to pass the card and address data in. The cardholder will not be presented with the card data entry page if the following fields are all passed in: 1. *card_number 2. *card_exp_date 3. *cvv2 4. cardholder_street_address 5. cardholder_zip If all of these fields are present, the cardholder is presented with a processing animation while the authorization automatically happens. *While collecting card data, setting the HTML form action to something other than the MeS PayHere URL will impact PCI Compliance. Refund U The user (the merchant in this case) is presented with a page to enter a transaction ID from a previous sale. When integrating PayHere into a website, it may be advantageous for administrators to take advantage of the refund functionality. By changing the transaction type to U, the only field required to proceed is the transaction ID. The transaction ID may be optionally auto-populated by sending it in the request (in the transaction_id field). Transactions which are refunded same-day result in a void. Transactions which are refunded after settlement result in a credit. Refunds performed in this way are always for 100% of the settled amount. Store Card T PayHere has the ability to store card data on our secure servers, returning a token to the merchant. This is called Tokenization. Because sensitive card data is never on the merchant website, PayHere is a convenient way to minimize PCI requirements. Utilizing a stored token however, will require processing the authorization through the MeS Payment Gateway. PayHere is not designed to process a transaction using a token ID at this time. The card store functionality was specifically designed for a merchant to process cards without the full card number ever existing on their system. The cardholder will not be presented with the card data entry page if the following fields are all passed in: 1. *card_number 2. *card_exp_date If both of these fields are present, the cardholder is presented with a processing animation while the card token is generated. *While collecting card data, setting the HTML form action to something other than the MeS PayHere URL will impact PCI Compliance Merchant e-solutions, Inc. 10

13 Sale & Store Card DT This transaction type combines the functionality of a Sale, with the Tokenization of the Store Card. Tokenization will not happen until an approval is received from the issuing bank. Both the transaction_id (for the Sale) and card_id (for the Store Card) are returned in the response data. Verify & Store Card AT This transaction type will perform a zero-dollar authorization with the issuing bank before a tokenize can occur. Tokenization will not occur unless the issuing bank validates the card. The response field card_id will be the token that should be stored for later use Merchant e-solutions, Inc. 11

14 Chapter 4 Examples 4.1 Cascading Style Sheet Fields The following image shows each of the classes and IDs available to be styled. An Example where each element is styled: 2010 Merchant e-solutions, Inc. 12

15 4.2 Cascading Style Sheet Stub The following CSS stub may be used as a basis to style the Checkout Page. This latest version of the default CSS file can always be downloaded online at #securecheckoutform, #paymentformheader, #paymentinfoheader, #billinginfoheader,.messagebox, #transactioninformation, #transactionresult, #transactionresultheader, #billinginformation, #submitbutton text-align: center; margin-left: auto; margin-right: auto; #securecheckoutform width: 100%; #merchantlogobox, #meslogobox width: 100%; text-align: center; margin-top: 6px; #paymentformheader width: margin-bottom: 600px; 12px; #paymentinfoheader, #billinginfoheader, #transactionresultheader width: 600px; margin-bottom: 4px; text-align: center; border: # px solid; #transactioninformation, #billinginformation, #submitbutton, #transactionresult width: 600px; margin-bottom: 12px; border: 1px solid #666666;.formHeader font-weight: bold; font-size: 12pt; font-family: Verdana, Tahoma, Arial; text-decoration: none font-style: normal; text-align: center;.formsectionheader width: font-weight: font-family: text-align: auto; bold; verdana, helvetica, sans-serif; center;.smalltext 2010 Merchant e-solutions, Inc. 13

16 font-family: font-size: line-height: text-align: Arial, Helvetica, sans-serif; 7pt; 9pt; left;.formlabeltext font-weight: normal; font-size: 8pt; font-family: Verdana, Tahoma, Arial; text-decoration: none; text-align: right; width: 45%; vertical-align: bottom;.formdatatext font-family: Arial, Helvetica, sans-serif; font-weight: normal; font-size: 8pt; text-decoration: none; text-align: left; width: 55%;.buttonText font-weight: font-size: font-family: text-decoration: none; text-align: center; /* Error messages */ normal; 8pt; Verdana, Tahoma, Arial;.messageBox width: 600px; margin-bottom: border: text-align:.errormessage font-family: font-size: font-weight: color:.errortext text-align: font-family: font-size: margin: 12px; # px solid; center; Arial, Helvetica, sans-serif; 12pt; bold; red; left; Arial, Helvetica, sans-serif; 9pt; 8px; /* Receipt Page */ #summarytable #summarymerchantlogo 2010 Merchant e-solutions, Inc. 14

17 #summarycolumnheader background-color: #CCCCCC; margin-top: 6px; font-weight: bold; #summarytabledata.summarylabeltext,.summarydatatext background-color: #DDDDDD;.summaryLabelText width: 30%;.summaryDataText width: 70%; 2010 Merchant e-solutions, Inc. 15

18 4.3 HTML Example The following is a simple example of a form element which submits a transaction to MeS Pay Here. The PayHere HTML Generator can also be used to make simple HTML forms with basic JavaScript validation. It can be found in the PayHere section of our resource site at resources.merchante-solutions.com This example has name-pair values within the cancel and return URL. Any name-pair values submitted in these fields are preserved. This is useful for internal tracking by adding additional fields. The invoice number also is passing the tenant s name for tracking purposes. <form method="post" action=" onsubmit="return dosubmit(this)"> <input type="hidden" name="profile_id" value=" xxxxx000000xx"> <input type="hidden" name="transaction_amount" value=""> <input type="hidden" name="css_url" value=" <input type="hidden" name="cancel_url" value=" <input type="hidden" name="return_url" value=" <input type="hidden" name="logo_url" value=" <input type="hidden" name="invoice_number" value="123456"> <input type="hidden" name="merchant_ " value="your@ .com"> <table> <th colspan="2">billing Information</th> <td>cardholder First Name</td> <td><input type="text" name="cardholder_first_name" size="30" maxlength="40"></td> <td>cardholder Last Name</td> <td><input type="text" name="cardholder_last_name" size="30" maxlength="40"></td> <td>cardholder Phone Number</td> <td><input type="text" name="cardholder_phone" size="30" maxlength="40"></td> <td>cardholder </td> <td><input type="text" name="cardholder_ " size="30" maxlength="40"></td> <td>apartment Number</td> <td><input type="text" name="client_reference_number" size="30" maxlength="96"></td> <th colspan="2">amount</th> <td>&nbsp</td> <td>$<input type="text" name="amount" value=""></td> <td></td> <td><input type="submit" class="formfields" value="pay Rent" name="subbut"></td> </table> </form> 2010 Merchant e-solutions, Inc. 16

19 PayHere HTML Example 4.4 Extended Example The following extends upon the previous rent example. It is a sample of what is capable with the PayHere HTML Generator, and augments the form with JavaScript validation. Here, we verify the dollar amount is valid, have all required fields, and disable the submit button before submitting. <script type="text/javascript"> function dosubmit(thisform) with(thisform) var error = ""; var amtsel = false; //All required fields need to be filled if(cardholder_first_name.value == "" cardholder_first_name.value == null) error = error + "Please fill in the Tenant First Name field.\n"; if(cardholder_last_name.value == "" cardholder_last_name.value == null) error = error + "Please fill in the Tenant Last Name field.\n"; if(client_reference_number.value == "" client_reference_number.value == null) error = error + "Please fill in the Apartment Number field.\n"; //Lets make sure there is an amount, and that its valid. for(x=0; x < amount.length; x++) if(amount[x].checked == true) amtsel = true; if(amount[x].value == "custom") if(isnan(customamount.value) customamount.value == "" customamount.value == null) error = error + "Invalid dollar amount.\n"; else transaction_amount.value = roundnumber(customamount.value, 2); else transaction_amount.value = amount[x].value; if(!amtsel) error = error + "Please choose an amount.\n"; if(error!= "") alert(error); return false; else subbut.disabled = true; return true; 2010 Merchant e-solutions, Inc. 17

20 function roundnumber(num, dec) var result = Math.round(num*Math.pow(10,dec))/Math.pow(10,dec); return result; </script> <style type="text/css" media="screen"> #payheretable th border: 1px solid #666666; background-color: #AAAAAA;.req color: red; </style> <form method="post" action=" onsubmit="return dosubmit(this)"> <input type="hidden" name="profile_id" value=" xxxx000000xx"> <input type="hidden" name="transaction_amount" value=""> <input type="hidden" name="css_url" value=" <input type="hidden" name="cancel_url" value=" <input type="hidden" name="return_url" value=" <input type="hidden" name="logo_url" value=" <input type="hidden" name="invoice_number" value="123456"> <input type="hidden" name="merchant_ " value="your@address.com"> <table id="payheretable"> <th colspan="2">billing Information</th> <td><span class="req">*</span> Tenant First Name</td> <td><input type="text" name="cardholder_first_name" size="30" maxlength="40"></td> <td><span class="req">*</span> Tenant Last Name</td> <td><input type="text" name="cardholder_last_name" size="30" maxlength="40"></td> <td>apartment Phone Number</td> <td><input type="text" name="cardholder_phone" size="30" maxlength="40"></td> <td> Address</td> <td><input type="text" name="cardholder_ " size="30" maxlength="40"></td> <td><span class="req">*</span> Apartment Number</td> <td><input type="text" name="client_reference_number" size="30" maxlength="96"></td> <th colspan="2">amount</th> <td><span class="req">*</span> Select Amount</td> <td><input type="radio" name="amount" value="500.00">$ (single bedroom)</td> <td></td> <td><input type="radio" name="amount" value="750.00">$ (two bedroom)</td> <td></td> <td><input type="radio" name="amount" value=" ">$ (suite)</td> <td></td> <td><input type="radio" name="amount" value="custom">$ <input type="text" name="customamount"></td> <td><span class="req">*</span> Required Fields</td> <td><input type="submit" class="formfields" value="pay Rent" name="subbut"></td> </table> 2010 Merchant e-solutions, Inc. 18

21 </form> Extended Example 2, Illustrating error checking Extended Example Form 2010 Merchant e-solutions, Inc. 19

22 Chapter 5 Web Configuration 5.1 Overview Several key fields can be set via a merchant login at The PayHere Web Configuration allows some request fields to be replaced with links or files hosted by Merchant e-solutions. This makes the resulting request smaller (fewer fields to send, more secure (the response_url can be hidden), and easier to use (hosting the CSS file and images relieves the burden of requiring a SSL certificate). Additionally, the security section offers advanced integrations the ability to secure incoming and outgoing requests. To access these features from the main menu, select PayHere Configuration. If multiple PayHere profiles exist on a merchant account, a drop-down will appear, prompting the user to choose which to edit. 5.2 Hosted Files There are three files which may be hosted by Merchant e-solutions. These are the header logo, the footer logo, and the CSS; the Cascading Style Sheet used to style the hosted page. Selecting update will display a Choose File button. Once chosen, the file is uploaded and stored; it will then be used as the header, footer, or stylesheet for the hosted page. Once uploaded and after the profile is saved, the delete option will appear. This allows for removal of the hosted file. Supported image formats for the header and footer logo include PNG, GIF, and JPEG. If the header, footer or Stylesheet are set via the Web Configuration, the corresponding parameters are ignored if passed in. For example, if the header, footer, and stylesheet have been uploaded, the following request fields will be ignored: logo_url, footer_url, css_url. This is by design, and is for security purposes. 5.3 URLs Three of the URLs typically passed in during the request may also be configured via the Web Configuration. These include the cancel_url, return_url, and response_url. Once these URLs are set in the Web Configuration, they do not need to be passed in each request to PayHere. This is mostly for convenience; however the response_url can be hidden this way, as layer of security to prevent abuse Merchant e-solutions, Inc. 20

23 5.4 Security Settings The last section in the Web Configuration is the security settings. These settings are intended for advanced integrations of PayHere, and will require a server-side programming language to implement properly, such as PHP, JSP, ASP, etc. The Security Code is a password used to secure requests to PayHere. When a Security Code is set, requests which do not validate will be redirected to the cancel_url appended with the name-pair value resp_text=invalid_tran_key. To validate a request, create an MD5 hash of the following fields (in this order): Profile Key (A security code generated by MeS) Security Code Transaction Amount The result of this MD5 hash then needs to be sent in the field transaction_key. PHP Example <?php $tran_key = md5("eslvinonbtrsmxzzqaprppqqwvvjaggi"."test123"."0.03")?> <input type="text" name="transaction_key" value="<?php echo($tran_key);?>"> Lastly, there are two fields: Resp HTTP Username and Password. These are used when sending the response data to the response_url. If present, standard HTTP authentication will be used when POSTing this data. Reading this data will depend on the programming language used, however the first row of the header will be the word BASIC followed by the username and password base64 encoded, separated by a colon. Ex. Header row 1: BASIC dgvzddp0zxn0 Ex. dgvzddp0zxn0 Base64 decoded: test:test The following PHP function will return the decoded authentication pair (test:test in the above example). PHP Example for retrieving Apache headers function gethttpcredentials() $headers = apache_request_headers(); foreach ($headers as $header => $value) if(strtolower(substr($value, 0, 5)) == 'basic') return base64_decode(substr($value, 6)); 2010 Merchant e-solutions, Inc. 21