Transaction processing method and apparatus

• US 10,438,193 B2
• Filed: 08/26/2013
• Issued: 10/08/2019
• Est. Priority Date: 08/26/2013
• Status: Expired due to Fees

• Current Assignee: Xiaoxiong Zhang
• Original Assignee: Xiaoxiong Zhang
• Inventors: Zhang, Xiaoxiong
• Primary Examiner(s): Ebersman, Bruce I
• Assistant Examiner(s): Gaw, Mark H
• Application Number:
  US13/975,389
• Publication Number:
  US 20150058218A1
• Time in Patent Office: 2,234 Days
• Field of Search: 705 44
• CPC Class Codes: G06Q 20/352 Contactless payments by cards

Abstract

The present disclosure relates to a transaction processing method and apparatus. The method comprises: reading a tag via a user device t obtain a provide identifier associated with a provider for a transaction; generating via the user device a user request containing the provider identifier and a user identifier associated with a user for the transaction; and transmitting the user request to a transaction server, wherein a provider request containing transaction information and the provider identifier has been sent to the transaction server and stored therein.

Claims

1. A method of electronically processing a transaction using a user device remotely communicated with a transaction server, the method comprising:

obtaining a provider identifier associated with a provider for the transaction by reading a tag disposed in a position associated with the provider, wherein the tag stores the provider identifier and enables a short-range wireless communication with the user device through a radio wave field, and wherein the user device comprises a tag reader for reading the provider identifier from the tag and a remote communication module for communicating with the transaction server;

generating via the user device a user request containing the provider identifier, location information of the provider, and a user identifier associated with a user of the user device;

transmitting the user request to the transaction server,

wherein the transaction server is configured to store a request database which comprises multiple provider requests received from a provider device of the provider and receipt times of the multiple provider requests, wherein the multiple provider requests comprise at least a provider request containing the provider identifier, the location information of the provider, and transaction information, and

wherein the transaction server is configured to, when receiving the user request, match the user request with the provider request among the multiple provider requests based on the provider identifier, the location information of the provider and the receipt times of the multiple provider requests;

receiving from the transaction server a server request containing the transaction information after the transaction server matches the user request with the provider request;

generating a user response to the server request by taking a user action via the user device regarding the transaction information; and

transmitting the user response to the transaction server to complete the transaction between the user and the provider, wherein the transaction server

transmits a transaction request containing the transaction information and information related to the provider and the user to an application server for conducting the transaction between the user and the provider, and

receives a transaction response indicating whether or not the transaction is completed from the application server.

2. The method of claim 1, further comprising:

receiving a server response informing the status of the transaction, wherein the server response is generated via the transaction server by matching the user request and the provider request through the provider identifier; and

presenting the server response via the user device.

3. The method of claim 1, wherein the server request contains a plurality of candidate choices for the user to choose from, or prompt information for the user to accept the transaction, cancel the transaction or revise the transaction information.

4. The method of claim 3, wherein the plurality of candidate choices comprise a plurality of candidate financial accounts associated with the user.

5. The method of claim 3, wherein the prompt information comprises a financial account associated with the user.

6. The method of claim 1, wherein the user action comprises acceptance of the transaction, cancellation of the transaction or revision of the transaction information.

7. The method of claim 1, wherein the user response comprises personal identifying information associated with the user.

8. The method of claim 1, wherein the transaction information comprises an amount of payment to be paid from the user to the provider, or an amount of refundment to be transferred from the provider to the user.

9. The method of claim 1, wherein the provider request is dynamically provided by the provider.

10. The method of claim 1, wherein the provider request further comprises the user identifier, and the transaction information contains a payment that has been paid from the user to the provider.

11. The method of claim 10, further comprising:

receiving a server response informing the status of the transaction, wherein the server response is generated via the transaction server by matching the user request and the provider request through the provider identifier and the user identifier; and

presenting the server response via the user device.

12. The method of claim 1, wherein the tag is disposed on a POS machine, an ATM machine, an ID card, a financial card, a table, a package of a commodity, a shelf, a catalog or a menu associated with the provider.

13. A method of electronically processing a transaction using a user device remotely communicated with a transaction server, the method comprising:

receiving from a provider device multiple provider requests comprising at least a provider request containing transaction information, a provider identifier associated with a provider for the transaction, and location information of the provider,

wherein the provider identifier is obtained by reading a tag disposed in a position associated with the provider,

wherein the tag stores the provider identifier and enables a short-range wireless communication with the user device through a radio wave field, and

wherein the user device comprises a tag reader for reading the provider identifier from the tag and a remote communication module for communicating with the transaction server;

storing the multiple provider requests and receipt times of the multiple provider requests in a request database;

receiving a user request from a user device, wherein the user request contains the provider identifier, location information of the provider, and a user identifier associated with a user of the user device; and

searching the request database to match the user request with the provider request based on the provider identifier, the location information of the provider and the receipt times of the multiple provider requests;

generating a server request containing the transaction information after the matching of the user request and the provider request;

transmitting the server request to the user device;

receiving a user response in answer to the server request to complete the transaction between the user and the provider, wherein the user response is generated via the user device by taking a user action by the user regarding the transaction information;

transmitting a transaction request containing the transaction information and information related to the provider and the user to an application server for conducting the transaction between the user and the provider; and

receiving a transaction response indicating whether or not the transaction is completed from the application server.

14. The method of claim 13, further comprising:

generating a server response indicating the status of the transaction; and

transmitting the server response to the user device and/or a provider device associated with the provider.

15. The method of claim 13, wherein the server request further contains a plurality of candidate choices for the user to choose from, or prompt information for the user to accept the transaction, cancel the transaction or revise the transaction information.

16. The method of claim 15, wherein the plurality of candidate choices comprise a plurality of candidate financial accounts associated with the user.

17. The method of claim 15, wherein the prompt information comprises a financial account associated with the user.

18. The method of claim 13, wherein the user action comprises acceptance of the transaction, cancellation of the transaction or revision of the transaction information.

19. The method of claim 13, wherein the user response comprises personal identifying information associated with the user.

20. The method of claim 13, wherein the transaction information comprises an amount of payment to be paid from the user to the provider, or an amount of refundment to be refunded from the provider to the user.

21. The method of claim 13, wherein the provider request is dynamically provided by the provider.

22. The method of claim 13, wherein the provider request further comprises the user identifier, and the transaction information contains a payment that has been paid from the user to the provider.

23. The method of claim 22, wherein the step of matching the user request with the provider request further comprises matching the user request with the provider request through the provider identifier and the user identifier.

24. The method of claim 13, wherein the tag is disposed on a POS machine, an ATM machine, an ID card, a table, a financial card, a table, a package of commodity, a shelf, a catalog or a menu associated with the provider.

25. A computer readable storage medium for storing a program of instructions executable by a computer to perform a process, the process comprising:

obtaining a provider identifier associated with a provider for the transaction by reading a tag disposed in a position associated with the provider, wherein the tag stores the provider identifier and enables a short-range wireless communication with the user device through a radio wave field, and wherein the user device comprises a tag reader for reading the provider identifier from the tag and a remote communication module for communicating with the transaction server;

generating via the user device a user request containing the provider identifier, location information of the provider, and a user identifier associated with a user of the user device;

transmitting the user request to the transaction server,

wherein the transaction server is configured to store a request database which comprises multiple provider requests received from a provider device of the provider and receipt times of the multiple provider requests, wherein the multiple provider requests comprise at least a provider request containing the provider identifier, the location information of the provider, and transaction information, and

wherein the transaction server is configured to, when receiving the user request, match the user request with the provider request among the multiple provider requests based on the provider identifier, the location information of the provider and the receipt times of the multiple provider requests;

receiving from the transaction server a server request containing the transaction information after the transaction server matches the user request with the provider request;

generating a user response to the server request by taking a user action via the user device regarding the transaction information; and

transmitting the user response to the transaction server to complete the transaction between the user and the provider, wherein the transaction server

transmits a transaction request containing the transaction information and information related to the provider and the user to an application server for conducting the transaction between the user and the provider, and

receives a transaction response indicating whether or not the transaction is completed from the application server.

26. A computer readable storage medium for storing a program of instructions executable by a computer to perform a process, the process comprising:

receiving from a provider device multiple provider requests comprising at least a provider request containing transaction information, a provider identifier associated with a provider for the transaction, and location information of the provider,

wherein the provider identifier is obtained by reading a tag disposed in a position associated with the provider,

wherein the tag stores the provider identifier and enables a short-range wireless communication with the user device through a radio wave field, and

wherein the user device comprises a tag reader for reading the provider identifier from the tag and a remote communication module for communicating with the transaction server;

storing the multiple provider requests and receipt times of the multiple provider requests in a request database;

receiving a user request from a user device, wherein the user request contains the provider identifier, location information of the provider, and a user identifier associated with a user of the user device; and

searching the request database to match the user request with the provider request based on the provider identifier, the location information of the provider and the receipt times of the multiple provider requests;

generating a server request containing the transaction information after the matching of the user request and the provider request;

transmitting the server request to the user device;

receiving a user response in answer to the server request to complete the transaction between the user and the provider, wherein the user response is generated via the user device by taking a user action by the user regarding the transaction information;

transmitting a transaction request containing the transaction information and information related to the provider and the user to an application server for conducting the transaction between the user and the provider; and

receiving a transaction response indicating whether or not the transaction is completed from the application server.