CN113079224A - Account binding method and device, storage medium and electronic equipment - Google Patents
Account binding method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN113079224A CN113079224A CN202110295329.5A CN202110295329A CN113079224A CN 113079224 A CN113079224 A CN 113079224A CN 202110295329 A CN202110295329 A CN 202110295329A CN 113079224 A CN113079224 A CN 113079224A
- Authority
- CN
- China
- Prior art keywords
- server
- account
- user
- bank
- card
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims description 47
- 230000008520 organization Effects 0.000 claims description 37
- 238000004590 computer program Methods 0.000 claims description 18
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 10
- 230000006872 improvement Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000012545 processing Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/255—Maintenance or indexing of mapping tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the specification sends a binding request to an intermediary server by a first service side server, the intermediary server sends identification information of a user and a first account registered by the user in the first service side server to a second service side server, and the second service side server binds the first account with a second account registered by the user in the second service side server. Thus, even if the first service server and the second service server are prohibited from directly interacting, the user can still directly bind the first account with the second account registered by the user at the second service server when the first service server registers the first account.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to an account binding method and apparatus, a storage medium, and an electronic device.
Background
With the development of internet services, users can register accounts on various service platforms, and binding the accounts registered by the users on different service platforms becomes a current popular requirement. For example, a bank card of a certain bank (corresponding to an account number registered by a user at the bank) of the user is bound with an account number registered by the user at a certain payment platform.
In the prior art, when a user transacts a bank card in a bank, the transacted bank card can be directly bound with an account number registered by the user on other service platforms, specifically, when the user transacts the bank card in the bank, the user can inform the bank of the platform to which the user wants to bind, a server of the bank sends an identifier of the user and a card number of the bank card to a server corresponding to the platform, and the server binds the received card number with the account number registered by the user on the platform and returns a binding result.
However, in an actual application scenario, the server of the platform is prohibited from directly communicating with the server of the bank, which results in that the user cannot directly bind the bank card with the account of the service platform when the bank transacts the bank card.
Disclosure of Invention
Embodiments of the present specification provide an account binding method, an account binding apparatus, a storage medium, and an electronic device, so as to partially solve the problems in the prior art.
The embodiment of the specification adopts the following technical scheme:
the account binding method provided by the specification comprises the following steps:
the second service side server receives the identification information of the user and the first account number sent by the intermediate side server; the identification information and the first account are sent by the intermediary server after receiving a binding request sent by a first service server, and the first account is an account registered in the first service server by the user;
determining a second account number registered in the second service party server by the user according to the identification information;
and binding the received first account with the determined second account, and returning a binding result to the intermediary server, so that the intermediary server returns the binding result to the first service server.
Optionally, the intermediary server is a server corresponding to a card organization;
the first business side server is a server corresponding to a bank;
the first account number is the card number of a bank card transacted by the user in the bank.
Optionally, the binding request is sent by the server corresponding to the bank to the server corresponding to the card organization when the user transacts the bank card.
Optionally, the receiving, by the second service server, the identification information of the user and the first account sent by the intermediary server specifically includes:
the second business side server receives the identification information of the user and the card number of the bank card sent by the server corresponding to the card organization through a designated channel; wherein the designated channel is a channel that does not require authentication of the user's identity.
Optionally, the receiving, by the second service server, the identification information of the user and the first account sent by the intermediary server specifically includes:
the second business server receives the user identification information, the bank card number and the protocol identification which are sent by the server corresponding to the card organization;
after the received first account and the determined second account are bound, the method further comprises the following steps:
adding the second account into a protocol corresponding to the protocol identification;
setting the state of the agreement added with the second account as a valid state, wherein the agreement corresponding to the agreement identifier at least comprises: the identification information of the bank, the identification information of the user, the card number of the bank card and the second account number.
Optionally, the protocol identifier is generated by the server corresponding to the card organization after receiving a binding request sent by the server corresponding to the bank.
Optionally, the protocol identifier is generated by a server corresponding to the bank and carried in the binding request to be sent to a server corresponding to the card organization.
An account binding apparatus provided in this specification, applied to a second service server, includes:
the receiving module is used for receiving the identification information of the user and the first account number sent by the intermediary server; the identification information and the first account are sent by the intermediary server after receiving a binding request sent by a first service server, and the first account is an account registered in the first service server by the user;
a determining module, configured to determine, according to the identification information, a second account that is registered by the user in the second service provider server;
and the binding module is used for binding the received first account with the determined second account and returning a binding result to the intermediate server so that the intermediate server returns the binding result to the first service server.
The present specification provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the account binding method described above.
The electronic device provided by the present specification includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the account binding method when executing the program.
The embodiment of the specification adopts at least one technical scheme which can achieve the following beneficial effects:
in the embodiment of the present description, a first service server sends a binding request to an intermediary server, the intermediary server sends identification information of a user and a first account registered by the user in the first service server to a second service server, and the second service server binds the first account with a second account registered by the user in the second service server. Thus, even if the first service server and the second service server are prohibited from directly interacting, the user can still directly bind the first account with the second account registered by the user at the second service server when the first service server registers the first account.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:
fig. 1 is a schematic diagram of an account binding method provided in an embodiment of the present specification;
fig. 2 is a schematic structural diagram of an account binding apparatus according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device provided in an embodiment of this specification.
Detailed Description
In order to make the objects, technical solutions and advantages of the present disclosure more clear, the technical solutions of the present disclosure will be clearly and completely described below with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort belong to the protection scope of the present specification.
The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic diagram of an account binding method provided in an embodiment of the present specification, including:
s100: and the first service party server sends a binding request to the intermediate party server after the user registers the first account.
In this embodiment of the present specification, the first business server and the second business server may be servers corresponding to different services provided by different service providers, for example, the first business server may be a server corresponding to a bank, or may be a server corresponding to a service provider providing an instant messaging service, and the second business server may be a server corresponding to a service provider providing services such as takeout, trip, and payment.
In the following, the first service server is taken as a server corresponding to a bank as an example for explanation, and the second service server is not limited.
When the first service server is a server corresponding to a bank, the first account number registered by the user in the first service server may be a card number of a bank card handled by the user in the bank.
Specifically, when the bank transacts the bank card, the user can inform the bank of the second service party to which the bank wants to bind, and the server corresponding to the bank sends a binding request to the intermediary server. The intermediary server may be a server corresponding to the card organization.
The binding request may specifically carry identification information of the user and a card number of a bank card handled by the user, and may also carry identification information of a second service party. The identification information of the user described in the embodiments of the present specification may include at least one of a name, an identification number, and a mobile phone number of the user.
S102: the intermediate server receives the binding request sent by the first service server and sends the identification information of the user and the first account number to the second service server.
After receiving the binding request, the card organization server serving as the intermediary server may determine the second service party server according to the identification information of the second service party carried in the binding request, and send the identification information of the user and the card number of the bank card of the user carried in the binding request to the second service party server.
S104: and the second service party server determines a second account number registered in the second service party server by the user according to the received identification information.
After the second service side server receives the identification information of the user and the card number of the bank card, the second service side server can determine a second account corresponding to the identification information of the user according to the received identification information of the user, namely the second account registered in the second service side server by the user.
S106: and the second service party server binds the received first account with the determined second account.
And after the second service party determines the second account number of the user, the received card number of the bank card can be bound with the determined second account number.
S108: and the second service side server returns the binding result to the intermediate side server.
S110: and the intermediate server returns the binding result to the first service side server.
After the second service server binds the card number of the bank card of the user with the second account number of the user, the binding result can be returned to the server corresponding to the card organization, and the server corresponding to the card organization returns the binding result to the server corresponding to the bank.
Subsequently, when the user uses the second account to pay, the second business server can send a payment request to the server corresponding to the bank through the server corresponding to the card organization according to the binding relationship between the second account and the card number of the bank card, the server corresponding to the bank carries out corresponding payment operation according to the payment request, and the result of the payment operation is returned to the second business server through the server corresponding to the card organization.
It can be seen from the above process that the second service server does not interact directly with the first service server, but indirectly interacts with the first service server through the intermediary server, and even if the first service server and the second service server are prohibited from directly interacting, the user can still directly bind the first account with the second account registered by the user at the second service server when the first service server registers the first account.
In the embodiment of the description, because the binding request is sent to the intermediate server by the server corresponding to the bank when the bank handles the bank card, that is, the triggering of the binding process is triggered by the user handling the bank card in the bank, and the user needs to perform necessary authentication on the user by the bank when the bank handles the bank card, when the card number of the bank card is bound with the second account, authentication does not need to be performed again, and the efficiency of account binding can be improved. Thus, in step S102, when the server corresponding to the card organization receives the binding request and sends the identification information of the user and the card number of the bank card to the second service server, a specified channel that does not need to verify the identity of the user may be selected to send the identification information of the user and the card number of the bank card. Correspondingly, the second business side server also receives the identification information of the user and the card number of the bank card sent by the server corresponding to the card organization through the appointed channel, and then the card number of the bank card received through the appointed channel can be directly bound with the second account number of the user without carrying out identity verification on the user before binding.
Further, in an actual application scenario, the binding between the bank card and the account number of the service platform requires an agreement among multiple parties, and the agreement is mainly used for recording the correspondence between the account numbers of the bank, the bank card, the card organization, the service platform, and the service platform, that is, the agreement records which bank card of which bank is bound with which account number of which service platform through which card organization. Therefore, in step S102, the server corresponding to the card organization may send the identification information of the user, the card number of the bank card, and the protocol identifier to the second service server, where the protocol corresponding to the protocol identifier is the protocol required for binding the card number of the bank card and the second account number.
Correspondingly, after binding the received card number of the bank card with the second account number of the user, the second service server may add the second account number to an agreement corresponding to the agreement identifier, and set the state of the agreement to which the second account number is added to a valid state, where the agreement at least includes: the identification information of the bank, the identification information of the user, the card number of the bank card and the second account number. The effective state then indicates: and when a payment request of the second account number is received, allowing the bank card corresponding to the card number to execute corresponding payment operation.
Similarly, the server corresponding to the card organization and the server corresponding to the bank both store the protocol corresponding to the protocol identifier, and after the subsequent second service server returns the binding result to the server corresponding to the card organization and the server corresponding to the bank, the server corresponding to the card organization and the server corresponding to the bank may also add the second identifier to the protocol corresponding to the protocol identifier, and set the state of the protocol to the valid state.
So far, after the bank card is bound with the second account, all nodes (a server corresponding to the card organization and a server corresponding to the bank) which are required to execute the payment operation through the bank card bound with the second account are opened.
The protocol identifier and the protocol corresponding to the protocol identifier may be generated by the server corresponding to the card organization after receiving a binding request sent by the server corresponding to the bank. Specifically, after receiving the binding request, the server corresponding to the card organization may generate a corresponding protocol according to the identification information of the bank, the card number of the bank card carried in the binding request, and the identification information of the user, create a protocol identifier corresponding to the protocol, and then send the protocol identifier and the protocol corresponding to the protocol identifier to the server corresponding to the bank and the second service server, respectively.
The protocol identifier and the protocol corresponding to the protocol identifier may also be generated by a server corresponding to a bank when the user handles the bank card and informs the second service party to which the user is bound. Specifically, the server corresponding to the bank may generate a corresponding protocol according to the identification information of the bank, the card number of the bank card, and the identification information of the user, create a protocol identifier corresponding to the protocol, send the protocol identifier and the protocol corresponding to the protocol identifier to the server corresponding to the card organization, and finally send the protocol identifier and the protocol corresponding to the protocol identifier to the second service server by the server corresponding to the card organization.
Based on the same idea, the account binding method provided in the embodiments of the present specification further provides a corresponding apparatus, a storage medium, and an electronic device.
Fig. 2 is a schematic structural diagram of an account binding apparatus provided in an embodiment of this specification, where the apparatus is applied to a second business server, and the apparatus includes:
a receiving module 201, configured to receive identification information of a user and a first account sent by an intermediary server; the identification information and the first account are sent by the intermediary server after receiving a binding request sent by a first service server, and the first account is an account registered in the first service server by the user;
a determining module 202, configured to determine, according to the identification information, a second account that is registered by the user in the second service provider server;
the binding module 203 is configured to bind the received first account with the determined second account, and return a binding result to the intermediary server, so that the intermediary server returns the binding result to the first service server.
Optionally, the intermediary server is a server corresponding to a card organization;
the first business side server is a server corresponding to a bank;
the first account number is the card number of a bank card transacted by the user in the bank.
Optionally, the binding request is sent by the server corresponding to the bank to the server corresponding to the card organization when the user transacts the bank card.
Optionally, the receiving module 201 is specifically configured to receive, through a specified channel, the identification information of the user and the card number of the bank card, where the identification information is sent by a server corresponding to the card organization; wherein the designated channel is a channel that does not require authentication of the user's identity.
Optionally, the receiving module 201 is specifically configured to receive the identification information of the user, the card number of the bank card, and the protocol identifier, which are sent by the server corresponding to the card organization;
the binding module 203 is further configured to, after binding the received first account with the determined second account, add the second account to a protocol corresponding to the protocol identifier; setting the state of the agreement added with the second account as a valid state, wherein the agreement corresponding to the agreement identifier at least comprises: the identification information of the bank, the identification information of the user, the card number of the bank card and the second account number.
Optionally, the protocol identifier is generated by the server corresponding to the card organization after receiving a binding request sent by the server corresponding to the bank.
Optionally, the protocol identifier is generated by a server corresponding to the bank and carried in the binding request to be sent to a server corresponding to the card organization.
The present specification also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, is operable to perform the account binding method provided above.
Based on the account binding method provided above, an embodiment of the present specification further provides a schematic structural diagram of the electronic device shown in fig. 3. As shown in fig. 3, the drone includes, at the hardware level, a processor, an internal bus, a network interface, a memory, and a non-volatile memory, although it may also include hardware required for other services. The processor reads the corresponding computer program from the nonvolatile memory to the memory and then runs the computer program to realize the account binding method.
Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
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.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage 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, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.
Claims (10)
1. An account binding method is characterized by comprising the following steps:
the second service side server receives the identification information of the user and the first account number sent by the intermediate side server; the identification information and the first account are sent by the intermediary server after receiving a binding request sent by a first service server, and the first account is an account registered in the first service server by the user;
determining a second account number registered in the second service party server by the user according to the identification information;
and binding the received first account with the determined second account, and returning a binding result to the intermediary server, so that the intermediary server returns the binding result to the first service server.
2. The method of claim 1, wherein the mediator server is a server to which a card organization corresponds;
the first business side server is a server corresponding to a bank;
the first account number is the card number of a bank card transacted by the user in the bank.
3. The method of claim 2, wherein the binding request is sent by a server corresponding to the bank to a server corresponding to the card organization when the user transacts the bank card.
4. The method of claim 3, wherein the second service server receiving the identification information of the user and the first account sent by the intermediary server specifically comprises:
the second business side server receives the identification information of the user and the card number of the bank card sent by the server corresponding to the card organization through a designated channel; wherein the designated channel is a channel that does not require authentication of the user's identity.
5. The method of claim 2, wherein the second service server receiving the identification information of the user and the first account sent by the intermediary server specifically includes:
the second business server receives the user identification information, the bank card number and the protocol identification which are sent by the server corresponding to the card organization;
after the received first account and the determined second account are bound, the method further comprises the following steps:
adding the second account into a protocol corresponding to the protocol identification;
setting the state of the agreement added with the second account as a valid state, wherein the agreement corresponding to the agreement identifier at least comprises: the identification information of the bank, the identification information of the user, the card number of the bank card and the second account number.
6. The method of claim 5, wherein the protocol identification is generated by the server corresponding to the card organization after receiving a binding request sent by the server corresponding to the bank.
7. The method of claim 5, wherein the protocol identification is generated by a server corresponding to the bank and carried in the binding request to the server corresponding to the card organization.
8. An account binding apparatus, applied to a second business server, the apparatus comprising:
the receiving module is used for receiving the identification information of the user and the first account number sent by the intermediary server; the identification information and the first account are sent by the intermediary server after receiving a binding request sent by a first service server, and the first account is an account registered in the first service server by the user;
a determining module, configured to determine, according to the identification information, a second account that is registered by the user in the second service provider server;
and the binding module is used for binding the received first account with the determined second account and returning a binding result to the intermediate server so that the intermediate server returns the binding result to the first service server.
9. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any of the preceding claims 1-7.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of claims 1-7 when executing the program.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110295329.5A CN113079224A (en) | 2021-03-19 | 2021-03-19 | Account binding method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110295329.5A CN113079224A (en) | 2021-03-19 | 2021-03-19 | Account binding method and device, storage medium and electronic equipment |
Publications (1)
Publication Number | Publication Date |
---|---|
CN113079224A true CN113079224A (en) | 2021-07-06 |
Family
ID=76613480
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110295329.5A Pending CN113079224A (en) | 2021-03-19 | 2021-03-19 | Account binding method and device, storage medium and electronic equipment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN113079224A (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113766496A (en) * | 2021-08-30 | 2021-12-07 | 青岛海尔科技有限公司 | Cross-platform binding method and system of intelligent equipment and related equipment |
CN113766503A (en) * | 2021-08-31 | 2021-12-07 | 青岛海尔科技有限公司 | Binding method and system of intelligent equipment and related equipment |
CN113934383A (en) * | 2021-09-23 | 2022-01-14 | 北京三快在线科技有限公司 | Method, device, server and storage medium for binding cloud printer and service |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180343261A1 (en) * | 2017-05-24 | 2018-11-29 | Microsoft Technology Licensing, Llc | Transfer of secure external sharing link |
CN109993513A (en) * | 2019-03-22 | 2019-07-09 | 北京三快在线科技有限公司 | The methods, devices and systems of payment account binding bank card |
CN112308545A (en) * | 2020-10-14 | 2021-02-02 | 北京三快在线科技有限公司 | Account binding method and device |
-
2021
- 2021-03-19 CN CN202110295329.5A patent/CN113079224A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180343261A1 (en) * | 2017-05-24 | 2018-11-29 | Microsoft Technology Licensing, Llc | Transfer of secure external sharing link |
CN109993513A (en) * | 2019-03-22 | 2019-07-09 | 北京三快在线科技有限公司 | The methods, devices and systems of payment account binding bank card |
CN112308545A (en) * | 2020-10-14 | 2021-02-02 | 北京三快在线科技有限公司 | Account binding method and device |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113766496A (en) * | 2021-08-30 | 2021-12-07 | 青岛海尔科技有限公司 | Cross-platform binding method and system of intelligent equipment and related equipment |
CN113766496B (en) * | 2021-08-30 | 2024-01-26 | 青岛海尔科技有限公司 | Cross-platform binding method and system for intelligent equipment and related equipment |
CN113766503A (en) * | 2021-08-31 | 2021-12-07 | 青岛海尔科技有限公司 | Binding method and system of intelligent equipment and related equipment |
CN113766503B (en) * | 2021-08-31 | 2023-10-24 | 青岛海尔科技有限公司 | Binding method and system of intelligent device and related device |
CN113934383A (en) * | 2021-09-23 | 2022-01-14 | 北京三快在线科技有限公司 | Method, device, server and storage medium for binding cloud printer and service |
CN113934383B (en) * | 2021-09-23 | 2024-01-26 | 北京三快在线科技有限公司 | Method, device, server and storage medium for binding cloud printer and service |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106899666B (en) | Data processing method and device for service identification | |
CN113079224A (en) | Account binding method and device, storage medium and electronic equipment | |
CN109669709B (en) | Data migration method and data migration system for block chain upgrading | |
CN107070871B (en) | Identity verification method and device | |
CN110992040A (en) | Transaction processing method, device and equipment | |
CN111882317A (en) | Business processing system, readable storage medium and electronic device | |
CN111651467A (en) | Block chain link point interface issuing and calling method and device | |
CN111897542A (en) | Method and device for gray scale release | |
CN114331403A (en) | Data processing, resource transfer and payment method, device, equipment and medium | |
CN109144600B (en) | Application program running method and device and computer readable medium | |
CN109376988B (en) | Service data processing method and device | |
CN108596581B (en) | Verification method and device for resource transfer and electronic payment verification method and device | |
CN112491885B (en) | Electronic certificate transmission method, device and equipment | |
CN112286968A (en) | Service identification method, equipment, medium and electronic equipment | |
CN112529576A (en) | Resource processing method and device and payment processing method and device | |
CN115563584B (en) | Model training method and device, storage medium and electronic equipment | |
CN110022351B (en) | Service request processing method and device | |
CN113435889B (en) | Transaction processing method and device based on credit | |
CN115330372A (en) | Payment processing method and device based on prepaid voucher | |
CN111639931A (en) | Service processing method and device | |
CN112308545A (en) | Account binding method and device | |
CN110245115B (en) | File processing method, engine and system | |
CN113347110A (en) | Flow control method, flow control device, storage medium and equipment | |
CN112286572A (en) | Configuration method and device of business process | |
CN112308560A (en) | Service processing system and method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
TA01 | Transfer of patent application right |
Effective date of registration: 20220628 Address after: 200050 C201, 2nd floor, building 4, 492 Anhua Road, Changning District, Shanghai Applicant after: HANHAI INFORMATION TECHNOLOGY SHANGHAI Co.,Ltd. Address before: 100080 2106-030, 9 North Fourth Ring Road, Haidian District, Beijing. Applicant before: BEIJING SANKUAI ONLINE TECHNOLOGY Co.,Ltd. |
|
TA01 | Transfer of patent application right | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210706 |
|
RJ01 | Rejection of invention patent application after publication |