System for reducing transaction failure
US-12175472-B2 · Dec 24, 2024 · US
US10861091B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10861091-B2 |
| Application number | US-201715678493-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 16, 2017 |
| Priority date | Dec 26, 2013 |
| Publication date | Dec 8, 2020 |
| Grant date | Dec 8, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A registration sever receives registration data from a client terminal, wherein the registration data includes user identity information and payment account information, and is generated by the client terminal through scanning one or more tangible information carriers provided by a user and extracting the user identity information and payment account information from one or more images obtained through the scanning. The registration server identifies a bank server based on the payment account information, verifies whether the user identity information is associated with a payment account identified by the payment account information; generates a registration code for the user upon successful verification, sends the registration code to the client terminal; and sends the registration code and a terminal identifier to the bank server, wherein the bank server establishes corresponding relationships between the registration code, the terminal identifier, and the payment account for verifying subsequent payment requests by the client terminal.
Opening claim text (preview).
What is claimed is: 1. A payment account registration method, comprising: at a registration server having one or more processors and memory storing programs executed by the one or more processors, receiving registration data from a client terminal, wherein: the registration data includes user identity information and payment account information, and the registration data is generated by the client terminal through scanning one or more tangible information carriers provided by a user of the client terminal and extracting the user identity information and payment account information from one or more images obtained through the scanning; identifying a bank server based on the payment account information; verifying whether the user identity information is associated with a payment account identified by the payment account information; generating a registration code for the user in accordance with a determination that the verification is successful; sending the registration code to the client terminal; and sending the registration code and a terminal identifier to the bank server, wherein the terminal identifier identifies the client terminal, and wherein the bank server establishes corresponding relationships between the registration code, the terminal identifier, and the payment account for verifying subsequent payment requests by the client terminal. 2. The method of claim 1 , wherein: the user identity information comprises a name and an identifying number of the user associated with the client terminal. 3. The method of claim 1 , wherein: the client terminal displays a confirmation message comprising the user identity information and the payment account information extracted from the one or more images, and requests the user to confirm or modify the extracted user identity information and payment account information, before generating the registration data. 4. The method of claim 3 , wherein: the client terminal receives updated user identity information and payment account information from the user after displaying the confirmation message to the user, and the client terminal generates the registration data using the updated user identity information and payment account information. 5. The method of claim 1 , wherein: an association between the user identity information and the payment account is verified by acquiring saved information from the bank server and comparing the saved information to the user identity information. 6. The method of claim 1 , wherein: the registration code comprises a user name and a password. 7. The method of claim 1 , further comprising: receiving a payment request from the client terminal, wherein the payment request includes a payment amount, the terminal identifier, and the registration code; verifying the payment request; and sending the payment request to the bank server, wherein the bank server processes a payment from the payment account based on the payment request. 8. A registration server, comprising: one of more processors; memory; and one or more programs modules stored in the memory and configured for execution by the one or more processors, the one or more program modules including instructions for: receiving registration data from a client terminal, wherein: the registration data includes user identity information and payment account information, and the registration data is generated by the client terminal through scanning one or more tangible information carriers provided by a user of the client terminal and extracting the user identity information and payment account information from one or more images obtained through the scanning; identifying a bank server based on the payment account information; verifying whether the user identity information is associated with a payment account identified by the payment account information; generating a registration code for the user in accordance with a determination that the verification is successful; sending the registration code to the client terminal; and sending the registration code and a terminal identifier to the bank server, wherein the terminal identifier identifies the client terminal, and wherein the bank server establishes corresponding relationships between the registration code, the terminal identifier, and the payment account for verifying subsequent payment requests by the client terminal. 9. The registration server of claim 8 , wherein: the user identity information comprises a name and an identifying number of the user associated with the client terminal. 10. The registration server of claim 8 , wherein: the client terminal displays a confirmation message comprising the user identity information and the payment account information extracted from the one or more images, and requests the user to confirm or modify the extracted user identity information and payment account information, before generating the registration data. 11. The registration server of claim 10 , wherein: the client terminal receives updated user identity information and payment account information from the user after displaying the confirmation message to the user, and the client terminal generates the registration data using the updated user identity information and payment account information. 12. The registration server of claim 8 , wherein: an association between the user identity information and the payment account is verified by acquiring saved information from the bank server and comparing the saved information to the user identity information. 13. The registration server of claim 8 , wherein: the registration code comprises a user name and a password. 14. The registration server of claim 8 , wherein the one or more program modules further include instructions for: receiving a payment request from the client terminal, wherein the payment request includes a payment amount, the terminal identifier, and the registration code; verifying the payment request; and sending the payment request to the bank server, wherein the bank server processes a payment from the payment account based on the payment request. 15. A non-transitory computer readable storage medium having stored therein one or more instructions, which, when executed by a registration server, cause the registration server to perform operations comprising: receiving registration data from a client terminal, wherein: the registration data includes user identity information and payment account information, and the registration data is generated by the client terminal through scanning one or more tangible information carriers provided by a user of the client terminal and extracting the user identity information and payment account information from one or more images obtained through the scanning; identifying a bank server based on the payment account information; verifying whether the user identity information is associated with a payment account identified by the payment account information; generating a registration code for the user in accordance with a determination that the verification is successful; sending the registration code to the client terminal; and sending the registration code and a terminal identifier to the bank server, wherein the terminal identifier identifies the client terminal, and wherein the bank server establishes corresponding relationships between the registration code, the terminal identifier, and the payment account for verifying subsequent payment requests by the client terminal. 16. The non-transitory computer readable storage medium of claim 15 , wherein
Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) · CPC title
Identity check for transactions · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.