Barclaycard SmartPay. Hosted Payment Page Integration Guide. Version 3.0 released April 2012

Size: px
Start display at page:

Download "Barclaycard SmartPay. Hosted Payment Page Integration Guide. Version 3.0 released April 2012"

Transcription

1 Barclaycard SmartPay Hosted Payment Page Integration Guide Version 3.0 released April 2012

2 DOC Version Control Version No. Date Issued Reason for Change 1.0 July 2010 Initial Document 2.0 February 2012 Update 3.0 May 2012 Update COPYRIGHT NOTICE No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means electronic or mechanical, including photocopying and recording, for any purpose, without the prior written permission of Product Development, Barclaycard Global Payment Acceptance, Barclays Bank PLC

3 Contents Purpose of this Document... 5 Intended Audience... 5 Contacting us... 5 Documentation & Code Examples... 5 Glossary... 6 How to use this Document... 7 Payment Process... 8 Introduction...8 Payment Process...8 Payment Process Steps 1 to Step 1 Order Ready Step 2 String Encryption What is the HMAC Key? Step 3 Passing the customer to the Payment Pages Explanation of the Session Fields GET (redirect) vs POST Using an iframe Step 4 - The Payment Pages Step 5 - Process Payment Step 6 - Notification Step 7. Payment Completion Step 8 - Return to Merchant Website Address Verification Service (AVS) Collect Address and Pre-populate the Address on the HPP Modifications Notifications Skins What is a Skin? HPP - Oneclick Payments Setting up the Payment HPP - Recurring Payments Creating a Recurring Contract Setting up the Payment Submitting Recurring Payments Recurring paymentrequest Payments Recurring paymentrequest response Disable a Recurring Contract Disable Response Supported Payment Methods HPP - Tokenisation Tokenising a Payment using the SmartPay Hosted Payment Pages Downloading Reports... 40

4 Payment Methods Passing Payment Methods with Shopper Adding Payment Methods Set Order of Payment Methods Activate/Disable Payment Method Set Payment Method Options Minimum Quantity Maximum Quantity Adding Costs or discounts Payment Methods - PayPal...44 Moving from Test to Live Appendix A Test and Live URL s URL s for test URL s for Live Appendix B Computing the HMAC Payment Set-up Payment Result Example HTML Post Form Appendix C Format Standards Appendix D Currency Codes Appendix E Payment Methods Appendix F Trouble Shooting Merchant signature was not valid Merchant account NULL or not configured in Skin Merchant account [merchant account name] not configured in Skin: Billing address incomplete: Session validity is in the past: CurrencyCode value missing Merchant Reference is missing Recurring is not enabled The server sent HTTP status code 401: Unauthorized Problem Displaying Page Appendix G Payment Page HTML Skeleton Appendix H HTML Structure Appendix I Reset.css... 60

5 Purpose of this Document This document is designed to provide internet merchants with the relevant instructions and HTML code to integrate Barclaycard SmartPay into their storefront. It also provides details on how Barclaycard SmartPay handles transactions that can be authenticated using Internet Authentication. Intended Audience This document is intended for use by: Merchants performing their own integrations Web developers working on behalf of merchants Merchant Development Partners It is recommended that the merchant responsible for the merchant account reviews this document to ensure appropriate configuration of the account. A thorough knowledge of HTML and web-based scripting language is required for successful integration of Barclaycard SmartPay. You must ensure that you have the necessary experience and required skill sets in order to avoid problems with integration. If you do have any queries or questions whilst reading this document then please feel free to contact us, our contact details can be found below. Contacting us Contact the support team via at: Support.SmartPay@barclaycard.co.uk Alternatively you can call the support team on the following: From the UK * Outside the UK * Support hours: Monday to Friday: 8.00 to 18:00 GMT * Calls may be monitored and/or recorded to maintain high levels of security and quality of service Documentation & Code Examples This document and others which can help you with you integration and store setup can be found at the support website. Please refer to your set up .

6 Glossary Term AVS CSC GBP HMAC HPP HTML HTTP HTTPS ISO RSS MasterCard SecureCode Barclaycard SmartPay SOAP SSL URL VbV Definition Address Verification Service Card Security Code also known as CV2, CVV2, CID and CVN Great British Pound (Sterling) Hash Message Authentication Code a method of encrypting data Hosted Payment Page Barclaycard SmartPay s payment pages which take the payment for you Hypertext Mark up Language language used to construct web pages HyperText Transfer Protocol the protocol used most often to transfer information from World Wide Web servers to browsers. Also called HyperText Transport Protocol HyperText Transfer Protocol, Secure a version of http for secure transactions International Standards Organisation a recognised protocol for transaction transmission Really Simple Syndication or Rich Site Summary MasterCard s process to authenticate the customer as the cardholder during online purchases Barclaycards secure payment service Simple Object Access Protocol a generic message structure used by programming languages to communicate data in a standard format. Secure Sockets Layer a protocol designed to provide secure communications on the internet Uniform Resource Locator an internet address Verified by Visa. A Visa initiative to authenticate the customer as the cardholder during online purchases

7 How to use this Document This document combines essential integration and user information, plus tips on how to get the most from Barclaycard SmartPay. For ease of use, it is indexed by section, topic and product as shown below: Section A Topic Recurring Payments This type of header will appear at the start of each new subject. There are 9 Sections to this document. The Topic provides information on what can be performed by Barclaycard SmartPay within the section. You can mix and match the topics within the sections to tailor this user guide to your specific needs. Section Content Description A Payment Process How the payment pages can fit into the purchase process. B Address Verification Service (AVS) How to pass and pre-populate customer address details on the hosted payment pages. C Modifications How to perform actions on a transaction via SOAP. D Notifications The format and values returned in response to the transaction. E Skins Changing the look and feel of the Hosted Payment Pages. F Remember Shopper Details Introduces CSC-only functionality, for the use of repeat shoppers. G Recurring Payments How to perform and manage recurring transactions. H Downloading Reports Explaining how to download reports which have been run by the Backoffice. I Payment Methods Managing the payment methods available. J Appendix Test and Live URL s, Computing the HMAC, Format Standards, Currency Codes, Payment Methods, Payment Page HTML Skeleton, HTML Structure and Reset.css.

8 Section A Topic Payment Process Introduction The Barclaycard SmartPay Hosted Payment Pages (HPP) provides a flexible, secure and easy way to allow customers to pay for goods or services on a merchant s website. When a customer needs to complete an order they will be transferred from the merchant website to the HPP where the customer will perform the payment. The customer is then directed back to the merchant website with the result of the payment. In order to integrate seamlessly into a merchant website, the HPP is customisable in look and feel. We refer to a set of look-and-feel customisations as a Skin which consists of a set of custom HTML fragments, images and CSS style sheets, which form the template to displaying the hosted payment pages. Please see the Skin section for more detail on how to create and manage your skin. Payment Process The following diagram s illustrate how the website could be integrated with Barclaycard SmartPay HPP s and the steps involved, in the following sections we will explain each of these steps. There are 2 versions of the Barclaycard SmartPay Hosted Payment Page (HPP): Single Page HPP - Multi Page HPP - which attempts to host the payment process on a single page. which attempts to host the payment process on 2 or 3 pages depending on the payment method. Please see Step 4 of Payment Process Steps 1 to 8 for an explanation of how to integrate your preferred option. Note: Please see following page for flow diagram of the process.

9 One Page Payment Process Diagram: Mulit Page Payment Process Diagram:

10 Section Topic A Payment Process Steps 1 to 8 Step 1 Order Ready The customer visits your website/shopping cart and adds to the basket the items or services they wish to purchase, typically you website will then store this information in an orders database associated with a unique order reference number which your system creates that can be passed over with the customer to the hosted payment page. This will help to identify the customer when returning to your website at the end of the process. Step 2 String Encryption The hand-off between your website and the HPP hosted payment page is achieved by setting up a payment session for the customer and adding this data to the HTML form parameters before you transfer the customer with this data to the HPP. To avoid the possibility of a customer tampering with the payment session data, you will cryptographically sign the data using a HMAC key. Note - We provide code examples in common programming languages (please see the Documentation and Code Examples link at the start of this document). What is the HMAC Key? The HMAC key is the merchant s shared secret between your integration and Barclaycard SmartPay, the HMAC key is an alphanumeric value that the merchant sets and it is used by your integration to encrypt the string of details for the payment which you then pass the Barclaycard SmartPay, we then use the same HMAC key to compare the string passed with the values contained to check they have not been tampered with. Step 3 Passing the customer to the Payment Pages Once you have created your encrypted string containing the payment session data using the HMAC this becomes your merchantsig (see Appendix B for more detail on the computing the HMAC). Your website will pass this over to the HPP using a standard HTML form. The following is an example of how the payment session may look if you have a customer who has to pay a total of GBP for an order which is known to you in your Backoffice systems as Internet Order The goods will be shipped to the customer before or on October 20th, 2007 and you want to present the text 1 Digital Camera as an order summary on the payment review page. The customer is using (British) English as their language. The Skin name you will be using is 4aD37dJA and the (financial) account you have with us is TestMerchant. Furthermore, you want this payment offer to expire today at 11 am. (assuming it is October 11th, :30 am. In the UTC time zone). Test Hosted Payment Pages (Multiple): - Hosted Payment Pages (Single) -

11 <input type="hidden" name="merchantreference" value="internet Order 12345" /> <input type="hidden" name="paymentamount" value="10000" /> <input type="hidden" name="currencycode" value="gbp" /> <input type="hidden" name="shipbeforedate" value=" " /> <input type="hidden" name="skincode" value="4ad37dja" /> <input type="hidden" name="merchantaccount" value="testmerchant" /> <input type="hidden" name="shopperlocale" value="en_gb" /> <input type="hidden" name="orderdata" value="h4siaaaaaaaaalmpsoplckssyswvlvziz89pkvzizetrke4tkstmti3w4+wy0s+waw DOGUCXJgAAAA==" /> <input type="hidden" name="sessionvalidity" value=" t11:00:00z" /> <input type="hidden" name="merchantsig" value="33syartfsxd47jexzoleyz0j3pg=" />

12 Explanation of the Session Fields There are a number of mandatory field values which must be passed with the customer to the payment pages. Please find in the following an explanation about the contents of these fields. Mandatory Field Names Description merchantreference This reference will be used in all communication to you about the status of the payment. Although it is a good idea to make sure it is unique, this is not a requirement. paymentamount The payment amount is specified in minor units (without decimal separator). Thus (GBP) is specified as and EUR is specified as Most currencies are like this and have 100 minor units to a major unit (e.g. pennies to the Pound, cents to the Euro). However the Japanese YEN is an exception and doesn't have any minor units; thus 1001 YEN is specified as currencycode The three-letter capitalised ISO currency code to pay in. For the full list of currency codes supported by Barclaycard SmartPay, please refer to the appendix. shipbeforedate The date by which the goods or services specified in the order must be shipped or rendered. (YYYY-MM-DD format, see the appendix for more detail) skincode The Skin to be used. You can have more than one Skin associated with the account if you require a different branding. merchantaccount The merchant account you want to process this payment with (This will be provided to you in your SmartPay set up documentation). merchantsig The signature in Base64 encoded format. The signature is generated by encrypting the values of a number of the payment session fields and computing the HMAC over this using the shared secret (configured in the Skin). (See the Appendix for details on computing the signature). We provide code examples in common programming languages for this (please see the Documentation and Code Examples link at the start of this document). sessionvalidity The final time by which a payment needs to have been made. This is especially useful for tickets/reservations, where you want to lock the item for sale for only a short time and payments made after this time would lead to extra costs and administrative hassle. (YYYY-MM-DDThh:mm:ssTZD format, see the appendix for more detail. Note: TZD is the Time Zone Designator which can either be the letter 'Z' or +hh:mm or -hh:mm.)

13 Mandatory for ONECLICK or RECURRING transactions Only shopper The address of the shopper. This is an optional field, but if available it is useful to specify it as there is used in a velocity fraud check. This is not optional if you are creating an ONECLICK of RECURRING contract. shopperreference An id that refers uniquely to the shopper (e.g. a customer id in a shopping cart system). This is an optional field, but useful as we can do velocity fraud checking on it. Note - that any transaction scoring 100 or more will automatically be declined, therefore it is not advised to have this value set to 100 or more as this will mean all your transactions will be blocked. This is not optional if you are creating an ONECLICK of RECURRING contract. recurringcontract The value of the recurringcontract parameter above must be inserted into the signature string over which the HMAC is computed between the shopperreference and allowedmethods. e.g.: + sessionvalidity + shopper + shopperreference + recurringcontract + allowedmethods The payment will proceed as usual and if the result is a successful authorisation, a recurring contract will automatically be created. We show you how to get the contract reference in the following section. If you are also using the CSC-only functionality, then the value of the recurringcontract field should be RECURRING,ONECLICK. Note - Shoppers are uniquely identified using the shopperreference parameter; it is most important that shoppers are securely logged in on your website and that the shopperreference parameter cannot be modified by the shopper. There are a number of optional field values which can be passed with the customer to the payment pages. Please find in the following an explanation about the contents of these fields. Optional Field Names Description shopperlocale A combination of language code and country code to specify the language used in the session (e.g. en_gb for (British) English). Use just the language code when the country distinction is not required (i.e. fr, not fr_fr ). Default locale is en_gb.

14 orderdata OrderData is a fragment of HTML which will be displayed to the customer on a review payment page just before final confirmation of the payment. In order to guarantee correct transmission of this data, including the sending of non-western characters (e.g. the Japanese or Cyrillic character sets), the data is compressed and encoded in the session (GZIP compressed and Base64 encoded). Note: We provide code examples in common programming languages for this (please see the Documentation and Code Examples link at the start of this document). PLEASE NOTE: orderdata cannot be displayed on the HPP if the merchantaccount is set up for MOTO payments. merchantreturndata (maximum length 128 characters) This field will be passed back on the return URL when the shopper completes the payment and returns to your shop. This can be used to pass through a session id if needed. Note Due to how some payment methods work the merchantreturndata may not be returned. This can especially effect ideal payments where the parameter can make the string to the issuer to long causing the payment to fail. To help avoid this try to reduce the length of the merchantreturndata to make it as concise as possible. countrycode By default, the payment methods offered to the shopper are filtered based on the country which the IP address of the shopper is mapped to. This prevents a UK shopper from being presented with a German payment method like ELV. This IP-to-country mapping is not 100% accurate, so if you have already established the country of the shopper you may set it explicitly using the countrycode parameter. Note that this parameter is optional and is not used as part of the signing data. (ISO alpha-2 format, see the Appendix for more detail) allowedmethods A comma-separated list of allowed payment methods. This acts as a filter on the payment methods which would normally be available in the Skin. Only the ones in this list will be shown (if available); all others will be ignored. No spaces are allowed. Please refer to section H Payment Methods in this document for more detail. Note that this parameter is optional. If the parameter is not used, the value for this field for the merchantsignature computing is an empty String. offset This numeric value will be added to the fraud score of the transaction, this enables you to use positive or negative values to either make the transaction less or more likely to be stopped by the fraud scoring.

15 blockedmethods A comma-separated list of payment methods which should not be made available. This acts as a filter on the payment methods which would normally be available in the Skin. The methods listed will be removed from the list of available payment methods. No spaces are allowed. Please refer to section H Payment Methods in this document for more detail Note that this parameter is optional. If the parameter is not used, the value for this field for the merchantsignature computing is an empty String. shopperstatement Some acquirers support a variable shopper statement. To submit a variable shopper statement you can set the shopperstatement field in the payment request. The shopperstatement field may not exceeds 135 characters and can only contain the characters: a-za- Z0-9.,-? Note that if the shopperstatement field is set, it is also included in the HMAC computation. resurl To override the Skin's result URL, specify the URL in the parameter resurl in the payment session. The resurl parameter does not need to be included in the signature. Note Due to how some payment methods work the resurl may not work as desired. This can especially effect ideal payments where the parameter can make the string to the issuer too long causing the payment to fail, to help avoid this use the shortest resurl needed. skipselection If you only intend to accept one payment method (e.g Visa), this allows you to automatically load the page that collects the customers payment information. If you supply this value you must ensure that your skin has only one payment method enabled. The value you must supply for this parameter is true.

16 GET (redirect) vs POST When passing the customer and their details to the HPP you can use a HTML form action of GET (redirect) or POST. If you use the GET (redirect) method please keep in mind the following: Not all browsers are capable of handling large URLs. Some browsers have a limited URL length which should not exceed 2083 characters. It is your own responsibility to make sure this limit is not exceeded. All parameters and their values should be URL-encoded using UTF-8 character encoding. The following is an example of the string which could be used in the redirect using the example values previously mentioned. Order 12345&paymentAmount=10000&currencyCode=GBP&shipBeforeDate= & skincode=4ad37dja&merchantaccount=testmerchant&shopperlocale=en_gb& sessionvalidity= t11%3a00%3a00%2b01%3a00& shopperreference=sr &merchantsig=33syartfsxd47jexzoleyz0j3pg= Using an iframe We do not support displaying the Hosted Payment Pages in an iframe. The use of iframes brings along known usability, security and cross-browser issues. However if you do choose to put the Hosted Payment Pages in an iframe, please consider the following: Some (redirect) payment methods like ideal do not permit their pages to be viewed in an iframe and will break out of the iframe. Other redirect payment methods will assume more available screen space than your iframe permits. Using an iframe could affect the Internet Authentication (MasterCard SecureCode/ Verified by Visa) window supplied by the card issuer, affecting how the page is displayed or possibly stopping the payment. You should also prepare to handle the difference in behaviour for the payment result URL, since when the payment completes the customer may not be in an iframe any more. Using an iframe may affect the shopper s cookie policy on their web browser, these are used by the Hosted Payment Page. Using an iframe means that the browser may impose restrictions under which conditions cookies are allowed to be set within the iframe. While there are workarounds for getting cookies accepted in the default configuration for most browsers, the shopper may have configured a more restrictive policy. The most common problem is with the Safari (Apple) and Chrome (Google) browsers which require (by default) that the loading of the page in the iframe must user initiated. This means that first the iframe needs to be loaded with a page hosted at the parent domain. Secondly, on this page the user needs to actively click on a button submitting the redirect to the Hosted Payment Pages. Note - The use of an iframe with the Hosted Payment Page is not recommended and as so we cannot guarantee that all payment methods will work when using an iframe, nor that the behaviour of a payment method will stay the same. Furthermore, the exact operation of a (redirect) payment method can differ between the Test environment and the Live environment.

17 Step 4 - The Payment Pages Single or Multi page Merchants can choose between two different payment flows; You control which method you wish to use by modifying the URL where you direct the cardholder to. The multi-page flow splits the payment process into two or three steps (depending on the payment method) and the single page flow (One Page Payment) which attempts to host the payment process on a single page. The multi-page flow does not require JavaScript. This makes it ideally suited for maximum compatibility with a wide range of browsers and devices; including mobile phones and PDAs. The single page (One Page Payment) flow on the other hand uses JavaScript to manipulate the page content and is suited for use on modern browsers or when page complexity is not an issue and there is enough screen estate. Hosted Payment Pages (Multiple) Hosted Payment Pages (Single) HPP Test URL s Hosted Payment Pages (Multiple) Hosted Payment Pages (Single) HPP Live URL s

18 Step 5 - Process Payment Once the customer has selected their payment method and entered their details they are processed by Barclaycard SmartPay engine and checked against the active fraud rules in the Fraud Control section in the merchant s Backoffice settings. Step 6 - Notification Once the transaction has been approved or declined, a response is returned to a notification handling script on the merchant s website. This script would normally read in the response returned and then use the Merchant Reference which was passed over with the customer to the payment page, enabling the merchant website to update the Order Databases with the result of the transaction, triggering the merchant order fulfilment process. In the Notification the following fields are returned:- Field Name live Description Notifying if the transaction was put through the Live or Test system. eventcode The event type of the notification. For example AUTHORISATION for a standard transaction via the HPP. pspreference The unique reference created by Barclaycard SmartPay to identify the transaction. originalreference This is empty unless you are using a modification request to change a previous transaction, where this will contain the reference of the original transaction you have sent the request for. merchantreference This reference is assigned by you or your website and passed over with the customer to the payment page and is used to identify the customer and help match the transaction to your order database. merchantaccountcode The merchant account the payment was processed with. eventdate The time the event was generated. success Whether or not the event succeeded (true/false). paymentmethod How the transaction was paid for, e.g. Visa. operations The operations which can be performed on this transaction

19 reason Text field which can contain an informational message. Please see below for possible values. - Refused. - FRAUD. - Referral. - 3d-secure: Authentication failed. - REFUSED. - Issuer Unavailable. - Invalid Card Number. - Acquirer Error. - Expired Card. - Transaction not found. - Insufficient balance on payment. - Invalid Amount. - Recurring transaction failed. - Recurring contract already exists. - Blocked Card. - ERROR. - Original transaction no longer open. - Recurring initial payment not available. The format of which is as follows: Reason appears: 97150:1111:12/2012" which is: "AUTH CODE:LAST 4 DIGITS:EXPIRY DATE" amount The amount (if relevant) associated with the payment or modification. This consists of a currency and a value which is the amount in minor. In case of HTTP POST notifications you will instead receive currency and value More details around the notification and how to handle this response can be found in the Notification section of this document. Step 7. Payment Completion When a customer has completed the payment, they are directed to a default result page. You can specify your own result page in the Skin which will be used instead of the default. We will append parameters to the resulturl that you have specified in your skin configuration to inform you of the status of the payment. Just as you cryptographically signed the payment session when sending the customer to us, we will use the same shared secret to sign the data we return to you. Therefore you can check that the data has not been tampered with. An example of such a result request for the example above is (assumes you set your resulturl to D37dJA&shopperLocale=en_GB&authResult=AUTHORISED&pspReference= &merchantSig=CPb2cObMxmIIE0khO8WhEYyKDJs%3D

20 The parameters passed back are contained in the table below: Field Name Description authresult AUTHORISED Authorisation was successfully completed REFUSED Authorisation was unsuccessful, Declined by issuer CANCELLED Shopper cancelled payment or used back button on initial page to return to merchants website PENDING Final status of the payment could not be established at the time, this can be due to the payment method (e.g PayPal) or requiring the shopper to take further action. ERROR An error occurred during the payment process pspreference The reference Barclaycard SmartPay assigned to the payment. This is globally unique and must be used when communicating about this payment to us. (For PENDING, ERROR or CANCELLED results the pspreference is not yet be known and is therefore empty) merchantreference This is the reference your shopping cart/integration assigned to the original payment skincode - The Skin used merchantsig The signature computed over the above values in Base64 encoded format. (See the Appendix for details on computing the signature) paymentmethod The payment method used, may be empty if authresult is CANCELLED shopperlocale Useful if you don't have the customer's language in-session merchantreturndata If set in the payment session setup, the value will be passed back This information is useful in constructing a custom result page, and can integrate smoothly with the customer's session on your server. Although it is best practice to use a fixed result URL, specified in the Skin, there are situations where it is desirable to set the result URL on a per-payment basis. To override the Skin's result URL, specify the URL in the parameter resurl in the payment session. Please see Step 3 for further details. The resurl parameter does not need to be included in the signature. Note Due to how some payment methods work the resurl may not work as desired. This can especially effect ideal payments where the parameter can make the string to the issuer too long causing the payment to fail. To help avoid this use the shortest resurl needed.

21 Step 8 - Return to Merchant Website If you have used the result page hosted by Barclaycard SmartPay the customer will still be on the hosted payment pages, to return them to your website in you Skin configuration you can specify a continue to URL value this will then place a continue button on the Result URL page, which when selected will direct the customer to your specified continue to URL. Please Note: If you do not specify a ResultURL the order information detailed in step in step 7 will not be sent to your Continue-toURL.

22 Section B Topic Address Verification Service (AVS) Address Verification System (AVS) is a security feature that verifies the billing address of the customer. It does so by comparing the numeric portions of the customer's registered billing address to those entered by the shopper. AVS is only supported on a limited set of acquiring connections and only for a limited set of countries (United States, Great Britain and Canada for MasterCard and Visa) and card types. Please check with support what AVS options are supported for your account. You can choose to have the payment pages collect the billing address and/or pre-populate these values from your own system. If you wish to pre-populate these fields you can add them to the payment session as follows. Field Name billingaddress.street Description The street name billingaddress.housenumberorname The house number (or name) billingaddress.city The city billingaddress.postalcode The postal/zip code billingaddress.stateorprovince The state or province billingaddress.country The country. (ISO alpha-2 format, see the appendix for more details) billingaddresssig A separate merchant signature is required over these fields. The protocol and shared secret is the same as the normal merchant signature, but over the following fields: billingaddress.street + billingaddress.housenumberorname + billingaddress.city + billingaddress.postalcode + billingaddress.stateorprovince + billingaddress.country You can specify whether the shopper is allowed to view and/or modify these personal details. For this the billingaddresstype can be specified. (Please see Collect Address and Prepopulate the Address on the HPP for more information)

23 Please note that the billingaddresstype field is part of the merchant Signature (see the Appendix for Computing the HMAC). billingaddresstype Value Description Not supplied modifiable / visible 1 fixed / visible 2 fixed / invisible If you want to have the shopper enter the billing address on the payment pages, you can add the billing address data entry fields on the Skin edit page. In this case you should not supply a billingaddresstype so that the fields are modifiable.

24 Section B Topic Collect Address and Pre-populate the Address on the HPP Allow the cardholder to input their address on the HPP To add address fields to the hosted payment pages simply select Billing Address Fields (AVS) within the configuration page of your chosen Skin. (See below). Pre-populating the HPP with the cardholder address If you wish to pre-populate the payment screen with the cardholders address information you have collected on your own website, you will need ensure that you supply the appropriate HTML form parameters in the form you use to re-direct to the Barclaycard SmartPay Hosted Payment Page. You will also need to ensure that supply an additional addresshmacdata string and also a separate billingaddresssig. For example your PHP script would be modified to include the following: //GZIP and base64 encode the orderdata $orderdata = base64_encode(gzencode($orderdataraw)); $housenumberorname = $housenum; $city = $town; $postalcode = $pcode; $stateorprovince = $state; $billingaddresstype = $addtype; // concatenate all the data needed to calculate the HMAC-string in the correct order $hmacdata = $paymentamount. $currencycode. $shipbeforedate. $merchantreference. $skincode. $merchantaccount. $sessionvalidity. $shopper . $shopperreference. $billingaddresstype; $addresshmacdata = $street. $housenumberorname. $city. $postalcode. $stateorprovince. $country; // base64 encode the binary result of the HMAC computation. If you use a PHP version < you // you may need to use a different HMAC implementation. Please refer to "Computing the HMAC in PHP"

25 $merchantsig = base64_encode(hash_hmac('sha1',$hmacdata,$sharedsecret,true)); $billingaddresssig = base64_encode(hash_hmac('sha1',$addresshmacdata,$sharedsecret,true)); // Include in the HTML form with mandatory form parameters: <input type="hidden" name="billingaddresssig" value="<?php print $billingaddresssig?>" /> <input type="hidden" name="billingaddresstype" value="1" /> <input type="hidden" name="billingaddress.street" value="<?php print $street?>" /> <input type="hidden" name="billingaddress.housenumberorname" value="<?php print $housenum?>" /> <input type="hidden" name="billingaddress.city" value="<?php print $town?>" /> <input type="hidden" name="billingaddress.postalcode" value="<?php print $pcode?>" /> <input type="hidden" name="billingaddress.stateorprovince" value="<?php print $state?>" /> <input type="hidden" name="billingaddress.country" value="<?php print $country?>" />

26 Section C Topic Modifications It is possible to perform modifications using your account on the Barclaycard SmartPay Backoffice. It is generally a good idea to automate this if you are processing more than a handful of payments daily. For this we offer a SOAP web service which accepts the modification requests from your Backoffice systems. The modification types include: capture refund cancel cancelorrefund To submit modification messages, you must supply HTTP basic authentication credentials (username/password). The username you should use is ws@company.yourcompanyaccount, you can set the password for this user in the Merchant Backoffice (under settings -> users ). For more information please refer to the SmartPay Modifications Guide.

27 Section D Topic Notifications Whenever a payment is made or a modification is processed, we will notify you of the event and whether or not it was performed successfully. Within your SmartPay back-office you can configure a URL that you wish to receive these messages. Notifications should be used to keep your own back-office systems up to date with the status of each payment or modification to a payment is made. Notifications allow you to receive updates on a payments status, for example you will receive a notification when a payment is processed and authorised. If the payment is then refunded using the back-office or a modification request you will receive a further a notification confirming the payment status has changed. If you choose to use the SmartPay subscription reports you will also receive a notification to confirm the report is available. The notification message also includes additional authorisation information that is not included at other points in the payment process. You must to ensure you have configured a Notification URL before you move your account from Test to Live. You can configure the Notification settings in the Barclaycard SmartPay Backoffice. For more information please refer to the SmartPay Notifications Guide.

28 Section E Topic Skins What is a Skin? A Skin is a set of look-and-feel customisations which consist of a set of custom HTML fragments, images and CSS style sheets, which define the look and feel of the Barclaycard SmartPay Hosted Payment Pages. This allows you to integrate the payment pages in the same style as your website. You can even create multiple skins if you have more than one web shop, or if you want to target a different type of device or application such as a mobile phone browser or point-of - sale terminal. HTML fragments which are included in the payment can also be supplied in different languages and many of the default strings and their translations can be changed by overriding them in resource files (which can also be supplied as part of the Skin). The Skin also allows you to manipulate which payment methods are offered by default and the order in which they are displayed. Also minimum and maximum transaction amounts per payment method can be specified. Please Note: The default skins that are created in your back-office are examples and can be used to process payments, if you make any modifications to the Skins it is your responsibility to test them and ensure they work before you go live. For more information please refer to the SmartPay Skins Guide.

29 Section F Topic HPP - Oneclick Payments If a significant portion of your business consists of returning shoppers you can use the CSConly (oneclick) functionality of Barclaycard SmartPay to store the card details used by a shopper. Returning shoppers will have the option to pay using a card they have previously used by simply filling in the Card Security Code (CSC/CVC) and confirming the purchase. Setting up the Payment The payment session is set up just like a regular payment. There are two normally optional fields which now become mandatory and one new field which needs to be provided in the payment session form. Field Name shopper Description The address of the shopper, no longer optional. shopperreference An id that refers uniquely to the shopper, no longer optional. recurringcontract This parameter defines what type of recurring contract is used. For the CSC-only payments the value ONECLICK should be used. For example: <input type="hidden" name="shopper " value="gras.shopper@somewhere.org" /> <input type="hidden" name="shopperreference" value="grasshopper52" /> <input type="hidden" name="recurringcontract" value="oneclick" /> The initial purchase will proceed just like a normal payment with a single exception: a checkbox will allow the shopper to opt-out of having their details stored. For a subsequent payment (provided the shopper didn't opt-out during the initial purchase) the shopper will see a graphic representation of their credit card with a blank field underneath in which to enter their card security code. Note - Shoppers are uniquely identified using the shopperreference parameter; it is most important that shoppers are securely logged in on your website and that the shopperreference parameter cannot be modified by the shopper.

30 Section G Topic HPP - Recurring Payments A similar process to Oneclick is followed to create a recurring contract. Creating a recurring contract is done by having the shopper perform a regular payment and storing the card details. We refer to this as the initial payment. Recurring payments reuse payment details submitted earlier in the initial payment by the shopper to perform the payment. This section explains how to submit recurring payments to the Barclaycard SmartPay Payment System. Recurring payments reuse payment details submitted earlier by the shopper to perform the payment. Note - Recurring payments are not enabled by default. If you would like to start processing recurring payments, you can request this through the support team. Creating a Recurring Contract Creating a recurring contract is done by having the shopper perform a regular payment. We refer to this as the initial payment, details from this will be used to perform later, recurring payments. Please Note: It is not possible to use the HPP to store card details without an authorisation attempt being made. Setting up the Payment The payment session is set up just like a regular payment. There are two normally optional fields which now become mandatory and one new field which needs to be provided in the payment session form. These additional fields are included in the standard HTML form used to direct the cardholder to the single or multi-page HPP. Field Name shopper Description The address of the shopper, no longer optional. shopperreference An id that refers uniquely to the (recurring) shopper, no longer optional. recurringcontract This parameter defines what type of recurring contract is used. The value of this parameter must be "RECURRING" currently.

31 For example: <input type="hidden" name="shopper " /> <input type="hidden" name="shopperreference" value="grasshopper52" /> <input type="hidden" name="recurringcontract" value="recurring" /> The value of the recurringcontract parameter above must also be inserted into the signature string over which the HMAC is computed between the shopperreference and allowedmethods. e.g.: + sessionvalidity + shopper + shopperreference + recurringcontract + allowedmethods The payment will proceed as usual and if the result is a successful authorisation, a recurring contract will automatically be created. We show you how to get the contract reference in the following section. Note - Shoppers are uniquely identified using the shopperreference parameter; it is most important that shoppers are securely logged in on your website and that the shopperreference parameter cannot be modified by the shopper. Submitting Recurring Payments Submitting recurring payments is implemented as a SOAP service similar to the way modifications are submitted. The URL (and WSDL) for submitting the recurring transaction listed in the Appendix. To submit recurring payments, you must supply HTTP basic authentication credentials (username/password). For the username you should use ws@company.yourcompanyaccount, you can set the password for this user in the Barclaycard SmartPay Backoffice (under Settings -> Users ). Please Note: It is typically possible to submit a subsequent recurring transaction after 5 minutes from the contract being created. To submit a recurring transaction you will need to call the authorise action in the payment service. Within this action there are two different requests according to the payment type used for the transaction: paymentrequest directdebitrequest For card, ELV and direct ebanking you will use the paymentrequest, Please see the following pages for a break down on the recurringpayment request and the response listing the possible values.

32 Recurring paymentrequest Payments The paymentrequest has the following fields: Field Name selectedrecurringdetailreference Description This is the recurringdetailreference you want to use for this payment. You can use the value LATEST to select the most recently used recurring detail. recurring The contract value of the recurring object should be present and contain value RECURRING for the contract field. merchantaccount The merchant account you want to process this payment with. amount The amount to authorise. This consists of a currencycode and a value which is the amount in minor units (see explanation for the paymentamount session). reference Your reference for this payment. This (merchant) reference will be used in all communication to you about the status of the payment. Although it is not a requirement it is a good idea to make this unique. shopper The address of the shopper. This does not have to match the address supplied with the initial payment, since it may have changed in the mean time. shopperreference The reference to the shopper. This shopperreference must be the same as the shopperreference used in the initial payment. shopperinteraction The shopperinteraction of the recurring payment must be set to ContAuth, fraudoffset (optional) A integer that is added to normal fraud score. The value can be either positive or negative. shopperip (optional) The IP address of the shopper. Used in various risk checks (number of payment attempts, location, etc.)

33 An example of a SOAP request is below showing how the above can be used to submit a recurring payment. <?xml version="1.0"?> <soap:envelope xmlns:soap=" xmlns:xsd=" xmlns:xsi=" <soap:body> <ns1:authorise xmlns:ns1=" <ns1:paymentrequest> <amount xmlns=" <currency xmlns=" <value xmlns=" </amount> <ns1:merchantaccount>yourmerchantaccount</ns1:merchantaccount> <ns1:reference>recurringpayment-0001</ns1:reference> <ns1:shopperip> </ns1:shopperip> <ns1:shopper > @shopper.com</ns1:shopper > <ns1:shopperreference>theshopperreference</ns1:shopperreference> <ns1:selectedrecurringdetailreference>latest</ns1:selectedrecurringdetailreference> <ns1:recurring> <ns1:contract>recurring</ns1:contract> </ns1:recurring> <ns1:shopperinteraction>contauth</ns1:shopperinteraction> </ns1:paymentrequest> </ns1:authorise> </soap:body> </soap:envelope> Example of a Recurring Payment SOAP request Recurring paymentrequest response If the message passes validation a risk analysis will be done and, depending on the outcome, authorisation will be attempted. You will receive a payment response with the following fields: Field Name pspreference Description The reference we assigned to the payment. This is guaranteed to be globally unique and must be used when communicating about this payment to us. resultcode The result of the payment. One of Authorised, Refused or Error authcode If the payment was successful the authcode (authorisation code) field will contain a value. In all other cases it will be blank. refusalreason If the payment was refused, the refusal reason will be specified here. Please see the following page for an example of the soap recurring payment response.

34 <?xml version="1.0"?> <soap:envelope xmlns:soap=" xmlns:xsd=" xmlns:xsi=" <soap:body> <ns1:authoriseresponse xmlns:ns1=" <ns1:paymentresult> <additionaldata xmlns=" xsi:nil="true"/> <authcode xmlns=" <dccamount xmlns=" xsi:nil="true"/> <dccsignature xmlns=" xsi:nil="true"/> <fraudresult xmlns=" xsi:nil="true"/> <issuerurl xmlns=" xsi:nil="true"/> <md xmlns=" xsi:nil="true"/> <parequest xmlns=" xsi:nil="true"/> <pspreference xmlns=" AnewPspReference </pspreference> <refusalreason xmlns=" xsi:nil="true"/> <resultcode xmlns=" </ns1:paymentresult> </ns1:authoriseresponse> </soap:body> </soap:envelope> Example of a Recurring Payment SOAP response You will be informed of the authorisation result via a notification sent to your Notification URL.

35 Disable a Recurring Contract When a recurring contract is no longer relevant for whatever reason (e.g. a cancelled or expired subscription) it can be disabled to prevent accidentally charging the account holder. Deactivating/disabling a recurring contract is achieved by calling the Recurring service and using the method disablerequest. The disablerequest has the following fields: Field Name merchantaccount Description Your merchant account shopperreference The reference to the shopper. This shopperreference must be the same as the shopperreference used in the initial payment. recurringdetailreference (optional) The recurringdetailreference of the details you wish to disable. If you do not supply this field, all details for the shopper will be disabled, including the contract. <?xml version="1.0"?> <soap:envelope xmlns:soap=" xmlns:xsd=" xmlns:xsi=" <soap:body> <ns1:disable xmlns:ns1=" <ns1:disablerequest> <ns1:merchantaccount>yourmerchantaccount</ns1:merchantaccount> <ns1:shopperreference>theshopperreference</ns1:shopperreference> <ns1:recurringdetailreference> </ns1:recurringdetailreference> </ns1:disablerequest> </ns1:disable> </soap:body> </soap:envelope> Example of a Recurring Disable SOAP Request Details of the Disable Response can be found on the following page.

Adyen Merchant Integration Manual. Version 1.60 Adyen B.V.

Adyen Merchant Integration Manual. Version 1.60 Adyen B.V. Adyen Merchant Integration Manual Version 1.60 Adyen B.V. Table of Contents Introduction...3 Audience...3 Changelog...4 1 Hosted Payment Pages (HPPs)...5 Setting Up the Payment...5 Payment Session Example...5

More information

Recurring payments manual

Recurring payments manual Recurring payments manual SmartPay Contents Introduction 3 Audience 3 What is a recurring contract? 4 Recurring vs One-Click 4 Usual workflow 4 Creating a recurring contract 5 Setting up the payment 5

More information

Adyen MOTO Manual 'Mail Order / Telephone Order' Version 1.06 Adyen B.V.

Adyen MOTO Manual 'Mail Order / Telephone Order' Version 1.06 Adyen B.V. Adyen MOTO Manual 'Mail Order / Telephone Order' Version 1.06 Adyen B.V. Table of Contents 1 Introduction...3 Audience... 3 Changelog... 3 Requirements...3 Interfaces and Integration...4 Payment Methods...4

More information

Recurring Payments Manual

Recurring Payments Manual Recurring Payments Manual Version: 3.2 Contact details Simon Carmiggeltstraat 6-50 1011 DJ Amsterdam P.O. Box 10095 1001 EB Amsterdam The Netherlands T +31 20 240 1240 E support@adyen.com Table of Contents

More information

Barclaycard SmartPay. Virtual Terminal / MOTO Guide

Barclaycard SmartPay. Virtual Terminal / MOTO Guide Barclaycard SmartPay Virtual Terminal / MOTO Guide Version 3.0 Released April 2012 DOC Version Control Version No. Date Issued Reason for Change 1.0 July 2010 Initial Document 2.0 February 2012 Update

More information

Adyen Magento extension

Adyen Magento extension Adyen Magento extension User manual Date: Apr 22, 2014 Filename: Adyen Magento Extension V2.0.0.odt Version: 2.0.0 Reference: Adyen Magento Extension V2.0.0 Adyen Magento extension - manual Version control

More information

Adyen Merchant Manual. Version 1.10 Adyen B.V.

Adyen Merchant Manual. Version 1.10 Adyen B.V. Adyen Merchant Manual Version 1.10 Adyen B.V. Introduction3 Table of Contents Introduction... 3 Audience...3 Changelog...3 1 Payment Life-cycle in the Adyen System... 4 What Happens to a Payment After

More information

int_adyen Version 15.1.0

int_adyen Version 15.1.0 int_adyen Version 15.1.0 LINK Integration Documentation - int_adyen Page 1 Table of Contents 1. General Information... 5 2. Component Overview... 6 2.1. Functional Overview... 6 Short description of the

More information

Realex Payments. Magento Community / Enterprise Plugin. Configuration Guide. Version: 1.1

Realex Payments. Magento Community / Enterprise Plugin. Configuration Guide. Version: 1.1 Realex Payments Magento Community / Enterprise Plugin Configuration Guide Version: 1.1 Document Information Document Name: Magento Community / Enterprise Plugin Configuration Guide Document Version: 1.1

More information

Visa Checkout Integration Guide V1.0

Visa Checkout Integration Guide V1.0 Visa Checkout Integration Guide V1.0 IP Payments Pty Ltd Level 3, 441 Kent Street Sydney NSW 2000 Australia (ABN 86 095 635 680) T +61 2 9255 9500 F +61 2 8248 1276 www.ippayments.com No part of this document

More information

PROCESS TRANSACTION API

PROCESS TRANSACTION API PROCESS TRANSACTION API Document Version 8.7 May 2015 For further information please contact Digital River customer support at (888) 472-0811 or support@beanstream.com. 1 TABLE OF CONTENTS 2 Lists of tables

More information

Process Transaction API

Process Transaction API Process Transaction API Document Version 5.9 March 2011 For further information please contact Beanstream customer support at (250) 472-2326 or support@beanstream.com. BEAN # Page 2 of 90 Date Overview...

More information

MiGS Virtual Payment Client Integration Guide. July 2011 Software version: MR 27

MiGS Virtual Payment Client Integration Guide. July 2011 Software version: MR 27 MiGS Virtual Payment Client Integration Guide July 2011 Software version: MR 27 Copyright MasterCard and its vendors own the intellectual property in this Manual exclusively. You acknowledge that you must

More information

My Sage Pay User Manual

My Sage Pay User Manual My Sage Pay User Manual Page 1 of 32 Contents 01. About this guide..4 02. Getting started.4 Online help Accessing My Sage Pay Test Servers Live Servers The Administrator account Creating user accounts

More information

MySagePay. User Manual. Page 1 of 48

MySagePay. User Manual. Page 1 of 48 MySagePay User Manual Page 1 of 48 Contents About this guide... 4 Getting started... 5 Online help... 5 Accessing MySagePay... 5 Supported browsers... 5 The Administrator account... 5 Creating user accounts...

More information

Accepting Ecommerce Payments & Taking Online Transactions

Accepting Ecommerce Payments & Taking Online Transactions Accepting Ecommerce Payments & Taking Online Transactions Accepting credit and debit cards is mandatory for Ecommerce websites. This method is fast and efficient for you and your customers and with the

More information

Swedbank Payment Portal Implementation Overview

Swedbank Payment Portal Implementation Overview Swedbank Payment Portal Implementation Overview Product: Hosted Pages Region: Baltics September 2015 Version 1.0 Contents 1. Introduction 1 1.1. Audience 1 1.2. Hosted Page Service Features 1 1.3. Key

More information

A: This will depend on a number of factors. Things to consider and discuss with a member of our ANZ Merchant Services team are:

A: This will depend on a number of factors. Things to consider and discuss with a member of our ANZ Merchant Services team are: 1 ANZ egate FAQ s Contents Section 1 General information: page 1 Section 2 Technical information for ANZ egate Merchants: page 5 November 2010 Section 1 General information Q: What is ANZ egate? A: ANZ

More information

ANZ egate Virtual Payment Client

ANZ egate Virtual Payment Client ANZ egate Virtual Payment Client Integration Notes Contents Purpose of notes 3 For enquiries and support 3 Contents of ANZ egate kit 3 Sample Codes 3 Bank Hosted, Merchant Hosted and Merchant Hosted with

More information

Internet Authentication Procedure Guide

Internet Authentication Procedure Guide Internet Authentication Procedure Guide Authenticating cardholders successfully V10.0 Released May 2012 Software Version: Internet Authentication Protocol COPYRIGHT NOTICE No part of this publication may

More information

Direct Post. Integration Guide

Direct Post. Integration Guide Direct Post Integration Guide Updated September 2013 Table of Contents 1 Introduction... 4 1.1 What is Direct Post?... 4 1.2 About this Guide... 4 1.3 Features and Benefits... 4 1.4 Card Types Accepted...

More information

COMMERCIAL-IN-CONFIDENCE

COMMERCIAL-IN-CONFIDENCE CardEaseMPI a technical manual describing the use of CardEaseMPI 3-D Secure Merchant Plug-In. Authors: Nigel Jewell Issue 2.9. November 2014. COMMERCIAL-IN-CONFIDENCE Copyright CreditCall Limited 2007-2014

More information

CyberSource Secure Acceptance Web/Mobile

CyberSource Secure Acceptance Web/Mobile Title Page CyberSource Secure Acceptance Web/Mobile Configuration Guide October 2015 CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095 CyberSource Contact Information

More information

Order Notifications - reporting a payment status

Order Notifications - reporting a payment status Corporate Gateway Order Notifications - reporting a payment status V5.0 May 2014 Use this guide to: Understand order notifications. Learn how to use the Order Notification Service. New to Order Notifications?

More information

UPG plc Atlas Technical Integration Guide

UPG plc Atlas Technical Integration Guide UPG plc Atlas Technical Integration Guide Version 13.8.16 Released Aug 2013 Description Integrating your website or payment system into the UPG plc Atlas ecommerce gateway platform UPG Plc. version 13.8.16

More information

Virtual Terminal User s Guide

Virtual Terminal User s Guide Virtual Terminal User s Guide For Professional Use Only Currently only available in English. A usage Professional Uniquement Disponible en Anglais uniquement pour l instant. Last updated: June 2008 PayPal

More information

GENERAL ADMINISTRATION - SHOPPING CART

GENERAL ADMINISTRATION - SHOPPING CART GENERAL ADMINISTRATION - SHOPPING CART Document Version 3.0 December 2014 For assistance, please message DRWP Client Services or call 0800 756 3350. Copyright 2014 Beanstream Internet Commerce. All rights

More information

Hosted Credit Card Forms Implementation Guide

Hosted Credit Card Forms Implementation Guide Hosted Credit Card Forms Implementation Guide Merchant implementation instructions to integrate to the Setcom s hosted credit card forms. Covers: fraud screening, Verified by Visa, MasterCard SecureCode

More information

Implementation guide - Interface with the payment gateway PayZen 2.5

Implementation guide - Interface with the payment gateway PayZen 2.5 Implementation guide - Interface with the payment gateway PayZen 2.5 Document version 3.5 Contents 1. HISTORY OF THE DOCUMENT... 4 2. GETTING IN TOUCH WITH TECHNICAL SUPPORT... 6 3. DIFFERENT TYPES OF

More information

Elavon Payment Gateway Hosted Payment Page

Elavon Payment Gateway Hosted Payment Page Elavon Payment Gateway Hosted Payment Developers Guide Version: v1.1 1 Table of Contents 1 About This Guide.. 4 1.1 Purpose....4 1.2 Audience.4 1.3 Prerequisites...4 1.4 Related Documents..4 1.5 Conventions..4

More information

Payment Response Guide. Version 4.3 September 2012 Business Gateway

Payment Response Guide. Version 4.3 September 2012 Business Gateway Version 4.3 September 2012 Business Gateway Table of Contents About this Book... 2 Copyright... 2 Introduction... 3 What is Payment Response?... 3 The Payment Response Process... 4 Reference... 5 Setting

More information

Risk Management Service Guide. Version 4.2 August 2013 Business Gateway

Risk Management Service Guide. Version 4.2 August 2013 Business Gateway Risk Management Service Guide Version 4.2 August 2013 Business Gateway This page is intentionally blank. Table Of Contents About this Guide... 1 Change History... 1 Copyright... 1 Introduction... 3 What

More information

itransact Gateway Fast Start Guide

itransact Gateway Fast Start Guide itransact Gateway Fast Start Guide itransact Gateway Fast Start Guide Table of Contents 1. Version and Legal Information... 1 2.... 2 Quick Setup... 2 The Card Setup... 2 Order Form Setup... 3 Simple

More information

ipayment Gateway API (IPG API)

ipayment Gateway API (IPG API) ipayment Gateway API (IPG API) Accepting e-commerce payments for merchants Version 3.2 Intercard Finance AD 2007 2015 Table of Contents Version control... 4 Introduction... 5 Security and availability...

More information

Server Protocol and Integration Guideline (Protocol v3.00) Published Date 27/08/2013

Server Protocol and Integration Guideline (Protocol v3.00) Published Date 27/08/2013 Server Protocol and Integration Guideline (Protocol v3.00) Published Date 27/08/2013 Document Index Version History... 3 LEGAL NOTICE... 3 Welcome to the Sage Pay Server integration method... 4 Overview

More information

Cardsave Payment Gateway

Cardsave Payment Gateway Cardsave Payment Gateway Cart Implementation David McCann Cardsave Online Version 1 1 st August 2010 Contents Page Overview 3-4 o Integration Types 3 Direct/Integrated (Preferred Method) Re-direct/Hosted

More information

Fraud Detection. Configuration Guide for the Fraud Detection Module v.4.2.0. epdq 2014, All rights reserved.

Fraud Detection. Configuration Guide for the Fraud Detection Module v.4.2.0. epdq 2014, All rights reserved. Configuration Guide for the Fraud Detection Module v.4.2.0 Table of Contents 1 What is the... Fraud Detection Module? 4 1.1 Benefits 1.2 Access 1.3 Contents... 4... 4... 4 2 Fraud detection... activation

More information

WEB TERMINAL AND RECURRING BILLING

WEB TERMINAL AND RECURRING BILLING PROCESSING TRANSACTIONS WITH WEB TERMINAL AND RECURRING BILLING Document Version 1.4 December 2013 For further information please contact Digital River customer support at 0800 756 3350 or clientsupport.uk@digitalriver.com.

More information

Credomatic Integration Resources. Browser Redirect API Documentation June 2007

Credomatic Integration Resources. Browser Redirect API Documentation June 2007 Credomatic Integration Resources Browser Redirect API Documentation June 2007 Table of Contents Methodology... 2 Browser Redirect Method (Browser to Server) FIG. 1... 2 API Authentication Parameters...

More information

Fraud Detection Module (basic)

Fraud Detection Module (basic) Table of contents 1. Introduction 1.1 Benefits 1.2 Contents 2. Activation and configuration 2.1 Blocking rules 2.1.1 Card country 2.1.2 IP address country 2.1.3 Country consistency 2.1.4 3-D Secure 2.2

More information

PayPal Manual. Version: 2.03. Contact details. Simon Carmiggeltstraat 6-50 1011 DJ Amsterdam. P.O. Box 10095 1001 EB Amsterdam The Netherlands

PayPal Manual. Version: 2.03. Contact details. Simon Carmiggeltstraat 6-50 1011 DJ Amsterdam. P.O. Box 10095 1001 EB Amsterdam The Netherlands PayPal Manual Version: 2.03 Contact details Simon Carmiggeltstraat 6-50 1011 DJ Amsterdam P.O. Box 10095 1001 EB Amsterdam The Netherlands T +31 20 240 1240 E support@adyen.com Table of Contents 1.Introduction...5

More information

Virtual Terminal User s Guide

Virtual Terminal User s Guide Virtual Terminal User s Guide For Professional Use Only Currently only available in English. A usage Professional Uniquement Disponible en Anglais uniquement pour l instant. Last updated: August 2009 PayPal

More information

Merchant Plug-In. Specification. Version 3.2. 110.0093 SIX Payment Services

Merchant Plug-In. Specification. Version 3.2. 110.0093 SIX Payment Services Merchant Plug-In Specification Version 3.2 110.0093 SIX Payment Services Table of contents 1 Introduction... 3 1.1 Summary... 3 1.2 Requirements... 4 1.3 Participation and Result of the Authentication...

More information

Manual. Netumo NETUMO HELP MANUAL WWW.NETUMO.COM. Copyright Netumo 2014 All Rights Reserved

Manual. Netumo NETUMO HELP MANUAL WWW.NETUMO.COM. Copyright Netumo 2014 All Rights Reserved Manual Netumo NETUMO HELP MANUAL WWW.NETUMO.COM Copyright Netumo 2014 All Rights Reserved Table of Contents 1 Introduction... 0 2 Creating an Account... 0 2.1 Additional services Login... 1 3 Adding a

More information

Virtual Terminal User Guide

Virtual Terminal User Guide Payment solutions for online commerce Virtual Terminal User Guide Copyright PayPoint.net 2010 This document contains the proprietary information of PayPoint.net and may not be reproduced in any form or

More information

Virtual Payment Client Integration Reference. April 2009 Software version: 3.1.21.1

Virtual Payment Client Integration Reference. April 2009 Software version: 3.1.21.1 Virtual Payment Client Integration Reference April 2009 Software version: 3.1.21.1 Copyright MasterCard and its vendors own the intellectual property in this Manual exclusively. You acknowledge that you

More information

Merchant Integration Guide

Merchant Integration Guide Merchant Integration Guide Card Not Present Transactions Authorize.Net Customer Support support@authorize.net Authorize.Net LLC 071708 Authorize.Net LLC ( Authorize.Net ) has made efforts to ensure the

More information

Virtual Terminal User s Guide

Virtual Terminal User s Guide Virtual Terminal User s Guide For Professional Use Only Currently only available in English. A usage Professional Uniquement Disponible en Anglais uniquement pour l instant. Last updated: June 2009 PayPal

More information

This Annex uses the definitions set out in the Agreement on service of payment cards on the Internet (hereinafter the Agreement).

This Annex uses the definitions set out in the Agreement on service of payment cards on the Internet (hereinafter the Agreement). SERVICE OF PAYMENT CARDS ON THE INTERNET ANNEX 2 TO AGREEMENT Requirements for Queries to I-Payment Terminal This Annex uses the definitions set out in the Agreement on service of payment cards on the

More information

Merchant Integration Guide

Merchant Integration Guide Merchant Integration Guide Card Not Present Transactions January 2012 Authorize.Net Developer Support http://developer.authorize.net Authorize.Net LLC 082007 Ver.2.0 Authorize.Net LLC ( Authorize.Net )

More information

Mail & Telephone Order Payments Service (WorldAccess) Guide. Version 4.3 February 2014 Business Gateway

Mail & Telephone Order Payments Service (WorldAccess) Guide. Version 4.3 February 2014 Business Gateway Mail & Telephone Order Payments Service (WorldAccess) Guide Version 4.3 February 2014 Business Gateway Table Of Contents About this Guide... 1 Update History... 1 Copyright... 1 Introduction... 2 What

More information

Global Transport Secure ecommerce Decision Tree

Global Transport Secure ecommerce Decision Tree Global Transport Secure ecommerce Decision Tree Development work* or software configuration** is required. Please be prepared to engage a webmaster/developer for assistance Are you looking for a hosted

More information

Blackbaud Merchant Services Web Portal Guide

Blackbaud Merchant Services Web Portal Guide Blackbaud Merchant Services Web Portal Guide 06/11/2015 Blackbaud Merchant Services Web Portal US 2015 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any

More information

Three Step Redirect API V2.0 Patent Pending

Three Step Redirect API V2.0 Patent Pending Three Step Redirect API V2.0 Patent Pending Contents Three Step Redirect Overview... 4 Three Step Redirect API... 4 Detailed Explanation... 4 Three Step Transaction Actions... 7 Step 1... 7 Sale/Auth/Credit/Validate/Offline

More information

MiGS Merchant Administration Guide. July 2013 Software version: MR 29

MiGS Merchant Administration Guide. July 2013 Software version: MR 29 MiGS Merchant Administration Guide July 2013 Software version: MR 29 Copyright MasterCard and its vendors own the intellectual property in this Manual exclusively. You acknowledge that you must not perform

More information

Magento Extension User Guide: Payment Pages. This document explains how to install the official Secure Trading extension on your Magento store.

Magento Extension User Guide: Payment Pages. This document explains how to install the official Secure Trading extension on your Magento store. This document explains how to install the official Secure Trading extension on your Magento store. Module version: 3.5 Published: 6 August 2015 Table of Contents 1 Introduction... 3 1.1 Features... 3 1.2

More information

Merchant Interface Guide. Version 4.0 December 2011 Business Gateway

Merchant Interface Guide. Version 4.0 December 2011 Business Gateway Merchant Interface Guide Version 4.0 December 2011 Business Gateway Merchant Interface Guide Table of Contents About this Guide... 4 Update History... 4 Copyright... 4 Introduction... 5 What is the Merchant

More information

PAY BUTTON USER GUIDE PAY BUTTON USER GUIDE. Version: 1.2

PAY BUTTON USER GUIDE PAY BUTTON USER GUIDE. Version: 1.2 PAY BUTTON Version: 1.2-1 - 1 About Pay Button... 3 2 Using the Pay Button Creator... 3 2.1 Fields... 4 2.2 Inserting the Link/QR Code... 5 3 Advanced Integration... 10 3.1 Advanced Integration... 10 3.1.1

More information

Secure Hosting and Payments Technical Integration Guide

Secure Hosting and Payments Technical Integration Guide Secure Hosting and Payments Technical Integration Guide Version 12.8.8 Released Aug 2012 Description Integrating your website or payment system into the Secure Hosting and Payment ecommerce gateway platform

More information

Customising Your Mobile Payment Pages

Customising Your Mobile Payment Pages Corporate Gateway Customising Your Mobile Payment Pages V2.0 May 2014 Use this guide to: Understand how to customise your payment pages for mobile and tablet devices XML Direct Integration Guide > Contents

More information

Paynow 3rd Party Shopping Cart or Link Integration Guide

Paynow 3rd Party Shopping Cart or Link Integration Guide Paynow 3rd Party Shopping Cart or Link Integration Guide Version 1.0.5 15 August 2014 A guide outlining merchant integration into Paynow for externally hosted shopping carts or applications. For details

More information

Elavon Payment Gateway- Reporting User Guide

Elavon Payment Gateway- Reporting User Guide Elavon Payment Gateway- Reporting User Guide Version: v1.1 Contents 1 About This Guide... 4 1.1 Purpose... 4 1.2 Audience... 4 1.3 Prerequisites... 4 1.4 Related Documents... 4 1.5 Terminology... 4 1.6

More information

Cardholder Authentication Guide. Version 4.3 August 2013 Business Gateway

Cardholder Authentication Guide. Version 4.3 August 2013 Business Gateway Cardholder Authentication Guide Version 4.3 August 2013 Business Gateway ii This page is intentionally blank Table of Contents About this Guide... 1 History... 1 Copyright... 2 Introduction... 3 What is

More information

Online signature API. Terms used in this document. The API in brief. Version 0.20, 2015-04-08

Online signature API. Terms used in this document. The API in brief. Version 0.20, 2015-04-08 Online signature API Version 0.20, 2015-04-08 Terms used in this document Onnistuu.fi, the website https://www.onnistuu.fi/ Client, online page or other system using the API provided by Onnistuu.fi. End

More information

Title Page. payplace.express giropay Connection for traders and integrators

Title Page. payplace.express giropay Connection for traders and integrators Title Page payplace.express giropay Connection for traders and integrators Connection for traders and integrators This document relates to payplace.express version 1.2. Revision: 1.3.4 Date of issue: 14/04/2014

More information

Secure XML API Integration Guide. (with FraudGuard add in)

Secure XML API Integration Guide. (with FraudGuard add in) Secure XML API Integration Guide (with FraudGuard add in) Document Control This is a control document DESCRIPTION Secure XML API Integration Guide (with FraudGuard add in) CREATION DATE 02/04/2007 CREATED

More information

Form Protocol and Integration Guideline. Form Protocol and Integration Guideline (Protocol v3.00)

Form Protocol and Integration Guideline. Form Protocol and Integration Guideline (Protocol v3.00) Form Protocol and Integration Guideline (Protocol v3.00) Published Date 30/01/2014 Document Index Version History... 3 LEGAL NOTICE... 3 Welcome to the Sage Pay Form integration method... 4 Overview of

More information

Merchant Interface User Guide

Merchant Interface User Guide Business Gateway and Corporate Gateway Merchant Interface User Guide V5.0 May 2014 Use this guide to: Understand the Merchant Interface and the functionality it provides Learn how to use the Merchant Interface

More information

Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained.

Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained. For etapestry Customers www.blackbaud.co.uk Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained. What is BBPS/BBMS? Blackbaud Payment Services (BBPS) is Blackbaud

More information

RealAuth Hosted Payment Page

RealAuth Hosted Payment Page RealAuth Hosted Payment Page Developers Guide Version: v1.1.4 Document Information Document Name: RealAuth HPP Developer's Guide Document Version: 1.1.4 Release Date: 15th January 2015 Legal Statement

More information

MONETA.Assistant API Reference

MONETA.Assistant API Reference MONETA.Assistant API Reference Contents 2 Contents Abstract...3 Chapter 1: MONETA.Assistant Overview...4 Payment Processing Flow...4 Chapter 2: Quick Start... 6 Sandbox Overview... 6 Registering Demo Accounts...

More information

Account Management System Guide

Account Management System Guide Account Management System Guide Version 2.2 March 2015 Table of Contents Introduction...5 What is the Account Management System?...5 Accessing the Account Management System...5 Forgotten Password...5 Account

More information

Web Services Credit Card Errors A Troubleshooter

Web Services Credit Card Errors A Troubleshooter Web Services Credit Card Errors A Troubleshooter March 2011 This manual and accompanying electronic media are proprietary products of Optimal Payments plc. They are to be used only by licensed users of

More information

I. Simplifying Payment Processing. II. Authorizing Your Transactions Correctly page 6

I. Simplifying Payment Processing. II. Authorizing Your Transactions Correctly page 6 Welcome to PaySimple! Congratulations on choosing PaySimple for all your payment processing needs! You will quickly notice that billing and collections is transformed into an effortless process. With PaySimple,

More information

Klarna Magento module

Klarna Magento module Klarna Magento module User guide Payment module version: 5.x.+ User guide 1.0 Revision: 1.1 Table of Contents User guide Welcome to Klarna How do you benefit? What is Klarna s offering? Prerequisites Before

More information

AliPay International Services

AliPay International Services Title Page AliPay International Services Using the Simple Order API September 2015 CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095 CyberSource Contact Information

More information

Web Services Credit Card Errors A Troubleshooter

Web Services Credit Card Errors A Troubleshooter Web Services Credit Card Errors A Troubleshooter January 2012 This manual and accompanying electronic media are proprietary products of Optimal Payments plc. They are to be used only by licensed users

More information

DIRECT INTEGRATION GUIDE DIRECT INTEGRATION GUIDE. Version: 9.16

DIRECT INTEGRATION GUIDE DIRECT INTEGRATION GUIDE. Version: 9.16 DIRECT Version: 9.16-1 - 1 Direct HTTP Integration... 4 1.1 About This Guide... 4 1.2 Integration Disclaimer... 4 1.3 Terminology... 5 1.4 Pre-Requisites... 6 1.5 Integration Details... 7 1.6 Authentication...

More information

Secure Email User Guide

Secure Email User Guide Secure Email User Guide Contents Secure email at HSBC. 2 About SecureMail... 2 Receiving a secure email sent via SecureMail 3 Opening a secure email sent via SecureMail... 4 Resetting your SecureMail password..

More information

How To Pay With Worldpay (Hosted Call Centre)

How To Pay With Worldpay (Hosted Call Centre) Corporate Gateway Mail and Telephone Order Payment Service (Hosted Call Centre) Guide V4.0 June 2014 Use this guide to: Learn how to use the Mail and Telephone Order Payment service (Hosted Call Centre)

More information

Authorize.net for WordPress

Authorize.net for WordPress Authorize.net for WordPress Authorize.net for WordPress 1 Install and Upgrade 1.1 1.2 Install The Plugin 5 Upgrading the plugin 8 2 General Settings 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 Connecting

More information

Portal Recipient Guide

Portal Recipient Guide Portal Recipient Guide Lindenhouse Software Limited 2015 Contents 1 Introduction... 4 2 Account Activation... 4 3 Forgotten Password... 9 4 Document signing... 12 5 Authenticating your Device & Browser...

More information

Fairsail REST API: Guide for Developers

Fairsail REST API: Guide for Developers Fairsail REST API: Guide for Developers Version 1.02 FS-API-REST-PG-201509--R001.02 Fairsail 2015. All rights reserved. This document contains information proprietary to Fairsail and may not be reproduced,

More information

1. Introduction to CardPay

1. Introduction to CardPay 1. Introduction to CardPay The introduction manual describes the technical aspects of payments processing using CardPay's hosted payment page. CardPay is an online payment processor for e-commerce transactions

More information

Network Merchants Inc (NMI) Integration Resources. Direct Post API Documentation April 2010

Network Merchants Inc (NMI) Integration Resources. Direct Post API Documentation April 2010 Network Merchants Inc (NMI) Integration Resources Direct Post API Documentation April 2010 Table of Contents Methodology... 2 Direct Post Method (Server to Server) FIG. 1... 2 Transaction Types... 3 Sale

More information

Integration Guide Last Revision: July 2004

Integration Guide Last Revision: July 2004 Last Revision: July 2004 PayPal Integration Guide 2004 PayPal, Inc. All Rights Reserved. PayPal and the PayPal logo are registered trademarks of PayPal, Inc. Designated trademarks and brands are the property

More information

Increase revenue. Reduce operating costs. Improve efficiencies. Accomplish all this and more with eselectplus.

Increase revenue. Reduce operating costs. Improve efficiencies. Accomplish all this and more with eselectplus. Increase revenue. Reduce operating costs. Improve efficiencies. Accomplish all this and more with eselectplus. eselectplus makes payment simple for you, and for your customers. eselectplus is an easy-to-use,

More information

Skipjack ezpay Secure Online Order Form User Guide

Skipjack ezpay Secure Online Order Form User Guide Skipjack ezpay Secure Online Order Form User Guide About this Document...3 Copyright Notice... 3 Publication History... 3 Documentation Conventions... 4 Assumptions Used in this Guide... 4 Obtaining Additional

More information

A BETTER WAY TO PAY Unified Merchants API (UMAPI).Net Integration Manual

A BETTER WAY TO PAY Unified Merchants API (UMAPI).Net Integration Manual A BETTER WAY TO PAY Unified Merchants API (UMAPI).Net Integration Manual Version 2.3 Contents 1 INTRODUCTION... 5 1.1 Purpose and Objective... 5 1.2 Audience... 5 1.3 Assumptions / Exclusions... 5 1.4

More information

Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained.

Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained. Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained. What is BBPS/BBMS? Blackbaud Payment Services (BBPS) is Blackbaud s solution for secure credit card storage.

More information

API For Chopstickpay Merchants Configuration: Server-to-server Version: 3.4 Status: Published

API For Chopstickpay Merchants Configuration: Server-to-server Version: 3.4 Status: Published API For Chopstickpay Merchants Configuration: Server-to-server Version: 3.4 Status: Published Contents 1. Version Control... 1 2. Introduction... 2 3. Prerequisites... 2 4. Payment Submission Workflow...

More information

Cofred Automated Payments Interface (API) Guide

Cofred Automated Payments Interface (API) Guide Cofred Automated Payments Interface (API) Guide For use by Cofred Merchants. This guide describes how to connect to the Automated Payments Interface (API) www.cofred.com Version 1.0 Copyright 2015. Cofred.

More information

Single Sign-On Guide for Blackbaud NetCommunity and The Patron Edge Online

Single Sign-On Guide for Blackbaud NetCommunity and The Patron Edge Online Single Sign-On Guide for Blackbaud NetCommunity and The Patron Edge Online 062212 2012 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any

More information

CloudQR Software Usage Guide

CloudQR Software Usage Guide CloudQR Software Usage Guide 1 Document Release 17/09/2014 0.1 - Document Tracking Version ID User Changed By Dated Comments 1 David Morrison 18/01/2014 Initial draft created. 2 Thomas Morrison 27/01/2014

More information

Web Services Credit Card Errors A Troubleshooter

Web Services Credit Card Errors A Troubleshooter Web Services Credit Card Errors A Troubleshooter January 2014 This manual and accompanying electronic media are proprietary products of Optimal Payments plc. They are to be used only by licensed users

More information

Address Verification System (AVS) Checking

Address Verification System (AVS) Checking Address Verification System (AVS) Checking The Address Verification System (AVS) is a service provided by credit card Issuers intended to authenticate the Purchaser (Customer) as the authorized cardholder.

More information

Recurring Payments Service (FuturePay) Guide. Version 4.2 April 2013 Business Gateway

Recurring Payments Service (FuturePay) Guide. Version 4.2 April 2013 Business Gateway Recurring Payments Service (FuturePay) Guide Version 4.2 April 2013 Business Gateway Table Of Contents About this Guide... 4 Update History... 4 Copyright... 4 Introduction... 5 Enable the Service... 6

More information

Payflow Link User s Guide

Payflow Link User s Guide Payflow Link User s Guide For Professional Use Only Currently only available in English. A usage Professional Uniquement Disponible en Anglais uniquement pour l instant. Last updated: June 2008 Payflow

More information