Disclosure of Invention
To solve the problems in the existing transfer schemes, in order to implement more efficient transfer, an embodiment of the present specification provides a transfer method, which is used in a scenario where a first user and a second user transfer money on the same side, and specifically includes:
the first client acquires the biological characteristics of the second user, and sends the biological characteristics to the server, so that the server determines a second user identifier according to the biological characteristics;
receiving a second user identification returned by the server, and displaying the second user identification;
receiving a confirmation instruction of a first user, generating a transfer request containing a first user identification, a second user identification and a transfer amount, and sending the transfer request to a server so that the server can transfer money;
when the first user is a payee, the second user is a payer; when the first user is a payer, the second user is a payee.
Meanwhile, the present specification also provides a transfer method applied to a server, which is used in a scenario where a first user and a second user transfer money on the same side, and includes:
receiving the biological characteristics sent by the first client;
according to the biological characteristics, determining a second user identification based on a pre-stored database containing the biological characteristics of the user;
sending the second user identification to a first party client;
receiving a transfer request containing a first user identification, a second user identification and a transfer amount, and performing transfer processing;
when the first user is a payee, the second user is a payer; when the first user is a payer, the second user is a payee.
Correspondingly, an embodiment of the present specification provides a transfer device, which is used in a scenario where a first user and a second user perform transfer on the same side, and specifically includes:
the acquisition module acquires the biological characteristics of the second user;
the sending module is used for sending the biological characteristics to the server so that the server can determine a second user identifier according to the biological characteristics;
the receiving module is used for receiving a second user identifier returned by the server;
the display module displays the second user identification;
the generating module receives a confirmation instruction of the first user, generates a transfer request containing a first user identifier, a second user identifier and a transfer amount, and sends the transfer request to the server so that the server can transfer the transfer;
when the first user is a payee, the second user is a payer; when the first user is a payer, the second user is a payee.
Correspondingly, the embodiment of the present specification further provides another transfer device, which is used in a scenario where a first user and a second user perform transfer on the same side, and includes:
the receiving module is used for receiving the biological characteristics sent by the first client;
the determining module is used for determining a second user identifier based on a pre-stored database containing the biological characteristics of the user according to the biological characteristics;
the sending module is used for sending the second user identification to the first party client;
the receiving module is also used for receiving a transfer request containing a first user identifier, a second user identifier and a transfer amount;
the processing module is used for carrying out transfer processing;
when the first user is a payee, the second user is a payer; when the first user is a payer, the second user is a payee.
Correspondingly, the embodiment of the specification also provides a computer device which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor executes the program to realize the transfer method.
Correspondingly, the embodiment of the specification also provides a computer readable storage medium, and a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the computer program executes the transfer method.
According to the scheme provided by the embodiment of the specification, in a face-to-face account transfer scene, the first user scans the second user by using the first client to obtain the biological characteristics of the second user, uploads the biological characteristics to the server, enables the server to identify the second user based on the biological characteristics, further generates a corresponding account transfer request at the first client, sends the account transfer request to the server to transfer accounts, and transfers/pays the accounts, so that the operation steps of the user are reduced, and the account transfer efficiency and the user experience are improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the invention.
In addition, any one of the embodiments in the present specification is not required to achieve all of the effects described above.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings. As shown in fig. 1, fig. 1 is a schematic diagram of an architecture of a transfer scheme provided by an embodiment of the present specification, in which a first user and a second user are two types of users, namely, a payee and a payer, and when the first user is the payee, the second user is the payer; when the first user is a payer, the second user is a payee. It is easy to understand that the client corresponding to the first user is the first client, and the client corresponding to the second user is the second client. In addition, the first client and the second client may be integrated in a software program or hardware as different functional modules, or may be implemented as independent functional modules to perform their respective functions.
The transfer scheme provided by the embodiment of the present specification is explained in detail below with reference to the architecture diagram provided in fig. 1. The scheme specifically includes two aspects of a client and a server, and for the aspect of the client, the flow specifically includes the following steps, as shown in fig. 2, fig. 2 is a schematic flow diagram of a transfer method of the aspect of the client provided by the embodiment of the present specification, including
S201, the first client acquires the biological characteristics of the second user, and sends the biological characteristics to the server, so that the server determines the second user identification according to the biological characteristics.
The first user corresponding to the first client may be a payer or a payee. When the first user is a payee, the second user is a payer; when the first user is a payer, the second user is a payee. The biometric features may include facial features, iris features, fingerprint features, and other biometric features that may be used to identify the user. In the first client which can carry out transfer payment by adopting other modes (such as code scanning), the scanning function can be realized by adding corresponding function options in corresponding service pages, for example, adding a function option of 'face scanning' in a page for carrying out code scanning for payment, so as to facilitate the operation of a user. As shown in fig. 3, fig. 3 is an exemplary diagram for providing a scan face option in a client according to an embodiment of the present specification.
When the first user uses the transfer payment function of the first client, generally speaking, the first user has already performed login at the first client, and the first client may already obtain the first user identifier, for example, the account number, the identification number, the mobile phone number, and the like of the first user.
S203, receiving a second user identification returned by the server, and displaying the second user identification.
And the server receives the biological characteristics of the second user, namely, the second user can be identified, and the second user identification is returned. It will be readily appreciated that the form of the second user identification is not different from the first user. After receiving the identifier, the first user terminal can jump to a corresponding page to display the second user identifier. Under the face-to-face transfer scene, the users of the two parties can confirm the second user identification returned by the server on the face, and errors are avoided.
S205, receiving a confirmation instruction of the first user, generating a transfer request containing the first user identification, the second user identification and the transfer amount, and sending the transfer request to the server so that the server can perform transfer processing.
The confirmation instructions may include confirmation of the identity of the second user, confirmation of entry of the transfer amount, confirmation of generation of the transfer request, and the like. Of course, if the returned second user identifier is incorrect, the first user may also terminate the above-described transfer payment process.
According to the scheme provided by the embodiment of the specification, in a face-to-face account transfer scene, the first user scans the second user by using the first client to obtain the biological characteristics of the second user, uploads the biological characteristics to the server, enables the server to identify the second user based on the biological characteristics, further generates a corresponding account transfer request at the first client, sends the account transfer request to the server to transfer accounts, and transfers/pays the accounts, so that the operation steps of the user are reduced, and the account transfer efficiency and the user experience are improved.
In practical applications, the manner of obtaining the second user biometric characteristic may include the following manners: scanning the face of a second user to acquire the facial features of the second user; or scanning the eyes of a second user to acquire the iris characteristics of the second user.
In addition, when the server returns the second user identifier, the server may also return some other information of the second user to assist in identifying the second user identity, for example, a registered mailbox, a nickname, an avatar, and the like of the second user. And, in order to protect the privacy of the second user, the returned second user identifier or other information may be further encrypted by an algorithm, and desensitized, for example, hiding a middle part of characters from a nickname or a mobile phone number of the second user, mosaicing eyes of an avatar thereof, or displaying only a part of the avatar, and so on. Therefore, when the first user displays the second user identification, other information of the second user can be displayed together, and if the information is desensitized by the server, the information after desensitization is displayed. As shown in fig. 4, fig. 4 is a schematic diagram providing a desensitized display of second user identification and other information in the first client according to an embodiment of the present specification.
In practical applications, the desensitization process may also be performed on the first client side, that is, for displaying the second user identifier in S203, the desensitization process may further include: desensitizing the second subscriber identity; and displaying the second user identification after the desensitization treatment. By desensitizing the second user identification or other information related thereto, the privacy of the second user may be better protected.
When the first user is a payer, the second user is a payee. At this time, the first user scans the payee as the payer, and can directly confirm at the first user.
However, when the first user is the payee and the second user is the payer, the second user may be considered as the payer, since the scanning of the facial features or iris features of the user usually requires the approval of the second user, and the second user may be considered as authorized to make the payment. Alternatively, in some cases, the second user may not need to confirm the transfer payment initiated by the first user, for example, when the second user has initiated micropayment non-confirmation and the transfer amount does not exceed the micropayment range; or, the first user identification and the second user identification both exist in the friend list of the other party in the user service side, and the like. However, in another embodiment, the server may also push the relevant information in the first transfer request to the payer (in this case, the second client of the second user) in the transfer request for authentication. After receiving the verification request, the second client can facilitate the second user to confirm the corresponding transfer request, including passing or failing the verification, and return verification success/failure information to the server, so that the server performs corresponding processing. By sending the authentication request to the payer, the security of the transfer scheme provided by the embodiment of the specification can be further improved.
The above section describes an execution flow of the client side, for a scheme provided by the embodiment of the present description, in the service side, the execution flow is as shown in fig. 5, and fig. 5 is a schematic flow diagram of the service side provided by the embodiment of the present description, and specifically includes:
s501, receiving the biological characteristics sent by the first client, wherein the biological characteristics comprise facial characteristics, iris characteristics, fingerprint characteristics and the like.
S503, according to the biological characteristics, based on a pre-stored database containing the biological characteristics of the user, determining a second user identification. In other words, the biometric feature can be used for the user to log in at the client and also can be used for the server to identify the user.
And S505, sending the second user identifier to the first party client.
And S507, receiving a transfer request containing the first user identification, the second user identification and the transfer amount, and performing transfer processing.
In practical applications, the server may also determine other information (e.g., an avatar, a nickname, a name, etc., to assist in identity confirmation) of the second user according to the second user identifier, and send the other information to the first user. And the server side can also perform desensitization processing on the second user identification and the other information and then send the second user identification and the other information to the first client side. The detailed description of the embodiments is not repeated here.
In an embodiment, when the first user is a payee and the second user is a payer, the server may further send the information related to the transfer request to the second server for the second user to confirm. And when the information that the second user passes the verification is received, executing the transfer, otherwise, not executing the transfer. By the mode, the safety in the transfer process is further improved.
Correspondingly, an embodiment of the present specification further provides a transfer device, which is used in a scenario where a first user and a second user perform transfer on the same side, as shown in fig. 6, where fig. 6 is a schematic structural diagram of a transfer device in the aspect of a client side provided in the embodiment of the present specification, and includes:
an obtaining module 601, configured to obtain a biometric feature of a second user;
a sending module 602, configured to send the biological characteristic to a server, so that the server determines a second user identifier according to the biological characteristic;
the receiving module 603 is configured to receive a second user identifier returned by the server;
a display module 604, configured to display the second user identifier;
the generating module 605 receives a confirmation instruction of the first user, generates a transfer request containing the first user identifier, the second user identifier and the transfer amount, and sends the transfer request to the server side so that the server side can perform transfer processing;
when the first user is a payee, the second user is a payer; when the first user is a payer, the second user is a payee.
Further, the obtaining module 601 scans a face of a second user to obtain facial features of the second user; or scanning the eyes of a second user to acquire the iris characteristics of the second user.
Further, the receiving module 603 receives a second user identifier and other information of the second user, which are returned by the server, where the other information of the second user is determined by the server according to the second user identifier, and is used to assist in identifying the identity of the second user; the display module 604 displays the second user identifier and other information of the second user.
Further, the display module 604 performs desensitization processing on the second user identifier; and displaying the second user identification after the desensitization treatment.
When the first user is a payee and the second user is a payer, the device further comprises a verification module 606, wherein the verification module is used for receiving a verification request returned by the server by the second user so that the second user can confirm the transfer; and receiving a confirmation instruction of the second user, and sending verification success/failure information to the server.
Correspondingly, an embodiment of the present specification further provides a transfer device, which is used in a scenario where a first user and a second user perform transfer on the same side, as shown in fig. 7, where fig. 7 is a schematic structural diagram of a transfer device in the aspect of a server side provided by the embodiment of the present specification, and includes:
a receiving module 701, configured to receive a biometric feature sent by a first client;
a determining module 702, configured to determine a second user identifier according to the biometric feature based on a pre-stored database containing the biometric feature of the user;
a sending module 703, configured to send the second user identifier to the first party client;
the receiving module 701 is further configured to receive a transfer request including a first user identifier, a second user identifier, and a transfer amount;
a processing module 704 for performing transfer processing;
when the first user is a payee, the second user is a payer; when the first user is a payer, the second user is a payee.
Further, after determining the second user identifier, the determining module 702 is further configured to determine other information of the second user according to the second user identifier, where the other information of the second user is determined by the server according to the second user identifier, and is used to assist in identifying the second user identity; the sending module 703 sends the second user identifier and other information of the second user to the first client.
Further, the apparatus further comprises a desensitization module 705 for performing desensitization processing on the second subscriber identity; the sending module 703 sends the desensitized second user identifier to the first party client.
When the first user is a payee and the second user is a payer, the sending module 703 is further configured to send a verification request to the second client, so that the second user verifies the transfer; the processing module 704 executes the transfer process if receiving the verification success message sent by the second client, otherwise, does not execute the transfer process.
Embodiments of the present specification also provide a computer device including at least a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the transfer method shown in fig. 2 or fig. 5 when executing the program.
Fig. 8 is a schematic diagram illustrating a more specific hardware structure of a computing device according to an embodiment of the present disclosure, where the computing device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.
The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
Bus 1050 includes a path that transfers information between various components of the device, such as processor 1010, memory 1020, input/output interface 1030, and communication interface 1040.
It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor, implements the transfer method shown in fig. 2 or fig. 5.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The systems, methods, modules or units described in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the method embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to the partial description of the method embodiment for relevant points. The above-described method embodiments are merely illustrative, wherein the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present specification. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is only a specific embodiment of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, a plurality of modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as the protection scope of the embodiments of the present disclosure.