
HTTPS Interface Developer’s Guide August 2007 5
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 OTE: 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.com/IntegrationCenter/ic_downloads.html.
This guide contains the information you will need to construct the HTTPS message. The body
of the transaction is in name-value pair (NVP) or XMLPay format. For details of the NVP
format, see Website Payments Pro Developer’s Guide. For details of XMLPay format, see
Website Payments Pro – XMLPay Developer’s Guide.
Moving from the Payflow SDK to the HTTPS interface
The Payflow Pro SDK contains APIs that do the following:
1. Create a connection with the Payflow server
2. Submit the transaction
3. Destroy the transaction
When you move to the HTTPS interface, you will have to rewrite these portions of the code.
You will need to complete four steps:
1. Write code that creates an HTTPS connection with the Payflow server.
2. Write an HTTPS request to submit your transaction data.
3. Receive the HTTPS reponse and extract the parameters.
4. Add code for error handling, retry logic, and duplicate transaction handling.
Comentarios a estos manuales