# US 2017/0372415 A1 · Method, terminal, server and system for information registration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0372415 A1
- Document ID: US20170372415A1
- Status: Published application
- Kind: A1
- Application number: 15/678,493
- Filed: 2017-08-16
- Published: 2017-12-28
- Earliest claimed: 2013-12-26
- Assignees: Tencent Technology (Shenzhen) Company Limited
- Applicants: Tencent Technology (Shenzhen) Company Limited
- Inventors: Chang HE
- Web page: https://patentgrep.com/patent/US20170372415A1

## CPC

- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- G06Q 20/4014: {Identity check for transactions}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

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.

## Claims

### Claim 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.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

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.

### Claim 4 (depends on 3)

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.

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 1)

The method of claim 1, wherein:
the registration code comprises a user name and a password.

### Claim 7 (depends on 1)

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.

### Claim 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.

### Claim 9 (depends on 8)

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.

### Claim 10 (depends on 8)

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.

### Claim 11 (depends on 10)

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.

### Claim 12 (depends on 8)

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.

### Claim 13 (depends on 8)

The registration server of claim 8, wherein:
the registration code comprises a user name and a password.

### Claim 14 (depends on 8)

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.

### Claim 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.

### Claim 16 (depends on 15)

The non-transitory computer readable storage medium of claim 15, wherein:
the user identity information comprises a name and an identifying number of the user associated with the client terminal.

### Claim 17 (depends on 15)

The non-transitory computer readable storage medium of claim 15, 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.

### Claim 18 (depends on 17)

The non-transitory computer readable storage medium of claim 17, 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.

### Claim 19 (depends on 15)

The non-transitory computer readable storage medium of claim 15, 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.

### Claim 20 (depends on 15)

The non-transitory computer readable storage medium of claim 15, 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.
