MOBILE PAYMENT PROCESSING
First Claim
1. A computer-implemented method for processing a payment between a payor device and a payee device comprising:
- enabling, by the payee device, a device authorization function using a third-party server;
receiving, by the payee device, identity authentication information from a payor device, wherein the identity authentication information includes an identifier of the payor device, and wherein the payor device does not have a payment application (APP) installed;
in response to receiving the identity authentication information, forwarding, by the payee device, the received identity authentication information to the third-party server;
receiving, by the payee device, token information from the third-party server, wherein the token information is generated by the third-party server and corresponds to the identifier of the payor device;
receiving, by the payee device, a payment request from the payor device, wherein the payment request includes the identifier of the payor device and the generated token; and
in responsive to receiving the payment request, sending, by the payee device, payment information including the generated token and the to the third-party server for verification.
3 Assignments
0 Petitions
Accused Products
Abstract
The present specification relates to a mobile payment method, device, and system. One example method includes enabling, by the payee device, a device authorization function using a third-party server; receiving, by the payee device, identity authentication information from a payor device, wherein the identity authentication information includes an identifier of the payor device, and wherein the payor device does not have a payment application (APP) installed; forwarding, by the payee device, the received identity authentication information to the third-party server; receiving, by the payee device, token information from the third-party server, wherein the token information corresponds to the identifier; receiving, by the payee device, a payment request from the payor device, wherein the payment request includes the identifier of the payor device and the generated token; and sending, by the payee device, payment information including the generated token and the to the third-party server for verification.
4 Citations
20 Claims
-
1. A computer-implemented method for processing a payment between a payor device and a payee device comprising:
-
enabling, by the payee device, a device authorization function using a third-party server; receiving, by the payee device, identity authentication information from a payor device, wherein the identity authentication information includes an identifier of the payor device, and wherein the payor device does not have a payment application (APP) installed; in response to receiving the identity authentication information, forwarding, by the payee device, the received identity authentication information to the third-party server; receiving, by the payee device, token information from the third-party server, wherein the token information is generated by the third-party server and corresponds to the identifier of the payor device; receiving, by the payee device, a payment request from the payor device, wherein the payment request includes the identifier of the payor device and the generated token; and in responsive to receiving the payment request, sending, by the payee device, payment information including the generated token and the to the third-party server for verification. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A non-transitory computer-readable storage medium coupled to one or more computers and configured with instructions executable by the one or more computers to:
-
enable, by the payee device, a device authorization function using a third-party server; receive, by the payee device, identity authentication information from a payor device, wherein the identity authentication information includes an identifier of the payor device, and wherein the payor device does not have a payment application (APP) installed; in response to receiving the identity authentication information, forward, by the payee device, the received identity authentication information to the third-party server; receive, by the payee device, token information from the third-party server, wherein the token information is generated by the third-party server and corresponds to the identifier of the payor device; receive, by the payee device, a payment request from the payor device, wherein the payment request includes the identifier of the payor device and the generated token; and in responsive to receiving the payment request, send, by the payee device, payment information including the generated token and the to the third-party server for verification. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A system, comprising:
-
one or more computers; and one or more computer-readable memories coupled to the one or more computers and configured with instructions executable by the one or more computers to; enable, by the payee device, a device authorization function using a third-party server; receive, by the payee device, identity authentication information from a payor device, wherein the identity authentication information includes an identifier of the payor device, and wherein the payor device does not have a payment application (APP) installed; in response to receiving the identity authentication information, forward, by the payee device, the received identity authentication information to the third-party server; receive, by the payee device, token information from the third-party server, wherein the token information is generated by the third-party server and corresponds to the identifier of the payor device; receive, by the payee device, a payment request from the payor device, wherein the payment request includes the identifier of the payor device and the generated token; and in responsive to receiving the payment request, send, by the payee device, payment information including the generated token and the to the third-party server for verification. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification