
Mobile Checkout Developer Guide October 2009 7
1
PayPal Mobile Checkout
Overview
PayPal Mobile Checkout provides merchants with the essential components necessary for
mobile commerce:
z A hosted quick buyer flow
z A straightforward merchant interface
z Transaction completion data
z PayPal merchant support
PayPal defines mobile commerce as any and all transactions completed using a mobile phone.
Buyers use a simple two step process (login and review) to make payments. The merchant
interface can be plugged into any mobile medium that can initiate a mobile browser session,
and uses either the PayPal Web Services SOAP or Name/Value Pair (NVP) API interface.
After a transaction is completed, the necessary buyer and transaction data is delivered to the
merchant via the interface.
The processing flow and APIs for Mobile Checkout are similar to those for Express Checkout.
For more information about Express Checkout, see the Name-Value Pair (NVP) Developer
Guide and Reference and the SOAP API Reference.
Security on the Mobile Web
PayPal Mobile Checkout is designed to support the vast majority of mobile devices sold by
major carriers that can make secure connections. To access mobile checkout, a device, mobile
carrier, and browser must support the following:
z WAP 2.0 phones (not WAP 1.0)
z xHTML or HTML markup language
z SSL connections
z Cookies enabled
z No carrier "WAP gap"
If a device or connection fails any of the these checks, the customer will not be able to connect
to the PayPal servers.
N OTE: Mobile web generally refers to the collection of accepted web standards used on
mobile devices. Most modern mobile devices use mini-browsers, much like a web
browser on a computer. A growing portion of phone subscribers pay for data plans to
access information, services, and commerce on their mobile devices though these
mobile browers. Most mobile browsers use the xHTML markup language, while
others also use cHTML, HTML, and WML. Most devices support cookies with default
Comentários a estes Manuais