Merchant Card Payment Engine

Transcription

1 Merchant Card Payment Engine GATEWAY FREEDOM +BANK AVS INTEGRATION SUPPLEMENT Copyright PayPoint.net 2010 This document contains the proprietary information of PayPoint.net and may not be reproduced in any form or disclosed to any third party without the expressed written permission of a duly authorised representative of PayPoint.net Limited. Registered in England No: VAT Reg. No:

2 PayPoint.net Gateway Freedom +Bank AVS Supplement 30th June 2008 Table of Contents 1 Overview AVS Checks AVS Request Initiation AVS Request Parameters AVS Response Transaction Detail Reporting AVS via Merchant Extranet Support & Disclaimer... 7 Table of Figures Figure 1: AVS Request Parameters Customer and Card Details... 4 Figure 2: AVS Response Parameters... 4 Figure 3: AVS Report screenshot... 6 Figure 4: AVS Terminal... 7 Page 2 of 7

3 1 Overview Many businesses now require the facility to validate their customer addresses and/or check whether the customer is in possession of a valid debit or credit card. This might include verifying delivery addresses before despatching high value goods, or checking consumers for Mobile Phone contract agreements, for example. PayPoint.net AVS (Address Verification Service) is a powerful solution that enables you to confirm that your UK consumer is in possession of a valid debit or credit card, and that it is billed and registered to the address which they provide. Using this service does not require a Merchant Account and no funds are debited from the customer s card. These checks are performed in real time as part of an authorisation request to the Merchant Card Payment Engine (MCPE). The service is designed to automatically validate address, check a card CV2 security code (verifies possession of card) and authorise the card, providing an instant response and a permanent record via the Merchant Extranet. This document assumes you ve read MCPE Gateway Freedom +Bank Integration Guide and Merchant Extranet User Guide. 2 AVS Checks PayPoint.net AVS performs address and card checks against the information supplied by each card issuer. Please note that at present under card scheme rules only UK based card issuers are mandated to perform an AVS check on their cardholders and provide the outcome of such a look up. Therefore this service is only suitable for UK businesses. The AVS check attempts to validate both the full address and the postal code of your customer and provide an outcome for each. The card CV2 (Security Code) is also checked and an outcome provided, with an overall response for card authorisation supplied, indicating validity of the card. 3 AVS Request Initiation The MCPE Gateway Freedom +Bank integration supports application level AVS by making a Pre-Authorisation request via HTTP POST to (see MCPE Gateway Freedom +Bank Integration Guide). As this service is available without a Merchant Account, you will be unable to make any other type of authorisation request. An AVS Request can be initiated as part of a Pre-Authorisation request POST to MCPE, using these mandatory fields: intauthmode Set to 2 to designate it a Pre-Authorisation request, i.e. intauthmode=2 strtranstype Set to PAYMENT even for a Pre-Authorisation, i.e. strtranstype= PAYMENT intinstid ID of your MCPE Freedom +Bank installation, can be found at Account Management > Installations fltapiversion The version of MCPE Freedom +Bank you are using, see page 6 of the Freedom +Bank Integration strdesc A meaningful description for your authorisation request, i.e. strdesc=address+verification+check fltamount A decimal amount to be checked at Authorisation. fltamount=1.0 is sufficient for AVS strcurrency The 3-letter ISO code for the currency of the above, for AVS must be strcurrency=gbp All other card and address details should be supplied as per pages 5 and 6 of the Freedom +Bank Integration Guide, and also as detailed on the following page. The AVS check will take place as part of the card authorisation. Page 3 of 7

4 3.1 AVS Request Parameters The table below details those MCPE Gateway Freedom +Bank fields that must be additionally submitted to ensure that a full Card and Address Verification can take place. Figure 1: AVS Request Parameters Customer and Card Details Field Type(Size) Notes strcartid char(192) Your unique identifier for this authorisation, allows you to reconcile our response. strcardholder char(20) The name of the card holder, as it appears on the card. straddress char(255) The purchaser s postal billing address. strcity char(40) The purchaser s city. strstate char(40) The purchaser s state, province or county. strpostcode char(15) The postal code associated with the address given in straddress. strcountry char(2) The 2-letter ISO code for the purchaser s country. str char(100) An address to which an authorisation receipt can be sent. strcardtype char(8) The type of card - either VISA, DELTA (for VISA DELTA), SOLO, MAESTRO, MC (for MASTERCARD) or UKE (for VISA ELECTRON). strcardnumber char(20) The card number. strstartdate char(4) The optional valid from date that appears on the card, formatted as MMYY. strexpirydate char(4) The expiry date that appears on the card, formatted as MMYY. intcv2 char(4) The security code that appears on the signature strip of the card. strissueno char(2) The issue number of the card, if it has one, including a leading zero if one appears on the card. 4 AVS Response You will be notified of the outcome of your AVS check in the same session as your authorisation request, as part of an MCPE Freedom +Bank authorisation response. See page 8 of the Freedom +Bank Integration Guide for more detail. The AVS Response is included as part of an MCPE Freedom +Bank response: a URL-encoded query string which will include your original submitted values. For AVS checks the key response fields are as follows: intavs (the outcome of the Address Verification check has the customer provided their registered address?) intcv2 (the outcome of the Card CV2 check is the customer in possession of the card?) intstatus (the outcome of the overall Card Authorisation are all details correct and is the card valid?) A simple boolean format response is provided in each case, returning a value of 1 if the customer passes the check and a value of 0 if the customer fails the check. If for any reason the check is not performed, the field will not be returned. Two additional responses provide extra information regarding the outcome of the Address Verification check: stravspostcode (will report the outcome when checking the Postcode submitted) stravsaddress (will report the outcome when checking the Address submitted) Figure 2: AVS Response Parameters Field Type(Size) Notes intavs int(1) The result of the AVS check performed for this transaction. This field will be omitted if the check was not performed. Values: 0=AVS check failed, 1=AVS check passed. intcv2 int(1) The result of the AVS check performed for this transaction. This field will be omitted if the check was not performed. Values: 0=CV2 check failed, 1=CV2 check passed. intstatus int(1) Indicates the outcome of the Card Authorisation. Values: 0 = failed, 1 = passed. stravspostcode str(32) Will report validity of the Postal Code. Values: MATCH, NO MATCH. This field will respond AVS NOT SUPPORTED if the check was not performed. stravsaddress str(32) Will report validity of the Address. Values: MATCH, NO MATCH. This field will respond AVS NOT N SUPPORTED if the check was not performed. 5 Transaction Detail In addition to API-level responses provided by MCPE Freedom +Bank, any AVS check transaction can be reviewed via the Merchant Extranet for audit purposes. The Merchant Extranet is located at Page 4 of 7

5 Any specific Address Verification can be located by Transaction ID using Sales > Transaction Search, whilst individual transactions can be browsed using Sales > Account Statement or Sales > AVS Report (see section 6). Displaying an individual AVS transaction via the Merchant Extranet will provide all the transaction detail, preceded by a summary of the AVS Result, highlighting in green the outcome of the individual checks and the card authorisation. Where any checks have failed or not been performed, this will be indicated in a neutral colour, as below. Full detail of the individual checks are listed in the Fraud Solutions panel, along with other useful information. Page 5 of 7

6 6 Reporting Any AVS transaction can be accessed and viewed using traditional reporting means, including transaction search (Sales > Search) or listed alongside all other transactions in an Account Statement view (Sales > Statements). However, a dedicated AVS report provides a simple colour coded summary of only those transactions in which checks were performed, along with their results. It can be found via Sales > AVS Report. Figure 3: AVS Report screenshot The report highlights the outcome of the Address check, Postcode check, CV2 and card authorisation. It can be re-configured according to a desired date range or other specific criteria. Each transaction can be accessed directly simply by click-through. For businesses which need to retain individual hard-copy proofs for each customer verified via AVS, a unique print function is available with the report output which in one click will print all the results properly presented and divided one per page! Page 6 of 7

7 7 AVS via Merchant Extranet For ease of use and to get you up and running in minutes, you can also perform manual AVS checks via the Merchant Extranet, using the AVS Terminal. The Merchant Extranet is located at The AVS Terminal is located on your account under Sales > AVS Terminal. Here you can simply tap in your customer s card and address details and receive an instant response to screen, as detailed in the previous section. Figure 4: AVS Terminal 8 Support & Disclaimer If you have any questions or you require further information or support, please contact the Merchant Helpdesk at completesupport@paypoint.net or call during office hours GMT on +44 (0) Please do not contact us for any non-technical queries regarding individual results provided by any AVS check. These checks are performed against confidential data held by the card issuers about their card holders. Unfortunately we cannot access or comment on the actual records held. This is a requirement of the Data Protection Act. All checks performed merely validate information which is provided against that which is held by the card issuer. Page 7 of 7