Website Payments Pro – HTTPS Interface Developer’s Guide For Professional Use Only Currently only available in English. A usage Professional Uniquement Disponible en Anglais uniquement pour l’instant.
Website Payments Pro – HTTPS Interface Developer’s Guide Document Number: 200039.en_US-200708 © 2007 PayPal, Inc. All rights reserved. PayPal is a registered trademark of PayPal, Inc. The PayPal logo is a trademark of PayPal, Inc. Other trademarks and brands are the property of their respective owners. The information in this document belongs to PayPal, Inc. It may not be used, reproduced or disclosed without the written approval of PayPal, Inc. PayPal (Europe) Ltd.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Documentation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Chapter 1 About the HTTPS Interface . . . . . . . . . . . . . . . . . 5 Overview . . . . . . . . . . . . . . . . . . . . . . . .
Contents 2 August 2007 HTTPS Interface Developer’s Guide
Preface This Document This document describes the HTTPS interface, which allows you to post transactions directly to the Payflow servers. Use the HTTPS interface for all operating systems and language besides Java and .NET. Documentation Problems If you discover any errors in or have any problems with this documentation, please email us by following the instructions below.
Revision History 4 August 2007 HTTPS Interface Developer’s Guide
1 About the HTTPS Interface This chapter contains the following topics: z Overview z Moving from the Payflow SDK to the HTTPS interface z Getting sample code z Contacting Support Overview The HTTPS interface allows you to post transactions directly to the Payflow servers. N O T E : If you are programming in Java or .NET, you can simplify the implementation by using an SDK. The SDKs are based upon this HTTPS interface. The .NET SDK can be used with classic ASP. For SDKs, see https://www.paypal.
About the HTTPS Interface Getting sample code Getting sample code For sample code, visit the Payflow Gateway forum in the PayPal Developer Community. Contacting Support For support, post your question or issue on the Payflow Gateway forum or go to https://www.paypal.com/mts, select Contact Support, and create a ticket.
2 Reference This chapter contains the following topics: z URLs for sending messages z Standard HTTPS headers z Transaction message z Common problems URLs for sending messages Use the following URLs for sending transactions to PayPal's Payflow servers: z Production (Live): https://payflowpro.verisign.com/transaction z Pilot (Test): https://pilot-payflowpro.verisign.
Reference HTTPS headers PayPal protocol headers Protocol Header Description Req? X-VPS-REQUEST-ID A unique identifier for each request, whether the request is a single NVP transaction or an XMLPay 2.0 document with multiple transactions. This identifier is associated with all the transactions in a particular request. You must provide the X-VPS-REQUEST-ID value in the transaction request. The Payflow server uses the X-VPS-REQUEST-ID to check for duplicate transaction requests.
Reference Transaction message Integrator-provided headers These headers are extensions to the Payflow HTTPS interface. The extension parameters describe the version of the application and the application’s environment. N O T E : Even though these parameters are not required, it is strongly recommended that you send them. Parameter Description Req? X-VPS-VITINTEGRATION-PRODUCT Identifies the product that is integrated with the Payflow server.
Reference Transaction message N O T E : The examples below are in NVP format. XMLPay uses the same format as NVP except that the content-type is text/xml and the body of both the request and response contain the XML document. Transaction request The transaction request consists of a transaction request header and body. Transaction request header The following is an example of a transaction request header associated with a message in NVP format: Connect: close Content-Length: ...
Reference Common problems X-VPS-REQUEST-ID is the same ID sent in the transaction request. N O T E : Ignore the X-VPS-RESPONSE-ID. It will be removed at a later time. Transaction response body The transaction response body contains the response to the request.
Reference Common problems 12 August 2007 HTTPS Interface Developer’s Guide
