Apply Now Sage Pay phone numbers 
Sage Pay - The new name for Protx

Home

Sage Pay Go
Bolt-ons
Tailored Solutions
Integrating Sage Pay
Existing Sage customers
Merchant services
Support centre & FAQs
Forum
Simulator

 

Integration Manual

The Integration Manual is designed to provide you will all the technical information
you need to integrate and set up your account with Sage Pay.





Different Integration options

An introduction into the three different methods to integrate and set up your account with Sage Pay.

Using the Simulator

If you are starting your integration from scratch and are not using a shopping cart, one of the best places to start, is the Simulator.

Integration Processes

There are 3 different methods of submitting a transaction with Sage Pay. This section provides an in-depth, step-by-step, information on how each of these methods work along with the required protocol for each payment method.

 

Step-by-step guide


Protocol


Going Live

Before you can start processing live transactions through your account with Sage Pay, there are some required steps which you need to perform to ensure that your account is all set up correctly with us.

Customising the Payment Pages

If you are using our Form or Server integration method, you are able to customise the payment page which your customers are directed to.

Setting up PayPal

We now provide the option to accept PayPal through your Sage Pay account.  This section provides the steps you need to take to set this up.

Setting up a Merchant Account

One of the first things you will need when processing transactions online will be a merchant account and a merchant number.

Shopping Cart Guides

If you have decided to integrate your website with Sage Pay using a shopping Cart, this section provides some guides on how to set up the most popular shopping carts with us.

 

Form Shopping Cart Guides

Server Shopping Cart Guides

Direct Shopping Cart Guides

Error Message Troubleshooting

If you come across any error messages in testing please find the status detail below.

Simulator

 

Downloads

Welcome to the Sage Pay downloads page. This section contains all the latest Sage Pay integration kits, supplied in all popular script languages. In addition to these kits you will find relevant integration documentation for all our integration methods, My Sage Pay admin user manuals, custom template options and the ability to download the Sage Pay logos and industry payment card images.

This page has been categorised by each Sage Pay Integration method - Please choose the product or area you are interested in and click the relevant ' ' symbol next to it to expand the download options for that particular product.

 


Form

 

Documents

The Form Protocol & Integration Guidelines document explains exactly how the Form Integration method works and contains the protocols a web developer needs to follow when integrating. This document can be downloaded by clicking the link below.

Form Protocol & Integration Guideline - Click Here

Integration Kits

Sage Pay provide example code in several languages to aid developers integrating the Form payment method - these integration kits should be used in conjunction with the Form Protocol and Integration Guide.

Click on the Integration Kit you require below:

ASP Integration Kit - Click Here
ASP.NET Integration Kit - Click Here
PHP Integration Kit - Click Here


Custom templates

Sage Pay provide all our vendors using the Form integration method with default payment pages but we also provide them with the facility to customise the payment pages so that the look and feel is similar to the vendor's website. The available payment page templates can be downloaded using the link below.

 

Custom Template Kit - Click Here

 

Server

 

Documents

The Server Protocol & Integration Guidelines document explains exactly how the Server Integration method works and contains the protocols a web developer needs to follow when integrating. This document can be downloaded by clicking the link below.

Server Protocol & Integration Guideline - Click Here

Because the Server payment method is a Server to Server based communication, vendors integrating this product have the ability to submit Refund, Repeat, Release and other transaction requests directly from their servers without having to log into their My Sage Pay account. This document can be downloaded by clicking the link below.

Server & Direct Shared Protocols Guideline - Click Here

Integration Kits

Sage Pay provide example code in several languages to aid developers integrating the Server payment method - these integration kits should be used in conjunction with the Server Protocol and Integration Guide.

Click on the Integration Kit you require below:

ASP Integration Kit - Click Here
ASP.NET Integration Kit - Click Here
PHP Integration Kit - Click Here

 

Custom templates

 

Sage Pay provide all our vendors using the Server integration method with default payment pages but we also provide them with the facility to customise the payment pages so that the look and feel is similar to the vendor's website. The available payment page templates can be downloaded using the link below.

Custom Template Kit - Click Here

Direct

 

Documents

The Direct Protocol & Integration Guidelines document explains exactly how the Direct Integration method works and contains the protocols a web developer needs to follow when integrating. This document can be downloaded by clicking the link below.

Direct Protocol & Integration Guideline - Click Here

Because the Direct payment method is a Server to Server based communication, vendors integrating this product have the ability to submit Refund, Repeat, Release and other transaction requests directly from their servers without having to log into their My Sage Pay account. This document can be downloaded by clicking the link below.

Server & Direct Shared Protocols Guideline - Click Here

Integration Kits

Sage Pay provide example code in several languages to aid developers integrating the Direct payment method - these integration kits should be used in conjunction with the Direct Protocol and Integration Guide.

Click on the Integration Kit you require below:

ASP Integration Kit - Click Here
ASP.NET Integration Kit - Click Here
PHP Integration Kit - Click Here

 

My Sage Pay

 

My Sage Pay Admin Account

The My Sage Pay User Manual explains all the functions and uses of the My Sage Pay Admin Account, from viewing your daily transactions to learning how to perform a refund via the Admin Account. This document can be downloaded by clicking the link below.

My Sage Pay user manual - Click Here

 

Customer Management Services account

The Customer Management Services (CMS) User Manual explains all the functions and uses of the CMS Account, from viewing your invoices to changing your billing address. This document can be downloaded by clicking the link below.

 

Customer Management Services Manual - Click Here

 

Logos & Images

 

If you would like to display our Sage Pay logos or maybe use any of the accepted credit card images on your website then you can get them from this download section. These logos and images can be obtained by clicking the link below - hover your mouse over the desired image, right click, and choose "Save Picture As".

Sage Pay Logos and Credit Card images

Fraud Prevention

 

User manual

The Sage Pay Fraud Prevention Advice Guide provides vendors with an excellent reference on how to deal with on-line fraud and advice on how to successfully manage the security of your web business. This document can be downloaded by clicking the link below.

Sage Pay Fraud Prevention - Click Here

The Sage Pay AVS/CV2 and 3D Secure Rulebase Guide provides vendors with a manual on how to setup both AVS/CV2 (security code and billing address/postcode) and 3D Secure (Verified by Visa / Mastercard securecode) rulebases on their Sage Pay Account.  This document can be downloaded by clicking the link below.

Sage Pay Rule Base Guide - Click Here

Simulator

 

Glossary

 

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V W  X  Y  Z

 

 

A

   
ABORT A Status value returned in the Response Crypt field contents for Form transactions, or in the Notification results for Server transactions.  The Transaction could not be completed because the user clicked the CANCEL button on the payment pages, or went inactive for 15 minutes or longer. 
   
Account Management Sage Pay provides an account management service for some of our larger merchants, available on request. If you as the vendor signs up to this service you can benefit from a dedicated account manager who will take care of your Sage Pay account to ensure your enquiries are dealt with straight away.
   
Account Parameters An option within the Administration section of My Sage Pay  The Account Parameters screen allows the vendor to activate, deactivate or modify settings on their Sage Pay account with immediate effect. 
   
AccountType An optional flag for Direct vendors to use in their Transaction Registration Post to tell the Sage Pay System which merchant account to use for a transaction in situations where more than one type of merchant account is set up for their Sage Pay vendor account. If omitted, the system will use E (Ecommerce), then M (MOTO), then C (Continuous Authority) by default.  See page 42 of the Direct Protocol and Integration Guide.
   
Acquiring Banks An acquiring bank is another term used to describe a merchant bank.  In order to use the Sage Pay service, the vendor needs to obtain a merchant account with one of the merchant banks that we work with.  Sage Pay is an approved payment solutions provider for the majority of UK banks: for a full list refer to the KEY.  
   
Actinic Secret Key The Actinic Secret Key is the 12-character string that will look something like:
KotwWr56RtaW.  The Actinic Secret Key is a unique password provided to all Actinic vendors when a Sage Pay test account is created.
   
Additional services Sage Pay provides a range of additional services that can be added to your package on request. For example, they can take payments through PayPal, request an account manager or sign up for priority support. Details on request.
   
Address Verification Service See AVS
   
Admin Area The Admin area is now known as My Sage Pay, within this area you can manage your accounts.
   
Administration See Liquidation
   
Alliance and Leicester (now Elavon) A Merchant Acquiring Bank. 
   
American Express American Express is both a card issuing and an acquiring bank. 
   
AMEX The value to pass in the CardType field of the Transaction Registration Post to process an American Express transaction (Direct only).
   
Amount A mandatory field to be passed in the Transaction Registration Post.  It is the total monetary value for the Transaction.  Must be positive and numeric, and may include a decimal place where appropriate. Minor digits should be formatted to two decimal places. e.g.5.10, or 3.29. Values such as 3.235 will be rejected.
   
API Application Programming Interface allows different server based applications to process card details by linking together. Sage Pay equivalent is Direct.
   
Application Form https://support.sagepay.com/apply/default.aspx?ire=1" target="_blank
   
Apply3DSecure An optional flag that can be used in a Transaction Registration Post to fine tune the 3D Secure checks and rule set that has been defined at a transaction level. .
   
ApplyAVSCV2 An optional flag you can use in your Transaction Registration Post to fine tune the AVS/CV2 checks and rule set you’ve defined at a transaction level. This is useful in circumstances where direct and trusted customer contact has been established and you wish to override the default security checks.
   
ATTEMPTONLY A 3DSecureStatus value (Direct only).  The cardholder attempted to authenticate themselves but the process did not complete. A CAVV is returned, therefore a liability shift may occur for non-Maestro cards. Please refer to your Merchant Agreement.
   
AUD Australian Dollars
   
AUTHENTICATE Authenticate and Authorise is a payment type that is available to you as a Sage Pay merchant who wishes to delay settlement of your orders for longer than 6 days. It is also useful for you if you do not know the exact price of the goods at the time an order is placed. Unlike normal Payment or Deferred transactions, AUTHENTICATE transactions do not obtain an authorisation at the time the order is placed. Instead the card and card holder are validated using the 3D-Secure mechanism provided by the card-schemes and card issuing banks. The transaction must receive full 3D-Authentication for the transaction to be 'Authenticated'. If 3D-Authentication is not available, the transaction is REGISTERED.
   
AUTHENTICATED A Status value returned in the Sage Pay response to the Transaction Registration Post or Callback Post. The 3D-Secure checks were performed successfully and the card details secured at Sage Pay.
   
Authorisation Authorisation is obtained from the banks the moment the card details have been either forwarded to Sage Pay systems or entered by the shopper on the Sage Pay secure payment pages. Once a transaction has been authorised, the shopper’s card is shadowed for the amount that the authorisation was obtained for. This means that for a certain period of time, those funds (transaction amount) are reserved and cannot be spent elsewhere by the shopper.
   
AUTHORISE When you are ready to fulfil an Authenticated order, login to My Sage Pay, select the Authenticated/Registered transaction and click 'Authorise' to receive the funds.You will can Authorise any amount up to 115% of the value of the Authenticated/Registered transaction, and use any number of Authorise requests against an original transaction so long as the total value of those authorisations does not exceed the 115% limit, and the requests are inside the 90 days limit.
   
Automated Posts If you are a Server/Direct vendor youcan choose to automate many of the daily procedures, (such as (Releasing and Aborting Deferred transactions) by sending an HTTPS POST containing a collection of Name=Value pairs directly to the Sage Pay system (rather than the having to log into My Sage Pay to perform the tasks manually).
   
AVS Address Verification Service.  The Address Verification Service checks the shopper's address and postcode, as entered at the point of order. The numeric data (billing house/flat number and numerics in the postcode) of the shopper's billing address and postcode is checked against the details of the card issuer.
   
AVS/CV2 and 3D Secure Rule Base Guide http://www.sagepay.com/downloads/docs/protxrulebaseguide.pdf
   

Back to the Top

B

   
B2B Business to Business. Supplier customer relationship is between two businesses.
   
Bank Of Ireland (now Elavon) A Merchant Acquiring Bank. 
   
Bank Of Scotland A Merchant Acquiring Bank. 
   
Bank Transfers (Giros) See Giros
   
Barclays Merchant Services A Merchant Acquiring Bank. 
   
Base 64 encryption A simple method used to encrypt data in several web scripting languages.  Base 64 literally means a positional numbering system using a base of 64.  It is the largest power of two bases that can be represented using only printable ASCII characters. This has led to its use as a transfer encoding for email among other things. All well-known variants of base 64 use the characters A-Z, a-z, and 0-9 in that order for the first 62 digits but the symbols chosen for the last two digits vary considerably between different systems that use base 64.
   
BASKET An optional field the vendor can pass in the Transaction Registration Post to supply details of the shopper's order.  The format of the Basket field can be found in the Protocol Guide.
   
Batch (settlement) A collection of transactions that are sent to the Merchant Acquiring bank.
   
Batch Detail Report (Bank Settlement Details) This report within the My Sage Pay lists the contents of the selected batch for a specified acquirer.
   
Batch ID (settlement) A identification number used to identify a batch for settlement purposes. Used specifically in a Batch Detail Report.
   
Batch Settlement Report (Monthly) This report within the My Sage Pay area lists the Settlement Batch totals for each acquirer you work with, sent in the select month.
   
Batch Settlement Report (Weekly) This report within the My Sage Pay area lists seven days worth of Settlement Batch totals for each acquirer you work with. 
   
Bespoke Integration When an electronic payment solution requires an experienced programmer, a bespoke integration may be necessary.
   
BillingAddress An optional field you can pass in the Transaction Registration Post (field becomes compulsory if AVS checks are switched on).  You must ensure the Post code is not included or Address Verification checks will fail.
   
BillingPostCode An optional field you can pass in the Transaction Registration Post (field becomes compulsory if AVS checks are switched on).
   
Blocked Card Ranges and Issuing Countries A section within the Account Parameters you can use to block payments from possible fraudulent users by restricting payments by card range and the card issuing country. These blocks should be used with caution and only if required by repeated fraud attempts. 
   
Blocked IP Addresses and Country Codes You can block payment requests from IP Addresses and Countries which have been listed in the Account parameters section of the My Sage Pay.  All customer requests from these countries or specific IP ranges will be denied at transaction registration. These blocks should be used with caution and only if required by repeated fraud attempts.
   
BOS See Bank Of Scotland
   
Browser A browser or web browser is a software application which enables a user to display and interact with text, images, videos, music, games and other information typically located on the World Wide Web.
   
Bulk Release A feature in My Sage Pay area which allows you to release multiple Deferred transactions.

Back to the Top

C

   
CAD Canadian Dollars
   
Callback The callback is the URL used in a transaction to contact you with a response.  Form redirection URLS may also be referred to as a call back.
   
CANTAUTH A 3DSecureStatus (VSP Direct only).  This normally means the card Issuer is not part of the scheme.
   
Capture amount  Put simply, the 'Capture' is PayPal's terminology for a 'Release' or 'Authorise' request.  The 'Capture' amount only refers to PayPal transactions.  If you are experiencing problems with authorising Released transactions, read the additional info section:
   
Card Authenticate Validation Value (CAVV)  This is the value passed back in the PARes (Visa only).  If a CAVV value is provided, the transaction has been 3D-Secured, and a liability shift occurs should the transaction later be found to be fraudulent.
   
Card Issuer The financial institution that supplies customers with credit and/or debit cards for their personal/company use.
   
CardType

A compulsory field, if you are a Direct vendor, must be included in theTransaction Registration Post. The following cards can only be accepted if you have additional merchant accounts with those acquirers:

AMEX,

DINERS

JCB

 

Other cards accepted through the Sage Pay system are:

Visa

Visa Debit

Visa Electron

MasterCard

UK Maestro

Laser

International Maestro

Solo

   
Card Verification Value (CV2)  See CV2
   
Cardholder authentication The process of checking the identity of a cardholder online. When using MasterCard SecureCode and Verified by Visa, the cardholder is prompted to enter their pre-registered password, which is verified against their issuing bank's records at the time of the transaction (see 3D Secure).
   
Cardholder present (CP) A transaction where you have physical access to the payment card, i.e. in a point-of-sale environment. Also known as face-to-face.
   
Cardholder not-present (CNP) A transaction where you do not have physical access to the payment card. Examples include transactions over the Internet (Ecommerce), telephone, fax or by mail order (MOTO).  
   
Ceiling Limits Upper price level for individual transactions, Sage Pay is set at 100,000 
   
Chargeback A sum of money deducted by a credit card company from your account to cover losses for disallowed or fraudulent transactions.  This transaction dispute procedure is usually initiated by a cardholder/shopper disputing a transaction.
   
CHF Swiss Francs
   
CMS (Customer Management Services) The Sage Pay Customer Management Services (CMS) allows you to edit the details of your Sage Pay account.  You can change or add billing contact details, view your account history, download or pay outstanding invoices, or edit the bank details from where your Direct Debit is taken.
   
Company Number Each Natwest Streamline Merchant Number will be accompanied by a 6 digit Company Number, which is used by the bank to identify a merchant on its system.  
   
Continuous Authority

Also called Periodic billing / Recurring Payments.  Continuous Authority applies to you if you process regular, recurring or subscription payments (only available with Visa, Visa Debit and MasterCard - Natwest Streamline also allow Visa Electron).  In order to process these payments a Continuous Authority merchant account is required from your Merchant Bank.

   
Country-Specific Cards Unique card types specific to individual countries or regions:
Carte Bleue (France)
CartaSi (Italy)
Dankort (Denmark)
ideal (Netherlands)
Laser (Ireland)
Nordea Solo (Sweden)
Nordea Solo (Finland)
POLi (Australia)
Sofortueberweisung (Germany)
   
Cross Border Transactions occurring between countries or jurisdictions.
   
Currency Codes Three-letter currency code to ISO 4217, for example: GBP.  The currency must be supported by your merchant bank.
   
Custom Templates Sage Pay provide all our Form / Server vendors with default payment pages but we also provide them with the facility to customise the payment pages so that the look and feel is similar to the vendor's website.
   
CustomerEMail An optional field you can send in the Transaction Registration Post (Form only).  If an email address is provided, the customer will be e-mailed on completion of a successful transaction (but not an unsuccessful one).
   
Customer Service / Customer Support Sage Pay strives to provide the best customer service in the payments industry.  Our amazing UK based customer support teams provide telephone and email support 24 hours a day 7 days a week. This service is included in all of our packages at no extra cost.
   
CV2 The CV2 value (also known as: CVV/security number) is the last 3 digits of the number on the signature strip on the back of all debit and credit cards including JCB and Diners club cards. Amex cards differ and have a 4 digit number on the front of the card. In order to enter the correct number the person placing the transaction must either be in possession of the card, or must have made a note of the CV2 number whilst handling the card.
   
CZK Czech Koruna
   

Back to the Top

D

   
Daily Summary Report This report within My Sage Pay summarises all transactions by User Name, Transaction Type and Currency for the selected day.
   
Daily Transaction Report This report within My Sage Pay is a printer friendly version of the Daily Transaction List.
   
DATA NOT CHECKED A possible response to the AVS and CV2 checks.  This means that the bank has not been able to check the details of the transaction (for example, if the address is a foreign address).  The Data Not Checked result is displayed as an amber question mark within the My Sage Pay  
   
DEFERRED Deferred payments allow you to hold onto an authorised transaction, without taking any money from the Shopper's credit card and then send it for settlement at a later date by Releasing the transaction.  You can Release ONLY ONCE and ONLY for an amount up to and including the amount of the original DEFERRED transaction.
   
DINERS The value to pass in the CardType field of the Transaction Registration Post to process a Diners Card transaction (Direct only).
   
Diners Club Diners Club is both a card issuing and an acquiring bank. 
   
Direct Debit This is an electronic payment system that allows Sage Pay to request directly from the bank of the customer monetary amounts due each month for the services provided by Sage Pay. You must complete a direct debit mandate to ensure your bank receive sufficient authorisation to allow Sage Pay to collect payment.
If you are new vendor you will need to complete the online Direct Debit form when completing your application, or if you are an existing vendorb you can log into your CMS account to edit the details.
   
Direct Refunds Direct Refunds are the Sage Pay option that allows you as a vendor to refund any card for any amount. This means that the you would be able to refund any card regardless of whether the original transaction was processed via Sage Pay or not. This option is not given to all Vendors and must be sanctioned by the your acquiring bank, in writing, before we will consider setting this up.  The vendor will require an additional Merchant Number to process Direct Refunds.
   
DKK Danish Krone

Back to the Top

E

   
ECI The Electronic Commerce Indicator indicates the 3D Secure status of a transaction.  This value is obtained from the Card Issuing Bank.  Sage Pay convert the ECI results into coloured flags in My Sage Pay to help vendors clearly and simply identify the 3D Secure result.  The ECI Value is displayed in the PARES section of the TxInfo pages.
   
Ecommerce Allows the online purchasing of goods or services by credit cards or PayPal.
   
Elavon A Merchant Acquirer for Alliance & Leiecester and Bank of Ireland vendors.
   
Encryption The process of converting data into a format that prevents casual observers from deciphering the information.  Also see XOR Encryption.
   
Encryption Password  A password issued to Form users to allow them to encrypt the payment data before it is sent to Sage Pay.  Usually 16 characters.
   
Enrollment The process whereby Visa and MasterCard cardholders register with their issuing bank to participate in the 3D - authentication programmes.
   
EPDQ Barclaycard online solution for accepting cards over the internet.
   
ERROR A Status value returned in the Sage Pay response to the Transaction Registration Post or Callback Post.  A problem occurred at Sage Pay which prevented transaction completion. An Error value returned in the 3DSecureStatus field (Direct only) indicates a problem with creating or receiving the 3D-Secure data. This should not occur on the live environment.
   
Escalations Team  When an issue is unable to be resolved by a 1st Line Team member or requires more indepth investigation, it is passed to the Escalations Team for resolution.  
   
EUR Euro
   
Euroconex See Elavon.
   
Expired Card  A card on which the embossed, encoded, or printed expiry date has passed.  The bank will reject transactions which use an expired card.
   
Expiry Date  The date printed on the debit/credit card that signifies when the card will expire and can no longer be used.  The ExpiryDate is also a optional field included in the Transaction Registration Post (Direct only).  The ExpiryDate value should be passed in MMYY format i.e. 1209 for December 2009.
No / or – characters should be included.

Back to the Top

F

   
Finance Team Our finance team provides reporting to the wider Sage environment and to our management team. We work hard chasing bad debts and managing closed accounts. If you have a query regarding their invoice or want to close your account, you should be passed through to this department.
   
Find a Transaction This page within My Sage Pay can be used to find a specific transaction if you are having trouble finding it in the main transaction List screen.
   
Fixed IP Address A fixed IP address is the number (in the format nnn.nnn.nnn.nnn) that is assigned to a computer/Server by an Internet Service Provider (ISP) to be a permanent address on the internet, allowing it to be easily identified and located.  To use our Server or Direct product, a fixed IP address is required to ensure server-server communication is via a secure and trusted link.
   
Flag (3d secure) See ECI
   
Forum An area intended for the use of Sage Pay vendors to discuss topics relevant to trading online using the Sage Pay payment gateway.
   
Fraud Fraud is deception made for personal gain or to damage another individual.
   
Fraud Checking Options Sections within the Account Parameters where you can activate the 3D Secure and AVS/CV2 checks and determine the rule base to automatically reject transactions.
   
Fraud Prevention Advice Guide http://www.sagepay.com/developers.asp#downloads
   

Back to the Top

G

   
Gateway The technical term used when describing the path for the authorisation via a merchant bank. For example Payment Gateway.
   
GBP British Pound
   
Gift Aid Setting this field in the Transaction Registration Post means the customer has ticked a box on the payment page to indicate they wish to donate the tax.  Only of use if your account is Gift Aid enabled.  Form field = GiftAid, Server field = AllowGiftAid, Direct field = GiftAidPayment.
   
Go live process http://www.sagepay.com/developers.asp#integration
   
Grouping If you haves 2 or more Sage Pay accounts which use the same Merchant Number, or incorporate the same business within different Merchant Numbers, these accounts can be 'grouped' for billing purposes (for a £50 plus tax Admin fee).  Once two Sage Pay accounts are ‘grouped’ you will only pay one fee to Sage Pay from this point onwards.  This means you will have one Direct Debit agreement which encompasses both accounts.

This is not available for Irish customers.
   

Back to the Top

H

   
HBOS Also known as the Halifax Bank of Scotland group. 
   
Homepage The first page, which is usually a welcoming or organising page, on an internet site.
   
Hosting A term used for storing and maintaining files, email or domains on a server that is connected with the Internet.
   
Hosting-Dedicated  A web server which holds the web pages and e-commerce content of a single client. Large companies and those whose business is entirely dependent upon the web usually prefer a fully dedicated setup which is fast and reliable.
   
Hosting-Shared  A web server which holds the web pages of several clients. Shared hosting is a cheaper e-commerce solution for consumers and small stores with relatively little traffic.
   
HSBC

A Merchant Acquiring Bank. 

   
HTML Hypertext Markup Language. A set of code that determines how an E-commerce store and a web page will appear, including graphics, links, and text characteristics. Other code sets that build on HTML include dHTML, VRML, and XML.
   
HTTP Hypertext Transfer Protocol. This is the protocol most often used to transfer information from Web servers to browsers, which is why Web addresses begin with "http://." 
   
HTTPS Hypertext Transfer Protocol over Secure Socket Layer or HTTP over SSL. URL's beginning with HTTPS indicate that the connection between client and browser is secure and encrypted using SSL.
   
HTTPS Proxy  Shows the result URL through an existing secure connection, instead of redirecting the shopper directly.
   
Hyperlink An element in an electronic document that links to another place in that same document, or to an entirely different document.
   

Back to the Top

I

 

Back to the Top

J

Back to the Top

K

   
Key Accounts The Key Accounts Team is available for high volume and high transaction vendors, providing a dedicated point of contact for the top 250 vendors for technical, sales, and account queries.
   
Kits Sage Pay provide example code in several languages to aid developers integrating our products - these integration kits should be used in conjunction with the Protocol and Integration Guide. The available integration kits can be downloaded from the Support website.
   

Back to the Top

 

L

   
Language A programming language can be used to control the behaviour of a machine, particularly a computer, to perform specific tasks.
   
Laser Sage Pay is now able to support this Elavon card type. Please see the Merchant Bank section of our technical support website for more details.
   
Liability  In regards to 3D Secure, you as a vendor may not be held liable for a fraudulent transaction which has received 3D Secure Authentication. 
   
Line item details Sage Pay is a 'Business to Consumer' service not a 'Business to Business' service and so does not support the VGIS module (line item detail), therefore we are unable to process purchasing or corporate cards with this feature.
   
Linux A trademark for an open-source version of the UNIX operating system.
   
Liquidation/Administration In legal terms, liquidation refers to the process by which a company (or part of a company) is brought to an end. This usually occurs because the company has failed in its endeavours to generate profits and cash flows and therefore can no longer afford to trade.
   
Live Account In order to go live all of the following criteria MUST be met:

· You have completed the Online Direct Debit sign-up form to allow Sage Pay to invoice you for services each month.
· Sage Pay have received confirmation from your Merchant Acquiring Bank that your Merchant Number has been correctly set up and Terminal ID’s have been successfully allocated.
· You have completed testing all your transaction types against the Test Server account.
· You have logged into the My Sage Pay system on the Test Server, created a user for yourself and viewed and refunded some of your Test transactions as that user.
NB Your account will not be set Live until all actions have been completed, however you will be charged as soon as we have confirmed the merchant number with your merchant bank and it is set up for use with Sage Pay.
   
Live Server In order to accept real transactions, you must be pointing to the Live Server, which is connected to the banks via X25 lines.
   
Live Service The Live Service Team look after the live system as well as our internal office based systems and prepare for future system updates. The team are also responsible for ensuring that our systems remain PCI compliant, and for supporting First Line Support and the Escalations Team when needed.
   
Lloyds TSB Cardnet  A Merchant Acquiring Bank. You will require a 15 Digit Merchant Number starting 5404. 2 TIDs are provided by Sage Pay.
   
Logo You can provide us with your Company Logo, which will then appear on the payment pages.
   
LUHN check The Luhn algorithm or Luhn formula, also known as the "modulus 10" or "mod 10" algorithm, is a simple checksum formula used to validate a variety of identification numbers, such as credit card numbers. If the shopper receives a LUHN check error, it means the card number entered on the payment pages does not validate. Then yourself or the shopper should check to ensure they have entered the number correctly (and only those numbers on the front of the card) and try again.
   

Back to the Top

M

 

Back to the Top

N

 

Back to the Top

O

   
OK A Status value returned in the Sage Pay response to the Transaction Registration Post or Callback Post. An OK Status indicates that the transaction was authorised by the bank.

An OK value returned in the 3DSecureStatus field indicates the 3D-Authentication step completed successfully. If the Statusfield is OK too, then this indicates that the authorised transaction was also 3Dauthenticated and a CAVV will be returned. Liability shift occurs.
   
OmniPay A processing platform for Lloyds TSB Cardnet multicurrency transactions.
   
Operations Team

 

The Operations Team co-ordinate and manage all necessary procedures to maximise operational performance. They also implement necessary processes to minimise risk and reduce the impact of performance interruption
   

Back to the Top

P

   
Packages Sage Pay provides three different packages depending on transaction volume:

*Sage Pay Go: This is the complete online payment service that is simple to implement.

*Tailored Solutions: Unique payment solutions tailored specifically to your business.
   
Partners Sage Pay specialises in providing secure card payment solutions. We work with a diverse range of business partners that provide integrated solutions to add value for our mutual customers.

Most of our partners provide web design, web development, ecommerce or shopping cart solutions. You can use these pages to find a solution provider or to check whether your chosen solution integrates with Sage Pay.
   
PAYMENT This is the standard real-time method of registering a transaction, which simply authorises and settles automatically within 24 hours.k
   
Payment Gateway Sage Pay is a Payment Gateway, also known as a Payment Service Provider (PSP). A Payment Gateway provides the secure link between your website and your merchant bank to ensure that your customers’ card details remain secure throughout the transaction process.
   
Payment Service Provider (PSP) Sage Pay is a Payment Service Provider (PSP), also known as a Payment Gateway. A Payment Service Provider provides the secure link between your website and your merchant bank to ensure that your customers’ card details remain secure throughout the transaction process.
   
PAYMENT TYPE This is also known as a Transasction Type, or TxType. Sage Pay offers a number of different methods of registering a transaction and completing the payment. Essentially, there are two stages to every transaction: Authorisation and Settlement.
   
PAYPAL PayPal is a safe, easy way to pay and get paid online. The service allows anyone to pay in any way they prefer, including through credit cards, bank accounts, buyer credit or account balances, without sharing financial information. Sage Pay has integrated with PayPal giving vendors the opportunity to add PayPal as a payment option on their payment pages.
   
PayPal Integration Sage Pay has integrated with PayPal giving vendors the opportunity to add PayPal as a payment option on their payment page. If the vendor is a certified PayPal Business Account user and would like to use the Sage Pay payment pages, this facility can be included in the package free of charge. Standard PayPal transaction fees apply.
   
PCI The Payment Card Industry Data Security Standard (PCI DSS) was set up by Visa and MasterCard to standardize the security surrounding the card payments industry. Sage Pay is a level 1 PCI compliant Payment Service Provider. If you accept payments by credit and debit card you will need to comply with the rules set out by PCI DSS. If you use our Form or Server solution you are covered for PCI under the Sage Pay approval. If you plan to use our Direct solution you will need to make sure that you are PCI compliant. 
   
Periodic Billing See Continuous Authority
   
Port In computer networking, the protocols of the Transport Layer of the Internet Protocol Suite, most notably the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP), but also other protocols, use a numerical identifier for the data structures of the endpoints for host-to-host communications. Such an endpoint is known as a port and the identifier is the port number. Sage Pay vendors need to allow Ports 80 and 443 in order to communicate with our servers (on Simulator/Test/Live).
   
Pricing policy Sage Pay offers different pricing packages depending on your transaction volume.
   
PSP  Payment Service Provider
   
Priority Support Sage Pay provides Priority Support as an additional service, available on request. If you would like to ensure that your enquiries are dealt with straight away, you can receive guaranteed response times through this service. Details are available on request.
   

Back to the Top

Q

Back to the Top

R

   
RBS Royal Bank of Scotland
   
Real-time Credit Card Processing  This is the on-line authorisation of a credit card number in real time informing the merchant that the card has been approved. A real-time payment is used by our systems as the default option. There are two stages to a real-time payment: authorisation and settlement.
   
Receipt Contrary to the traditional meaning, a receipt is not an indication of physical paperwork issued. Rather, a receipt indicates that a customer has fulfilled their obligation by settling outstanding funds due for payment by Sage Pay.
   
Recurring Payments  Also known as Periodic billing / Continuous Authority Payments. Regular, usually monthly, transactions used by subscription websites such as magazine subscriptions, membership payments. In order to process these payments a Continuous Authority merchant account is required.
   
RedirectURL This is a fully qualified URL to which you would like the customer to be redirected to on completion of a transaction (Sage Pay Server only). The RedirectURL field should be included in the acknowledgement of the Notification Post. The value should include the http:// or https:// header. The URL supplied will usually depend on the Status of the transaction.
   
Referral This occurs when the shopper's bank would like to perform further security checks on the card before authorising the transaction, or would like to speak to the shopper directly before allowing the authorisation to be processed.
   
REFUND A Refund is the reimbursement of funds for any goods or services which the shopper has paid for. If the transaction has already been sent for settlement, then you will need to perform a refund on the transaction. This will send the merchant acquiring bank a refund request to credit the shopper's account and transfer the funds back into their account. A refund indicates Sage Pay have made payment to a customer either to rectify amounts overpaid by the customer or to refund credit notes that will not be used against future invoices.
   
Register Register and Authorise is a payment type that is available to Sage Pay merchants who wish to delay settlement of their orders for longer than 6 days, but do not have 3D Secure available on their account, or are processing the transaction as a MOTO transaction. The card details are registered at the time the order is placed, but are not sent for authorisation until requested by the merchant. When a transaction is processed as an AUTHENTICATE and 3D Secure checks cannot be performed (either because the transaction is a MOTO transaction, 3D Secure checks are not active on your account, or the shopper's card is not part of the 3D Secure scheme), the transaction is held in a Registered state. An 'AUTHORISE' request must still be sent in order for you to receive the funds.
   
REGISTERED A Status value returned in the Sage Pay response to the Transaction Registration Post or Callback Post. 3D-Secure checks failed or were not performed, but the card details are still secured Sage Pay.
   
REJECTED A status value returned in the Sage Pay response to the Transaction Registration Post or Callback Post. The Sage Pay System rejected the transaction because of the fraud screening rules that you have set up on your account.
   
RELEASE A Release allows you to release the funds reserved from a previously Deferred payment. If a Deferred transaction is not released the customer will never be charged for the transaction. A request to release an authorised Deferred transaction sends the transaction for settlement within that day's batch settlement file to your acquiring bank affirming that you now wish to complete the transaction process and take payment from the shopper's account.
   
REPEAT This is a transaction type that is used to repeat a previously settled transaction. A repeat can be performed for a different amount to the original transaction. This payment type is available to Sage Pay merchants who wish to take a one-off repeat payment, for example if a customer places another order, or decides to extend an existing order. If you would like to make one-off repeat payments through Sage Pay you can do so provided this payment type has been enabled on your account.
   
Reporting My Sage Pay offers extensive reporting functions to allow you to view transaction and batch settlement reports. Our comprehensive reporting and reconciliation tool is included with each of the Sage Pay packages at no extra cost. My Sage Pay enables you to manage your transactions and run bank settlement reports to reconcile payments directly with your bank account.
   
Reporting Password  Also known as the Administrator password, this password allows the account administrator to log into My Sage Pay.
   
Rule Base A Rule Base allows you to accept or reject transactions based on their fraud screening results. This saves you from manually checking the results of each transaction and allows you to tailor the way in which AVS/CV2 and 3D Secure authentication responses are handled on your account.
   

Back to the Top

S

   
Sage (UK) Limited Sage Pay is a division of Sage (UK) Limited, a subsidiary of the Sage Group plc. Sage is a leading supplier of business management software and services to 5.4 million customers worldwide.
   
Sage Line 50 Sage Accountancy software is a software package that helps you to improve your cash flow. It also helps you manage your other day-to-day finances - everything from VAT returns to year-end accounts. This software is now integrated with Sage Pay. You will require a MOTO Merchant Number to use Sage 50.
   
Script This is an executable list of commands created by a scripting language.
   
Script Engine This interface provides the capability to interconnect any suitably written application or server with any scripting language.
   
Secure Sockets Layer See SSL
   
SecurityKey This is a ten character long alphanumeric string used for confirming the MD5 hash signature in the notification post. This value is used to allow detection of tampering with notifications from Sage Pay Server. It must be kept secret from the customer and held in your database. This key is only present if Status is OK.
   
SEK Swedish Krona
   
Service Selector If you need help deciding which package is right for you, we will recommend a package based on the information you provide.
   
Session A session refers to all the connections that a single client might make to a server in the course of viewing any pages associated with a given application. Sessions are specific to both the individual user and the application. As a result, every user of an application has a separate session and has access to a separate set of session variables.
   
Settlement In order for you to receive funds into their bank account, the transactions must be sent for settlement with their merchant bank. Sage Pay sends a batch settlement file to each merchant bank on a daily basis, containing all the authorisation codes obtained that day. It then takes the banks 3 to 4 days to pay this money into your business bank account, depending on the agreement you have with your bank.
   
Shared Server If a website is hosted by an Internet Service Provider (ISP) or a third-party hosting company, it is more than likely that you are sharing server space with other websites. This means that it is hosted on a shared server. If you are in this situation you should use our Sage Pay Form product. If you wish to use our Server or Direct solutions, it is advisable that you have your own dedicated server with a fixed IP address.
   
Shopping Cart A shopping cart is a piece of software that is used to create an online “storefront” or an ecommerce website. Shopping carts are generally very easy to use and will allow you to do everything from designing the look and feel of your website, to handling stock and shipping transactions. Sage Pay is pre-integrated with many of the major shopping carts.
   
Showpost If you are having problems debugging your scripts, you can run a test against our 'show post' address. This will post your transaction to a page that we can see at this end, allowing us to view all the information you are posting to Sage Pay during a single transaction, and identify any potential problems with your Post.
   
Simulator The Simulator is an expert system that emulates the Sage Pay systems and allows the vendor to develop their site to correctly send and process the messages exchanged between their site and ours. The Simulator provides more detailed feedback of any errors or issues than the real Direct system, allowing the vendor to debug and enhance their code.
   
SLA Service Level Agreement.
   
Small Business Service A package for small businesses that are likely to process under 1,000 transactions per quarter. Vendors who fall into this category will be charged €25 per month (+VAT) with no other fees.
   
SME Small and Medium-sized Enterprise
   
Software Development Team The Software Development team are responsible for development and support of the Sage Pay IT systems (excluding the payment gateway itself). Our team provides IT system support to the sales and marketing, finance and support teams as well as providing external systems for our customers, partners and vendors.
   
SOLO The value to pass in the CardType field of the Transaction Registration Post to process a SOLO transaction (Direct only).
   
SQL A standard interactive and programming language for querying and modifying data and managing databases.
   
SSL A protocol designed by Netscape Communications Corporation to provide encrypted communications on the Internet. SSL is layered beneath application protocols such as HTTP, SMTP, Telnet, FTP, Gopher, and NNTP and is layered above the connection protocol TCP/IP. It is used by the HTTPS access method.
   
Standard Payment Terms Sage Pay standard payment terms are 14 days from invoice date.
   
StartDate An optional field sent in the Transaction Registration Post (Direct only).  A Start Date becomes compulsory for some Maestro, SOLO and Amex cards.  The start date MUST be in MMYY format i.e. 0699 for June 1999. No / or – characters should be included.
   
Status Once the transaction has been sent to the bank for attempted authorisation, Sage Pay will respond with information about the transaction. The Status is one of the fields Sage Pay passes back in response to the Transaction Registration Post.
   
StatusDetail Human-readable text providing extra detail for the Status message.
   
Streamline See Natwest Streamline
   
Sub-net mask A Subnet is a portion of the network's computers and network devices that have a common, designated IP address routing prefix.  Adding a Subnet mask allows you to identify which part of an IP address is reserved for the network, and which part is available for host use.  
   
SuccessURL It is the URL of the page/script to which the shopper is redirected if the transaction is successful. You may attach parameters if they wish. Sage Pay Form will also send an encrypted field containing important information appended to this URL.
   
Surcharge An amount charged by Sage Pay in the absence of a direct debit agreement. If Sage Pay collect payment manually (BACS/Credit Card or by Cheque), an administration fee of £5 plus VAT is chargeable to the customer.
   
Style Sheet Instructions for the layout of a document, such as the type faces to be used, point size of headers, placement of footers, etc., in order to maintain consistency throughout the document (for example, they are used in the Sage Pay Custom Templates Kit).
   

Back to the Top

T

   
TAS TAS Payment Services provide a range of solutions allowing you to process secure credit card and debit card payments. The service allows customers to accept credit and debit card payments from within TAS BOOKS.
   
Templates The templates surround each page allowing for standardisation. It remains constant throughout the site as the shopper browses through the store. Sage Pay provides all our Sage Pay Form vendors with default payment pages but we also provide you with the facility to customise the payment pages so that the look and feel is similar to your website. The available payment page templates can be downloaded from the downloads section of the Support website.
   
TermUrl  Also known as the Terminal URL and is the URL that you would like your shopper to be returned to after 3D-authentication has occurred (Direct only). Once the user has completed their 3D-authentication, their Issuing Bank will redirect the customer back to the TermUrl supplied in the Post sent to the ACSURL.
   
Terminal ID  A Terminal ID (TID) is a unique identifier that recognises Sage Pay as your Payment Service Provider. TIDs are numbers assigned by Sage Pay to identify a specific vendor, these numbers are then sent to your merchant bank. Two TIDs are typically assigned to each merchant web site or business unit.
   
Termination Fees A charge levied when you wish to cancel your account with Sage Pay. As part of the Sage Pay standard terms and conditions of sale, we require a minimum of 3 months service fees payable if you wish to close their account.
   
Test Account  An account that enables a merchant to test integration with the payment service.
   
Third Party Processor  A company that processes transactions on behalf of banks or other participants to the transactions.
   
Ticketing System  A web based email interface that allows the Technical Advisors to view Sage Pay customer emails and answer them accordingly.
   
Time out A pre-set time period during which a given computer task must be completed or the task is cancelled. A time out can cause a transaction to fail if your server does not respond to Sage Pay during the set session length or the authorisation from the bank takes too long.
   
Traffic The amount of activity over a communication system during a given period of time. Usually this is the measurement of the amount of visitors to a website.
   
Transaction An agreement between a buyer and a seller to exchange an asset for payment.
   
Transaction Process There are a number of stages involved in the transaction process, from securely processing customer’s card details to sending the funds for settlement with the merchant bank.
   
Transaction Registration Post For Sage Pay Form transactions, the final confirmation page on your web site should contain an HTML FORM with the Action set to the Form submission URL and 4 hidden fields as part of that Form (VPSProtocol, TxType, Vendor and Crypt). For Server and Direct transactions, this is performed via a HTTPS POST request, sent to the initial Payment URL. The details should be URL encoded Name=Value fields separated by ‘&’ characters.
   
Transaction Type  This identifies the nature of the transaction and determines how the transaction will be handled. See Payment Type.
   
Troubleshooting This is a systematic approach to locating the cause of a fault in an electronic circuit or system.
   
Truncate The definition of truncate is to shorten or cut off the end. Common use of this term is used where vendors 'truncate' the PARes and PAReq values during the 3D Secure Direct process.
   
TX Sage Pay abbreviation for ‘Transaction’
   
TxAUTHNo see VPS Auth Code
   
TxType A compulsory field in the Transaction Registration Post. The TxType value indicates the payment method to apply to a transaction. Also see Payment Type
   

Back to the Top

U

   
UCAF (Universal Cardholder Authentication Field) This is the value passed back in the PARes (MasterCard only).  If a UCAF value is provided, the transaction has been 3D-Secured, and a liability shift occurs should the transaction later be found to be fraudulent.
   
UK Maestro The domestic Maestro card type. It is advised that you have 3D Secure active on their Sage Pay account (or a 3D Secure exemption date) to process this card type.
   
Ulster Bank An Irish Merchant Acquiring Bank.  See Natwest Streamline for Merchant Number criteria.
   
URL Uniform Resource Locator: a protocol for specifying addresses on the Internet, usually consisting of the protocol, as http, followed by the domain name. 
   
USD US Dollars
   

Back to the Top

V

   
VAT Value Added Tax is a consumption tax levied by the British Government (HMR&C) to consumers of certain products or services. The standard rate for VAT in the UK is 17.5%. Sage Pay receive no benefit from charging VAT. All VAT charged to customer is paid over to HMR&C by means of a VAT Return. We act as agents (as do all registered companies) in collecting taxes imposed on the consumer.
   
Vendor A compulsory field sent in the Transaction Registration Post. This should contain the Vendor Name supplied by Sage Pay when the account was created.
   
VendorTxCode A 'VendorTxCode' is the Sage Pay terminology for a transaction code or transaction identifier. Every time a customer places an order on your web site, or every time the My Sage Pay Terminal is used - a VendorTxCode is generated. VendorTxCodes are generated by yourweb site, either using a shopping cart or by scripts, or if using the My Sage Pay Terminal they are generated automatically. VendorTxCodes are unique to every single transaction for that particular vendor and the Sage Pay system will reject any transactions that use a VendorTxCode that has been used previously by the vendor.
   
Verified by Visa Verified by Visa (VbV) is a fraud screening initiative launched by Visa to provide a more secure method for authenticating the cardholder at the time of the transaction. The scheme requires the customer to enter a unique password at the checkout stage that has been registered with their issuing bank, thus verifying the cardholder. A fully authenticated transaction may not be charged back to you if the customer later denies the transaction. Sage Pay provides Verified by Visa as part of its 3D Secure service at no extra cost. 3D Secure is the technology behind Verified by Visa and MasterCard SecureCode.
   
VISA The value to pass in the CardType field of the Transaction Registration Post to process a VISA transaction (Direct only).
   
VISA Debit / Delta The value to pass in the CardType field of the Transaction Registration Post to process a VISA Debit transaction (Direct only).
   
VISA Electron The value to pass in the CardType field of the Transaction Registration Post to process a VISA Electron transaction (Direct only).
   
VOID A Void nullifies information regarding the authorisation (such as the bank code) on a particular transaction to ensure that it does not send any values/information for settlement. However, the information is only removed from the Sage Pay system and may still remain active on the acquiring bank's system. If the transaction has not yet been sent for settlement, you will be able to Void the transaction. This will cancel the transaction and not include it within the daily bank settlement file.
   
VPSProtocol Version number of the protocol of the system. The latest release is 2.23
   
VPSSignature This is an MD5 hash of the contents of the message. MD5 signature of the concatenation of the values of:
VPSTxId+VendorTxCode+ Status+TxAuthNo+ VendorName+ AVSCV2+SecurityKey+AddressResult+ PostCodeResult+CV2Result+ GiftAid+3DSecureStatus+ CAVV+AddressStatus+PayerStatus+ CardType+Last4Digits.
To detect any possible tampering with messages, the vendor should compute the same MD5 signature (which incorporates the Security Key provided at Transaction Registration) and check it against the VPSSignature.
   
VPSTxId A value returned in the Sage Pay response to the Transaction Registration Post. It is the Sage Pay ID to uniquely identify the Transaction on our system
   
VPS Auth Code The Sage Pay authorisation code for a transaction.
   

Back to the Top

W

   
Web Developer If you have not yet developed your website up to the point where customers can select the goods they wish to purchase, you may need to enlist the help of a web developer. Sage Pay partners with numerous web agencies that can help.
   
Website A connected group of pages on the World Wide Web regarded as a single entity, usually maintained by one person or organization and devoted to a single topic or several closely related topics. 
   
Worldwide Payment Cards Payment methods for Western Europe, North America, South America, and
Asia.
   

Back to the Top

X

   
X25 The connection between the Sage Pay Live servers and the banks.
   
XML eXtensible Markup Language.
   
XOR Encryption XOR stands for Exclusive-OR encryption and is almost unbreakable through brute force methods. Both yourself and Sage Pay have access to a pre-defined encryption password in order to encrypt and decrypt the information provided. XOR encryption uses a password generated by Sage Pay to encrypt text (the Encryption password).
   
XSLT eXtensible Stylesheet Language Transformations.  
   

Back to the Top

Y

 

Back to the Top

Z

   
ZAR South African Rand
   

Back to the Top

 

Simulator

 

Administration Manual

The Administration Manual is designed to provide you will all the information
you need in order to manage your account with Sage Pay, from setting up
additional currencies and adding merchant numbers to understanding your

fraud tools


Introduction to your Sage Pay Account

We now provide the option to accept PayPal through your Sage Pay account.  This section provides the steps you need to take to set this up.

Transaction Administration

By default, all accounts are set up to accept standard Payment, Refunds and Void, however, there are many other payment types which you can use with Sage Pay.

Understanding your fraud prevention tools

With Sage Pay, we offer a variety of fraud prevention tools to combat online fraud. This section should provide information enabling you to understands and use these tools.


Reports

Your My Sage Pay account, provides access to a variety of reports.  This section will detail what reports you are able to view and how to access them.

Mail Order / Telephone Order (MOTO)

The Mail Order/ Telephone (MOTO) facility available within your My Sage Pay account allows you to process transactions taken over the telephone or through the post.  This sections provides instructions on how to use this facility.

PCI

Trading online required you to be PCI compliant regardless of how your process transactions. This section provided useful information on what steps you need to take in order to become PCI Compliant.

Using My Sage Pay

Your My Sage Pay account is your control panel to your Sage Pay allowing you and other users to view transactions and perform certain task. This section provides detail on how to administer users.

Simulator

 

Industry knowledge

The Industry Knowledge manual is designed to provide you with all the industry

information you need to trade online, from how to start up and obtain a merchant
number to understanding the the different card Schemes.

 


Starting Up

Starting up a business online can be confusing and daunting.  This sections should hopefully provide some useful information to get you started.

Merchant Banks and Accounts

One of the first step and most crucial element to trading online, is obtaining a merchant number.  With the variety of providers available and set up with Sage Pay, this section provides details on how to go about getting a merchant number and the different merchant acquirers.

Card Schemes

All cards are issued by a card scheme. This section provides an overview of each of the card schemes.

Integration

Taking payments online will require you to integrate with a Payment Service Provided (PSP).  This sections should help determine which method is most suitable for you to do.

Payment Types

There are a variety of ways to process transactions online and depending on your business.  The information in this section will detail how transactions online work.

Fraud

There are several fraud prevention schemes that have been set up within the Payment Card industry. This sections provides an overview of these tools.

Simulator

 

FAQs

Here you will find some frequently asked questions, if the answers you are looking for cannot be found below then of course you can contact us at support@sagepay.com or by telephone on 0845 111 4455

 



My Sage Pay

How do I amend the default payment page?

If you are using the payment page hosted by us then you can change the templates that appear on your payment pages via you’re My Sage Pay. To do this:

  1. You need to be logged in as either the 'administrator' or a 'user' with administrative privileges.
  2. Hover your mouse over the 'Administration' button and select 'Account Parameters' from the drop-down menu.
  3. At the bottom of this page you will see a section labelled 'Payment Page Templates for Server and Form'. You simply need to tick the box against the option you wish to use.

How do I change the USER Account Password?

If you need to change the User account password, then please follow the steps below:

  1. Log into the main Admin section within your My Sage Pay account.
  2. Select 'User Administration' from the 'Administration' menu.

    You will be presented with a list of usernames and options regarding each one.

  3. Select the User's details that you wish to change.
  4. Click on 'edit'.
  5. In the options 'Set New Password' and 'Confirm New Password', ensure that you enter indentical passwords.
  6. Go to the bottom of the screen and select 'update'.
  7. Log out, then log back in using your new password.

What are the different payment page template options which you provide?

We provide 3 generic payment pages which will allow you to change the function of the payment page without having to customizing them.  This can be done within your My Sage Pay administration area. The options are as follows:

  1. DEFAULT - The default payment pages will require a customer to enter their billing address when AVS/CV2 is turned on. If you supply a billing address and postcode, this is displayed and can be edited by the customer if there are mistakes in the address.
  2. ADDRESS READ ONLY - Like the default payment pages the address is shown when AVS/CV2 checking is on, but the address CANNOT BE EDITED by the customer. They will need to cancel and go back to your site to change their billing address and start again. This template should ONLY be used if you are supplying VSP with the customer's billing address from your own database.
  3. NO ADDRESS - Even when AVS/CV2 is switched on, the customer's billing address is never displayed and cannot be edited. This template should ONLY be used if you are supplying VSP with the customer's billing address from your own database.
  4. CUSTOM - If you have designed your own customised payment pages, you can activate them by selecting this option. If you would like to create your own pages, please download the custom template kit (includes read me document) from the link below:

http://www.sagepay.com/developers.asp#downloads

DO NOT activate this setting until your templates have been designed and uploaded by Sage Pay, or your customers will receive and error during payment.

How do I change the Support Email address within the confirmation Emails?

If you want to change the support email address which appears on your customer email confirmations, then you can do this via your My Sage Pay area. To do this:

  1. You need to be logged in as either the 'administrator' or a 'user' with administrative privileges.
  2. Hover your mouse over the 'Administration' button and select 'Account Parameters' from the drop down menu.
  3. At the bottom of this page you will see a section labelled 'Display and Mail Settings', you can change the support e-mail address to whatever you wish it to be in the field that reads "Your support e-mail address:".

How do I log into the My Sage Pay admin area?

You firstly need to decide whether you will be logging into the test or Live My Sage Pay admin areas and then visit the relevant URK:

My Sage Pay TEST URL: https://test.sagepay.com/mysagepay

My Sage Pay LIVE URL: https://live.sagepay.com/mysagepay

Once you reach the login page, you will need to determine if you are logging into the Administrator account or your User Account

You only need to log on as the Administrator under the following conditions:

a) When logging into your Sage Pay Admin pages for the first time.
b) To create a new User account or unlock an existing User account.

If you wish to perform any other functions, E.g. View your transaction activity or process a MOTO transaction, then you need to login to your User account.

  1. To log into your Administrator account, you enter the following:

    Vendor Name : Enter your Vendor Name
    User Name : Enter your Vendor Name
    Password: Enter your Admin password

    Once accessed;

    If you are logging in for the first time then you need to add a User account, so click on the 'Add' button.

    This will take you to a page where you can create a User account for yourself (and your colleagues).

    User Name: (enter a User Name of your choice)
    Password: (enter a Password or your choice)
    Confirm Password: (confirm your Password)

    Assign full permissions to access all areas. e.g. ticking all the tick boxes, and click 'Add' at the bottom.

    This will take you to the main User account screen, where you will see the User accounts listed that have been created.

    You will now need to log out, using the red log out button at the top left of the screen and log in using the new New User account details you have just created.

  2. To enter your User account, you enter the following:

    Vendor Name: Enter your Vendor Name (this is always the same).
    User Name: Enter your New User Name that you created.
    Password: Enter your New Password that you created.

    This will take you to the reports section where you will be able to view all your transaction reports.

    NB: The Administrator account is for creating new users accounts, assigning permissions, unlocking accounts etc.

    You need to use your New user account to view your transactions etc.

    Please use the following Link to the view the My Sage Pay User Manual:

    http://www.sagepay.com/downloads/vsp_admin_user_manual.pdf
    or
    http://www.sagepay.com/downloads/vsp_admin_user_manual.doc

    ***Please read this manual as it will inform you how to use your New Reports pages.**

How do I refund?

You are able to refund transactions through your My Sage Pay admin area pages.
(Please be aware that Sage Pay cannot refund any transactions for you.)

  1. Log into your My Sage Pay User account. Log in at https://live.sagepay.com/vspadmin/
  2. Locate the transaction that you wish to refund. You can do this via the 'Find a Transaction' page or 'Daily Transaction List'.
  3. Click on the transaction from the result list.
  4. Click on the "Refund" button.
  5. Enter the amount you wish to refund (it can never be more than the original amount of the transaction.)
  6. Enter your login password.
  7. Click Proceed.

The banks will either authorise the refund or not.

If the refund button does not appear?
- Check that you have gave yourself the rights to refund when you created your User account.

NB: If you wish to refund a transaction the same day it was processed, VOID it instead, by clicking the Void button. This will stop the transaction being sent to the banks for settlement. (This will save you the cost of the transaction and the refund with the banks)

The refund failed
It is the banks decision whether they authorise the refund or not.
Reasons for failure would be:
The card has expired
The card has been terminated
The card has been reported stolen
The card has been re issued.

In these circumstances you would need to refund via another means




CMS

How do I change my Bank Account details?


To amend the bank details that appear on your Sage Pay account please access your My Sage Pay Customer Management System (CMS).

Please note that this is for our reference purposes only, and to change the bank details where your funds are settled you will also need to inform your acquiring bank, because they control the settlement process.

Your Direct debit can also be amended from this location.

The Sage Pay Customer Management System (CMS) has been designed to make the administration of your Sage Pay account as fast and easy as possible.

The Sage Pay CMS system enables you to perform the following functions:

· Change your billing details
· Set up or modify your Direct Debit details
· View your current invoice

How to login to Customer Management Services?

In order to login to CMS for the first time you need to login as an Administrator. The Administrator account will only allow you to create and administer other user accounts, from which you will be able to access the entire CMS system.

To access CMS, you need to type the following URL into your browser:

https://customerservices.sagepay.com/

To login as an Administrator please enter the following information:

· In the Customer Login ID field: enter your Vendor Name
· In the Username field: enter your Vendor Name
· In the Password field: enter your Reporting Password

Your Reporting Password is the same as your Admin Reporting Password. If you do not know your password, please contact unlock@sagepay.com to ontain.

Please note, this page will require you to enter your name and internet merchant number that is registered with Sage Pay.

For more information on the CMS system please consult the link below, you can also download the user manual from here:

https://customerservices.sagepay.com/CustomerLogin.aspx

If you require any further help or assistance please do not hesitate to contact us.



Technical Support

What is a Shadow? / Funds appear to have been taken but the transaction has failed.

When a transaction is authorised, the shopper's bank/card issuer will allocate the funds owed to you by placing a 'shadow' on the shopper's account. This will remain on the account for up to 6 days ensuring that the customer does not spend this allocated fund anywhere else.

If you require a shadow to be cancelled then you will need to provide your shopper with the bank auth code so they can contact their card Issuer to request the auth is cancelled from the card, as it is down to their Issuer to remove this.

If you do not have access to this information, Our Support team may be able to provide you with the Authorisation Code for the Transaction in question which you can then provide to your Shopper who will need to contact their own Card Issuer to remove this. Simply e-mail your VSP Vendor Name and the VendorTxCode of the transaction in question to support@sagepay.com

Please note, in some cases the Issuer will not remove the 'shadow'. If this is the case, then it will remain on the card for anything up to approximately 6 days.

Is the Sage Pay system secure?

Sage Pay collect card details via a 128-bit SSL secured payment page. We request card number, expiry dates, cardholder name and address and security code value. This information is then further encrypted to be held against the transaction details on our system before being sent to the UK acquiring banks for authorisation (over secure, offline channels). We don't store the security code (in line with Visa requirements) but we do store the card number (only in an encrypted format that none of our staff have access to).

Sage Pay secure your card details within our database using AES-256, the keys for which are held on tamper-proof hardware security modules which as stated are unavailable to Sage Pay staff.

When your details are supplied to us over SSLv3, the algorithm used is RC4, as it is for almost every major e-commerce site.

SSL generates the encryption keys it uses for RC4 by hashing (using both MD5 and SHA1), so that different sessions have unrelated keys. Also, SSL does not re-key RC4 for each packet, but uses the RC4 algorithm state from the end of one packet to begin encryption with the next packet.

The SSLv3 certificates we obtain from Verisign to secure our site can support AES-256 as the encryption algorithm, but the vast majority of customers use IE6 or below and older versions of Firefox and Netscape. Most also run on Microsoft Windows, which until Vista is released, cannot use AES in SSL encryption. At present, the vast majority of sessions will be encrypted at 128-bit, but with a strong algorithm like correctly implemented RC4, 128-bits is more than enough to ensure the security of your card details.

We can also assure you that your details would not have been gleaned from our system (which has been approved, and is regularly audited by Visa and Mastercard as one of the most secure sites in the UK). 

Our systems are independently audited by the UK acquiring banks and we are compliant with the card schemes themselves (both Visa and Mastercard) under their Payment Card Industry Data Security Standard which ensures we meet very strict security guidelines (see this link http://www.visaeurope.com/aboutvisa/security/ais/main.jsp for more information).

I hope this explanation helps allay your security fears.  Please do not hesitate to contact us if you have any further concerns.

Why are the email notifications sent from donotreply@sagepay.com?

All confirmation e-mails are now sent from ‘donotreply@sagepay.com’. The reason for this is because the Sender Policy Framework (SPF) is becoming extensively used these days.

The aim is to prevent SPAM e-mails, by only allowing certain servers to send mails from certain e-mail addresses. So whilst we can send mails from sagepay.com, for a mail server with SPF in place we could not send mails from jamesgadgets.com (example) because we are not registered to do so. We cannot register ourselves either, so the mail simply bounces.

So please ensure you have amended your e-mail settings to allow e-mails to be received from ‘donotreply@sagepay.com, otherwise your e-mail settings may have filtered these e-mails into your spam folder.

I don't seem to be receiving any email notifications?

We send emails out but have no control over whether they get to their destination or not, unfortunately this is the nature of the internet. As a result we cannot guarantee the delivery of emails, as there are too many factors outside of our control that determine what route an email takes.

This is why we have our reports pages to list all transactions that have been processed.

If you view your My Sage Pay Admin reports pages you will see what orders were made and what to fulfill. We do not recommend that you just rely on the email confirmations; you should always check your My Sage Pay reports pages at the end of each day.

It may also be worth providing two e-mail addresses in the ‘VendorEMail’ field that you send through to Sage Pay with every transaction, then if one e-mail address fails, it should be received by the other.

If you wish to use multiple email addresses, you should add them to the ‘VendorEMail’ field using the : (colon) character as a separator. E.g. myemail@myemail.com:anotheremail@anotheremail.com.

If shoppers are complaining that they are not receiving confirmation e-mail, first get them to check their spam folder. Please also bear in mind that we have no control over external email servers or spamming software at the shoppers end.

How do I change HTML Confirmation Emails to Plain Text?


If you do not want the Sage Pay order confirmation e-mails to be HTML formatted then you can change them to be in plain text via your My Sage Pay admin pages.

To do this:

  1. Log into your VSP Admin User Account.
  2. Hover your mouse over the 'Administration' button and select 'Account Parameters' from the drop-down menu.
  3. At the bottom of this page you will see a section titled 'Display and Mail Settings'. From here, untick the tick box against 'Send HTML e-mails'.

I am using your Server/Direct Integration and I need to register/change my IP address. How do I do this?

If you would like to register/change your IP address(es) then you can do this via your My Sage Pay administration area. To do this:

  1. Log into your User account.
  2. Hover your mouse over the 'Administration' button and select 'Account Parameters' from the drop down menu.
  3. In the middle of this page you will see a section labelled 'Valid IP Addresses for this Account'. Simply add your IP address(es) where it reads: 'Add New IP'.

I am customising the payment pages using your templates kit.  Can I add any external links to them?

Unfortunately, we do not allow any external links which will take the customers away from the payment pages and affect the transaction process.

As this can cause errors and therefore the links on the error pages will need to be removed in order to pass our validation process.

You can have links to a pop up page which you provide in your images files like a help page which can then link back to your site but just not on the payment pages.



General

How do I change the company name that appears on my customers bank statements?

If you require the company name which appears on your customers’ bank statement to be changed, you will need to contact your merchant service provider/acquiring Bank, who will amend this on your behalf. The company name would normally be what was set up when you entered into you merchant account agreement with your acquiring bank.

Sage Pay do not dictate what information appears on these statements as we do not settle any funds directly.

I am an international company, can I use the Sage Pay service?

Sage Pay is only able to accept customers who are able to obtain a UK/Irish internet merchant number from one of the UK or Irish merchant banks listed at the following link on the Sage Pay website: www.sagepay.com/sagepay_acquiring_partners.asp.

The banks that supply merchant accounts to online businesses require that either you or your company reside in the UK or Ireland.

If you or your company resides outside of the UK or Ireland, unfortunately we cannot work with you at this point in time.


Is Sage Pay PCI Compliant?

Sage Pay is fully approved as a Level 1 compliant provider under the Payment Card Industry Data Security Standard (PCI DSS). This is the highest level of compliance that can be achieved.

Sage Pay were audited by an independent third party company, Trustwave, who are an official Visa Qualified Security Assessor.

Our approval status can be viewed on the Visa website at the following link:

http://www.visaeurope.com/documents/ais/pci_dss_compliant_service_providers.pdf?140409

What is 3D Secure?

Verified by Visa and MasterCard SecureCode (3D Secure) are the latest fraud prevention initiatives launched by Visa and MasterCard.

3D Secure works in a similar way to Chip and Pin, by asking the customer to enter a unique password in order to complete their online order.

How does Verified by Visa and MasterCard SecureCode work?

If Verified by Visa and SecureCode by MasterCard has been enabled on your Sage Pay account, your shoppers will be given the option to register their cards and/or verify their transaction, when purchasing from you. Once the shopper has entered their card details on Sage Pay’s hosted payment page they will be prompted (on the confirmation page) to register their card for 3D Secure (if they have yet to do so) or proceed with the transaction and enter their pin number they have set up for online transactions.

Key Benefits of 3D Secure?

  • There are no additional charges for VbV and MSC from Sage Pay. Your acquiring bank may charge you to add this to your merchant number, but you may also find that they will lower their charges to you if you support these schemes.
  • 3D Secure technology provides a more secure method for authenticating the Cardholder at the time of the transaction, therefore minimising fraudulent transactions.
  • A transaction which has been fully 3D-Secure Authenticated cannot be returned as a Chargeback if it is subsequently found to be fraudulent. This is because the banks themselves assume liability for all transactions passed under 3D Secure. NB. A 3D secure validated transaction will not protect you in circumstances such as in the event where the customer denies receipt of goods.

To enable this facility on your Sage Pay account please email support@sagepay.com.

For further information regarding 3D Secure, please visit http://www.sagepay.com/developers/industry_knowledge/3d_secure.asp



PayPal

What are the charges for processing PayPal transactions?

There are no set up costs, no monthly fees and no cancellation fees, however PayPal charges per transaction between 1.4% - 3.4% +20p per transaction depending on the merchant volume with PayPal.

For further information regarding the transaction fees, please visit the PayPal website:

https://www.paypal.com/uk/cgi-bin/webscr?cmd=_display-receiving-fees-outside

How do I change the bank account where PayPal transactions are settled

PayPal transactions are settled by PayPal. The funds from your customers’ PayPal payments are deposited into your PayPal Business account immediately.

You can then withdraw or transfer the funds electronically into your specified bank account.

Please contact PayPal directly to change the Bank Account where the funds will be transferred.

What Fraud prevention measures are taken on PayPal transactions?

PayPal implements its own fraud prevention measures (please see details above).

As a PayPal transaction is not sent to the bank for authorisation by Sage Pay, AVS/CV2 results cannot be obtained, therefore the AVS/CV2 results will always display the ‘Not Provided’ symbol within the My Sage Pay Admin area.

Similarly with 3D Secure, if a shopper selects to use PayPal they will not go through the 3D-Authentication process, therefore 3D Secure results will not be obtained.

The 3rd Man results are not available on PayPal transactions because many of the details used to make a payment through PayPal are not released to the 3rd Man, which means they do not have enough data to make a valid risk score.

If you want to learn more about PayPal’s own Fraud Prevention methods, please visit the PayPal website using the link below:

https://www.paypal.com/uk/cgi-bin/webscr?cmd=_security-center-outside



Finance

How do I cancel my account with Sage Pay

When you signed up to use our services you agreed to our terms and conditions. Our terms state that you need to give 3 months notice to close your Sage Pay account, and all fees become payable immediately on termination.

You can pay your termination fee via credit/debit card by calling us on 0845 111 4455. Alternatively, payment can be made by cheque or by BACS using the following bank details:

Account:          Sage Pay

Bank:               HSBC

Sort Code:        40-01-06

Account No:      92071401

Please use your vendor name or your account reference to help us identify your payment.

Once the termination fee has been paid we will cancel your Direct Debit and your account can remain open for the notice period.



Shoppers

How do I know if my payment has gone through?

When you pay for your order you will be sent to either a successful payment page or a failed payment page on the merchant website. You may also receive a confirmation email from the Sage Pay system which confirms the status of your transaction.

If you are in doubt about the status of your order, please contact the company you ordered from with all the relevant details and they will be able to advise you of your order status.

I received an error code, what do I do?

If you receive an error code during the transaction process, please email this code to support@sagepay.com and we will advise you on how to proceed.

My credit card has been rejected by your system as it is the wrong length / the issue number is incorrect?

The Sage Pay system will detect and reject any card number which is incorrectly formatted. If you believe that our system should accept the details you are entering, please email the first 6 digits of your card number to support@sagepay.com and we will advise you further.

How do I know my details are secure?

Sage Pay is audited by an independent auditor on a regular basis to ensure that we comply with the latest security standards set out by Visa and MasterCard. If you have processed your order online using the payment pages hosted by Sage Pay, please locate and click on the padlock image which can be found on our payment pages to confirm that your details are collected in a secure environment.

The padlock is located in a different area of the payment page screen depending on the internet browser you are using – it can normally be found in the bottom right hand corner of the screen, at the top of the screen next to (or inside) the address bar or at the very top right hand corner of the screen. This padlock shows that your details are collected using 128 bit SSL technology.

Once you have entered your card details, Sage Pay will securely send these details to the bank to be authorised. This is a completely secure process and we ensure that your details cannot be accessed by a third party.

For more information on the security standards employed by Sage Pay, please visit our security overview section.

Where can I find the Padlock on the Payment Page?

If you are using a MAC Browser then the padlock will be situated in the top right of your browser.

If the company that you are trying to purchase the goods from are using a html frameset, then you will need to click on the padlock around the top middle of the payment page. This will then allow you to bring the payment page out of its frameset and therefore your browser will be able to detect that the page is secure and thus display the padlock in your browser.

If you have anymore questions on this, please contact the company that you are trying to purchase the goods from

I have placed an order through your payment system but I have not received the goods/services which I paid for?

Sage Pay is a Payment Service Provider. We process payments on behalf of our customers and make sure that your transaction details are kept secure throughout the transaction process.

We do not hold any order or delivery details and we cannot process any refunds or cancel any orders on behalf of the merchants who use our service.

If you have a query regarding your order, please first contact the company you ordered from.

You should find the company's contact details on the company's website, the customer receipt, or on the Sage Pay transaction confirmation email if one has been sent.