Ebay, Incorporated

Paypal, Inc.

Ray Hideki Tanaka

Alan Tien

Zahid N Ahmed

Hugo Olliphant

Bhaven Avalani

Alon Cohen

Daniel Tsun Kao

Gary Yue

Roy Vella

Saumil Ashvin Gandhi

Srikanth Nandiraju

Mehryar Mansoor

Steve S Chen

Osama Bedier

Peter Zhe Chu

Nida Zada

Aaron M Lee

J Paul Janney

Henry H Pham

A payment button on a device capable of making telephone calls, such as a mobile phone, allows a payer to electronically transfer money while in a phone call with a payee. The payment button also allows a payee to initiate an electronic payment transaction while in a phone call with a payer. The payment button may be a clickable or tappable virtual button presented on a display of the phone when being used to make or receive a call. The payer or the payee can simply enter a payment amount on the phone to complete an electronic payment transaction. A notification of payment is instantly transmitted to the phones being used for the phone call, so that the parties can safely and conveniently conclude a purchase and/or payment transaction during one phone call.

System and method for facilitating electronic financial transactions during a communication session

Methods and systems for automatically providing dynamic content for facilitating a transaction are described herein. An online marketplace is accessed by a client device over a network. A user identifier associated with the client device is passed to a payment service provider via a merchant system associated with the online market place. Dynamic content is generated by the payment service provider in response to the user identifier and subsequently served to the client device over the network.

Systems and methods for providing user-specific dynamic content for facilitating online transactions

System and method for facilitating electronic financial transactions during a phone call

In one example, a server system facilitates an exchange of messages with a remote client application. An Application Program Interface (API) receives a first request message and a second request message, wherein the first request message includes a first data payload defined by a common definition and including a first payload data, the first payload defined by a first schema definition. The second request message includes a second data payload defined by the common definition and a second payload data, wherein the second payload is defined by a second schema definition different than the first schema definition. In response to receiving the first request message, the API transmits a first response message, and in response to receiving the second request message, the API transmits a second response.

API and business language schema design framework for message exchanges

A user's location is determined by location information communicated by a user device, such as a smart phone. Merchants near the user location are determined and selected. Merchant payment information is transmitted to the user device so that the user can easily make a payment to the merchant through the user device. Merchant offerings may also be sent to the user device for purchase and subsequent payment, where the merchant offerings may be specifically selected for the user.

Location based transactions

Methods and systems for providing dynamic content during payment transactions are described herein. A user identifier stored on a client device of a user is transmitted to a payment service provider in response to the user's interaction with a user interface associated with a merchant. Based on the user identifier, dynamic content specific to the user is retrieved from the payment service provider. The dynamic content may include an available account balance with the payment service provider, merchant rating associated with the merchant, and other information that may assist the user in determining whether to engage in an online transaction with the merchant. The dynamic content may then be provided to the client device.

In one example, a server system in an electronic trading system facilitates an exchange of messages with a remote client application. An Application Program Interface (API) receives a first request message and a second request message, wherein the first request message including a first data payload defined by a common data component and including a first extended payload data, the first extended payload defined by a first schema definition. The second request message includes a second data payload defined by the common data component and a second extended payload data, wherein the second extended payload is defined by a second schema definition different than the first schema definition. In response to receiving the first request message, the API transmits a first response message, and in response to receiving the second request message, the API transmits a second response message different than the first response message.

Systems, methods and media are provided for facilitating an exchange of messages between a remote client application and a server system the server system, the server system being capable of supporting a plurality of application program interfaces (APIs) that includes a targeted API. In one example, a method includes receiving a plurality of request messages generated by the remote client application, each request message requesting an activity to be performed by the targeted API, with respect to an associated application, and comprising at least one data component common to each of the plurality of request messages and selected from a group comprising a predetermined required level of detail, an error language component and a version identifier, and a request component including a reusable identified schema definition.

Growing community of inventors

Sunnyvale, CA, United States of America

Ray Hideki Tanaka