Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Mobile Applications Worldwide 2. 2 2 Spending ($B) App stores fueling apps sales
2 .2 2 . 2 2 . 2
22 22
22 22
22 22
22 22
Source: Piper Jeffrey
mCOMMERCE TRENDS
2009 Global m-Commerce ($105B)
Digital Content ($24B) Money transfer ($5B)
Source: Informa
Portion of $600+B Ecommerce migrating to mcommerce: brands moving from product brochure to storefronts New Mobile Use cases: LBS Comparison shopping Private and time sensitive sales Mobile Coupons Personalized services
Consumers have less patience on mobile devices. Experience has to be better then the web Entering credit card info on a phone still a hassle Users are not willing to fill forms on a mobile device for billing and shipping information When redirected to a browser to pay within an app, consumers get confused and abandon the process
CONSUMER TRUST
Consumers not comfortable entering financial info into an unknown developer app
14/04/12
14/04/12
Library designed for simple integration No need to code payment UI Flexible Payment Flows (Adaptive Payments)
Making it better for consumers
More convenient than entering credit card No need to redirect to a browser. Consumers dont need to share their financial info
A growing feature set
P2P transactions In-app purchase for physical good and services Payment settled immediately to your PP account Supports Android, iOS, Blackberry OS
Integration overview
13
2. Redirect to PayPal Mobile URL https://www.paypal.com/cgibin/webscr?cmd=_expresscheckout&token=valueFromSetExpressCheckoutResponse 3. If the buyer approves the payment, PayPal redirects to the successURL with Token + The buyers unique identifier (Payer ID) 4. GetExpressCheckout: Obtains information about the buyer from PayPal, including shipping information. DoExpressCheckout: Handles the payment and completes the transaction.
5.
MPL INTEGRATION
Four simple steps: 1. Initialize the library 2. Generate the Pay with PayPal button 3. Add the payment details 4. Wait for callback
Two button types can be used, This will determine the text on the checkout pages
TEXT_PAY TEXT_DONATE
4. Handle a Callback
Three types of call back responses to handle in the optional ResultDelegate class
public void paymentSucceeded() public void paymentCancelled() public void paymentFailed()
Supported Languages
Argentina: es_AR Brazil: pt_BR Australia: en_AU Belgium: en_BE, nl_BE, fr_BE Canada: en_CA, fr_CA France: fr_FR, en_FR Germany: de_DE, en_DE Hong Kong: zh_HK, en_HK India: en_IN Italy: it_IT Japan: ja_JP, en_JP Mexico: es_MX, en_MX Netherlands: nl_NL, en_NL Poland: pl_PL, en_PL Singapore: en_SG Spain: es_ES, en_ES Switzerland: de_CH, en_CH, fr_CH Taiwan: zh_TW, en_TW United States: en_US (default)
21
22
23
My Apps Status
HELPFUL HINTS
1. Visit Apps 101 on www.x.com/developers/paypal 2. Understand the PayPal X Developer Agreement to know what is and is not allowed before you begin coding: https:// www.x.com/developers/paypal/paypal-developer-agreement 3. Be as descriptive as possible when relating; What your application does Your application payment flow Who all the players (senders and receivers) are in the payment flow 1. Contact Developer Technical Services (DTS) if you have any technical MPL questions via www.paypal.com/dts
QUESTIONS?