Disclosure of Invention
In view of this, the embodiment of the invention provides an account registration method and device, which can provide a perfect implementation scheme for registering accounts in batches, improve the accuracy and efficiency of account registration, and reduce the security risk.
In order to achieve the above object, according to an aspect of an embodiment of the present invention, there is provided an account registration method.
An account registration method, comprising: verifying each sub-account registration data sent by a service party, feeding back a verification result of the sub-account registration data to the service party, and storing the sub-account registration data passing verification into a database; acquiring a batch note and booklet account list submitted by the business side through a main account, wherein the batch registration sub-account list comprises sub-account data to be registered, and the sub-account registration data comprises information to be verified before registration of the sub-account data; and carrying out batch registration on the sub-account data to be registered in the batch registration sub-account list according to the sub-account registration data which is saved in the database and passes the verification.
After signing a contract with a platform party, the platform party generates a main account corresponding to the service party, meanwhile, the platform party opens the authority of a service manager for the service party, the authority of the service manager corresponds to the main account of the service party, the authority of the manager comprises preset sub-account authority, one main account can correspond to a plurality of sub-accounts, for example, a plurality of staff of the service party can register the sub-account corresponding to the main account, and the staff of the service party can obtain the preset sub-account authority through the respective sub-accounts.
Optionally, before verifying the registration data of each sub-account sent by the service party, the method includes: and receiving the sub-account registration data sent by each terminal device of the service party in a short message mode, wherein each sub-account registration data comprises a communication number of the terminal device.
Optionally, the feeding back the verification result of the sub-account registration data to the service party includes: and respectively sending a short message which is sent by the terminal equipment and indicates that the verification of the sub-account registration data is passed or a short message which indicates that the verification is not passed and the sub-account registration data needs to be retransmitted to each terminal equipment.
Optionally, the sub-account registration data further includes a unique identifier of the service party; the verifying the registration data of each sub-account sent by the service party comprises the following steps: scanning a short message list formed by the received sub-account registration data through a timing task, and performing word segmentation on the sub-account registration data in the short message list to obtain a unique identifier of the service party and the communication number in the sub-account registration data; and respectively verifying the unique identification of the service party and the communication number in each sub-account registration data.
Optionally, the batch registration of the sub-account data to be registered in the batch registration sub-account list includes: and determining that the communication number in the sub-account data to be registered is the communication number in the sub-account registration data passing verification according to the sub-account registration data passing verification stored in the database, performing field verification on the sub-account data to be registered, and performing batch registration on the sub-account data to be registered, wherein the field verification is passed.
Optionally, the sub-account data to be registered includes a sub-account name and a communication number; the performing field verification on the sub-account data to be registered includes: and carrying out field verification on the sub-account data to be registered according to a registration rule, wherein the registration rule comprises one or more of a naming rule of a sub-account name, whether the sub-account name is repeated or not and whether a communication number is repeated or not.
Optionally, the batch registration of the sub account data to be registered, where the verification of the field is passed, includes: and sending the sub-account data to be registered, which pass the field verification, to a sub-account registration interface, respectively registering each sub-account data to be registered, which passes the field verification, through the sub-account registration interface, and adding a mark indicating successful registration to the corresponding communication number stored in the database after successful registration, wherein the mark is used for verifying whether the communication number is repeated.
According to another aspect of the embodiment of the invention, an account registration device is provided.
An account registration apparatus comprising: the verification module is used for verifying each sub-account registration data sent by the service party, feeding back a verification result of the sub-account registration data to the service party, and storing the sub-account registration data passing verification into a database; the batch booklet account list acquisition module is used for acquiring a batch booklet account list submitted by the business party through the main account, wherein the batch registration sub-account list comprises sub-account data to be registered, and the sub-account registration data comprises information to be verified before registration of the sub-account data; and the account registration module is used for registering the sub-account data to be registered in the batch registration sub-account list in batches according to the sub-account registration data which is saved in the database and passes the verification.
Optionally, the device further comprises a receiving module for: and receiving the sub-account registration data sent by each terminal device of the service party in a short message mode, wherein each sub-account registration data comprises a communication number of the terminal device.
Optionally, the verification module is further configured to: and respectively sending a short message which is sent by the terminal equipment and indicates that the verification of the sub-account registration data is passed or a short message which indicates that the verification is not passed and the sub-account registration data needs to be retransmitted to each terminal equipment.
Optionally, the sub-account registration data further includes a unique identifier of the service party; the verification module is further configured to: scanning a short message list formed by the received sub-account registration data through a timing task, and performing word segmentation on the sub-account registration data in the short message list to obtain a unique identifier of the service party and the communication number in the sub-account registration data; and respectively verifying the unique identification of the service party and the communication number in each sub-account registration data.
Optionally, the account registration module is further configured to: and determining that the communication number in the sub-account data to be registered is the communication number in the sub-account registration data passing verification according to the sub-account registration data passing verification stored in the database, performing field verification on the sub-account data to be registered, and performing batch registration on the sub-account data to be registered, wherein the field verification is passed.
Optionally, the sub-account data to be registered includes a sub-account name and a communication number; the account registration module is further configured to: and carrying out field verification on the sub-account data to be registered according to a registration rule, wherein the registration rule comprises one or more of a naming rule of a sub-account name, whether the sub-account name is repeated or not and whether a communication number is repeated or not.
Optionally, the account registration module is further configured to: and sending the sub-account data to be registered, which pass the field verification, to a sub-account registration interface, respectively registering each sub-account data to be registered, which passes the field verification, through the sub-account registration interface, and adding a mark indicating successful registration to the corresponding communication number stored in the database after successful registration, wherein the mark is used for verifying whether the communication number is repeated.
According to yet another aspect of an embodiment of the present invention, an electronic device is provided.
An electronic device, comprising: one or more processors; and the memory is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are caused to realize the account registration method provided by the embodiment of the invention.
According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.
A computer readable medium having stored thereon a computer program which, when executed by a processor, implements the account registration method provided by the embodiment of the present invention.
One embodiment of the above invention has the following advantages or benefits: verifying each sub-account registration data sent by the service party, feeding back a verification result of the sub-account registration data to the service party, and storing the sub-account registration data passing verification into a database; acquiring a batch note and booklet account list submitted by a business party through a main account, wherein the batch registration sub-account list comprises sub-account data to be registered, and the sub-account registration data comprises information to be verified before registration of the sub-account data; and registering the sub-account data to be registered in the batch registration sub-account list in batches according to the sub-account registration data which is saved in the database and passes the verification. The realization scheme of perfect batch account registration can be provided, the accuracy and efficiency of account registration are improved, and the security risk is reduced.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
DetailedâDescription
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of main steps of an account registration method according to an embodiment of the present invention.
As shown in fig. 1, the account registration method according to an embodiment of the present invention mainly includes the following steps S101 to S103.
Step S101: and verifying the sub-account registration data sent by the service party, feeding back a verification result of the sub-account registration data to the service party, and storing the sub-account registration data passing verification into a database.
The information that needs to be verified before the sub-account data is registered can specifically include a communication number of the terminal device and a unique identifier of the service party. That is, each sub-account registration data may include a communication number of the terminal device, a unique identifier of the service party, and further may include a set keyword.
The service party is the party applying for the booklet account, and the sub-account registration data sent by the service party can be the sub-account registration data sent by the terminal equipment of the service party through the short message.
The sub-account number of the service party is relative to the main account number of the service party, and a plurality of sub-account numbers can be arranged under one main account number.
Before the business side applies for the booklet account, the platform side needs to apply for the main account in advance. The platform side is the side executing the account registration method of the embodiment of the invention.
In one embodiment, after a business party, such as a merchant, signs a contract with a platform party, the platform party generates a primary account number corresponding to the merchant and a unique identifier of the business party bound to the primary account number, and meanwhile, the platform party opens a permission of a business manager for the merchant to open a sub-account number and assign a right to the sub-account number to the merchant, where the unique identifier of the business party may be a Customer code (Customer No., abbreviated as C code), and the business manager corresponds to the primary account number of the business party. The authority of the administrator may include preset sub-account authority, one main account may correspond to a plurality of sub-accounts, for example, a plurality of employees of the merchant may register sub-accounts corresponding to the main account, and the employees may obtain the preset sub-account authority through respective sub-accounts.
Before verifying the registration data of each sub-account sent by the service party, the method may include: sub-account registration data sent by each terminal device of a service party in a short message form are received, and each sub-account registration data comprises a communication number of the terminal device. Terminal equipment such as a mobile phone, and a communication number of the terminal equipment such as a mobile phone number. The content of the short message can be: c code (i.e. unique identification of service party) +registered sub-account number (i.e. keyword) +employee's own mobile phone number (i.e. communication number of terminal equipment).
The feedback of the verification result of the sub-account registration data to the service party may include: and respectively sending a short message which is sent by the terminal equipment and indicates that the sub-account registration data passes verification, or sending a short message which indicates that the sub-account registration data fails verification and the sub-account registration data needs to be retransmitted to each terminal equipment.
The sub-account registration data may also include a unique identification of the business party.
Verifying the registration data of each sub-account sent by the service party may include: scanning a short message list formed by the received sub-account registration data through a timing task, and performing word segmentation on the sub-account registration data in the short message list to obtain a unique identifier and a communication number of a service party in the sub-account registration data; and respectively verifying the unique identification and the communication number of the service party in the registration data of each sub-account.
The sub-account data to be registered may include a sub-account name, a communication number, an account password of the sub-account, a contact phone number (i.e., a communication number) of the sub-account, a contact name of the sub-account, a contact mailbox of the sub-account, remark information, and the like.
Step S102: the method comprises the steps of obtaining a batch note and booklet account list submitted by a business party through a main account, wherein a batch registration sub-account list comprises sub-account data to be registered, and the sub-account registration data comprises information to be verified before registration of the sub-account data.
Step S103: and registering the sub-account data to be registered in the batch registration sub-account list in batches according to the sub-account registration data which is saved in the database and passes the verification.
Batch registration of the sub-account data to be registered in the batch registration sub-account list may include: according to the sub-account registration data which is saved in the database and passes verification, determining that the communication number in the sub-account data to be registered is the communication number in the sub-account registration data which passes verification, performing field verification on the sub-account data to be registered, and performing batch registration on the sub-account data to be registered, wherein the sub-account data to be registered passes field verification.
The performing field verification on the sub-account data to be registered may include: and carrying out field verification on the sub-account data to be registered according to a registration rule, wherein the registration rule comprises one or more of a naming rule of a sub-account name, whether the sub-account name is repeated or not and whether the communication number is repeated or not.
Batch registration of sub-account data to be registered, which passes field verification, can include: and transmitting the sub-account data to be registered, which is checked by the field, to a sub-account registration interface, respectively registering the sub-account data to be registered, which is checked by the field, through the sub-account registration interface, and adding a mark indicating successful registration to the corresponding communication number stored in the database after successful registration, wherein the mark is used for checking whether the communication number is repeated.
Fig. 2 is a flow chart of a method of account registration according to an embodiment of the present invention.
As shown in fig. 2, in one embodiment, after a merchant (i.e., a service party) signs up with a platform party, the platform party generates a main account number corresponding to the merchant and a unique identifier of the service party bound to the main account number, and at the same time, the platform party opens a right of a service manager for the merchant to open a sub-account number and assign a right to the sub-account number to the merchant, where the unique identifier of the service party may be a C-code (Customer No).
In one embodiment, the service party sends the sub-account registration data to the platform party in the form of a short message through each terminal device, and each sub-account registration data includes a communication number of one terminal device and a unique identifier of the service party. Specifically, the communication number of the terminal device may be a mobile phone number, all employees needing to register sub-accounts of the merchant need to write the short message content (i.e. sub-account registration data) in the format of "C code+register sub-account+employee own mobile phone number", and send the short message to the short message verification platform registering sub-accounts of the platform side, for example, the merchant C code is C01010101, and the mobile phone number of the employee registering the sub-account is 18801010101, where the short message content required to be written by the employee may be: c01010101 registers child account number 18801010101. The registration sub-account is a preset keyword, and is used for identifying that the short message content is sub-account registration data.
In one embodiment, the platform side scans a short message list formed by the received sub-account registration data through a timing task, and performs word segmentation on the sub-account registration data in the short message list to obtain a unique identifier and a communication number of a service side in the sub-account registration data, and respectively verifies the unique identifier and the communication number of the service side in each sub-account registration data; and storing the sub-account registration data which passes verification into a database, and feeding back a verification result of the sub-account registration data to the service party. Specifically, the server of the platform side starts a timing task to scan a short message list formed by the registration data of each sub-account, for each short message in the short message list, performs formatting operations such as space removal and sign removal on the short message content, then automatically cuts words, obtains the C code (namely the unique identifier of the service side) and the mobile phone number (namely the communication number) in the registration data of the sub-account, respectively verifies the validity of the C code and the mobile phone number, including verifying whether the C code exists, whether the mobile phone number accords with the format (for example, whether the mobile phone number is 11 bits or not, whether the mobile phone number is all digital or not, and the like, stores the C code, the mobile phone number which pass verification and the corresponding relation between the C code and the mobile phone number into a database, simultaneously, the short message verification platform of the registration sub-account of the platform side feeds back the verification result to the service side in the form of short message, and the short message content which passes verification of the C code and the mobile phone number is verified by-! The failed short message content verification may include a failed verification reason, such as "C code error," and is sent again after correction. "," error in handset number, please correct and then send again. ", to facilitate the staff of the merchant to modify the sub-account registration data for re-verification.
In one embodiment, the business side generates a batch booklet account table (i.e., a batch registration sub-account table) according to the verified sub-account registration data, wherein the batch booklet account table includes sub-account data to be registered. Specifically, after all mobile phone numbers of the sub-accounts to be registered receive short messages passing verification, the merchant downloads a batch booklet account form template through a merchant workstation of a main account login platform side, the merchant fills the sub-account data to be registered into the batch registration sub-account form template according to a format, obtains batch registration sub-account forms, and uploads the batch booklet account forms to the merchant workstation. The batch note booklet account table is shown in table 1, and the sub-account data may include an account name, an account password, a contact phone number (i.e., a communication number) of the sub-account.
Table 1 batch booklet account table example
In one embodiment, according to the sub-account registration data which is saved in the database and passes the verification, determining that the communication number in the sub-account data to be registered is the communication number in the sub-account registration data which passes the verification, performing field verification on the sub-account data to be registered, and performing batch registration on the sub-account data to be registered, wherein the field verification is passed. Specifically, after receiving a batch registration sub-account number table submitted by a business side through a login main account number, the platform side analyzes the batch booklet account number table by using an Excel tool, and takes each row of the table as one piece of data to obtain sub-account number data to be registered. Checking whether the communication number in the sub-account data to be registered is the communication number in the sub-account registration data passing verification and whether the corresponding relation between the mobile phone number and the C code of the merchant corresponding to the current main account exists in a database, if the communication number in the sub-account data to be registered is the communication number in the sub-account registration data passing verification and the corresponding relation between the mobile phone number and the C code of the merchant corresponding to the current main account exists in the database, continuing to perform field verification on the sub-account data to be registered, otherwise, checking the sub-account data to be registered is not passed, and the sub-account registration fails. When the field verification is performed on the sub-account data to be registered, the field verification may be performed on the sub-account data to be registered according to a registration rule, where the registration rule may include a naming rule of a sub-account name, whether the sub-account name is repeated, whether a communication number is repeated, and the like, if the field verification is passed, the verification on the sub-account data to be registered is passed, otherwise, the verification on the sub-account data to be registered is not passed, and the sub-account registration fails. After all the sub-account data to be registered are checked, the checked sub-account data to be registered is used as an entry to be sent to a batch registration sub-account interface, after the batch registration sub-account interface is returned, a batch registration result is sent to a merchant, and meanwhile, for the sub-account data which is successfully registered, a mark indicating that the registration is successful is added to the corresponding communication number stored in the database, and the mark is used for checking whether the communication number is repeated. The batch registration result is shown in table 2, and the merchant can upload the form booklet account again after modifying the corresponding data according to the registration failure reason.
Table 2 example batch registration results
Fig. 3 is a schematic diagram of main modules of an account registration apparatus according to an embodiment of the present invention.
As shown in fig. 3, an account registration apparatus 300 according to an embodiment of the present invention mainly includes: the system comprises a verification module 301, a batch note booklet account list acquisition module 302 and an account registration module 303.
The verification module 301 is configured to verify each sub-account registration data sent by a service party, feed back a verification result of the sub-account registration data to the service party, and store the sub-account registration data that passes verification in a database.
The batch note booklet account list obtaining module 302 is configured to obtain a batch note booklet account list submitted by the business party through the primary account, where the batch registration sub-account list includes sub-account data to be registered, and the sub-account registration data includes information that the sub-account data needs to be verified before registration.
And the account registration module 303 is configured to perform batch registration on the sub-account data to be registered in the batch registration sub-account list according to the sub-account registration data that passes the verification and is stored in the database.
In one embodiment, the device may further comprise a receiving module for: sub-account registration data sent by each terminal device of a service party in a short message form are received, and each sub-account registration data comprises a communication number of the terminal device.
In one embodiment, the verification module 301 is specifically configured to: and respectively sending a short message which is sent by the terminal equipment and indicates that the sub-account registration data passes verification or fails verification and needs to be retransmitted to each terminal equipment.
In one embodiment, the sub-account registration data may also include a unique identification of the business party; the verification module 301 is specifically configured to: scanning a short message list formed by the received sub-account registration data through a timing task, and performing word segmentation on the sub-account registration data in the short message list to obtain a unique identifier and a communication number of a service party in the sub-account registration data; and respectively verifying the unique identification and the communication number of the service party in the registration data of each sub-account.
In one embodiment, the account registration module 303 is specifically configured to: according to the sub-account registration data which is saved in the database and passes verification, determining that the communication number in the sub-account data to be registered is the communication number in the sub-account registration data which passes verification, performing field verification on the sub-account data to be registered, and performing batch registration on the sub-account data to be registered, wherein the sub-account data to be registered passes field verification.
In one embodiment, the sub-account data to be registered may include a sub-account name and a communication number; the account registration module 303 is specifically configured to: and carrying out field verification on the sub-account data to be registered according to a registration rule, wherein the registration rule comprises one or more of a naming rule of a sub-account name, whether the sub-account name is repeated or not and whether the communication number is repeated or not.
In one embodiment, the account registration module 303 is specifically configured to: and transmitting the sub-account data to be registered, which is checked by the field, to a sub-account registration interface, respectively registering the sub-account data to be registered, which is checked by the field, through the sub-account registration interface, and adding a mark indicating successful registration to the corresponding communication number stored in the database after successful registration, wherein the mark is used for checking whether the communication number is repeated.
In addition, in the embodiment of the present invention, the specific implementation content of the account registration device has been described in detail in the above account registration method, so that the description is not repeated here.
Fig. 4 illustrates an exemplary system architecture 400 to which the account registration method or the account registration apparatus of the embodiment of the present invention may be applied.
As shown in fig. 4, the system architecture 400 may include terminal devices 401, 402, 403, a network 404, and a server 405. The network 404 is used as a medium to provide communication links between the terminal devices 401, 402, 403 and the server 405. The network 404 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 405 via the network 404 using the terminal devices 401, 402, 403 to receive or send messages or the like. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 401, 402, 403.
The terminal devices 401, 402, 403 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 405 may be a server providing various services, such as a background management server (by way of example only) providing support for shopping-type websites browsed by users using the terminal devices 401, 402, 403. The background management server may analyze and process the received data such as the product information query request, and feedback the processing result (e.g., the target push information, the product informationâonly an example) to the terminal device.
It should be noted that, the account registration method provided in the embodiment of the present invention is generally executed by the server 405, and accordingly, the account registration device is generally disposed in the server 405.
It should be understood that the number of terminal devices, networks and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 5, there is illustrated a schematic diagram of a computer system 500 suitable for use in implementing a terminal device or server in accordance with an embodiment of the present invention. The terminal device or server shown in fig. 5 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present invention.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU) 501, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input section 506 including a keyboard, a mouse, and the like; an output portion 507 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The drive 510 is also connected to the I/O interface 505 as needed. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as needed so that a computer program read therefrom is mounted into the storage section 508 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 509, and/or installed from the removable media 511. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 501.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: the processor comprises a verification module, a batch note booklet account list acquisition module and an account registration module. The names of the modules do not limit the module itself in some cases, for example, the account registration module may also be described as a module for verifying each sub-account registration data sent by the service party, feeding back a verification result of the sub-account registration data to the service party, and storing the sub-account registration data passing the verification into the database.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: verifying each sub-account registration data sent by the service party, feeding back a verification result of the sub-account registration data to the service party, and storing the sub-account registration data passing verification into a database; acquiring a batch note and booklet account list submitted by a business party through a main account, wherein the batch registration sub-account list comprises sub-account data to be registered, and the sub-account registration data comprises information to be verified before registration of the sub-account data; and registering the sub-account data to be registered in the batch registration sub-account list in batches according to the sub-account registration data which is saved in the database and passes the verification.
According to the technical scheme of the embodiment of the invention, each sub-account registration data sent by the service party is verified, the verification result of the sub-account registration data is fed back to the service party, and the verified sub-account registration data is stored in a database; acquiring a batch note and booklet account list submitted by a business party through a main account, wherein the batch registration sub-account list comprises sub-account data to be registered, and the sub-account registration data comprises information to be verified before registration of the sub-account data; and registering the sub-account data to be registered in the batch registration sub-account list in batches according to the sub-account registration data which is saved in the database and passes the verification. The realization scheme of perfect batch account registration can be provided, the accuracy and efficiency of account registration are improved, and the security risk is reduced.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4