VeriSign Payment Services

Transcription

1 VeriSign Payment Services Payflow Link User s Guide USER GUIDE IMPORTANT! This document is intended for merchants who do not subscribe to VeriSign s Fraud Protection Services. If you currently use Payflow Link and recently added a Fraud Protection Services package, then you must change your HTML code to send transaction data to a different Payflow Link URL. Do not use this document. Instead, use User s Guide for Payflow Link with Fraud Protection Services. Customer Support: vps-support@verisign.com VeriSign, Inc /Rev. 4

2 VeriSign Payment Services Payflow Link User s Guide VeriSign Payment Services Payflow Link User s Guide VeriSign, Inc /Rev. 4 Copyright VeriSign, Inc. All rights reserved. Printed in the United States of America. Publication date: July 2003 Trademark Notices VeriSign is a registered trademark of VeriSign, Inc. The VeriSign logo, VeriSign Trust Network, and Go Secure! are trademarks and service marks of VeriSign Inc. XMLPay and OnSite are registered trademarks of VeriSign, Inc. Other trademarks and service marks in this document are the property of their respective owners. No part of this publication may be reproduced, stored in or introduced into a retrieval system, or transmitted, in any form or by any means (electronic, mechanical, photographic, audio, or otherwise) without prior written permission of VeriSign, Inc. Notwithstanding the above, permission is granted to reproduce and distribute this document on a nonexclusive, royalty-free basis, provided that (i) the foregoing copyright notice and the beginning paragraphs are prominently displayed at the beginning of each copy, and (ii) this document is accurately reproduced in full, complete form with attribution of the document to VeriSign, Inc. Note This document may describe features and/or functionality that are not present in your software or your service agreement. Contact your account representative to learn more about what is available with this VeriSign product. ii VeriSign, Inc /Rev. 4

3 Contents Contents Summary of Revisions vii Chapter 1 Introduction What is Payflow Link? Payflow Link Features How Payflow Link Works The Flow of the Payflow Link Order Processing Forms Overview: Integrating with Payflow Link Requirements Payment Types, Credit Cards, Processors, and E-commerce Shopping Carts Supported by Payflow Link Supported Payment Types Supported Credit Cards Supported Processors Integrated E-commerce Shopping Carts Contacting the Customer Support Group About This Document Related Documents Performing Recurring Transactions Chapter 2 Configuring Payflow Link Opening the Edit Configuration Page Configuring Payflow Link Settings Complete the Form Configuration section Complete the General Display Options section Configuring the Appearance of the Order Processing Pages Configure the Receipt page Configure options Configure security options Address Verification Service (AVS) Security Feature Card Security Code Validation Accepted URL Security Feature Save your configuration settings VeriSign, Inc /Rev. 4 iii

4 Contents Chapter 3 Integrating Your Web Site with Payflow Link (Basic Integration) Example of a Simple Integration Payflow Link Transaction Types Chapter 4 Integrating Your Web Site with Payflow Link (Advanced Integration) Example of a Custom Integration Payflow Link Transaction Types Chapter 5 Testing Payflow Link Testing TeleCheck Transactions Testing Credit Card Transactions Verify that the Transaction Process Mode is set to TEST Performing Test Transactions Alternative Methods for Generating Specific Result Codes Testing Address Verification Service (AVS) Testing Card Security Code (CSC) Chapter 6 Going Live with Payflow Link Going Live Register to go live Set the Transaction Process Mode to LIVE Verify that live transactions are processed correctly Chapter 7 Managing Payflow Link Generating Reports Report Formats Interpreting the Result Code Generating the Payflow Link Orders Report Generating Daily Activity Reports Generating Transaction Summary Reports Generating Custom Reports Generating Settlement Reports Generating Shipping and Billing Reports Viewing the Transaction Detail Page VeriSign, Inc /Rev. 4 iv

5 Contents Chapter 8 Integrating TeleCheck Transactions Integrating Check Processing Enabling Customers to Specify the Payment Method Data That You Must Post if You do not use Payflow Link s Order Form.. 71 Transaction Results Returned for TeleCheck Transactions Testing TeleCheck Transactions Appendix A Transaction Results Transaction ID Value Transaction ID Format Transaction Result Codes Result Codes for Declined Transaction and Other Errors Transaction Result Codes for Communications Errors Appendix B Submitting Transaction Data to the Payflow Link Server About VeriSign s Transaction Database Collecting Customer Transaction Data, Option 1: Use the Payflow Link Order Form Data That You Must Pass if You Use Payflow Link s Order Form Collecting Customer Transaction Data, Option 2: Collect the data on your Web page and Post it to the Payflow Link server Data That You Must Post if You do not use Payflow Link s Order Form 85 Optional Transaction Data Payflow Link Transaction Types Returning Data to Your Web Site Retaining Session Data and other Temporary Information Specifying How Data is Returned to Your Web Site Data Returned by the Post and Silent Post Features Values Returned When ECHODATA is False Values Returned When ECHODATA is True Parameters That Specify Payflow Link Operation Appendix C Frequently Asked Questions Using Payflow Link with other Applications VeriSign, Inc /Rev. 4 v

6 VeriSign Payment Services Payflow Link User s Guide How Payflow Link Works Using Payflow Link Appendix D About the Confirmation Messages Example Customer Message Example Merchant Message List of Fields Returned in the Confirmation Message Transaction Information Billing Information Shipping Information Additional Information Index vi VeriSign, Inc /Rev. 4

7 Summary of Revisions /Rev. 4, July 2003 The following changes have been made to this document since the last revision: Payflow Link server URL corrected The chapters on integrating your Web Store with Payflow Link specified an incorrect URL for the Payflow Link server. The URL has been corrected. See Chapter 3 and Chapter /Rev. 3 The following changes have been made to this document since the last revision: Integrating your Web Store with Payflow Link Passing Transaction Data Address Validation Service Card Security Code Delayed Capture transactions The chapter on integrating your Web Store with Payflow Link has been split into two chapters. See Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration), and Chapter 4, Integrating Your Web Site with Payflow Link (Advanced Integration). The appendix on submitting transaction data has bee significantly restructured to improve clarity. See Appendix B, Submitting Transaction Data to the Payflow Link Server. Information on the AVS feature has been expanded. See Address Verification Service (AVS) on page 26. Information on the CSC feature has been expanded. See Card Security Code Validation on page 27. Delayed Capture transactions are performed from VeriSign Manager, not from Payflow Link /Rev. 2 The following changes have been made to this document since the last revision: New Processors Supported The list of supported processors has changed. See Supported Processors on page 9. VeriSign, Inc /Rev. 4 vii

8 DOC-DOM-PMT-GID-0010/Rev. 4 The following changes have been made to this document since revision 3: Shipping and billing information ORIGID parameter is replaced by TRANSID Using the Payflow Link Configuration page in VeriSign Manager, you can specify that customers can provide both shipping and billing information on the Payflow Link Order form. See Shipping and Billing Fields on page 18. The ORIGID parameter is replaced by TRANSID for Delayed Capture transactions. The use of the ORIGID parameter causes an error. DOC-DOM-PMT-GID-0010/Rev. 3 The following changes have been made to this document since revision 2: Card Security Code Validation Payflow Link now gives you the option to use the card security code (CSC) when making a decision about a Payflow Link Order transaction. See Card Security Code Validation on page 27. The process of passing the CSC value to the Payflow Link server is described in Optional Transaction Data on page 87. Testing Information on testing Payflow Link has been expanded. See Chapter 5, Testing Payflow Link. DOC-DOM-PMT-GID-0010/Rev. 2 The following changes have been made to this document since revision 1: Return Link Receipt Header and Receipt Footer option Voided transactions Reports described more fully EXPDATE field Date formats The fact that no transaction data is POSTed with the Return Link feature is clarified in the note on page 17. The number of characters supported in the Receipt Header and Receipt Footer fields is changed to 511. See Configure the Receipt page. You can now send confirmation independently to customers and to persons at your organization. See Configure options. The note on page 26 describes the process of identifying voided transactions. Report types and formats and the process of preparing reports are described in more detail than in the previous version of this document. See Chapter 6, Managing Payflow Link. The EXPDATE field now supports a greater variety of date formats. See Appendix B, Advanced Integration. VeriSign, Inc /Rev. 4 viii

9 re t pahc CHAPTER 1 1Introduction IMPORTANT! This document, Payflow Link User s Guide, is intended for merchants who do not subscribe to VeriSign s Fraud Protection Services. If you currently use Payflow Link and recently added a Fraud Protection Services package, then you must change your HTML code to send transaction data to a different Payflow Link URL. Do not use this document. Instead, use User s Guide for Payflow Link with Fraud Protection Services. Payflow Link is the fast and easy way to add transaction processing to your Web site. With Payflow Link, your customers are linked to order forms on VeriSign s secure Web server where transactions are processed in real time. Tip If the topic of Internet payment transaction processing is new to you, see VeriSign s Payment Services Web site for information by going to: With Payflow Link s simple cut and paste integration, you can be up and running with a completely automated payment solution in a matter of hours. You can: Customize the look and feel of your secure order forms to match your Web site appearance Automatically send confirmation to customers Post transaction data behind-the-scenes to your Web server Take advantage of security features Use VeriSign Manager to generate Payflow Link order reports and to search transaction reports. VeriSign, Inc /Rev. 4 1

10 VeriSign Payment Services Payflow Link User s Guide CAUTION VeriSign recommends that you verify each order and the dollar amount of all Payflow Link transactions using VeriSign Manager. It is your responsibility to protect your passwords and other confidential data and to implement security safeguards on your Web site and in your organization, or to ensure that your hosting company or internal Web operations team is implementing them on your behalf. You or your ISP/shopping cart provider should be able to adhere to security requirements as protective as those described at: What is Payflow Link? Payflow Link is a secure, VeriSign-hosted, Web-based Internet payment solution. It allows you (a merchant with an Internet merchant account) to connect your customers to VeriSign s secure order form server and use it to automate order acceptance, authorization, processing, and transaction management. Payflow Link is the choice for merchants who process low to moderate order quantities and prefer a solution that is especially easy to implement and maintain. Note If your Web site processes more than 500 transactions per month, you should consider using Payflow Pro, VeriSign s high performance Internet payment solution. Payflow Link Features Easy to implement and use. VeriSign supplies you with the HTML code you need to get started. Customizable to your Web site. You can customize the look and feel of the VeriSign-hosted order forms to reflect your Web site design. Responsive and reliable. Payflow Link immediately advises customers whether their transaction was successful. receipt notification. With approved transactions, Payflow Link can send an confirmation receipt to you and your customers. High security. All transactions processed on VeriSign-hosted forms occur over secure SSL connections. All certificates required to ensure both authentication and security are hosted by VeriSign. You can specify that only 2 VeriSign, Inc /Rev. 4

11 Chapter 1 Introduction certain Web pages (for example, your e-commerce site) are valid entry points for the transaction processing pages. Fraud protection. Payflow Link supports Address Verification Service (AVS) and Card Security Code (CSC) as a layer of fraud protection. See Configure security options on page 25. In addition, VeriSign offers the powerful Fraud Protection Services suite of services. See User s Guide for Payflow Link with Fraud Protection Services. VeriSign Manager. The VeriSign Manager service enables transaction management with features like a transaction terminal, search tools, reports, and so on. Access for offline orders. VeriSign Manager's Transaction Terminal gives you the flexibility to process orders offline, including orders received via phone, fax, , or in person. IMPORTANT! Payflow Link is a single payment amount solution. If you want your customers to be able to order multiple items or quantities, you must develop a solution that calculates the total transaction amount based upon customer choices. If you do not have development staff, you could use a shopping cart that integrates Payflow Link. See Integrated E-commerce Shopping Carts on page 9. How Payflow Link Works You insert a small piece of HTML code into your Web page. The code creates a button on your Web page that links your customers to VeriSign s secure Payflow Link Web server. At the Payflow Link site, your customer fills in an order processing form that you can tailor to reflect the look and feel of your Web store. The customer submits the transaction and VeriSign acts as the gateway to the transaction processing networks (very much like the swipe machine for physical credit cards). After the transaction is approved, the customer is returned to your site. You can configure VeriSign, Inc /Rev. 4 3

12 VeriSign Payment Services Payflow Link User s Guide Payflow Link to send both you and your customer receipts. You can also configure Payflow Link to return transaction data to your site. Buyer selects items at your Web store and clicks the BUY button Buyer Internet Merchant Merchant Web Store One case Merchant Web Store Buyer is redirected to the secure Payflow Link forms $ BUY Thank you for your purchase. HTTPS Buyer is returned to your Web store 5 Secure Forms Hosted by VeriSign Order Info Invoice# Shipping05.2 Tax 59.3 TOTAL 59.73$ Credit Card Info 3333 Number Exp Billing Info Name a ni Tnosnho J Address 32 1 Fou r rd a ti n b@ AUTHORIZE iv e Payflow Link connects with Processors, who perform real-time authorization 3 Internet-SSL uye r.com Credit Card Processors Transaction is processed 4 Your Acquiring Bank Buyer's money is transferred to your bank 6 $ Financial networks (Visa, MasterCard, AmEx, and so on) Note For more information on the payment processing cycle, go to Buyer's Issuing Bank The Flow of the Payflow Link Order Processing Forms When your customers click the Buy button at your Web store, they are connected to a sequence of secure Payflow Link order processing forms hosted on the VeriSign Payment Services servers. All forms except the Receipt form are optional. Using tools provided by VeriSign, you can configure the appearance and content of these forms to meet your needs. Note As a security measure, if a customer makes five invalid purchase attempts, access to Payflow Link is disabled. The customer must exit the Web site and attempt the purchase again. 4 VeriSign, Inc /Rev. 4

13 Chapter 1 Introduction The following example forms appear in order (your forms may include different or additional information): Form 1: Payment Method The Payment Method form appears only if you are registered to accept both credit cards and electronic checks. Form 2: Order Information The Order form enables the customer to enter any additional order data on Payflow Link s secure servers. You have the option to eliminate this page and pass the transaction data directly to the Payflow Link server. In this example, the merchant added their logo to the form. To improve the customer experience and to foster trust, VeriSign strongly recommends that you add your logo to the pages and customize the color scheme to match your Web store pages. Instructions appear in the next chapter. When entering the credit card number, the customer can enter just numbers or can use spaces, dashes, or periods to separate the groups of numbers that make up the credit card number. VeriSign, Inc /Rev. 4 5

14 VeriSign Payment Services Payflow Link User s Guide Form 3: Confirmation The Confirmation page enables the customer to verify and submit the order. You have the option to show this page to customers or to skip it. Form 4: Receipt The Receipt page presents a summary of the transaction and returns the customer to the URL that you specify (typically your Web store). Optionally, you can specify that Payflow Link should perform an HTML POST operation to send the transaction data to your Web server. This is the only Payflow Link page that you must present to the customer. 6 VeriSign, Inc /Rev. 4

15 Chapter 1 Introduction Overview: Integrating with Payflow Link Requirements You follow these steps to integrate your Web store with Payflow Link: 1 Register for a Payflow Link account and apply for an Internet Merchant account at 2 Configure Payflow Link. Specify the appearance and content of your VeriSign-hosted order processing forms. This step is described in Chapter 2, Configuring Payflow Link. 3 Connect your Web store to the Payflow Link service: Paste a small amount of HTML text into your Web page. This HTML code passes your customer (and a set of data) to VeriSign s Payflow Link server for transaction processing. This step is described in Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration). 4 Test Payflow Link before you activate your Web store for customer use. This step is described in Chapter 5, Testing Payflow Link. 5 Activate your account to go live. This step is described in Chapter 6, Going Live with Payflow Link. To use Payflow Link, you must have the following: Web page. You must have a Web page for your e-commerce business. You must also be able to upload changes to your Web site. Internet Service Provider. An ISP must host your Web site. A basic text editor or HTML editor. You will use the editor to add the HTML text that links your site to Payflow Link. Web browser. You must have Internet Explorer 3.0 (or newer) or Netscape 4.0 (or newer) to access the VeriSign Manager administrative Web site. Internet Merchant Account. You will need to have an Internet Merchant account before you can begin accepting payments at your Web site. VeriSign has partnered with several Internet Merchant account providers to make applying easy. See VeriSign, Inc /Rev. 4 7

16 VeriSign Payment Services Payflow Link User s Guide Your Web site must calculate the total transaction amount. Payflow Link enables your customers to process a single transaction amount. Payflow Link does not calculate the transaction amount based on customer selections. To enable customers to order multiple items or quantities, you must develop a solution that dynamically calculates the total transaction amount based upon customer selections in your Web store. Your code must then pass the total transaction amount to VeriSign's Payflow Link server. VeriSign provides simple HTML code that passes the amount, as described in Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration). Payment Types, Credit Cards, Processors, and E-commerce Shopping Carts Supported by Payflow Link Supported Payment Types Payflow Link supports the following tender types: Credit cards Check/debit cards issued by MasterCard or Visa TeleCheck electronic checks Supported Credit Cards Payflow Link supports the following credit cards: Visa MasterCard American Express/Optima Diners Club Discover/Novus JCB 8 VeriSign, Inc /Rev. 4

17 Chapter 1 Introduction Supported Processors Payflow Link supports the following processors: American Express EDS FDMS- Nashville FDMS - South Global Payments- Central Global Payments - East Nova Paymentech TeleCheck Vital Integrated E-commerce Shopping Carts Payflow Link is pre-integrated with the e-commerce shopping carts listed at VeriSign continuously works to integrate new shopping carts with its products. If a shopping cart of interest does not appear in the list, contact us to see if it is in process of being integrated. Note For technical support on shopping carts, please contact the vendor. Contacting the Customer Support Group When you purchase Payflow Link, VeriSign provides telephone-based customer support. Support during your initial integration phase is available by phone Monday through Friday between 8 AM and 6 PM Pacific Time. Once your account is integrated with your Web store, VeriSign provides free support 24 hours per day, 7 days per week. VeriSign, Inc /Rev. 4 9

18 VeriSign Payment Services Payflow Link User s Guide For integration and connectivity issues, VeriSign provides online documentation, direct support, and phone support. For technical support on shopping carts, please contact the vendor. VeriSign is committed to providing you with the most advanced technical support expertise to ensure availability and reliability of your e-commerce applications. Online Info: This site offers an FAQ (frequently asked question) section vps-support@verisign.com Phone: About This Document This document is intended for merchants who will integrate Payflow Link with their e-commerce Web site. The documentation first describes a simple implementation that gets you up and running quickly. More complex solutions are described in later chapters. Note Because most Payflow Link users process credit card transactions, this document generally discusses such transactions. Electronic check transactions processed by TeleCheck are fully supported by Payflow Link. A full description of TeleCheck transaction processing appears in Chapter 8, Integrating TeleCheck Transactions. Chapter 2, Configuring Payflow Link, describes the process of specifying the appearance and customer-provided data of your VeriSign-hosted order processing forms. Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration), describes the process of customizing and adding HTML text into your Web page. This HTML code passes your customer (and a set of data) to VeriSign s Payflow Link server for transaction processing. Chapter 4, Integrating Your Web Site with Payflow Link (Advanced Integration), describes a more sophisticated integration between your Web store and Payflow Link. Chapter 5, Testing Payflow Link, describes the process that you follow to test your Payflow Link integration and to verify that it is operating correctly. 10 VeriSign, Inc /Rev. 4

19 Chapter 1 Introduction Chapter 6, Going Live with Payflow Link, provides instructions on registering to go live with your Payflow Link account and changing the appropriate configuration settings. Chapter 7, Managing Payflow Link, provides instructions on reviewing Payflow Link reports using VeriSign Manager. Chapter 8, Integrating TeleCheck Transactions, provides instructions on enabling TeleCheck transactions for your customers. Appendix A, Transaction Results, provides reference material on the Silent Post option. Appendix B, Submitting Transaction Data to the Payflow Link Server, provides guidance for those who wish to develop more complex interactions between their Web page and Payflow Link. Appendix C, Frequently Asked Questions, provides answers to frequently asked questions. Appendix D, About the Confirmation Messages, describes the content of the optional confirmation (as introduced in Configure options on page 24). Related Documents VeriSign Payment Services Introduction describes all VeriSign Payment Services products and defines terms used in the transaction processing field. Payflow Pro Developer s Guide provides full documentation on the use of Payflow Pro. VeriSign Manager User s Guide describes the use of VeriSign Manager. Performing Recurring Transactions To learn more about VeriSign s Recurring Billing Service, please click the Recurring Billing banner on the VeriSign Manager Welcome page. If the banner does not appear, contact your Partner to request information. Recurring Billing Guide describes how to manage recurring (scheduled) payments. VeriSign, Inc /Rev. 4 11

20 VeriSign Payment Services Payflow Link User s Guide 12 VeriSign, Inc /Rev. 4

21 re t pahc CHAPTER 2 2Configuring Payflow Link Once you have registered for a Payflow Link account, your first step is to configure Payflow Link using the VeriSign Manager application. Using VeriSign Manager, you specify the appearance and content of your VeriSign-hosted order processing forms. In addition, you have the option to specify which fields your customers need to fill in, and how transaction data is passed and posted to scripts on your Web site. To configure Payflow Link, you open the VeriSign Manager to the Edit Configuration page and then specify your preferred values, as follows: Opening the Edit Configuration Page 1 Start VeriSign Manager at: The Login dialog box opens. The name of your Partner was provided to you by your VeriSign Reseller. If you registered with VeriSign directly, enter VeriSign. Enter the Login that you chose during registration. Enter the Password that you chose during registration. Click Login VeriSign, Inc /Rev. 4 13

22 VeriSign Payment Services Payflow Link User s Guide 2 VeriSign Manager opens. Click Account Info on the menu bar. 3 The Account Information page opens. Click Payflow Link Info. If the Payflow Link Info link does not appear, contact Customer Support. 14 VeriSign, Inc /Rev. 4

23 Chapter 2 Configuring Payflow Link The Edit Configuration page opens. The remaining steps describe how to fill in the sections of the Edit Configuration page. Click any underlined field name for a complete description. Described in Step 1, Complete the Form Configuration section on page 16. Described in Step 2, Complete the General Display Options section on page 18. Described in Step 3, Configure the Receipt page on page 23.\ Described in Step 4, Configure options on page 24. Described in Step 5, Configure security options on page 25. VeriSign, Inc /Rev. 4 15

24 VeriSign Payment Services Payflow Link User s Guide Configuring Payflow Link Settings To configure Payflow Link, you specify configuration settings in the Edit Configuration page. To view online help for any configuration field, click the field name. VeriSign recommends for your first pass that you create a minimum configuration using a TEST environment. You can re-open the Edit Configuration page and make improvements to the forms as often as you like be sure to save your configuration changes each time that you make changes. Once the pages meet your requirements, you can move your account to LIVE status, as described in Chapter 6, Going Live with Payflow Link. Any configuration that you perform on Payflow Link in TEST mode carries over directly to your LIVE account. Note Quotation marks ( ) and the ampersand (&) character are not allowed in most configuration fields. You can use these characters only in the Receipt Text, Text, Merchant Display Name, and Receipt Footer fields. The ampersand (&) character can be used in URLs, for example, the Return URL, Silent Post URL, and Forced Silent Post URL. Step 1 Complete the Form Configuration section The Form Configuration section enables you to specify the URL to which customers return, required and optional fields that should appear on the Payflow Link forms, and how data is handled upon completion of a transaction. 16 VeriSign, Inc /Rev. 4

25 Chapter 2 Configuring Payflow Link The Form Configuration section contains the following configurable fields: Return URL Method Specify what should happen when the customer clicks the Continue button on the Receipt page (example on page 7). This action applies to successful transactions only. Specify one of the following values: Link: Returns the customer to the Web site that you specify in the Return URL field (typically your merchant Web site). Note Link is the default setting and is strongly recommended for merchants new to HTML. This setting returns the customer to the specified site. No additional transaction data is posted if this option is specified. POST: Returns the customer and transaction data to the Web site that you specify in the Return URL field. This option is typically used by experienced HTML/CGI developers to collect the information that was submitted on the VeriSign-hosted Order form. For more detailed information on POST, see Specifying How Data is Returned to Your Web Site on page 92 in Appendix B. Return URL Enter the URL of the Web site to which customers should be sent upon clicking the Continue button on the Receipt page (example on page 7). This URL is typically your merchant site. If you do not specify a URL, then the Continue button does not appear on the Receipt page. Silent Post URL Select the Silent Post URL box and enter the URL in the text field to specify the URL to which transaction data should be posted in the background (invisible to the customer) after transaction processing. For more detailed information on Return POST and Silent POST, see Specifying How Data is Returned to Your Web Site on page 92 in Appendix B. Force Silent POST Confirmation This option is used in conjunction with Silent POST it causes Payflow Link to verify that the Silent POST data was received by your Web site. If your server does not acknowledge receipt of the Silent POST data, then Payflow Link voids the transaction. Tip Even if you use Silent POST Confirmation to monitor sales, you should always verify transaction data in the Payflow Link Orders report, described on page 69. VeriSign, Inc /Rev. 4 17

26 VeriSign Payment Services Payflow Link User s Guide Failed Silent POST Return URL Specify where customers go if their transactions are voided by the Force Silent Post feature. This value is required if you specified Force Silent POST Confirmation. Required Fields The fields listed in this section represent information that you collect from the customer. A check mark specifies that the field is required the customer will not be allowed to continue with the transaction until the field is filled in. If you specify that a field is required, then you must do either of the following: Pass the data from your Web page to populate the field. Specify that the field is Editable in the next step. Editable Fields customer. Transaction Process Mode real transactions. A check mark specifies that the field can be edited by the Specify whether you want to conduct simulated or TEST: Transactions are handled through the test servers to enable you to verify and fine-tune system operation. Note VeriSign strongly urges that you operate in TEST mode and verify the operation of your account before you go live. See Chapter 7, Testing Payflow Link, for details. LIVE: Real financial transactions are performed through the VeriSign transaction servers. This option appears only if you have activated your account. Chapter 6, Going Live with Payflow Link, describes the full procedure for going live. Step 2 Complete the General Display Options section The General Display Options section enables you to configure the appearance of the order processing forms. You can display your organization s name and logo and specify the colors to be used on the forms. 18 VeriSign, Inc /Rev. 4

27 Chapter 2 Configuring Payflow Link Tip VeriSign strongly recommends that you add your logo to the pages and customize the color scheme to match your Web store pages. These actions help to support the customer s sense of security when using the Payflow Link forms. For initial testing, or to implement the simplest possible solution, you can safely skip this step no special graphics or colors will appear on the order forms, and default settings will be used. Enter the text (up to 63 characters) that will appear in the following locations: Browser title area for all forms At the top of all forms (unless you specify a logo) On receipts Specify whether the forms should be aligned with the left margin or should be centered in the Web page. Click this button to configure colors on the forms, and to specify a logo to appear on all forms, as described in Configuring the Appearance of the Order Processing Pages on page 20. VeriSign, Inc /Rev. 4 19

28 VeriSign Payment Services Payflow Link User s Guide Configuring the Appearance of the Order Processing Pages You have the option to specify the colors of the various parts of the processing forms and the color of the text on the forms, and to specify background and logo graphics. This example form shows the attributes that you can configure. Logo or Merchant Display Name text (described in Step 2 on page 18) Page background color or graphic image Header color Sidebar font color Header font color Sidebar color Body font color Body color Page font color Follow these steps to configure forms: 1 In the General Display Options section, click the Click to Configure button to open the Configure Your Transaction Pages page. 2 Select colors to appear on the forms. You can specify colors of both the body and text for headers, body of the page, sidebars, and footers, as shown in the Preview area. To change a color, click a field and then click a color in the color chart or enter a hexadecimal ASCII color number. At any time, click the 20 VeriSign, Inc /Rev. 4

29 Chapter 2 Configuring Payflow Link Preview button to view your color and graphical selections in the Preview area. To return to the default values or to the values that you last saved, click Reset. The Transparency option causes the item s color to be 50% transparent to reveal the background image or the page background color that you choose. Preview button Preview area Described in step 3 on page 22. Described in step 4 on page 22. Click any link for online help. VeriSign, Inc /Rev. 4 21

30 VeriSign Payment Services Payflow Link User s Guide 3 To upload a logo graphic to appear at the top of the forms, click Change Logo. The Upload Logo Image page opens. Note: If you both enter a merchant display name and upload a logo, only the logo image appears. The logo file should be a transparent GIF or JPG image less than 100K, with a resolution of 72 dpi, and maximum dimensions of 250 pixels wide by 65 pixels high. Select the file on your local system, then click Submit. To remove a logo, click Delete Logo Image, and then click Submit. 4 To upload a graphic to appear as the background for the forms, click Change Background. The Upload Background Image page opens. Note: If you both choose a page background color and upload a background graphic, only the background graphic appears. 5 The background file should be a GIF or JPG image. Select the file on your local computer and then click Submit. To remove a background image, click Delete Background Image and then click Submit. 6 Click Save to save your settings. You can reconfigure the order processing forms at any time be sure to save any changes. 7 Click Close to return to the Edit Configuration page. 22 VeriSign, Inc /Rev. 4

31 Chapter 2 Configuring Payflow Link Step 3 Configure the Receipt page The Receipt Display Options section enables you to customize the Receipt page that customers see after a transaction has been successfully processed. Specify text as it should appear on the Receipt page. All fields are optional. Tip For initial testing, or to implement the simplest possible solution, you can safely skip this step no custom text will appear on the receipt page. 1 Specify the Receipt Header Text (up to 511 characters). 2 Specify a Receipt Footer Text (up to 511 characters). 3 Specify up to 32 characters for the Receipt Button Text. This button returns your customer to the Web site that you specified in the Form Configuration section (Step 1 on page 16). This example Receipt page shows the resulting text. VeriSign, Inc /Rev. 4 23

32 VeriSign Payment Services Payflow Link User s Guide Step 4 Configure options Using the Options section, you can choose to send order confirmation messages to the customer, to yourself, or to both. The message includes the purchase amount, phone and fax numbers, the date and time of the transaction, and configurable text. To send order confirmation to the customer 1 Select YES for Receipt to Customer. 2 from Merchant Address: Enter the address from which the should appear to come (typically the address of a person or staff that can provide customer support). Note Verisign Payment Services generates this message on behalf of the merchant. However, this message does not appear in the merchant s Sent Items folder, nor is the actual message accessible to the merchant. 3 Optional: Header Text: Enter up to 510 characters to display at the top of the message. 4 Optional: Footer Text: Enter up to 510 characters to display at the bottom of the message. 24 VeriSign, Inc /Rev. 4

33 Chapter 2 Configuring Payflow Link To send order confirmation to your organization Fill in the fields as follows: 1 to Merchant Address: Enter the address to which messages confirming successful transactions should be sent. Leave this field blank if no confirmation should be sent. 2 Optional: to Merchant Address (copy): If desired, enter a second address for successful transaction confirmation s. Step 5 Configure security options Payflow Link enables you to configure the AVS, CSC, and Accepted URL security features. CAUTION It is your responsibility to protect your passwords and other confidential data and to implement security safeguards on your Web site and in your organization, or to ensure that your hosting company or internal Web operations team is implementing them on your behalf. You or your ISP/shopping cart provider should be able to adhere to security requirements as protective as those described at: VeriSign, Inc /Rev. 4 25

34 VeriSign Payment Services Payflow Link User s Guide Address Verification Service (AVS) Security Feature The Address Verification Service (AVS) compares the submitted street number and ZIP code with the values on file at the cardholder s bank. A separate Y, N, or X is returned for the customer s street number and ZIP code. Y = match, N = no match, X = cardholder s bank does not support AVS. Note AVS checks only for a street number match, not a street name match, so 123 Main Street returns the same response as 123 Elm Street. AVS is supported by most US banks and some international banks. Processors That Support AVS Visa MasterCard Discover American Express American Express EDS Aurora FDMS South FDMS First Data Nashville Global Payments Central (MAPP) Global Payments East Norwest Nova Paymentech Vital To specify the level of AVS checking Note AVS does not operate for accounts in TEST mode. In TEST mode, you must specify No or Light. If you specify Full or Medium, all transactions are declined. 26 VeriSign, Inc /Rev. 4

35 Chapter 2 Configuring Payflow Link Select one of the following values in the AVS field: No: This is the default setting: Accept the transaction regardless of the AVS response. Full: Accept the transaction only if a value of YY is returned (Y for street number and Y for ZIP code). If the bank does not return YY, then VeriSign voids the transaction and the customer is declined. Medium: Accept the transaction only if at least one Y is returned. If the bank does not return NY, XY, YN, or YX, then VeriSign voids the transaction and the customer is declined. Light: Accept the transaction for all return values except NN. If the bank does not return NN, then the transaction is approved. This table summarizes AVS levels: AVS Setting Allowed Responses Full (Y, Y) Medium (Y, Y), (Y, N), (Y, X), (N, Y), (X, Y) Light (Y, Y), (Y, N), (Y, X), (N, Y), (X, Y), (N, N), (N, X), (X, N) Using the Silent Post feature with AVS If you are using AVS checking and the Silent Post feature, then you can identify which transactions have been voided by looking for the following values: RESPMSG = AVSDECLINED and Result = 0. Card Security Code Validation The card security code (CSC) is a 3- or 4-digit number (not part of the credit card number) that appears on credit card. The customer enters the CSC on the Order Information form. Because the CSC appears only on the card and not on receipts or statements, the CSC provides some assurance that the physical card is in the possession of the buyer. VeriSign, Inc /Rev. 4 27

36 VeriSign Payment Services Payflow Link User s Guide Processors that Support CSC The CSC validation service is not available for all processors. CSC appears on the Edit Configuration page only if VeriSign is certified with your processor. For more information, see: Visa MasterCard Discover American Express American Express EDS Aurora FDMS South FDMS First Data Nashville Global Payments Central (MAPP) Global Payments East Norwest Nova Paymentech Vital Even though your processor may be certified for CSC, they may not be certified for all card types (for example, American Express (CID), or Discover). The list will change as VeriSign continues to enhance its service offering. See for the latest information. Special Cases: American Express and Discover American Express To enable the account to accept the CSC code, you must send an request to ES.Fraud.Prevention@aexp.com. 28 VeriSign, Inc /Rev. 4

37 Chapter 2 Configuring Payflow Link Once American Express has approved the request and has activated CSC for the you, you can begin passing CSC data and receiving the appropriate responses (Y, N, or X). If you attempt to send CSC data without having requested setup, American Express does not send a response. Discover Discover does not currently support CSC. If a merchant attempts to send CSC data, Discover does not send a response. About CSC The CSC appears on the back of most cards (usually in the signature field). All or part of the card number appears before the CSC (567 in the example). For American Express, the 4-digit number (1122 in the example) is printed on the front of the card, above and to the right of the embossed account number. If the buyer submits the CSC on the Order form, the cardholder s bank returns a Yes/No response on whether the value matches the number on file at the bank. Payflow Link accepts or rejects orders based on this information. The bank returns one of the following values: Y = The submitted value matches the data on file. N = The submitted value does not match the data on file. X = The cardholder s bank does not support this service. Configuring CSC Specify one of the following settings in the CSC field on the Edit Configuration page, as described in Step 1, Complete the Form Configuration section on page 16: VeriSign, Inc /Rev. 4 29

38 VeriSign Payment Services Payflow Link User s Guide No: This is the default setting: Approve the transaction regardless of the response. Full: Accept the transaction only if Y is returned. If N or X is returned, then void the transaction and send a declined message to the customer. Light: Accept the transaction only if Y or X is returned. If N is returned, then void the transaction and send a declined message to the customer. If you specify Light or Full, then you must set the CSC field (on the Form Configuration section of the Edit Configuration page) as Required. In addition, you must either set the field as Editable or pass the data from your Web page to pre-fill the field on the Order form. See Required Fields on page 18. Using the Silent Post feature with CSC If you have specified Silent Post, then, for voided transactions, Payflow Link returns the PNRef, a transaction type of V, and a response message of RESPMSG=CSCDECLINED. Accepted URL Security Feature The Accepted URL security feature stops fraudsters from changing the dollar value of amounts being passed to or from Payflow Link. When a customer places an order, Payflow Link compares the originating Web site against the domain names that you specify in the Accepted URL fields (typically, your Web store). If the Web site from which the transaction originates is not one of the specified domains, then the order is rejected. CAUTION The Accepted URL feature is designed to assist you, but is not a strong anti-fraud tool. If you are concerned about this issue, be sure to use VeriSign Manager to verify the dollar amount of all transactions. To Restrict Web sites from which a customer can be linked to Payflow Link These are optional fields. Leave these fields blank if you do not want to enforce domain-checking security. CAUTION If you leave the Accepted URL fields blank, Payflow Link will not authenticate the originating URL. This means that, even though you are a registered Payflow Link user, your URL is not automatically protected with domain-checking security. 30 VeriSign, Inc /Rev. 4

39 Chapter 2 Configuring Payflow Link In the Accepted URL fields, enter up to five URLs from which Payflow Link should accept orders (that is, the URL from which the HTML POST operation originates). These are typically your Web store address, a specific page on your Web store, or specific servers for your Web store. If someone attempts to post from a URL not specified in this list, Payflow Link rejects the order. Be sure to enter a valid URL prefixed with For example: This feature does not support (sites using SSL encryption). Tip You can specify a domain name in the Edit Configuration page such as to enable Payflow Link to accept orders from the same domain name with a path reference. For example, If you specify a path like however, Payflow Link will decline orders from Step 6 Save your configuration settings Click Save Changes (at the bottom of the Edit Configuration page) to implement the changes that you made. CAUTION If you leave the Edit Configuration page without clicking Save Changes, your changes are lost. VeriSign, Inc /Rev. 4 31

40 VeriSign Payment Services Payflow Link User s Guide 32 VeriSign, Inc /Rev. 4

41 re t pahc CHAPTER 3 3Integrating Your Web Site with Payflow Link (Basic Integration) This chapter provides full instructions for a simple integration option that enables you to begin to process transactions using Payflow Link in about an hour. IMPORTANT! VeriSign strongly recommends that you implement this minimum integration to familiarize yourself with Payflow Link operation before implementing a more customized integration. To implement a more robust implementation that customizes the customer s purchase experience, you can add data fields to the Payflow Link pages or eliminate the pages by collecting transaction data at your Web store and posting the data to the Payflow Link server. For more information on taking advantage of Payflow Link s advanced integration capabilities, see Chapter 4, Integrating Your Web Site with Payflow Link (Advanced Integration). Note Payflow Link enables your customers to process a single transaction amount. Payflow Link does not calculate the transaction amount based on customer selections. To enable customers to order multiple items or quantities, you must develop a solution that calculates the total transaction amount based upon customer selections in your Web store. Your code must then pass the total transaction amount to the Payflow Link server as described in this chapter. VeriSign, Inc /Rev. 4 33

42 VeriSign Payment Services Payflow Link User s Guide Example of a Simple Integration To connect your Web site to Payflow Link, you enter a few lines of HTML text into your store s Web page. In that text, you specify your Payflow account information and the amount and type of transaction. That s it! As a result, a Buy button appears on your Web page (you can specify the text that appears on the button). When a customer clicks the button, their browser displays the VeriSign-hosted pages, from which they submit the transaction. Upon closing the Receipt page, the customer is returned to your Web site. Follow these steps: 1 Copy and paste the following text into a text editor. (If you are viewing this document online, use the Adobe Acrobat Reader Text tool to select the text and click Ctrl-C to copy and Ctrl-V to paste it into the text editor.) <form method="post" action=" <input type="hidden" name="login" value="your LOGIN here"> <input type="hidden" name="partner" value="your PARTNER here"> <input type="hidden" name="amount" value="total transaction AMOUNT here"> <input type="hidden" name="type" value="transaction TYPE here"> <input type="submit" value="click here to Purchase"> </form> 2 Replace the bold text with actual values for the LOGIN, PARTNER, AMOUNT, and TYPE parameters, as follows: LOGIN: The login name that you chose for your Payflow account. PARTNER: The name of your Partner was provided to you by your VeriSign Reseller. If you registered with VeriSign directly, enter VeriSign. AMOUNT: Total amount of the transaction. The value must be greater than TYPE: A single letter that identifies the type of transaction (S: Sale or A: Authorization). Transaction types are described on page 35. Be sure to change only the text shown in bold in the example text. Leave the quotation marks ( ) in place. 34 VeriSign, Inc /Rev. 4

43 Chapter 3 Integrating Your Web Site with Payflow Link (Basic Integration) In this example, the LOGIN parameter has the value BeachBums, PARTNER is VeriSign, AMOUNT is 37.95, and TYPE has the value S (representing a Sale transaction type). The values shown in the example implement the purchase of a standard item or set of items (in the example, a case of each balls) for $ In addition, the example code adds the following button to your Web page: Type Code 3 Save the file and insert the HTML text into your Web page at the point where Payflow Link should complete the transaction. 4 Your next step is to open your Web page and test the button to ensure that it opens the VeriSign transaction pages and performs the transaction properly. See Chapter 7, Testing Payflow Link, for complete instructions. Payflow Link Transaction Types Payflow Link supports the following transaction types: Table 3-1 Transaction types Transaction Name S Sale / Payment Description Charges the specified amount against the account, and marks the transaction for immediate funds transfer (capture) during the next settlement period. VeriSign performs settlement on a daily basis. A Authorization A request to charge a cardholder. An Authorization reduces the cardholder s open-to-buy (credit card limit), but does not actually capture the funds. Merchants who do not ship goods immediately should use this transaction type. To actually charge the account and transfer the funds (settle the Authorization), you submit a Delayed Capture transaction using VeriSign Manager. If the Authorization is not settled within a certain period (determined by the issuing bank), it is deleted. The cardholder s open-to-buy is typically cleared in 5 to 7 days. VeriSign, Inc /Rev. 4 35

44 VeriSign Payment Services Payflow Link User s Guide 36 VeriSign, Inc /Rev. 4

45 re t pahc CHAPTER 4 4Integrating Your Web Site with Payflow Link (Advanced Integration) If you have HTML knowledge or Web development skills, you can create more customized Payflow Link integrations by starting with the code described in this chapter. VeriSign strongly recommends that before you implement the integration described in this chapter, you familiarize yourself with Payflow Link operation by implementing the simple integration described in Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration). Note Payflow Link enables your customers to process a single transaction amount. Payflow Link does not calculate the transaction amount based on customer selections. To enable customers to order multiple items or quantities, you must develop a solution that calculates the total transaction amount based upon customer selections in your Web store. Your code must then pass the total transaction amount to the Payflow Link server as described in this chapter. VeriSign, Inc /Rev. 4 37

46 VeriSign Payment Services Payflow Link User s Guide Example of a Custom Integration You may choose to collect detailed transaction data on your Web store and then pass the information to Payflow Link. Payflow Link accepts optional data fields that customize the purchase process. This enables either of the following options: Collect all billing information on your forms and pass it to VeriSign. The only data left for the customer to enter (on the secure VeriSign-hosted Order form) is the credit card information. Collect all billing and credit card information on your forms and pass the data to VeriSign. This enables you to disable all VeriSign-hosted pages (except the required Receipt page). CAUTION If you plan to collect credit card information on your Web site, VeriSign strongly recommends that you secure your Web site. For more information, visit Example HTML Code The following example collects purchase data on your form. When a customer enters data and clicks the button, the code sends the data to the Payflow Link server and opens the VeriSign-hosted Order form. <form method="post" action=" <!-- The following fields are required: --> <input type="hidden" name="login" value="your LOGIN here"> <input type="hidden" name="partner" value="your PARTNER here"> <input type="hidden" name="amount" value="total transaction amount here"> <input type="hidden" name="type" value="valid transaction type here"> <!-- See Payflow Link Transaction Types on page 39 for the list of valid transaction types. --> <!-- The following fields are optional--you can choose these or others: --> <input type="hidden" name="description" value="order description here"> <input type="hidden" name="name" value="billing name here"> <input type="hidden" name="address" value="billing address here"> <input type="hidden" name="city" value="billing city here"> <input type="hidden" name="state" value="billing state here"> <input type="hidden" name="zip" value="billing zip here"> <input type="hidden" name="country" value="billing country here"> <input type="hidden" name="phone" value="billing phone here"> <input type="hidden" name="fax" value="billing fax here"> <p>enter your Customer ID Number <input type="text" name="user1" size="12"></p> <align="left"> 38 VeriSign, Inc /Rev. 4

47 Chapter 4 Integrating Your Web Site with Payflow Link (Advanced Integration) <p>select the form of payment <select name="method" size="1"> <option selected value="cc">credit Card</option> <option value="echeck">telecheck</option></select></p> <p><input type="submit" value="click Here to Purchase"></p> </form> Note The example code shows a representative list of fields. You can further customize the code provided in this example by using fields described in Appendix B, Submitting Transaction Data to the Payflow Link Server. Passing Transaction Data to Payflow Link If you are collecting transaction data on your forms, you must write a script that passes the data to the Payflow Link HTML code. Alternatively, you can collect data by changing the fields from hidden fields to text fields. Instead of <input type="hidden"...>, use <input type="text"...>. This creates text boxes into which customers can enter information. The data is passed to VeriSign when the customer submits the order. Payflow Link Transaction Types Payflow Link supports the following transaction types: Table 4-1 Transaction types Type Code Transaction Name Description S Sale / Payment Charges the specified amount against the account, and marks the transaction for immediate funds transfer (capture) during the next settlement period. VeriSign performs settlement on a daily basis. A Authorization A request to charge a cardholder. An Authorization reduces the cardholder s open-to-buy (credit card limit), but does not actually capture the funds. Merchants who do not ship goods immediately should use this transaction type. To actually charge the account and transfer the funds (settle the Authorization), you submit a Delayed Capture transaction using VeriSign Manager. If the Authorization is not settled within a certain period (determined by the issuing bank), it is deleted. The cardholder s open-to-buy is typically cleared in 5 to 7 days. VeriSign, Inc /Rev. 4 39

48 VeriSign Payment Services Payflow Link User s Guide 40 VeriSign, Inc /Rev. 4

49 re t pahc CHAPTER 5 5Testing Payflow Link In Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration), you entered HTML code to connect your Web site to Payflow Link. Before you activate your Web store for actual customer use, you should test Payflow Link to verify proper operation. VeriSign s test server enables you to simulate transactions on your Web site and ensure that they are processed correctly. Transactions are handled through a test system and no actual funds are exchanged. This chapter describes the process that you follow to test your Payflow Link integration and to verify that it is operating correctly. Testing TeleCheck Transactions Testing TeleCheck Transactions on page 72 provides guidance on simulating TeleCheck transactions. Testing Credit Card Transactions Follow these steps to test the integration between your Web page and Payflow Link: Verify that the Transaction Process Mode is set to TEST Before you can begin simulating transactions, you must first ensure that the Transaction Process Mode is set to TEST so that no funds are transferred. Follow these steps: VeriSign, Inc /Rev. 4 41

50 VeriSign Payment Services Payflow Link User s Guide 1 Open VeriSign Manager to the Edit Configuration page, as described in Opening the Edit Configuration Page on page 13. Select TEST in the Transaction Process Mode field. Select NO or Light in the AVS field. 2 Click Save Changes (at the bottom of the page). Your account now connects with VeriSign s test servers so that you can safely run simulated transactions. Note Test Transactions are processed through VeriSign s simulated payment network to enable you to test Payflow Link no money changes hands. You must activate your account and set Transaction Process Mode to LIVE before accepting real orders. 42 VeriSign, Inc /Rev. 4

51 Chapter 5 Testing Payflow Link Performing Test Transactions To perform test transactions, go to your Web site and perform the purchase process as described here. Verify that the transactions are approved, declined, or referred as is appropriate. Testing Guidelines VeriSign provides test card numbers. Other numbers produce an error. Expiration Date must be a valid date in the future (use the mm/yy format). To view the credit card processor that you have selected for testing, see Account Info Processor Info in VeriSign Manager. Credit Card Numbers Used for Testing Use the following card numbers for testing. Any other card number produces a Live card used on test system error message or Result 23 Invalid Account Number. Visa Visa Visa MasterCard MasterCard American Express American Express Amex Corporate Discover Discover JCB JCB Diners Club Diners Club VeriSign, Inc /Rev. 4 43

52 VeriSign Payment Services Payflow Link User s Guide Testing Result Codes Responses You can use the amount of the transaction to generate a particular Result code. Table 5-1 lists the general guidelines for specifying amounts. Table 5-1 lists VeriSign result codes that are supported by this testing mechanism. Table 5-1 Result codes resulting from amount submitted Amount Result $0 $ (Approved) $1001 $2000 Certain amounts in this range will return specific VeriSign result codes, and can be generated by adding $1000 to that result code. For example, for Result 13 (Referral), submit the amount If the amount is in this range but does not correspond to a VeriSign result code supported by this testing mechanism, result 12 (Declined) is returned. $ Decline VeriSign Result Codes Returned Based on Transaction Amount This table lists the VeriSign Result codes that you can generate using the amount of the transaction. To generate a specific code, submit an amount of 1000 plus the code number (for example, submit an amount of 1013 for a Result code of 13). Note Appendix A, Transaction Results, describes each transaction Result code. Chapter 7, Managing Payflow Link, describes reports that display transaction details. Table 5-2 Processor VeriSign result codes supporting the amount control Result Codes available for testing Nashville 0, 12, 13, 104 Paymentech 0, 12, 13, 104 Vital 0, 4, 12, 13, 23, 104, 114, 1000 Nova 0, 12, 13, 104 EDS Aurora 0, 12, 13, 104 FDMS South 0, 12, 13, 104 Amex 0, 12, 13, 104, VeriSign, Inc /Rev. 4

53 Chapter 5 Testing Payflow Link Alternative Methods for Generating Specific Result Codes This table shows how to obtain VeriSign result codes. Non-zero results from processors are not returned by VeriSign s servers, and therefore cannot be simulated using the amount. In some cases, you may get certain results using the result code plus 1000 even though this table suggests another means of obtaining the result code. Table 5-3 Obtaining VeriSign result code Result Definition How to test using Payflow Pro 0 Approved Use an AMOUNT of $1000 or less Credit (C) and Force (F) transactions will always be approved regardless of dollar amount or card number. 1 User authentication failed Use an invalid PWD 2 Invalid tender Use an invalid TENDER, such as G 3 Invalid transaction type Use an invalid TRXTYPE, such as G 4 Invalid amount Use an invalid AMOUNT, such as 1 5 Invalid merchant information Use an AMOUNT of Applies only to the following processors: Global Payments East and Central, and American Express). 12 Declined Use an AMOUNT of 1012 or an AMOUNT of 2001 or more 13 Referral Use an AMOUNT of Original transaction ID not found Submit a Delayed Capture transaction with an invalid identifier of the original transaction: Use ORIGID for Payflow Pro. Use TRANSID (the Transaction ID in VeriSIgn Manager reports) for Payflow Link. 23 Invalid account number Submit an invalid account number, for example, Invalid expiration date Submit an invalid expiration date, for example, Transaction type not mapped to this host Submit a transaction for a card or tender you are not currently set up to accept, for example, a Diners card if you aren t set up to accept Diners. VeriSign, Inc /Rev. 4 45

54 VeriSign Payment Services Payflow Link User s Guide Table 5-3 Obtaining VeriSign result code (Continued) 101 Time-out value too small Set timeout value to Error reading response from host 104 Timeout waiting for processor response Use an AMOUNT of Use an AMOUNT of Credit error Attempt to credit an authorization. 108 Void error Attempt to void a captured authorization. 111 Capture error Capture an Authorization transaction twice or attempt to capture a transaction that is not an Authorization transaction. 112 Failed AVS check Use an AMOUNT of Note that in production this will only be encountered if you are configured by customer service to use the AVS Deny feature. 114 CVV2 Mismatch Use an AMOUNT of Only applies to Vital Generic Host Error Use an AMOUNT of Does not apply to Nova, EDS Aurora, American Express, or Global Payments East processors. Testing Address Verification Service (AVS) The VeriSign testing server simulates AVS by returning values for AVSADDR and AVSZIP based on the values shown in the tables. If the street address is 667 or higher or begins with a non-numeric character, the simulator returns AVSADDR=X, AVSZIP=X. Table 5-4 Testing AVS STREET Submitted Value for STREET Example STREET value AVSADDR Result Elm Y Main N 667 or higher or begins with a non-numeric character 792 Maple X 46 VeriSign, Inc /Rev. 4

55 Chapter 5 Testing Payflow Link Table 5-5 Testing AVS ZIP Submitted Value for ZIP Example ZIP value AVSZIP Result Y N Any value (if street address is 667 or higher or begins with a non-numeric character) 792 Maple, X Testing Card Security Code (CSC) For testing, the first three characters of the submitted CSC value determine the CVV2MATCH result. CSC value CSC Result (CVV2MATCH) Y N 601 or higher X If you have specified Silent POST, then, for voided transactions, Payflow Link returns the PNRef, a transaction type of V, and a response message of RESPMSG=CSCDECLINED. VeriSign, Inc /Rev. 4 47

56 VeriSign Payment Services Payflow Link User s Guide 48 VeriSign, Inc /Rev. 4

57 re t pahc CHAPTER 6 6Going Live with Payflow Link Once you have configured the Payflow Link forms, linked your Web store page to Payflow Link, and tested your Web site s integration with Payflow Link, you are ready to process live financial transactions (go live). You perform the following tasks: 1 Activate (register to go live with) your Payflow Link account (you may have already performed this step when you registered for the service at Note Activating your account does not take your account live. Your Payflow Link account is in TEST mode until you perform the next step. Going Live 2 Use the VeriSign Manager to change the Transaction Process Mode field from TEST to LIVE. (This is a manual step.) 3 Test live transactions. Once you have established your Internet Merchant account with an Acquiring Bank, follow these steps to begin processing financial transactions with Payflow Link: Step 1 Register to go live Perform this procedure only if you have not already registered to go live with your Payflow Link account. Follow these steps to register to go live: 1 Go to VeriSign Manager at and log in. VeriSign, Inc /Rev. 4 49

58 VeriSign Payment Services Payflow Link User s Guide 2 When the VeriSign Manager Welcome! page appears, click the Click Here to Go Live button. 3 The Merchant Services Agreement page opens. Review the agreement and click the Agree to Terms button. 50 VeriSign, Inc /Rev. 4

59 Chapter 6 Going Live with Payflow Link 4 The Enable Live Transactions page opens. Specify the credit cards that you will accept for payment and which processor you will use. In addition, you can specify whether you will accept checks and which processor to use for checks. Enter your Acquirer account information. Select Payflow Link. Read and follow VeriSign s branding requirements. Click Next to process your request. VeriSign, Inc /Rev. 4 51

60 VeriSign Payment Services Payflow Link User s Guide 5 The Confirmation page notifies you that VeriSign received your request. Click Next. 6 The Platform Setup requests the information provided to you by the Acquiring Bank. The information requested on this page varies, depending on the Acquirer. Enter the values and click Next. 52 VeriSign, Inc /Rev. 4

61 Chapter 6 Going Live with Payflow Link 7 The Pay by Credit Card page requests credit card information for the card that you want to use to pay for the Payflow Link service. Enter the values and click Next. 8 The Live Account Confirmation page confirms that your account status has been changed to LIVE. After a one hour processing period, your account will be able to perform live transactions. Take note of the links presented on the page. You can click either button, depending on what you would like to do next. VeriSign, Inc /Rev. 4 53

62 VeriSign Payment Services Payflow Link User s Guide Step 2 Set the Transaction Process Mode to LIVE 1 Go to VeriSign Manager at and log in. 2 Click Account Info on the menu bar. 3 Click Payflow Link Info. 4 In the Form Configuration section of the Edit Configuration page, set the Transaction Process Mode field to LIVE. 5 Click Save Changes. Step 3 Verify that live transactions are processed correctly Access your Web store and proceed with a transaction as if you were a customer. Verify proper operation as follows: Forms appear correctly (colors, logos, and text). The transaction is declined when the test credit card number is used. The transaction is approved when a working credit card number is used. (You can used VeriSign Manager to credit the card.) If you are using AVS, test it by entering false, then correct, address and Zip code information. 54 VeriSign, Inc /Rev. 4

63 re t pahc CHAPTER 7 7Managing Payflow Link In Chapter 2, you used VeriSign Manager to configure Payflow Link. You can also use VeriSign Manager to manage your Payflow Link account settings and transaction activity as well as to generate a variety of transaction reports. This chapter describes reports that you can use to monitor your Payflow Link account. Complete instructions for using VeriSign Manager and a more detailed discussion of available reports appear in VeriSign Manager User s Guide, available through the VeriSign Manager Download page. Using VeriSign Manager, you can perform the following tasks. Change your configuration settings, as described in Chapter 2, Configuring Payflow Link. Perform manual transactions (sale, credit, void, and so on) and view transaction details. Perform auto delayed captures, auto credits, and auto voids. CAUTION AVS does not operate for manual transactions performed from VeriSign Manager. Configure recurring payments. VeriSign s Recurring Billing Service is a scheduled payment solution that enables you to automatically bill your customers at regular intervals for example, a monthly fee of $42 for 36 months with an initial fee of $129. See VeriSign Payment Services Recurring Billing Guide. Perform searches for transactions by credit card number, transaction ID, or comment. View reports, as described in this chapter. VeriSign, Inc /Rev. 4 55

64 VeriSign Payment Services Payflow Link User s Guide Tip Before proceeding, learn how to get around in VeriSign Manager read the brief guided tour in VeriSign Manager User s Guide. In addition: Use VeriSign Manager s online help feature for information on using any page or field. To view online help, click the Help link. Generating Reports Click Reports on the VeriSign Manager menu bar to open the Reports page. To view a particular report, click the associated link. Use the Payflow Link Orders Report to search on Payflow Link sale orders processed through Payflow Link. See page 58. Use either the Daily Activity Report (page 61) or the Custom Report (page 62) to search on all transactions processed through either Payflow Link or VeriSign Manager (independent of whether the transaction succeeded or failed). Use the Transaction Summary Report (page 62) to view transaction totals by tender and transaction type for a given time period. This report is described in VeriSign Manager User s Guide. Transaction reports give daily account activity for the past three months. If you require reports for multiple processing days, use the Custom Report. Use the Settlement Report to view your transaction by transaction ID, time, transaction type, tender type, and other fields. This report is useful for reconciling transactions with bank statements/reports. The settlement report 56 VeriSign, Inc /Rev. 4

65 Chapter 7 Managing Payflow Link automatically adjusts the 24 hour time period for the report to the processor's settlement times. See page 64. Use the Shipping and Billing Report instead of the Payflow Link Orders Report when you have manually run transactions through VeriSign Manager and you recorded the shipping and billing information. See page 65. Tip Click the Transaction ID link on any transaction report to view the Transaction Detail page (described on page 66). Report Formats You can generate reports in the following formats (transactions are listed in rows and data in columns): HTML. HTML format, good for online viewing. Includes links that provide transaction details. ASCII Text. Tab-delimited ASCII text format. Use this format to export the data to a spreadsheet or to an accounting or reconciliation application, as described in VeriSign Manager User s Guide. The Daily Activity report offers the following formats: Summary (HTML). HTML format, good for online viewing. Includes links that provide transaction details. Full-Detail (HTML). HTML format, good for online viewing. Includes links that provide transaction details. Full-Detail (ASCII Text). Tab-delimited ASCII text format with the same fields as the Full-Detail (HTML) format. Use this format to export the data to a spreadsheet or to an accounting or reconciliation application, as described in VeriSign Manager User s Guide. Interpreting the Result Code A Result code appears for each transaction. A value of 0 (zero) indicates that no errors occurred and the transaction was approved. any other value indicates that an error occurred. Result codes are described in Transaction Result Codes on page 74. VeriSign, Inc /Rev. 4 57

66 VeriSign Payment Services Payflow Link User s Guide Generating the Payflow Link Orders Report You can generate sales reports for your Payflow Link customer orders using the Payflow Link Orders report. The Payflow Link Orders report shows only Authorizations and Sales that are performed using the Payflow Link order pages. Only Payflow Link users have access to this report. (Another useful report, the Shipping and Billing report, is described on page 65.) To view the Payflow Link Orders Report 1 Click Reports Payflow Link Orders. The Payflow Link Report page opens. 2 Specify the Report Type: Summary Report, Full-Detail Report, or ASCII. 3 Specify the date range of transactions and specify either Live or Test transactions. 4 Click Submit. The report type that you specified appears. 58 VeriSign, Inc /Rev. 4

67 Chapter 7 Managing Payflow Link Example Summary Report Example Full Detail Report To view the details of a particular order, click the Transaction ID link. The resulting Transaction Detail page is described in the next section. Table 7-1 Information in the Payflow Link Order report Field Description # Reference number of the transaction Date Transaction ID Name Transaction timestamp. Unique identifier for this transaction. Click this link to view the Transaction Detail page, as described in Viewing the Transaction Detail Page on page 66. Customer name. VeriSign, Inc /Rev. 4 59

68 VeriSign Payment Services Payflow Link User s Guide Table 7-1 Information in the Payflow Link Order report (Continued) Field Trans Type Amount Description Type code, as described in Payflow Link Transaction Types on page 90. This report shows only types S or A. Transaction amount. Result Result code, as described in Transaction Result Codes on page 74. Daily Activity Report: Full-Detail ASCII Text The ASCII text report contains these data fields in the following order: Row Number VeriSign Transaction ID Transaction Date and Time Transaction Type (Authorization, Sale, Credit, Delayed Capture, Void, Voice Authorization.) Tender Type (Visa, MasterCard, Discover, American Express/Optima, Diners Club, JCB) Amount VeriSign Transaction Result (0= Approved, 12 = Declined, etc.) Response Message Comment1 Comment2 60 VeriSign, Inc /Rev. 4

69 Chapter 7 Managing Payflow Link Generating Daily Activity Reports To generate a Daily Activity report: 1 Click Reports Daily Activity Report. The Daily Activity Report page opens. 2 Specify report criteria as described here and click Submit. Field Report Type Report Date Sort by Mode Enter/Select Summary Activity Report or Full-Detail Report, or Full-Detail ASCII text Specify a date for the report. Transaction ID, Transaction Time, Transaction Type, Card Type, Amount, or Result Ascending or Descending Specify Live or Test transactions. VeriSign, Inc /Rev. 4 61

70 VeriSign Payment Services Payflow Link User s Guide Generating Transaction Summary Reports Use the Transaction Summary Report to view transaction totals by tender and transaction type for a given time period. 1 Click Reports Transaction Summary Report. The Transaction Summary Report page opens. 2 Specify the date range of transactions. Specify Settled, Unsettled, or All transactions. If a Processor field appears, specify the processor. Specify the output format. 3 Specify either Live or Test transactions and click Submit. Generating Custom Reports The Custom report is a specialized report of your customer transactions for example, a report that lists all transactions over a three-day period for a particular credit card (Visa or MasterCard), or a report that lists only a particular type of transaction (sale or authorization) for all credit cards over a five-day period. 62 VeriSign, Inc /Rev. 4

71 Chapter 7 Managing Payflow Link 1 Click Reports Custom Report. The Custom Report page opens. Figure 7-1 Custom Report page 2 Specify the date and time range. The default Custom Time setting is 0:00:00 (midnight, local time). Be sure to set the appropriate time range for the report. 3 Specify the Report Filters (the criteria used to select which transactions to include in the report). For the example shown in Figure 7-1 on page 63, only declined Sale transactions on Visa and MasterCard between $50 and $300 will appear in the report. 4 Specify the output format (HTML or ASCII). 5 Specify which fields should appear in the report and how they should be sorted. 6 Click Submit to run the report. VeriSign, Inc /Rev. 4 63

72 VeriSign Payment Services Payflow Link User s Guide Generating Settlement Reports Use the Settlement report to view your transaction by transaction ID, time, transaction type, tender type, and other fields. This report is useful for reconciling transactions with bank statements/reports. The settlement report automatically adjusts the 24 hour time period for the report to the processor's settlement times. To generate a Settlement Report: 1 Click Reports Settlement Report. The Settlement Report page opens. 2 Specify a date and time range for the report. 3 Specify the report criteria as described in Table 7-2 and click Submit. Table 7-2 Settlement Report page fields Field Host Processor Settlement Status Display as Mode Select Specify the processor. Settled transactions, Unsettled transactions, All transactions. HTML or ASCII Specify Live or Test Transactions 64 VeriSign, Inc /Rev. 4

73 Chapter 7 Managing Payflow Link Generating Shipping and Billing Reports The Shipping and Billing report contains shipping, billing, and other information. 1 Click Reports Shipping and Billing Report. The Shipping / Billing Report page opens. Specify the date for the report. Specify how to sort the results: By Transaction ID, Transaction Time, Transaction Type, Card Type, Amount, or Result. Specify an Ascending or Descending sort. 2 Specify either Live or Test transactions and click Submit. The Shipping and Billing report opens. To view the details of a particular transaction, click the Transaction ID link. The resulting Transaction Detail page is described in Viewing the Transaction Detail Page on page 66. VeriSign, Inc /Rev. 4 65

74 VeriSign Payment Services Payflow Link User s Guide Viewing the Transaction Detail Page The Transaction Detail page displays specific information about a transaction, including the customer-entered data and the response data from the Processor. The Transaction Detail page appears whenever you click the Transaction ID link on any of the following pages: search utilities, reports, auto delayed capture, auto credits, or auto voids. Table 7-3 Information on the Transaction Detail page Request Data: Information submitted to the processor for the transaction. Trans ID Timestamp Duration Client IP Client Version AVS Street AVS Zip Vendor Transaction ID. This number uniquely identifies the transaction to enable you to refer to it in the future (for example, when Date and time that the transaction was submitted Length of transaction Client Internet Protocol. IP address of the Web server from which the transaction was submitted (usually your Web server or VeriSign Manager) Version of VeriSign software used to submit the transaction The street address submitted with this transaction The Zip code submitted with this transaction Your Login (see Opening the Edit Configuration Page on page 13). 66 VeriSign, Inc /Rev. 4

75 Chapter 7 Managing Payflow Link Table 7-3 Information on the Transaction Detail page (Continued) Trans Type Card Type Card Number Expiration Amount Comment1 Comment2 Transaction type (A = Authorization, S = Sale, C = Credit, D = Delayed Capture, V = Void, F = Voice Authorization). See Appendix A, Transaction Results, for more details. Type of credit card: determined by credit card number entered (0 = Visa, 1 = MasterCard, 2 = Discover, 3 = American Express/Optima, 4 = Diners Club, 5 = JCB, 255 = Invalid card type) Credit card number entered Expiration date of the credit card Amount of the transaction (in US dollars) Text entered in Comment1 field Text entered in Comment2 field Results: Information received for the transaction. Result Code Transaction result. Appendix A, Transaction Result Codes, in Appendix A, Transaction Results, provides full descriptions of these codes. Auth Code If transaction is approved, this is the authorization code returned by the credit card processor. AVS Street Match Result of the AVS check for street number and name (Y, N, or X) AVS Zip Match Result of the AVS check for zip code (Y, N, or X) Response Message Orig. Trans ID Orig. Amount Batch ID CSC Processor response code Original Transaction ID that this transaction references. For example, if this transaction is a delayed capture, the Orig Trans ID is the Transaction ID of the authorization. Amount of original transaction. For example, if the transaction were a delayed capture, this field would show the amount submitted with the original authorization. Settlement batch number. For most processors, 0 means that the transaction has not been settled. Any number above 0 means the transaction has been settled. (Note: For Vital, 6 means the transaction is not settled, 8 settled.) Deposits take 2 5 days. If the buyer enters a card security code number (CSC), then the value is masked and appears as xxxx. VeriSign, Inc /Rev. 4 67

76 VeriSign Payment Services Payflow Link User s Guide 68 VeriSign, Inc /Rev. 4

77 re t pahc CHAPTER 8 8Integrating TeleCheck Transactions In addition to accepting credit cards, your Web site can accept TeleCheck electronic checks using Payflow Link. This chapter describes how to implement TeleCheck payments. Tip Be sure to read Appendix B, Submitting Transaction Data to the Payflow Link Server, for information on more advanced implementations. In This Chapter Integrating Check Processing on page 70. Data That You Must Post if You do not use Payflow Link s Order Form on page 71. Transaction Results Returned for TeleCheck Transactions on page 72. Testing TeleCheck Transactions on page 72. Note If you did not indicate that you want to accept checks during the registration process for Payflow Link, you must contact VeriSign customer service to enable this function. For more information on TeleCheck, see the TeleCheck Web site at VeriSign, Inc /Rev. 4 69

78 VeriSign Payment Services Payflow Link User s Guide Integrating Check Processing CAUTION Payflow Link cannot void TeleCheck transactions. To integrate check processing with Payflow Link, you use the same HTML code that you use for credit cards, as described in Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration), However for check processing, the TYPE value must always be S, as shown in this example code: <form method="post" action=" <input type="hidden" name="login" value="acmetrampolines"> <input type="hidden" name="partner" value="verisign"> <input type="hidden" name="amount" value="42.00"> <input type="hidden" name="type" value="s"> <input type="submit" value="click here to Purchase"> </form> Enabling Customers to Specify the Payment Method If your Web site is structured to accept both checks and credit cards, then, by default, your customers will see the Select Payment Type page to enable them to specify the method of payment. To hide the page You can specify that the Payflow Link server should not display the page by specifying that the method of payment is TeleCheck. Include the following line in your HTML code: <input type="hidden" name="method" value="echeck"> 70 VeriSign, Inc /Rev. 4

79 Chapter 8 Integrating TeleCheck Transactions Data That You Must Post if You do not use Payflow Link s Order Form To use your custom order forms rather that the VeriSign-hosted forms, set ORDERFORM to False and POST the following name/value pairs to the Payflow Link server: Table 8-1 Transaction data required if ORDERFORM=False Field Name Description Max Length ADDRESS Billing address. 60 CHECKNUM Check number. 11 CITY Billing city. 32 DLNUM Driver s License Number. This value is required. 33 Billing address. 40 LOGIN The login name that you chose while enrolling for your Payflow account. METHOD Method of customer payment. ECHECK for electronic check. MICR MICR number of the check. The string appears at the bottom of the 31 check. NAME Billing name. 60 PARTNER The name of your Partner was provided to you by your VeriSign Reseller. If you registered with VeriSign directly, then enter VeriSign. PHONE Billing phone. 20 STATE Billing state. 20 STATEOFDL Driver s license state. (Two-letter abbreviation) 3 TYPEOFCHECK Type of check (P = Personal, B = Business). P is the default. ZIP Billing ZIP code. 15 VeriSign, Inc /Rev. 4 71

80 VeriSign Payment Services Payflow Link User s Guide Transaction Results Returned for TeleCheck Transactions The HOSTCODE return parameter returns the following six-digit code values: Table 8-2 Values returned by HOSTCODE Code Description Status Sale Approved Direct Check Sale/ECA approved Sale Approved Direct Check Sale approved (no ECA) Sale Approved Direct Check Sale/ECA approved no guarantee Sale Approved Direct Check Sale approved no ECA no guarantee Check Declined Direct Check Sale declined negative data Check Declined Direct Check Sale Decline Scoring Check Failure Direct Check Sale Check Failed Note For more information on other returned values, see Appendix B, Submitting Transaction Data to the Payflow Link Server. For more information on TeleCheck responses, see the TeleCheck Web site at Testing TeleCheck Transactions Use the following test data to test TeleCheck transactions: Table 8-3 Test TeleCheck transaction data Bank (MICR) Number Check No. Resulting HOSTCODE Value Check Approved ECA Check Approved No ECA Check Approved ECA, No Guarantee Check Approved No ECA, No Guarantee Check Decline Negative Data Check Decline Scoring Check Failed 72 VeriSign, Inc /Rev. 4

81 xi nd pe Ap APPENDIX A ATransaction Results This appendix describes the values that are returned for transactions. Transaction ID Value The Transaction ID is a unique transaction identification number issued by VeriSign that identifies the transaction for billing, reporting, and transaction data purposes. The Transaction ID associated with each transaction appears in all VeriSign Manager detail reports. If you use Post or Silent Post, then, for each completed transaction, the PNREF paramteter returns the Transaction ID value. (This identifier is know in the payments world as the Payment Network Reference ID value, so VeriSign named the parameter PNREF.) When you submit any of the following transaction types from VeriSign Manager, you enter the Transaction ID (the value returned by PNREF) in the Original Transaction ID field: Credit Delayed capture Void Transaction ID Format The Transaction ID value is 12 characters with the format Vxxxxxxxxxxx, for example, V89Z The content depends on whether the value represents a test or live transaction, as follows: VeriSign, Inc /Rev. 4 73

82 VeriSign Payment Services Payflow Link User s Guide For Test servers, the first and fourth characters are alpha characters (letters), and the second and third characters are numeric, for example V53A For Live servers, all of the first four characters are alpha characters (letters), for example: VPNE Transaction Result Codes The transaction Result indicates the overall status of the transaction attempt. The Result associated with each transaction appears in all VeriSign Manager detail reports. If you use Post or Silent Post, then the RESPMSG paramteter returns the description of the RESULT code. A value of 0 (zero) indicates that no errors occurred and the transaction was approved. A value greater than zero indicates a decline or error. Table A-1 on page 75 lists the result codes and their associated RESPMSG descriptions. A value less than zero indicates that a communication error occurred. In this case, no transaction is attempted. See Transaction Result Codes for Communications Errors on page VeriSign, Inc /Rev. 4

83 Appendix A Transaction Results Result Codes for Declined Transaction and Other Errors Table A-1 Result values for transaction errors RESULT RESPMSG (Description of the Result code) 0 Approved 1 User authentication failed 2 Invalid tender type. Your merchant bank account does not support the following credit card type that was submitted. 3 Invalid transaction type. Transaction type is not appropriate for this transaction. For example, you cannot credit an authorization-only transaction. 4 Invalid amount format 5 Invalid merchant information. Processor does not recognize your merchant account information. Contact your bank account acquirer to resolve this problem. 7 Field format error. Invalid information entered. See RESPMSG. 8 Not a transaction server 9 Too many parameters or invalid stream 10 Too many line items 11 Client time-out waiting for response 12 Declined. Check the credit card number and transaction information to make sure they were entered correctly. If this does not resolve the problem, have the customer call the credit card issuer to resolve. 13 Referral. Transaction was declined but could be approved with a verbal authorization from the bank that issued the card. Submit a manual Voice Authorization transaction and enter the verbal auth code. 19 Original transaction ID not found. The transaction ID you entered for this transaction is not valid. See RESPMSG. 20 Cannot find the customer reference number 22 Invalid ABA number 23 Invalid account number. Check credit card number and re-submit. 24 Invalid expiration date. Check and re-submit. 25 Invalid Host Mapping. Transaction type not mapped to this host VeriSign, Inc /Rev. 4 75

84 VeriSign Payment Services Payflow Link User s Guide Table A-1 Result values for transaction errors (Continued) RESULT RESPMSG (Description of the Result code) 26 Invalid vendor account 27 Insufficient partner permissions 28 Insufficient user permissions 29 Invalid XML document. This could be caused by an unrecognized XML tag or a bad XML format that cannot be parsed by the system. 30 Duplicate transaction 31 Error in adding the recurring profile 32 Error in modifying the recurring profile 33 Error in canceling the recurring profile 34 Error in forcing the recurring profile 35 Error in reactivating the recurring profile 36 OLTP Transaction failed 50 Insufficient funds available in account 99 General error. See RESPMSG. 100 Transaction type not supported by host 101 Time-out value too small 102 Processor not available 103 Error reading response from host 104 Timeout waiting for processor response. Try your transaction again. 105 Credit error. Make sure you have not already credited this transaction, or that this transaction ID is for a creditable transaction. (For example, you cannot credit an authorization.) 106 Host not available 107 Duplicate suppression time-out 76 VeriSign, Inc /Rev. 4

85 Appendix A Transaction Results Table A-1 Result values for transaction errors (Continued) RESULT RESPMSG (Description of the Result code) 108 Void error. See RESPMSG. Make sure the transaction ID entered has not already been voided. If not, then look at the Transaction Detail screen for this transaction to see if it has settled. (The Batch field is set to a number greater than zero if the transaction has been settled). If the transaction has already settled, your only recourse is a reversal (credit a payment or submit a payment for a credit). 109 Time-out waiting for host response 111 Capture error. Either an attempt to capture a transaction that is not an authorization transaction type, or an attempt to capture an authorization transaction that has already been captured. 112 Failed AVS check. Address and ZIP code do not match. An authorization may still exist on the cardholder s account. 113 Merchant sale total will exceed the sales cap with current transaction. ACH transactions only. 114 Card Security Code (CSC) Mismatch. An authorization may still exist on the cardholder s account. 115 System busy, try again later 116 VPS Internal error. Failed to lock terminal number 117 Failed merchant rule check. An attempt was made to submit a transaction that failed to meet the security settings specified on the VeriSign Manager Security Settings page. See VeriSign Manager User s Guide. 118 Invalid keywords found in string fields 122 Merchant sale total will exceed the credit cap with current transaction. ACH transactions only. 125 Fraud Protection Services Filter Declined by filters 126 Fraud Protection Services Filter Flagged for review by filters 127 Fraud Protection Services Filter Not processed by filters 128 Fraud Protection Services Filter Declined by merchant after being flagged for review by filters 1000 Generic host error. See RESPMSG. This is a generic message returned by your credit card processor. The message itself will contain more information describing the error. VeriSign, Inc /Rev. 4 77

86 VeriSign Payment Services Payflow Link User s Guide Table A-1 Result values for transaction errors (Continued) RESULT RESPMSG (Description of the Result code) 1001 Buyer Authentication Service unavailable 1002 Buyer Authentication Service Transaction timeout 1003 Buyer Authentication Service Invalid client version 1004 Buyer Authentication Service Invalid timeout value 1011 Buyer Authentication Service unavailable 1012 Buyer Authentication Service unavailable 1013 Buyer Authentication Service unavailable 1014 Buyer Authentication Service Merchant is not enrolled for Buyer Authentication Service (3-D Secure). To enroll, log in to VeriSign Manager, click Security, and then click the Buyer Authentication Service banner on the page Buyer Authentication Service Invalid card type 1022 Buyer Authentication Service Invalid or missing currency code 1023 Buyer Authentication Service Merchant has not activated buyer authentication for this card type 1041 Buyer Authentication Service Validate Authentication failed: missing or invalid PARES 1042 Buyer Authentication Service Validate Authentication failed: PARES format is invalid 1043 Buyer Authentication Service Validate Authentication failed: Cannot find successful Verify Enrollment 1044 Buyer Authentication Service Validate Authentication failed: Signature validation failed for PARES 1045 Buyer Authentication Service Validate Authentication failed: Mismatched or invalid amount in PARES 1046 Buyer Authentication Service Validate Authentication failed: Mismatched or invalid acquirer in PARES 1047 Buyer Authentication Service Validate Authentication failed: Mismatched or invalid Merchant ID in PARES 1048 Buyer Authentication Service Validate Authentication failed: Mismatched or invalid card number in PARES 78 VeriSign, Inc /Rev. 4

87 Appendix A Transaction Results Table A-1 Result values for transaction errors (Continued) RESULT RESPMSG (Description of the Result code) 1049 Buyer Authentication Service Validate Authentication failed: Mismatched or invalid currency code in PARES 1050 Buyer Authentication Service Validate Authentication failed: Mismatched or invalid XID in PARES 1051 Buyer Authentication Service Validate Authentication failed: Mismatched or invalid order date in PARES 1052 Buyer Authentication Service Validate Authentication failed: This PARES was already validated for a previous Validate Authentication transaction Transaction Result Codes for Communications Errors A value for RESULT less than zero indicates that a communication error occurred. In this case, no transaction is attempted. A value of -1 or -2 usually indicates a configuration error. Either the VeriSign server is unavailable, or incorrect server/socket pairs have been specified. A value of -1 can also result when there are Internet connectivity errors. Refer other errors to VeriSign at vps-support@verisign.com. Table A-2 Result values for communications errors Result RESPMSG (Description of the Result code) -1 Failed to connect to host -2 Failed to resolve hostname -5 Failed to initialize SSL context -6 Parameter list format error: & in name -7 Parameter list format error: invalid [ ] name length clause -8 SSL failed to connect to host -9 SSL read failed -10 SSL write failed -11 Proxy authorization failed -12 Timeout waiting for response VeriSign, Inc /Rev. 4 79

88 VeriSign Payment Services Payflow Link User s Guide Table A-2 Result values for communications errors (Continued) Result RESPMSG (Description of the Result code) -13 Select failure -14 Too many connections -15 Failed to set socket options -20 Proxy read failed -21 Proxy write failed -22 Failed to initialize SSL certificate -23 Host address not specified -24 Invalid transaction type -25 Failed to create a socket -26 Failed to initialize socket layer -27 Parameter list format error: invalid [ ] name length clause -28 Parameter list format error: name -29 Failed to initialize SSL connection -30 Invalid timeout value -31 The certificate chain did not validate, no local certificate found -32 The certificate chain did not validate, common name did not match URL -99 Out of memory 80 VeriSign, Inc /Rev. 4

89 xi nd pe Ap APPENDIX B BSubmitting Transaction Data to the Payflow Link Server This chapter is intended for merchants intermediate or advanced HTML knowledge or Web development skills. This chapter describes the options you have for sending transaction data to the Payflow Link server. This chapter also describes the transaction parameters that you can send to the Payflow Link server and the data that you can choose to have returned to your Web site when a transaction is complete. In This Chapter About VeriSign s Transaction Database on page 82. Collecting Customer Transaction Data, Option 1: Use the Payflow Link Order Form on page 82. Collecting Customer Transaction Data, Option 2: Collect the data on your Web page and Post it to the Payflow Link server on page 85. Optional Transaction Data on page 87. Payflow Link Transaction Types on page 90. Returning Data to Your Web Site on page 90. Data Returned by the Post and Silent Post Features on page 93. Parameters That Specify Payflow Link Operation on page 95. VeriSign, Inc /Rev. 4 81

90 VeriSign Payment Services Payflow Link User s Guide About VeriSign s Transaction Database All of the transaction data submitted to the Payflow Link server whether the source is the Payflow Link Order form or your Web page is stored in VeriSign s transaction database. You can search for particular transaction data using the search tools described in VeriSign Manager User s Guide. You can also view transaction data in VeriSign Manager reports, described in Chapter 8, Managing Payflow Link. In particular, the Order Detail report and the Custom report display a large amount of transaction data. Some transaction parameters are intended to enable you to retain session information and other temporary data these values are not stored in the database. See Retaining Session Data and other Temporary Information on page 91. Collecting Customer Transaction Data, Option 1: Use the Payflow Link Order Form You can use the Payflow Link Order form to collect transaction data from the customer. This default configuration is described in Chapter 3, Integrating Your Web Site with Payflow Link (Basic Integration). This configuration minimizes the data that you must collect at your site and pass to VeriSign. Tip One significant benefit of using this configuration is that you do not have to invest in the security infrastructure required to accept account information (credit card number and expiration date) at your site VeriSign performs the secure transfer of this data. As described in Complete the Form Configuration section on page 16, you specify the fields that appear on the Order form by selecting them in the Configuration page. For this case, the minimum set of data that you must POST to Payflow Link is described in Data That You Must Pass if You Use Payflow Link s Order Form on page 84. In addition, you can pass any of the data described in Optional Transaction Data on page VeriSign, Inc /Rev. 4

91 Appendix B Submitting Transaction Data to the Payflow Link Server Pre-populating Order Form Fields To improve your customer s experience, you may wish to populate the Order form with information that your site has already collected. You can pre-populate any Order form field by using the HTML POST method to send the associated name/value pair to the Payflow Link server. In this example, you populate the Total Amount (a required value), Name, Address, and City fields: <form method="post" action=" <input type="hidden" name="login" value="beachbums"> <input type="hidden" name="partner" value="verisign"> <input type="hidden" name="type" value="s"> <input type="hidden" name="amount" value="12.00"> <input type="hidden" name="name" value="tina Johnson"> <input type="hidden" name="address" value="123 Main St."> <input type="hidden" name="city" value="tahoma"> <input type="submit" value="buy"> </form> As a result, the values appear in the Order form (the card number and expiration date values were collected by the Credit Card Information page): VeriSign, Inc /Rev. 4 83