PayPal Inc. is providing the information in this document to you “AS-IS” with all faults. PayPal Inc. makes no warranties of any kind (whether express,
implied or statutory) with respect to the information contained herein. PayPal Inc. assumes no liability 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 f rom 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.
This document, which describes the PayPal virtual test environment called the Sandbox,
replaces the PayPal Sandbox User Guide issued December, 2005.
Intended Audience
This document is written for merchants and developers who want to test their PayPal-based
applications before using them in production.
Organization of This Document
Chapter 1, “Overview to the PayPal Sandbox,” describes the Sandbox in general and lists the
differences between the Sandbox and the production PayPal services.
Chapter 2, “Accessing the PayPal Sandbox and Email,” describes how to gain access to the
Sandbox and your Sandbox email.
Chapter 3, “Setting up Test Users,” describes the different kinds of business roles and
corresponding test accounts you need to set up on the Sa ndbox for effective testing of your
PayPal-based applications.
Chapter 4, “Testing PayPal Website Features,” describes how you can use the Sandbox
(
https://www.sandbox.paypal.com) to test features that correspond to the features on the main
PayPal interactive site
Chapter 5, “Testing PayPal Web Services API Applications,” is an overview of testing PayPal
Web Services API applications with the Sandbox, API digital certificates, and other related
information.
https://www.paypal.com/.
Notational Conventions
This document uses typefaces to identify the characteristics of text. These typefaces and the
characteristics they imply are described below:
June 20069
Preface
Revision History
TypefaceHow Used
serif italicsA document title.
monospaced Pathnames or file names that appear in body text frames.
A term being discussed or defined.
For example: A file is a readable or writable stream of characters …
Boolean values (not keywords).
For example: The function returns true if it encounters an error.
Code-related names that appear in body text frames. Such names are used for
functions, callbacks, arguments, data structures, and fields.
For example: AbstractResponseType is the SOAP response type definition on
which all PayPal API response methods are based.
Components of Internet protocol requests and responses, such as HTTPS and FORM
variables.
For example: The PayPal system uses a method=POST request to return IPN status
variables related to subscriptions, such as txn_type.
Serif boldUser interface names, such as window names or menu selections.
San-serif
oblique
To convey additional information, this document may also apply color and underlining to
words or phrases that use the typefaces described above. Such use is described below:
Text attributeHow Used
xxxxxxHypertext link to a page in the current document or to another document in the set.
xxxxxx
Revision History
For example: On the Profile page, click Email to confirm your email address.
Placeholders used in the context of a format or programming standard or formal
descriptions of PayPal system syntax. Placeholders indicate values or names that
the reader should provide.
Example: For example, amount is the variable for a single-item shopping cart, but
amount_
is the item amount for the third item in a multiple-item shopping cart.
Hypertext link to a URL or that initiates a web action, such as sending mail.
X is the name of the variable for a multi-item shopping cart. amount_3
Revision history for PayPal Sandbox User Guide.
10June 2006
Preface
Revision History
TABLE P.1 Revision History
DateDescription
June 2006Correction of Sort Code necessary to test UK accounts in Sandbox. Proper Sort
Code is 609204.
December 2005Miscellaneous corrections.
June 200611
Preface
Revision History
12June 2006
Loading...
+ 28 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.