Integration Guide

Website Payments Standard Checkout Integration Guide November 2005 13
Preface
This Document
This document, the PayPal Website Payments Standard Checkout Integration Guide, is a
complete revision of the version issued in September 2005.
Intended Audience
This document is for merchants whose websites obtain payments using PayPal features.
Notational Conventions
This document uses typefaces to identify the characteristics of text. These typefaces and the
characteristics they imply are described below:
Typeface How Used
serif italics A document title.
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.
monospaced Pathnames or file names that appear in body text frames.
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 bold User interface names such as window names or menu selections.
For example: On the Profile page, click Email to confirm your email address.
San-serif
oblique
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_
X is the name of the variable for a multi-item shopping cart. amount_3
is the item amount for the third item in a multiple-item shopping cart.