CN111626729A

CN111626729A - Transaction method, apparatus, computing device and medium executed by target institution

Info

Publication number: CN111626729A
Application number: CN202010482174.1A
Authority: CN
Inventors: 郑荣廷; 胡松鄂; 张立伟; 段正
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-05-29
Filing date: 2020-05-29
Publication date: 2020-09-04
Anticipated expiration: 2040-05-29
Also published as: CN111626729B

Abstract

The present disclosure provides a transaction method performed by a target institution, comprising: receiving a transaction request from a third-party mechanism, wherein the third-party mechanism comprises a third-party client, the transaction request is generated by a current user through transaction of the third-party client, and the transaction request comprises client type information of the third-party client; sending a first request to a third-party mechanism based on the transaction request, wherein the first request is used for acquiring a first user identifier of a current user in the third-party mechanism; receiving feedback information generated by the third-party organization in response to the first request, wherein the feedback information comprises a first user identification; determining whether the current user has a second user identifier in the target mechanism or not based on the client type information and the first user identifier to obtain a determination result, wherein the second user identifier is associated with the client type information and the first user identifier; based on the determination, a payment operation is performed for the transaction request. The present disclosure also provides an apparatus, a computing device, and a medium.

Description

Transaction method, apparatus, computing device and medium executed by target institution

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a transaction method executed by a target entity, a transaction apparatus, a computing device, and a computer-readable storage medium.

Background

With the change of payment means and consumption scenes, the payment habits of people are increasingly diversified. In order to improve the convenience of transaction between merchants and users, the bank realizes the function of supporting third-party payment on a payment platform. For example, a bank provides an offline collection two-dimensional code for a merchant, and supports both bank customers to use bank clients to perform code scanning payment and bank customers to use various third-party clients such as payment treasures, WeChat and the like to perform code scanning payment.

In carrying out the presently disclosed concept, the inventors have found that there are at least the following problems in the related art.

When a bank processes transactions, a user needs to log in a bank client for verification every transaction, and therefore transaction efficiency is low. When a user selects a third-party client to scan the code for payment, payment is usually carried out through a default third-party payment mode, the payment modes of different third-party clients are not uniform, and a bank is difficult to carry out uniform management on the payment process. When a user selects a third-party payment mode to call a bank account for payment and a bank enters a merchant, the clearing speed is slow due to the fact that a clearing process involves a card issuing bank, a third-party mechanism, an internet or bank union, an acquirer and other multi-party mechanisms, and therefore the merchant receives the payment in a delayed manner; in addition, since the clearing process involves a plurality of organizations, the clearing process occupies more server resources, which results in a large amount of server resources consumed in the clearing process.

Disclosure of Invention

In view of the above, the present disclosure provides an optimized trading method performed by a target institution, a trading apparatus, a computing device and a computer-readable storage medium.

One aspect of the present disclosure provides a method of transaction performed by a target institution, comprising: receiving a transaction request from a third-party organization, wherein the third-party organization comprises a third-party client, the transaction request is generated by a current user conducting transaction through the third-party client, the transaction request comprises client type information of the third-party client, a first request is sent to the third-party organization based on the transaction request, the first request is used for obtaining a first user identification of the current user in the third-party organization, feedback information generated by the third-party organization in response to the first request is received, the feedback information comprises the first user identification, whether the current user has a second user identification in the target organization is determined based on the client type information and the first user identification so as to obtain a determination result, and the second user identification is associated with the client type information and the first user identification, performing a payment operation for the transaction request based on the determination result.

According to an embodiment of the present disclosure, the performing a payment operation for the transaction request based on the determination result includes: and when the determination result indicates that the current user does not have the second user identifier in the target mechanism, sending login interface information to the third-party mechanism so as to log in a server of the target mechanism based on the login interface corresponding to the login interface information.

According to an embodiment of the present disclosure, the method further includes: and receiving a login request sent by the current user through the login interface, responding to the login request, sending the order interface information to the third-party mechanism so as to send a payment request to the target mechanism based on an order interface corresponding to the order interface information, and executing the payment operation based on the payment request.

According to an embodiment of the present disclosure, the method further includes: and generating a new second user identifier after the determined result indicates that the current user does not have the second user identifier in the target mechanism and the payment operation is executed, and storing the new second user identifier in association with the client type information and the first user identifier.

According to an embodiment of the present disclosure, the method further includes: after the determination result indicates that the current user has a second user identification in the target institution and the payment operation is executed, determining a current second user identification associated with the payment request, and deleting an association relation stored in the target institution in response to the second user identification and the current second user identification being inconsistent, wherein the association relation comprises a first association relation having the client type information and the first user identification and a second association relation having the current second user identification.

According to an embodiment of the present disclosure, the sending the first request to the third-party institution based on the transaction request includes: and determining whether the client type information is preset client type information or not based on the transaction request, and sending the first request to the third-party mechanism in response to determining that the client type information is the preset client type information.

According to an embodiment of the present disclosure, the transaction request further includes a merchant account, and the payment request includes a user account of the current user. Wherein the performing payment operations for the transaction request comprises: and acquiring transaction resources from the user account based on the account information, and sending the transaction resources to the merchant account based on the merchant information.

According to an embodiment of the present disclosure, the login request includes a communication identifier of the current user. Wherein the receiving of the login request sent by the current user through the login interface includes: and storing the communication identifier to the target mechanism as a reference communication identifier, generating a verification code based on the communication identifier, storing the verification code to the target mechanism as a reference verification code, sending the verification code to the current user through a communication operator, and receiving a login request sent by the current user based on the verification code.

According to the embodiment of the present disclosure, the login request further includes a current verification code input by the current user through a login interface and a current communication identifier when the current user initiates the login request. Wherein said sending order interface information to said third party authority in response to said login request comprises: and comparing the current verification code with the reference verification code to obtain a first comparison result, comparing the current communication identifier with the reference communication identifier to obtain a second comparison result, and sending the order interface information to the third-party organization based on the first comparison result and the second comparison result.

Another aspect of the present disclosure provides a transaction apparatus including: the system comprises a first receiving module, a first sending module, a second receiving module, a first determining module and a first payment module. The first receiving module receives a transaction request from a third-party organization, wherein the third-party organization comprises a third-party client, the transaction request is generated by a current user performing transaction through the third-party client, and the transaction request comprises client type information of the third-party client. And the first sending module is used for sending a first request to the third-party mechanism based on the transaction request, wherein the first request is used for acquiring a first user identifier of the current user in the third-party mechanism. A second receiving module, configured to receive feedback information generated by the third-party organization in response to the first request, where the feedback information includes the first user identifier. A first determination module, configured to determine, based on the client type information and the first user identifier, whether the current user has a second user identifier in the target organization to obtain a determination result, where the second user identifier is associated with the client type information and the first user identifier. A first payment module to perform a payment operation for the transaction request based on the determination result.

According to an embodiment of the present disclosure, the apparatus further includes: the system comprises a third receiving module, a second sending module and a second payment module. And the third receiving module is used for receiving the login request sent by the current user through the login interface. And the second sending module is used for responding to the login request, sending the order interface information to the third-party mechanism so as to send a payment request to the target mechanism based on an order interface corresponding to the order interface information. And the second payment module executes the payment operation based on the payment request.

According to an embodiment of the present disclosure, the apparatus further includes: the device comprises a generation module and a storage module. And the generating module generates a new second user identifier after the determination result indicates that the current user does not have the second user identifier in the target mechanism and the payment operation is executed. And the storage module is used for storing the newly added second user identifier, the client type information and the first user identifier in an associated manner.

According to an embodiment of the present disclosure, the apparatus further includes: a second determining module and a deleting module. Wherein the second determination module determines the current second user identity associated with the payment request after the determination result characterizes that the current user has the second user identity in the target institution and after performing the payment operation. And the deleting module is used for deleting the association relation stored in the target mechanism in response to the inconsistency between the second user identifier and the current second user identifier, wherein the association relation comprises a first association relation with the client type information and the first user identifier and a second association relation with the current second user identifier.

Another aspect of the present disclosure provides a computing device comprising: one or more processors; memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.

Another aspect of the disclosure provides a non-transitory readable storage medium storing computer-executable instructions for implementing the method as described above when executed.

Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.

According to the embodiment of the disclosure, by using the transaction method, the problems of low transaction efficiency, difficult uniform management of payment process and delayed merchant payment collection due to low clearing speed can be at least partially solved. Therefore, the technical effects of improving the transaction efficiency, managing the payment process and improving the speed of the merchant for posting can be achieved.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

fig. 1 schematically shows a system architecture of a transaction method and a transaction device according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a transaction method performed by a target institution in accordance with an embodiment of the present disclosure;

FIG. 3 schematically illustrates an interaction flow diagram of a transaction method according to an embodiment of the disclosure;

FIG. 4 schematically illustrates a flow chart of deduction and posting according to an embodiment of the disclosure;

FIG. 5 schematically shows a flow diagram for responding to a login request according to an embodiment of the present disclosure;

FIG. 6 schematically shows a block diagram of a transaction device according to an embodiment of the disclosure; and

FIG. 7 schematically illustrates a block diagram of a computer system for implementing the generation of a transaction according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, 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, or other programmable control apparatus to produce a machine, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.

Accordingly, the techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system. In the context of this disclosure, a computer-readable storage medium may be any medium that can contain, store, communicate, propagate, or transport the instructions. For example, a computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the computer-readable storage medium include: magnetic storage devices, such as magnetic tape or Hard Disk Drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or wired/wireless communication links.

Embodiments of the present disclosure provide a transaction method performed by a target institution, comprising: receiving a transaction request from a third-party mechanism, wherein the third-party mechanism comprises a third-party client, the transaction request is generated by a current user through transaction of the third-party client, and the transaction request comprises client type information of the third-party client. Then, based on the transaction request, a first request is sent to the third-party organization, the first request is used for obtaining a first user identifier of the current user in the third-party organization, and feedback information generated by the third-party organization in response to the first request is received, and the feedback information comprises the first user identifier. Next, it is determined whether the current user has a second user identification in the target institution to obtain a determination result based on the client type information and the first user identification, the second user identification being associated with the client type information and the first user identification, and a payment operation is performed for the transaction request based on the determination result.

Fig. 1 schematically shows a system architecture of a transaction method and a transaction apparatus according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, a system architecture 100 according to this embodiment may include a target institution 110, a third party institution 120, a terminal device 130, and a network 140.

According to an embodiment of the present disclosure, target institution 110 is, for example, a banking institution. The target institution 110 may include a server for processing data.

According to an embodiment of the present disclosure, a server for processing data may be included in the third party authority 120.

The server in the target institution 110 or the three-party institution 120 may be a server providing various services, such as a background management server (for example only) providing support for a website browsed by a current user using the terminal device 130. The backend management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a web page, information, or data obtained or generated according to the user request) to the terminal device 130.

The terminal device 130 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The network 140 is a medium for providing communication links between the target institution 110, the third party institution 120, and the terminal device 130 to each other. Network 140 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

For example, the terminal device 130 may install a bank client of the target institution 110 and a third party client of the third party institution 120. The current user generates a transaction request by conducting a transaction through a third party client using the terminal device 130. The target institution 110 then receives the transaction request from the third-party institution 120, and based on the transaction request, sends a first request to the third-party institution 120, where the first request is used to obtain a first user identifier of the current user at the third-party institution. The target institution 110 receives feedback information from the third-party institution 120 generated in response to the first request, the feedback information including the first subscriber identity. Then, the target institution 110 determines whether the current user has a second user identification in the target institution based on the client type information and the first user identification to obtain a determination result, and performs a payment operation for the transaction request based on the determination result.

It should be noted that the transaction method provided by the embodiment of the present disclosure may be generally executed by the target institution 110. Accordingly, the transaction devices provided by embodiments of the present disclosure may be generally located in the target institution 110.

It should be understood that the number of target entities, third party entities, terminal devices and networks in fig. 1 is merely illustrative. There may be any number of target entities, third party entities, terminal devices and networks, as desired for implementation.

A transaction method performed by a target institution according to an exemplary embodiment of the present disclosure is described below with reference to fig. 2 to 5 in conjunction with the system architecture of fig. 1. It should be noted that the above-described system architecture is shown merely for the purpose of facilitating understanding of the spirit and principles of the present disclosure, and embodiments of the present disclosure are not limited in any way in this respect.

Fig. 2 schematically illustrates a flow chart of a transaction method performed by a target institution in accordance with an embodiment of the present disclosure.

As shown in fig. 2, the transaction method of the embodiments of the present disclosure may be performed by a target institution, which may be, for example, a banking institution. The method may include, for example, the following operations S210 to S250.

In operation S210, a transaction request from a third party organization is received, where the third party organization includes a third party client, the transaction request is generated by a current user performing a transaction through the third party client, and the transaction request includes client type information of the third party client.

According to the embodiment of the disclosure, the third-party organization can be WeChat, Payment treasure and the like, and the third-party organization can comprise a third-party server and a third-party client.

The third-party client can be, for example, a WeChat application program and a Payment application program for code scanning payment. The target institution may provide the merchant with a collection two-dimensional code, which may include, for example, a URL address, merchant information, order information, etc., and merchant information, which may include, for example, a merchant number, a merchant name, etc., for example. The current user can use the third-party client to scan the two-dimensional code to generate a transaction request, and then the third-party organization sends the transaction request to the target organization through the URL address. The transaction request comprises client type information and two-dimensional code collection information of a third-party client, wherein the client type information represents the type of the client, the type of the client comprises the type of an application program, and the type of the application program comprises WeChat and Paibao.

In the disclosed embodiment, the target institution may include a bank server and a bank client. Wherein the transaction request may be received by a banking server.

In operation S220, a first request is sent to the third-party organization based on the transaction request, wherein the first request is used for obtaining a first user identifier of the current user in the third-party organization.

According to the embodiment of the disclosure, after the bank server receives the transaction request, whether the client type information is the preset client type information can be determined. For example, a white list table is stored in the bank server, and the white list table includes a plurality of preset client types. The target institution supports, for example, a transaction request initiated by a client corresponding to a preset client type. The preset client type may include, for example, a WeChat application, a Payment application, and the like.

Then, if the client type information is determined to be the preset client type information, a first request can be sent to the third-party organization so as to request to acquire a first user identifier of the current user in the third-party organization. For example, the banking server may send the first request to a third party server. Wherein the first user identification can be used to uniquely characterize the identity of the current user in the third party authority.

In another embodiment, the transaction request may include the receipt two-dimensional code information, and the receipt two-dimensional code includes the merchant information. Therefore, if it is determined that the client type information is the preset client type information, it may be further determined whether merchant information in the transaction request is preset merchant information. If the merchant information in the transaction request is preset merchant information, the first request can be sent to a third party organization.

In operation S230, feedback information generated from the third party authority in response to the first request is received, wherein the feedback information includes the first user identification.

According to the embodiment of the disclosure, after the third-party server in the third-party organization receives the first request, the third-party server can check whether the target organization has the authority to acquire the first user identifier. And if the verification result indicates that the target mechanism has the authority of acquiring the first user identifier, the third-party server can respond to the first request to generate feedback information and send the feedback information to the target mechanism. The feedback information may include a first user identifier.

In operation S240, it is determined whether the current user has a second user id in the target institution to obtain a determination result based on the client type information and the first user id, wherein the second user id is associated with the client type information and the first user id.

According to the embodiment of the disclosure, the target institution may store the related information of a plurality of historical users in the historical transaction process into a "binding table", which includes, for example, the binding relationship between "client type information and a first user identifier" and "a second user identifier" of each historical user. The second user identification is, for example, a bank client number of each historical user in the target institution, and the bank client number is used for uniquely representing the identity of each historical user in the target institution. If the target entity has previously processed the transaction information of the current user, the target entity stores the relevant information of the current user in the "binding table" of the target entity, for example.

In the embodiment of the present disclosure, the "binding table" may be "searched" based on the "client type information and the first user identifier of the current user, so as to determine whether the" binding table "has the" second user identifier "of the current user, and obtain a determination result.

Next, in operation S250, a payment operation is performed for the transaction request based on the determination result.

In an embodiment, when the determination result indicates that the current user has the second user identifier in the target institution, the order interface information may be sent to the third party institution so as to send the payment request to the target institution based on the order interface corresponding to the order interface information. For example, the banking server may send an order interface address to the third party client, and the third party client may access the order interface through the address information. The order interface includes, for example, order information, which may include information about the receiving merchant, payment amount information, and the like. The current user may confirm the order information in the order interface and select or enter a payment account in the order interface. Then, the third-party institution generates a payment request based on the order information and the payment account number, and transmits the payment request to the target institution so as to request the target institution to execute the payment.

In another embodiment, when the determination result indicates that the current user does not have the second user identifier in the target institution, the login interface information is sent to the third party institution so as to log in the server of the target institution based on the login interface corresponding to the login interface information. For example, the bank server sends a login interface address to the third-party client, and the third-party client can access the login interface through the address information.

The current user may then log into the target facility through a login interface. The bank server can receive a login request sent by a current user through a login interface, and sends order interface information to the third-party organization in response to the login request, so that a payment request is sent to the target organization based on an order interface corresponding to the order interface information. Next, the target institution may perform a payment operation based on the payment request. A process of receiving a login request sent by a current user through a login interface and sending order interface information to a third party authority in response to the login request will be described below.

Therefore, according to the technical scheme of the embodiment of the disclosure, when a bank processes a transaction, order interface information or login interface information can be fed back through the association relationship among the client type information, the first user identifier and the second user identifier. When the bank stores the association relationship among the client type information, the first user identification and the second user identification, the order interface information can be directly returned, and the current user does not need to log in the bank server again, so that the transaction efficiency is improved. In addition, by the technical scheme of the embodiment of the disclosure, no matter what kind of third-party client side is selected by the current user for code scanning payment, payment can be carried out through the bank account of the current user, and unified management of payment modes is realized.

According to the embodiment of the disclosure, after the determination result indicates that the current user does not have the second user identifier in the target institution and the payment operation is performed, a new second user identifier is generated. For example, if the second user identifier of the current user is not in the "binding table", the new second user identifier of the current user may be generated after the payment operation (the deduction from the user account is successful).

And then, the newly added second user identification is stored in a correlation mode with the client type information and the first user identification. For example, "client type information and first and second user identifications" are bound and stored into a "binding table" of the target authority. The second user id of the current user may be found from the "binding table" when the transaction request of the current user is processed later.

According to an embodiment of the present disclosure, after the determination result characterizes that the current user has the second user identity in the target institution and after performing the payment operation, the current second user identity associated with the payment request may be determined. For example, if the "binding table" has a second user identifier corresponding to the "client type information and first user identifier" of the current user, the current second user identifier in the current payment request may be determined after the payment operation (successful deduction from the user account) is performed. The current second user identifier may be a payment account, and the current second user identifier in the payment request may be, for example, the payment account of the payment.

If the second user identifier stored in the "binding table" is not consistent with the current second user identifier of the current payment, the association relationship stored in the target mechanism may be deleted, where the association relationship includes a first association relationship having the client type information and the first user identifier and a second association relationship having the current second user identifier.

For example, if "client type information and first user identifier" of the transaction is information of user a, "second user identifier" associated with "client type information and first user identifier" in the "binding table" is an identifier of user a. And if the current second user identification associated with the transaction request is the identification of the user B, the second user identification is inconsistent with the current second user identification. In this case, it may be indicated that user B initiates a transaction based on "client type information and first user identity" of user a and initiates a payment request with its own (user B) current second user identity (payment account).

If the second user identifier stored in the "binding table" is not consistent with the current second user identifier of the current payment, which may indicate that the current payment security is poor, the relevant information about the user a and the user B in the "binding table" may be deleted. For example, the first and second associations are deleted. Hereinafter, "client type information a", "first user identifier a", and "second user identifier a" represent information of the user a. The "client type information B", "first user identification B", and "current second user identification B" represent information of the user B.

For the user a, the first association relationship is, for example, "second user identifier a" associated with "client type information a and first user identifier a" in the "binding table". The client type information a and the first user identity a and the second user identity a are deleted.

For the user B, the second association relationship is, for example, "client type information B and first user identifier B" associated with "current second user identifier B" in the "binding table. The "current second user identification B" and the "client type information B and first user identification B" are deleted.

If the second user identifier stored in the "binding table" is consistent with the current second user identifier paid this time, the association relation of the current user in the "binding table" may not be operated, that is, no adding or deleting operation is performed.

To facilitate an understanding of the embodiment depicted in fig. 2, the interaction of various entities in performing the transaction method of an embodiment of the present disclosure is described below with reference to fig. 3.

Fig. 3 schematically shows an interaction flow diagram of a transaction method according to an embodiment of the present disclosure.

As shown in fig. 3, the transaction method of the disclosed embodiments involves, for example, interaction of a target institution and a third party institution. The target institution includes, for example, a bank server and a bank client, and the third party institution includes, for example, a third party server and a third party client. The method may include, for example, the following operations S301 to S310.

In operation S301, the bank provides a two-dimensional code for collection to the merchant. In the process of transaction between the merchant and the current user, the merchant displays the collection two-dimensional code for the current user. The current user scans the received two-dimensional code through a third party client (e.g., a WeChat application). The two-dimensional code for collection can be a string of URL addresses. After the current user uses the third-party client to scan the two-dimensional code to be collected, the client type (such as WeChat) and the two-dimensional code information can be sent to the bank server through the URL address.

In operation S302, after receiving the client type and the two-dimensional code information sent by the third-party client, the banking server may check whether the client type is in a white list table supported by the banking server, where the white list table maintains, for example, the client type supported by the bank. And then, the bank service side extracts the merchant information from the two-dimensional code information, compares the extracted merchant information with the merchant information stored in the bank service side, and verifies whether the merchant information is consistent and the merchant state is normal.

In operation S303, after operation S302 checks that the client type is in the white list table and the merchant information passes the verification, the banking server, for example, as an access party, reversely initiates an application to the third-party service terminal to request to obtain a third-party user identifier (the first user identifier described in the embodiment of fig. 2) of the current user. The addresses of the multiple different third-party servers are configured in the configuration file of the bank server in advance, for example, and the bank server can initiate an application to the corresponding third-party server based on the addresses in the configuration file.

In operation S304, after the third party service receives the application, the authority of the access party is verified, and the third party user identifier is returned to the bank service after the verification is successful.

In operation S305, after receiving the third party user identifier, the banking server queries a banking client number (a second user identifier described in the embodiment of fig. 2) in a "binding table" stored in the banking server according to the "client type and the third party user identifier". The binding table is, for example, a two-dimensional table in a database of a bank server, and the two-dimensional table contains three fields of a client type, a third-party user identifier, and a bank client number. Then, different processing is carried out according to the query result, and the specific processing rule is as follows:

if the corresponding bank client number is not inquired in the binding table according to the client type and the third party user identification, the bank server returns the h5 address corresponding to the bank client login page to the third party client, and the login interface can be accessed by accessing the h5 address.

If the corresponding bank client number is found in the binding table according to the client type and the third-party user identification, the bank server returns the h5 address corresponding to the order page to the third-party client, and the order page can be accessed by accessing the h5 address.

In operation S306, the third party client receives the h5 address returned by the banking server, and accesses the h5 address through a browser built in the third party client.

In operation S307, if the accessed address is the address of the login interface of the bank client, the bank client displays a login page for the current user, and the current user enters the order page after inputting the mobile phone number and the verification code on the login page. If the accessed address is the address of the order page, the bank client can directly display the order page for the current user.

In operation S308, the current user confirms order information (including information of the receiving merchant and payment amount) on an order page displayed at the bank client and selects a payment card number, and inputs a static payment password reserved in the bank to initiate a payment request to the bank server.

In operation S309, after receiving the payment request, the bank server adds a new piece of order information in the "order table" of the database, where the new piece of order information includes fields such as an order ID (main key), an order generation time, a payment client type, a third party user identifier, a merchant number, a merchant name, an order amount, a payment card number, an order completion time, and an order status. And after the order is successfully added, the bank server deducts money according to the payment card number selected by the current user and carries out settlement and account entry to the merchant. After the deduction and the check-in are successful, the information (the name of a merchant, an order number, the amount of an order and a payment card number) of successful payment is returned to the bank client, meanwhile, a binding table is checked, the client type and the third-party user identification which are successful in the payment and the bank client number are respectively inquired in the binding table, and the following processing is carried out according to the inquiry result:

if the records of the client type, the third party user identifier and the bank client number are not inquired, the client type, the third party user identifier and the bank client number which are successful in the payment can be inserted into a binding table as one record, and the binding relationship between the client type, the third party user identifier and the bank client number is established.

If the records of the client type, the third-party user identification and the bank client number are inquired and the binding relations are consistent, no operation is performed.

If the records of the client type, the third party user identifier and the bank client number are inquired and bound with other accounts respectively, the records corresponding to the client type and the third party user identifier can be deleted from the binding table, and meanwhile, the records corresponding to the bank client number are deleted from the binding table.

In operation S310, after receiving the payment success notification returned by the bank server, the bank client displays a page with successful payment to the current user, where the page displays information such as a merchant name, an order number, an order amount, and a payment card number, thereby completing payment.

According to the embodiment of the disclosure, the transaction request further includes a merchant account, and the payment request includes a user account of the current user. Wherein, the performing of the payment operation for the transaction request in the operation S250 may include: based on the account information, transaction resources are obtained from the user account and sent to the merchant account based on the merchant information, the transaction resources including, for example, funds that satisfy the current transaction amount. Namely, after deduction from the user account, the deducted money can be sent to the merchant account in time, and the clearing speed is improved due to fewer mechanisms involved in the clearing process, so that the speed of entering account of the merchant is improved. In addition, the clearance process involves fewer mechanisms, so that the occupation of server resources during clearance is reduced, and the server resources are saved.

To facilitate an understanding of the withholding and posting process of embodiments of the present disclosure, the withholding and posting process is described below with reference to fig. 4.

FIG. 4 schematically shows a flow chart of deduction and posting according to an embodiment of the disclosure. The process of deduction and posting may include the following operations S401 to S407, for example.

Besides the bank server and the bank client, the banking institution also includes, for example, an internal payment system, an internal account system, and an internal bank account.

In operation S401, after the bank server inserts the new order into the order table, the bank server sends the order id, the order amount, and the user payment card number to the internal payment system, and initiates a user payment application instruction to the internal payment system.

In operation S402, the internal payment system obtains the user payment card number and the order amount from the application instruction, and initiates an account entry application to the internal account system. And after receiving the account entry application, the internal account system judges that the user payment card number is normal, completes account deduction corresponding to the user payment card number according to the amount of the order (the internal payment system is informed of the successful deduction), and increases the related amount in the internal bank user.

In operation S403, after the bank server obtains a payment success notification from the internal payment system, the state of the order is updated to "paid" in the order table, and the bank client is notified that the payment is successful.

In operation S404, the bank server background obtains the order id, the order amount, and the merchant number of the transaction from the local order table, and sends the order id, the order amount, and the merchant number to the internal payment system, and initiates a merchant posting application instruction to the internal payment system.

In operation S405, the internal payment system obtains a merchant rate and a merchant account from the merchant file according to the merchant number in the instruction, and calculates a merchant transaction fee, where "fee amount" is "order amount" and "merchant rate" and "merchant net income" is "order amount — fee amount".

In operation S406, the internal payment system initiates a merchant posting application to the internal account system according to the obtained merchant net income and the merchant posting account.

In operation S407, after the internal account system receives the request for posting, it determines that the merchant posting account is normal, and according to the net income of the merchant, reduces the corresponding amount of money from the internal account of the bank, and posts the net income amount of the merchant to the merchant posting account, thereby increasing the posting speed of the merchant.

According to the embodiment of the disclosure, when the determination result in operation S250 indicates that the current user does not have the second user identifier in the target institution, the bank server may send the login interface address to the third party institution. Then, the current user can log in the target mechanism through the login interface, and the bank server can receive the login request sent by the current user through the login interface and send order interface information to the third-party mechanism in response to the login request.

In particular, the login request comprises a communication identification of the current user. The communication identifier is, for example, the mobile phone number of the current user.

Receiving a login request sent by a current user through a login interface includes, for example: the banking server may store the communication identifier to the target institution (banking server) as a reference communication identifier, which is used, for example, as a basis for subsequent verification.

The bank server can then generate a verification code based on the communication identification. For example, the bank server may verify whether the communication identifier is used to open a static password payment authority at a bank, and if the communication identifier is used to open the static password payment authority, the bank server may generate a verification code. Static passwords are, for example, a way for banks to verify the identity of users during micropayment.

The banking server may then store the passcode to the target institution as a reference passcode, for example as a basis for subsequent verification.

The bank server can generate a short message number besides the verification code. Then, the bank server can send the verification code to the mobile phone number of the current user through the communication operator in the form of short message. The bank server can send the short message number to the bank client and display the short message number on the front desk of the bank client, so that a current user can find the short message with the verification code based on the short message number.

And next, the bank server receives a login request sent by the current user based on the verification code. For example, the authentication code in the login request is the current authentication code input by the current user through the login interface, and the login request further includes the current communication identifier (current mobile phone number) when the current user initiates the login request.

According to an embodiment of the present disclosure, sending order interface information to a third party authority in response to a login request includes: and comparing the current verification code with the reference verification code to obtain a first comparison result, comparing the current communication identifier with the reference communication identifier to obtain a second comparison result, and sending order interface information to a third-party organization based on the first comparison result and the second comparison result.

For example, if the first comparison result indicates that the current verification code and the reference verification code are consistent, and the second comparison result indicates that the current communication identifier and the reference communication identifier are consistent, the order interface address may be returned to the third party client so that the current user sends a payment request to the target institution through the order interface.

According to the embodiment of the disclosure, the bank server sends the login interface address to the third-party organization, the current user logs in the target organization through the login interface, the bank server can receive the login request sent by the current user through the login interface, and the specific process of sending the order interface to the third-party organization in response to the login request can be realized by interaction between the bank server and the bank client.

In order to facilitate understanding of the login request sent by the user through the login interface, the bank server responds to the login request and sends order interface information to the third-party organization. The process of the bank server responding to the login request will be described below with reference to fig. 5.

Fig. 5 schematically shows a flow chart for responding to a login request according to an embodiment of the present disclosure. The process of the bank server responding to the login request includes the following operations S501 to S506, for example.

In operation S501, the current user inputs a payment mobile phone number reserved in the bank on the login page of the bank client, triggers an operation of "obtaining a short message verification code", and initiates a request for obtaining the short message verification code to the bank server.

In operation S502, after the bank service end receives the request, it is determined whether the payment mobile phone number sent from the client has opened the static password payment permission in the bank.

In operation S503, after the bank service determines that the payment authority of the payment mobile phone number has been opened, a short message number and a random dynamic verification code are correspondingly generated and stored for the mobile phone number, and then the bank service returns the short message number to the bank client, and sends the random dynamic verification code to the payment mobile phone number of the current user in a short message form through the communication operator.

In operation S504, the bank client receives the short message number and displays the short message number on the foreground, and the bank client obtains the short message verification code from the short message and inputs the short message verification code to the login page, and sends the payment mobile phone number and the short message verification code to the bank server to initiate a login request.

In operation S505, after receiving the payment mobile phone number and the short message verification code sent by the bank client, the bank server determines whether the payment mobile phone number and the short message verification code are consistent with those stored in the bank server.

In operation S506, if it is determined in operation S505 to be consistent, the banking server returns the h5 address of the order page to the third party server, so as to access the order interface based on the h5 address of the order page.

Another embodiment of the present disclosure also provides a computing device, for example, comprising one or more processors and memory. Wherein the memory is used to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the methods shown in fig. 2-5.

Fig. 6 schematically shows a block diagram of a transaction device according to an embodiment of the present disclosure.

As shown in fig. 6, the transaction apparatus 600 may include, for example, a first receiving module 610, a first transmitting module 620, a second receiving module 630, a first determining module 640, and a first payment module 650.

The first receiving module 610 may be configured to receive a transaction request from a third-party organization, where the third-party organization includes a third-party client, the transaction request is generated by a current user performing a transaction through the third-party client, and the transaction request includes client type information of the third-party client. According to the embodiment of the present disclosure, the first receiving module 610 may, for example, perform operation S210 described above with reference to fig. 2, which is not described herein again.

The first sending module 620 may be configured to send a first request to the third-party organization based on the transaction request, where the first request is used to obtain a first user identifier of the current user at the third-party organization. According to the embodiment of the present disclosure, the first sending module 620 may, for example, perform operation S220 described above with reference to fig. 2, which is not described herein again.

The second receiving module 630 may be configured to receive feedback information generated from a third party authority in response to the first request, where the feedback information includes the first subscriber identity. According to the embodiment of the present disclosure, the second receiving module 630 may, for example, perform operation S230 described above with reference to fig. 2, which is not described herein again.

The first determination module 640 may be configured to determine whether the current user has a second user identifier in the target institution based on the client type information and the first user identifier to obtain a determination result, where the second user identifier is associated with the client type information and the first user identifier. According to the embodiment of the present disclosure, the first determining module 640 may perform, for example, the operation S240 described above with reference to fig. 2, which is not described herein again.

The first payment module 650 may be configured to perform a payment operation for the transaction request based on the determination. According to the embodiment of the present disclosure, the first payment module 650 may, for example, perform operation S250 described above with reference to fig. 2, which is not described herein again.

According to an embodiment of the present disclosure, performing a payment operation for the transaction request based on the determination result includes: and when the determination result indicates that the current user does not have the second user identifier in the target mechanism, sending login interface information to the third-party mechanism so as to log in a server of the target mechanism based on the login interface corresponding to the login interface information.

According to an embodiment of the present disclosure, the apparatus further comprises: the system comprises a third receiving module, a second sending module and a second payment module. And the third receiving module is used for receiving a login request sent by a current user through a login interface. And the second sending module is used for responding to the login request, sending the order interface information to the third-party mechanism so as to send the payment request to the target mechanism based on the order interface corresponding to the order interface information. And the second payment module executes payment operation based on the payment request.

According to an embodiment of the present disclosure, the apparatus further comprises: the device comprises a generation module and a storage module. And the generating module generates a new second user identifier after the determination result indicates that the current user does not have the second user identifier in the target mechanism and the payment operation is executed. And the storage module is used for storing the newly added second user identifier, the client type information and the first user identifier in an associated manner.

According to an embodiment of the present disclosure, the apparatus further comprises: a second determining module and a deleting module. Wherein the second determination module determines the current second user identity associated with the payment request after the determination result characterizes that the current user has the second user identity in the target institution and after the payment operation is performed. And the deleting module is used for deleting the association relation stored in the target mechanism in response to the inconsistency between the second user identification and the current second user identification, wherein the association relation comprises a first association relation with the client type information and the first user identification and a second association relation with the current second user identification.

According to an embodiment of the present disclosure, sending the first request to the third party authority based on the transaction request includes: determining whether the client type information is preset client type information or not based on the transaction request, and sending a first request to a third-party organization in response to determining that the client type information is the preset client type information.

According to an embodiment of the present disclosure, the transaction request further includes a merchant account, and the payment request includes a user account of the current user. Wherein performing payment operations for the transaction request comprises: and acquiring the transaction resources from the user account based on the account information, and sending the transaction resources to the merchant account based on the merchant information.

According to an embodiment of the present disclosure, the login request includes a communication identification of the current user. The method for receiving the login request sent by the current user through the login interface comprises the following steps: the communication identification is stored to a target mechanism to serve as a reference communication identification, a verification code is generated based on the communication identification, the verification code is stored to the target mechanism to serve as a reference verification code, the verification code is sent to a current user through a communication operator, and a login request sent by the current user based on the verification code is received.

According to the embodiment of the disclosure, the login request further includes a current authentication code input by the current user through the login interface and a current communication identifier when the current user initiates the login request. Wherein, responding to the login request, sending order interface information to the third-party organization comprises: and comparing the current verification code with the reference verification code to obtain a first comparison result, comparing the current communication identifier with the reference communication identifier to obtain a second comparison result, and sending order interface information to a third-party organization based on the first comparison result and the second comparison result.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any plurality of the first receiving module 610, the first sending module 620, the second receiving module 630, the first determining module 640, and the first payment module 650 may be combined in one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first receiving module 610, the first sending module 620, the second receiving module 630, the first determining module 640, and the first paying module 650 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or by a suitable combination of any several of them. Alternatively, at least one of the first receiving module 610, the first transmitting module 620, the second receiving module 630, the first determining module 640, and the first payment module 650 may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.

FIG. 7 schematically illustrates a block diagram of a computer system for implementing the generation of a transaction according to an embodiment of the disclosure. The computer system illustrated in FIG. 7 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.

As shown in fig. 7, computer system 700 includes a processor 701, a computer-readable storage medium 702. The system 700 may perform a method according to an embodiment of the present disclosure.

In particular, the processor 701 may include, for example, a general purpose microprocessor, an instruction set processor and/or related chip set and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), and/or the like. The processor 701 may also include on-board memory for caching purposes. The processor 701 may be a single processing unit or a plurality of processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

Computer-readable storage medium 702 may be, for example, any medium that can contain, store, communicate, propagate, or transport the instructions. For example, a readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the readable storage medium include: magnetic storage devices, such as magnetic tape or Hard Disk Drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or wired/wireless communication links.

The computer-readable storage medium 702 may comprise a computer program 703, which computer program 703 may comprise code/computer-executable instructions that, when executed by the processor 701, cause the processor 701 to perform a method according to an embodiment of the disclosure, or any variant thereof.

The computer program 703 may be configured with, for example, computer program code comprising computer program modules. For example, in an example embodiment, code in computer program 703 may include one or more program modules, including for example 703A, modules 703B, … …. It should be noted that the division and number of the modules are not fixed, and those skilled in the art may use suitable program modules or program module combinations according to actual situations, so that the processor 701 may execute the method according to the embodiment of the present disclosure or any variation thereof when the program modules are executed by the processor 701.

According to an embodiment of the present disclosure, at least one of the first receiving module 610, the first transmitting module 620, the second receiving module 630, the first determining module 640, and the first payment module 650 may be implemented as a computer program module described with reference to fig. 7, which, when executed by the processor 701, may implement the respective operations described above.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method.

According to embodiments of the present disclosure, a computer-readable storage medium may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination 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 present disclosure, 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 contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable storage 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 storage medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, optical fiber cable, radio frequency signals, etc., or any suitable combination of the foregoing.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

While the disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.

Claims

1. A transaction method performed by a target institution, comprising:

receiving a transaction request from a third-party organization, wherein the third-party organization comprises a third-party client, the transaction request is generated by a current user performing transaction through the third-party client, and the transaction request comprises client type information of the third-party client;

sending a first request to the third-party institution based on the transaction request, wherein the first request is used for acquiring a first user identifier of the current user in the third-party institution;

receiving feedback information generated by the third-party organization in response to the first request, wherein the feedback information comprises the first user identification;

determining whether the current user has a second user identifier in the target mechanism based on the client type information and the first user identifier to obtain a determination result, wherein the second user identifier is associated with the client type information and the first user identifier; and

performing a payment operation for the transaction request based on the determination result.

2. The method of claim 1, wherein the performing a payment operation for the transaction request based on the determination comprises:

when the determined result represents that the current user has the second user identifier in the target mechanism, sending order interface information to the third-party mechanism so as to send a payment request to the target mechanism based on an order interface corresponding to the order interface information; and

and when the determined result indicates that the current user does not have the second user identifier in the target mechanism, sending login interface information to the third-party mechanism so as to log in a server of the target mechanism based on a login interface corresponding to the login interface information.

3. The method of claim 2, further comprising:

receiving a login request sent by the current user through the login interface;

responding to the login request, sending the order interface information to the third-party organization so as to send a payment request to the target organization based on an order interface corresponding to the order interface information; and

and executing the payment operation based on the payment request.

4. The method of claim 3, further comprising:

generating a new second user identifier after the determination result indicates that the current user does not have the second user identifier in the target mechanism and the payment operation is executed; and

and performing associated storage on the newly added second user identification, the client type information and the first user identification.

5. The method of claim 2, further comprising:

determining a current second user identification associated with the payment request after the determination result characterizes that the current user has a second user identification in the target institution and after performing the payment operation; and

and deleting the association relation stored in the target mechanism in response to the inconsistency between the second user identification and the current second user identification, wherein the association relation comprises a first association relation with the client type information and the first user identification and a second association relation with the current second user identification.

6. The method of claim 1, wherein said sending a first request to the third party authority based on the transaction request comprises:

determining whether the client type information is preset client type information or not based on the transaction request; and

and sending the first request to the third-party mechanism in response to the fact that the client type information is determined to be preset client type information.

7. The method of claim 2, wherein the transaction request further includes a merchant account, the payment request including a user account of the current user;

wherein the performing payment operations for the transaction request comprises:

acquiring transaction resources from the user account based on the account information; and

based on the merchant information, sending the transaction resource to the merchant account.

8. The method of claim 3, wherein the login request includes a communication identification of the current user;

wherein the receiving of the login request sent by the current user through the login interface includes:

storing the communication identifier to the target institution as a reference communication identifier;

generating a verification code based on the communication identification, and storing the verification code to the target institution as a reference verification code;

sending the verification code to the current user through a communication operator; and

and receiving a login request sent by the current user based on the verification code.

9. The method of claim 8, wherein the login request further comprises a current authentication code entered by the current user through a login interface and a current communication identifier when the current user initiates the login request;

wherein said sending order interface information to said third party authority in response to said login request comprises:

comparing the current verification code with the reference verification code to obtain a first comparison result;

comparing the current communication identifier with the reference communication identifier to obtain a second comparison result; and

and sending the order interface information to the third-party institution based on the first comparison result and the second comparison result.

10. A transaction device, comprising:

the system comprises a first receiving module, a second receiving module and a third-party organization, wherein the first receiving module receives a transaction request from the third-party organization, the third-party organization comprises a third-party client, the transaction request is generated by a current user through transaction of the third-party client, and the transaction request comprises client type information of the third-party client;

the first sending module is used for sending a first request to the third-party mechanism based on the transaction request, wherein the first request is used for acquiring a first user identifier of the current user in the third-party mechanism;

a second receiving module, configured to receive feedback information generated by the third-party organization in response to the first request, where the feedback information includes the first user identifier;

a first determination module, configured to determine, based on the client type information and the first user identifier, whether the current user has a second user identifier in the target organization to obtain a determination result, where the second user identifier is associated with the client type information and the first user identifier; and

a first payment module to perform a payment operation for the transaction request based on the determination result.

11. A computing device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.

12. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 9.