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. is authorised and regulated by the Financial Services Authority in the United
Kingdom as an electronic money institution. PayPal FSA Register Number: 226056.
Notice of Non-Liability
PayPal Inc. is p ro viding the information in this document to y o u “AS-IS” with all faults. PayPal Inc. make s
no warranties of any kind (whether express, implied or statutory) with respect to the information
contained herein. PayPal Inc. assumes no li ability for damages (whether direct or indirect), caused by
errors or omissions, or resulting from the use of this document or the information contained in this
document or resulting from the application or use of the product or service described herein. PayPal Inc.
reserves the right to make changes to any information herein without further notice.
PayPal Inc. does not guarantee that the features described in this document will be announced or made
available to anyone in the future.
4August 2006Express Checkout and Direct Payment Simulator Guide
Preface
About this Document
This document provides guidelines for testing your implementation of Express Checkout and
Direct Payment and for interpreting the results.
For complete information on the function calls and parameters referred to in this document,
see the Payflow Pro Developer’s Guide.
For specific details on how to implement Website Payments Pro Payflow Edition through the
Payflow Software Developer’s Kit (SDK), see the documentation provided with the Payflow
SDK. Implement the function calls as described, and then modify your application to point to
the test environment to conduct testing.
Audience
This guide assumes that its users:
z Are experienced Web or application developers
z Have a background in payments services
The user should also be familiar with Payflow Pro Developer’s Guide. That document, along
with this guide, are the primary sources of information on developing payments applications
using the Payflow SDK.
Conventions Used in this Guide
In this guide, you refers to the merchant and buyer refers to a customer of the merchant.
Where to Go for More Information
For more information, see the Payflow Pro Developer’s Guide.
For answers to specific questions about Payflow products, search PayPal’s Knowledge Base at
the following URL:
http://knowledge.paypal.com/.
Express Checkout and Direct Payment Simulator GuideAugust 20065
Preface
How to Contact Customer Service
How to Contact Customer Service
You may contact Customer Service at payflow-support@paypal.com.
Revision History
Revision history for Express Checkout and Direct Payment Simulator Guide.
TABLERevision HistoryP.1
DateDescription
July 2006Revision history started.
August 2006Added section titled
Updated note in
“Selecting a Predefined Buyer for Testing” on page 14.
“Setting Verbosity” on page 9.
6August 2006Express Checkout and Direct Payment Simulator Guide
1
Test Environment
The test environment allows you to easily test your integration without having to create a
Website Payments Pro Payflow Edition merchant account or PayPal buyer accounts. The test
environment allows you to test Express Checkout Transaction Processing and Direct Payment
Credit Card Processing.
In the production environment, you must create and configure a Website Payments Pro
Payflow Edition merchant account. Additionally, for Express Checkout, each of your
customers would have a PayPal buyer account to use as the source of funds in a transaction.
The test environment sets up “test” versions of these standard accounts for you in advance so
you can start testing right away.
For complete information on the function calls and parameters referred to in this document,
see the Payflow Pro Developer’s Guide.
For specific details on how to implement Website Payments Pro Payflow Edition through the
Payflow SDK, see the documentation provided with the Payflow SDK. Implement the
function calls as described, then modify your application to point to the test environment to
begin testing.
Express Checkout and Direct Payment Simulator GuideAugust 20067
Test Environment
1
8August 2006Express Checkout and Direct Payment Simulator Guide
2
Overview
The test environment allows you to test Direct Payment Credit Card transactions.
NOTE: Direct Payment Credit Card transactions require that you set the parameters as
In this Chapter
z “Setting the Host Address” on page 9
z “Setting Verbosity” on page 9
z “Transaction Response Parameters” on page 10
z “Void, Delayed Capture, and Credit Transaction Parameters” on page 11
Testing Direct Payment
described in the
Payflow Pro Developer’s Guide.
Setting the Host Address
To test your integration, simply change the host address to point to the test environment in
your website application.
z To test transactions in the test environment, use the following URL:
test-payflow.verisign.com
z To send transactions to live servers in the production environment, use the following URL:
payflow.verisign.com
Setting Verbosity
You must set the VERBOSITY parameter to MEDIUM to get return values for PROCAVS and
PROCCVV2.
Express Checkout and Direct Payment Simulator GuideAugust 20069
Testing Direct Payment
2
Transaction Response Parameters
Transaction Response Parameters
The following table shows parameter values returned in a transaction response in the test
environment.
TABLETransaction Response Return Parameter Values
2.1
ParameterTest Environment Behavior
PPREF Unique ID is generated
PROCAVS See “AVSCode Return Values” on page 10
PROCCVV2 See “CVV2 Code Return Values” on
AVSCode Return Values
The following table lists the PayPal Processor AVSCode returned based on the values of
address and zip code.
NOTE: For more information on PROCAVS and the meaning of the PayPal Processor
AVSCode, see the
TABLE 2.2AVSCode Returned Based on Address and Zip Code
Address RangeZip Range
000-33350001-99999 A
page 11
Payflow Pro Developer’s Guide.
PayPal Processor
AVSCode
000-33300101-00200 B
000-33300201-00300 C
000-33300301-00400 D
667-99900000-09999 E
667-99910000-19999 G
667-99920000-29999 I
667-99930000-39999 R
667-99940000-49999 S
667-99950000-59999 U
000-33300501-01000 F
000-33301001-01500 X
10August 2006Express Checkout and Direct Payment Simulator Guide
TABLE 2.2AVSCode Returned Based on Address and Zip Code (Continued)
Address RangeZip Range
000-33301501-02000 Y
334-66650001-99999 N
334-66600000-10000 P
334-66610001-20000 W
334-66620001-50000 Z
All other
CVV2 Code Return Values
The following table lists the PayPal Processor CVV2 codes returned based on the value of
CVV2.
Testing Direct Payment
Void, Delayed Capture, and Cred it Transaction Parameters
PayPal Processor
AVSCode
2
NOTE: For more information on CVV2 and the meaning of the PayPal Processor CVV2 Code,
see the
TABLECVV2 Code Returned Based on CVV2 Range
2.3
CVV2 RangePayPal Processor CVV2 Code
0-300M
301-600N
601-700P
701-800S
801-900U
901-999X
All other
Payflow Pro Developer’s Guide.
Void, Delayed Capture, and Credit Transaction Parameters
For information on Void, Delayed Capture, and Credit Transaction parameters, see Chapter 4,
“Testing Void, Delayed Capture, and Credit Transactions.”
Express Checkout and Direct Payment Simulator GuideAugust 200611
Testing Direct Payment
2
Void, Delayed Capture, and Credit Transaction Parameters
12August 2006Express Checkout and Direct Payment Simulator Guide
3
Overview
The test environment allows you to test the entire flow of your Express Checkout integration,
including the redirect to PayPal and the return back to your website.
In the test environment for Express Checkout, you can select a predefined buyer, customize
the simulated PayPal buyer login page, and redirect the buyer to that logi n page. The buyer can
log in and enter shipping information.
The test environment provides simulations of the following PayPal website pages:
z Login page
z Review Your PayPal Information page
The test environment also includes simulated buyer accounts that are set up in advance.
After logging in and confirming funding and shipping information, the buyer is redirected
back to your website to the RETURNURL (or CANCELURL) value that you declared in the call to
Set Express Checkout.
Testing Express Checkout
Because the test environment is set up in advance for you – and because you do not have a true
Website Payments Pro Payflow Edition merchant account – standard response s are returned
regardless of the input parameters or PayPal merchant profile configuration values you may
have set in the production environment.
NOTE: Express Checkou t requires that you set parameters as described in the Payflow Pro
Developer’s Guide
In this Chapter
z “Changing HOSTADDRESS for Testing” on page 13
z “Redirecting the Buyer to the PayPal Login Page” on page 14
z “Selecting a Predefined Buyer for Testing” on page 14
z “Setting Up the Test PayPal Login Page” on page 18
z “Express Checkout Parameters” on page 19
.
Changing HOSTADDRESS for Testing
To test your integration, simply change the host address to point to the test environment in
your website application.
Express Checkout and Direct Payment Simulator GuideAugust 200613
Testing Express Checkout
3
Redirecting the Buyer to the PayPal Login Page
z To test transactions in the test environment, use the following URL:
test-payflow.verisign.com
z To send transactions to the live servers in the production environment, use the following
URL:
payflow.verisign.com
Redirecting the Buyer to the PayPal Login Page
Once you have completed the call to Set Express Checkout, redirect the buyer to PayPal to
allow the buyer to log in to their account and select the shipping and billing information on the
Review Your PayPal Information page. When selections are complete, the buyer is redirected
back to your merchant website at the location indicated by RETURNURL or CANCELURL in
the call to Set Express Checkout.
In this test environment, you redirect the buyer to a simulated PayPal Login page exactly as
you would to the real PayPal Login page in production. Use the following URLs for the PayPal
Login page:
z To redirect the buyer to the simulated PayPal Login page in the test environment, use the
following URL, where value is the token value returned by Set Express Checkout:
The Set Express Checkout response returns the token value. If a token value is not returned or
is not valid, the browser is redirected to the documentation page at the following URL:
In the production environment, an error page appears.
Selecting a Predefined Buyer for Testing
As part of the test environment, predefined buyers are provided. These buyers have different
default attributes to allow you to test different scenarios.
NOTE: In the test environment, the EMAIL parameter is used to specify one of the four pre-
defined buyer profiles. The default is Buyer1. For more information, see
Checkout Parameters” on page 19.
“Set Express
The predefined buyers are:
z Buyer 1 (U.S. default) as described in Table 3.1, “Buyer 1 Profile U.S.”
z Buyer 2 (U.S.) as described in Table 3.2, “Buyer 2 Profile U.S.”
14August 2006Express Checkout and Direct Payment Simulator Guide
Buyer 1
Buyer 2
Testing Express Checkout
Selecting a Predefined Buyer for Testing
z Buyer 10 (UK default) as described in Table 3.3, “Buyer 10 Profile UK”
z Buyer 11 (UK) as described in Table 3.4, “Buyer 11 Profile UK”
Table 3.1, “Buyer 1 Profile U.S.,” shows the details of the default U.S. buyer.
Express Checkout and Direct Payment Simulator GuideAugust 200617
Testing Express Checkout
3
Setting Up the Test PayPal Login Page
TABLE 3.4Buyer 11 Profile UK (Continued)
AttributeValue in Test Environment
Address AddressStatus: confirmed
Address AddressStatus: confirmed
Name: Paul Casey
Street1: 114 Mason Street
Street2:
CityName: Westminster
StateOrProvince: London
PostalCode: WC3 1AF
Country: UK
Name: Donna Clarke
Street1: 118 Steeplechase Lane
Street2: Apt. 11
CityName: Derbyshire
StateOrProvince: Derbyshire
PostalCode: SW 15 2LJ
Country: UK
Setting Up the Test PayPal Login Page
When you redirect the buyer to the test URL, a simulation of the PayPal Login page appears.
The buyer username appears in the username field. Colors in the page are set as follows:
z The default page style is used regardless of the PAGESTYLE setting. The testing
environment creates a default style (testStyle) for the page. The colors and image for
testStyle are as described for the PAGESTYLE parameter in
Checkout Parameters in the T est Environment.” Normally , in p roduction, you would create
one or more page styles as part of your merchant profile and send one of those as a
parameter in the call to Set Express Checkout. In the test environment, testStyle is the
only page style available.
z If you set a specific color for the background, heade r background, or header border, these
colors will override the default colors. When setting specific colors, do not set
PAGESTYLE.
z If the page style is not set, and no individual colors or image is set, a standard set of colors
are used.
The Login page looks similar to the production Login page, but many links are non-operational
since they are not needed to test the integration. The Login and Cancel buttons are operational
and function as normal. When selecting the Login page, it is not necessary to enter a password.
The Cancel button returns the browser to the CANCELURL, as defined in the call to Set Express
Checkout. If the RETURNURL or the CANCELURL value is not set, the browser is redirected to
http://www.paypal.com/ as a default.
Table 3.5, “Set Express
18August 2006Express Checkout and Direct Payment Simulator Guide
Reviewing the Test Fun ding and Shipping Page
If the buyer clicks Login from the Login page, they go to the Review Your PayPal Information
page. This page allows the buyer to select a source of funds and enter shipping information.
Only the shipping information settings can be modified. The source of funds does not impact
your integration. The Continue Checkout and Cancel buttons operate normally to return the
buyer to the location defined by RETURNURL or CANCELURL, respectively.
Express Checkout Parameters
This section describes the differences between the behavior of Express Checkout parameters
in W ebsite Payments Pro Payfl ow Edition calls made in the test environment and calls made in
the production environment.
NOTE: See the Payflow Pro Developer’s Guide for details on Express Checkout parameters.
Set Express Checkout Parameters
Testing Express Checkout
Express Checkout Parameters
3
In the test environment, Set Express Checkout parameters are accepted and stored normally,
but many are inaccessible since the PayPal reporting services are not part of the test
environment. In these cases, the test environment does not enforce all the parameter
constraints that would be enforced in production.
Table 3.5, “Set Express Checkout Parameters in the Test Environment,” describes differences
in parameter behavior in the test environment. Parameters that are not listed have the same
behavior.
TABLE 3.5Set Express Checkout Parameters in the Test Environment
ParameterTest Environment Behavior
MAXAMT Not enforced.
RETURNURL Same as production environment. However, set the URL
to your test environment when using the test environment.
CANCELURLSame as production environment. However, set the URL
to your test environment when using the test environment.
REQCONFIRMSHIPPINGSame as production environment. This is enforced when
the buyer is redirected to the test environment Review Your Pa yPal Information page
NOSHIPPINGSame as production environment. This is enforced when
the buyer is redirected to the test environment Review Your Pa yPal Information page
.
.
Express Checkout and Direct Payment Simulator GuideAugust 200619
Testing Express Checkout
3
Express Checkout Parameters
TABLE 3.5Set Express Checkout Parameters in the Test Environment (Continued)
ParameterTest Environment Behavior
ADDROVERRIDE Same as production environment. This is enforced when
LOCALECODE Ignored.
PAGESTYLE If any value is passed in, a default page style with the
EMAIL Same as production environment. Select one of the
the buyer is redirected to the test environment Review
Your Pa yPal Information page
following characteristics is used:
z Header Image – an eBay logo
z Header Border Color – Orange
z Header Background Color – White
z Background Color – Yellow
predefined buyers. (See
.
“Selecting a Predefined Buyer
for T esting” on page 14.) Otherwise the default buyer is
used.
Get Express Checkout Details Parameters
The Get Express Checkout Details call requires that you pass in the TOKEN value returned in
the response to Set Express Checkout. The values returned are based on the parameter values
sent in Set Express Checkout, primarily to select the buyer, and then by the buyer’s selection
of shipping address on the Review Your PayPal Information page.
NOTE: See the Payflow Pro Developer’s Guide for details on Get Express Checkout Details
parameters.
Do Express Checkout Payment Parameters
The Do Express Checkout Payment call requires that you pass in the TOKEN returned in Set
Express Checkout, the payment ACTION, the PAYERID (as set for one of the test buyers) and
the payment details described in
Table 3.6, “Do Express Checkout Payment Response Parameters,” describes the behavior of
the Do Express Checkout Payment parameters returned.
See Table 3.7, “Payment Information.”As defined in the default test payment information.
Table 3.7, “Payment Information.”
20August 2006Express Checkout and Direct Payment Simulator Guide
Testing Express Checkout
Void, Delayed Capture, and Cred it Transaction Parameters
Test Payment Information
The following payment information is defined in the test environment.
3
TABLEPayment Information
3.7
AttributeTest Environment Behavior
PPREF Unique ID is generated
PAYMENTTYPE None
FEEAMT 0.5, where currency is USD
PAYMENTSTATUS Completed
TAXAMT 0.5, where currency is USD
PENDINGREASON Verify
Void, Delayed Capture, and Credit Transaction Parameters
For information on Void, Delayed Capture, and Credit Transaction parameters, see Chapter 4,
“Testing Void, Delayed Capture, and Credit Transactions.”
Express Checkout and Direct Payment Simulator GuideAugust 200621
Testing Express Checkout
3
Void, Delayed Capture, and Credit Transaction Parameters
22August 2006Express Checkout and Direct Payment Simulator Guide
4
Overview
The test environment allows you to test Void, Delayed Capture, and Credit transactions for
Express Checkout and Direct Payment.
These transactions require that you pass in the PNREF returned in the Do Express Checkout
Payment response or transaction reponse from Direct Payment.
In this Chapter
z “Void Parameters” on page 23
z “Delayed Capture Parameters” on page 23
z “Credit Parameters” on page 24
Testing Void, Delayed Capture,
and Credit Transactions