CN111815446A - Electronic transaction method, system and storage medium - Google Patents

Electronic transaction method, system and storage medium Download PDF

Info

Publication number
CN111815446A
CN111815446A CN202010640823.6A CN202010640823A CN111815446A CN 111815446 A CN111815446 A CN 111815446A CN 202010640823 A CN202010640823 A CN 202010640823A CN 111815446 A CN111815446 A CN 111815446A
Authority
CN
China
Prior art keywords
client
service
authorization
information
state
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
Application number
CN202010640823.6A
Other languages
Chinese (zh)
Inventor
李帅
张强
季纯杰
李碧野
刘翊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Taikang Insurance Group Co Ltd
Taikang Online Property Insurance Co Ltd
Original Assignee
Taikang Insurance Group Co Ltd
Taikang Online Property Insurance Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Taikang Insurance Group Co Ltd, Taikang Online Property Insurance Co Ltd filed Critical Taikang Insurance Group Co Ltd
Priority to CN202010640823.6A priority Critical patent/CN111815446A/en
Publication of CN111815446A publication Critical patent/CN111815446A/en
Priority to CN202110244037.9A priority patent/CN112819635B/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G06Q20/40145—Biometric identity checks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Abstract

The present disclosure relates to the field of network communication technologies, and in particular, to a method, a system, and a storage medium for electronic transaction. An electronic transaction method includes obtaining identity information of a customer; inquiring the authorization state of the client according to the identity information of the client; if the authorization state is a first state, performing a first electronic transaction with a third-party platform according to transaction information matched with the first state; if the authorization state is a second state, performing second electronic transaction with a third-party platform according to transaction information matched with the second state; and if the authorization state is a third state, performing third electronic transaction with a third-party platform according to the transaction information matched with the third state. By using the embodiment of the invention, the transaction information matched with the authorization state can be organized according to the authorization state of the client to carry out corresponding electronic transaction.

Description

Electronic transaction method, system and storage medium
Technical Field
The present disclosure relates to the field of network communication technologies, and in particular, to a method, a system, and a storage medium for electronic transaction.
Background
In the existing insurance payment service, the process of purchasing insurance payment by a customer is complicated, complete insurance information needs to be input each time, for example, the information needing to be input includes information such as name, sex, occupation, home address and the like, and a payment page needs to be popped up during payment, and a password, an authentication code, biological identification information and the like are input for payment. Therefore, in the prior art, the application is authorized by the client, so that the problem that the electronic transaction can be carried out only by repeatedly inputting client information is solved. However, when the authorization of the client is cancelled, the electronic transaction cannot be automatically completed. This is a problem that needs to be solved in the prior art.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present disclosure provide an electronic transaction method, system, and storage medium, which are used to solve the problem in the prior art that an electronic transaction cannot be automatically completed after a user cancels authorization.
There is provided a method of electronic transaction comprising,
acquiring identity information of a client and service information of the client;
sending a query request at least comprising the identity information of the client and the service information to the third-party platform so that the third-party platform matches the identity information of the client and the service information to obtain the authorization state of the client for the service; receiving the authorization state fed back by the third-party platform;
if the authorization state is a first state, performing a first electronic transaction with a third-party platform according to transaction information matched with the first state;
if the authorization state is a second state, performing second electronic transaction with a third-party platform according to transaction information matched with the second state;
and if the authorization state is a third state, performing third electronic transaction with a third-party platform according to the transaction information matched with the third state.
There is also provided an electronic trading system, comprising,
the client identity information acquisition unit is used for acquiring the identity information of the client;
a service information obtaining unit, configured to obtain service information of the client;
the query unit is used for sending a query request at least comprising the identity information of the client and the service information to a third-party platform so as to enable the third-party platform to match the identity information of the client and the service information to obtain the authorization state of the client for the service;
the receiving unit is used for receiving the authorization state fed back by the third-party platform;
the first processing unit is used for carrying out first electronic transaction with a third-party platform according to the transaction information matched with the first state if the authorization state is the first state;
the second processing unit is used for carrying out second electronic transaction with a third-party platform according to the transaction information matched with the second state if the authorization state is the second state;
and the third processing unit is used for carrying out third electronic transaction with a third-party platform according to the transaction information matched with the third state if the authorization state is the third state.
Embodiments herein also provide a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the above-mentioned method when executing the computer program.
Embodiments herein also provide a computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, implement the above-described method.
By utilizing the embodiment, the transaction information matched with the authorization state can be organized according to the authorization state of the client to carry out corresponding electronic transaction, the condition that the electronic transaction cannot be carried out due to the change of the authorization state is avoided, the execution efficiency of the electronic transaction is enhanced, the complicated operation of the client is avoided, the time of the client is saved, and the use experience of the client is improved.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram illustrating an overall structure of an electronic trading system according to an embodiment of the present disclosure;
FIG. 2 is a flow chart illustrating a method of electronic trading, according to an embodiment of the present disclosure;
FIG. 3 is a schematic structural diagram of an electronic transaction system according to an embodiment of the present disclosure;
FIG. 4 is a detailed diagram of the structure of the electronic trading system according to an embodiment of the present disclosure;
FIG. 5 is a data flow diagram illustrating querying of a client authorization status according to an embodiment herein;
fig. 6 is a data flow diagram illustrating a first authorization state according to an embodiment herein;
fig. 7 is a data flow diagram illustrating a second authorization state according to an embodiment herein;
fig. 8 is a data flow diagram illustrating a third authorization state according to an embodiment herein;
FIG. 9 is a flow diagram illustrating authorization of a transaction herein;
fig. 10 is a schematic structural diagram of a computing device according to an embodiment herein.
[ description of reference ]:
101. a client;
102. a front-end device;
103. a general purpose device;
104. a core device;
105. a service device;
106. a third party platform;
301. a client identity information acquisition unit;
302. a service information acquisition unit;
303. a query unit;
3031. an identifier acquisition module;
304. a receiving unit;
305. a first processing unit;
3051. a client identity authentication module;
3052. a service verification module;
3053. a first transaction information sending module;
306. a second processing unit;
3061. a client identity authentication module;
3062. a deletion module;
3063. a second transaction information sending module;
307. a third processing unit;
3071. a client identity authentication module;
3072. a third transaction information sending module;
308. an authorization permission acquisition unit;
1002. a computing device;
1004. a processing device;
1006. a storage resource;
1008. a drive mechanism;
1010. an input/output module;
1012. an input device;
1014. an output device;
1016. a presentation device;
1018. a graphical user interface;
1020. a network interface;
1022. a communication link;
1024. a communication bus.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection.
Fig. 1 is a schematic diagram of the overall structure of an electronic transaction system according to an embodiment of the present invention, in this embodiment, the overall structure of the electronic transaction system is described, in which although the electronic transaction system is divided into different main bodies (servers) according to functions, in reality, the functions of one main body may be implemented by several servers, or the functions of multiple main bodies may be integrated into one server, the main bodies may be located in the same geographical location (e.g., a machine room), may be located in different geographical locations for security, and use a dedicated network connection between different main bodies, or connect through the internet and use a tunnel (VPN) technology to communicate, and the electronic transaction system specifically includes multiple clients 101, a front-end device 102, a general-purpose device 103, a core device 104, a business device 105, a third-party platform 106, wherein the front-end device 102, the general device 103, the core device 104, the service device 105 are electronic trading internal systems, and the client 101 and the third party platform 106 all belong to peripheral systems of the electronic trading system, although the division may be determined according to actual requirements, for example, the third party platform 106 may be divided into the front-end device 102, the general device 103, the core device 104, and the service device 105 as part of the electronic trading internal systems.
The client 101 may include an electronic device such as a mobile phone, a notebook computer, a tablet computer, a desktop computer, etc., and a specific application software or a general browser is run on the electronic device, so that the client can be connected with the electronic transaction system in this document through these access modes to perform electronic transactions.
The front-end device 102 may be a web server for client access or an application server for intermediating clients in communicating with other servers in the electronic trading system.
The generic device 103 responds to the request of the client 101 through the front-end device 102, and initiates various customer-specified services to other servers of the electronic trading system.
The core device 104 stores the authorization status of the client, the authorization information, and the transaction information corresponding to the authorization status, and transmits the authorization status of the client and the transaction information corresponding to the authorization status to the general device 103 during the electronic transaction.
The service device 105 communicates with the third party platform 106 to make service requests and responses.
The third party platform 106 is, for example, a third party platform provided by a payer, a WeChat, another bank, and the like, and performs actual fund transfer and the like of the electronic transaction.
Fig. 2 is a flowchart of an electronic transaction method according to an embodiment of the present disclosure, in which an overall method of electronic transaction is described in this embodiment, in the method, a core system queries and stores an authorization state of a client, and determines execution of subsequent steps according to a state category specifically corresponding to the authorization state to complete the electronic transaction, and specifically includes the following steps:
step 201, acquiring identity information of a client and service information of the client;
step 202, sending a query request at least including the identity information of the client and the service information to the third-party platform, so that the third-party platform matches the identity information of the client and the service information to obtain an authorization state of the client for the service; receiving the authorization state fed back by the third-party platform;
step 203, if the authorization state is a first state, performing a first electronic transaction with a third party platform according to the transaction information matched with the first state;
if the authorization state is a second state, performing second electronic transaction with a third-party platform according to transaction information matched with the second state;
and if the authorization state is a third state, performing third electronic transaction with a third-party platform according to the transaction information matched with the third state.
As an aspect of the embodiments herein, the obtaining the identity information of the client further includes obtaining the identity information of the client according to a context of the client.
In this step, the context of the client refers to that when a client operates an electronic device such as a mobile phone, a tablet computer, a desktop computer, a notebook computer, etc., some variables with user identity information are generated in the using process by using software or APP therein, and these variables with specific contents are referred to as contexts.
As another embodiment, identity information of a part of the clients may also be obtained from the context of the client, for example, only a mobile phone number is obtained, and the client identity information with the same mobile phone number may be obtained from the core system through the mobile phone number, for example, information such as an identity card number of the client, a unique identifier of the client on a third party platform, and the like may be obtained.
As an aspect of the embodiments herein, in the sending, a query request including at least the identity information of the client and the service information to a third party platform, so that the third party platform matches the identity information of the client and the service information to obtain an authorization status of the client for the service; in the step of receiving the authorization state fed back by the third-party platform, the front-end device can query the core device according to the identity card number of the client, the unique identifier of the client in the third-party platform, the mobile phone number and the like, find out the corresponding service information of the client, such as the service number of the client, the service time and the like, the core device sends the information to the service device, the service device sends a query request consisting of the information to the third-party platform, the third-party platform queries the database thereof according to the information in the query request, and the authorization state of the client for the service is queried by using the identity information and the service information of the client for matching; and the third-party platform feeds back the authorization state of the client for the service to a service device and a core device, wherein the core device stores the authorization state of the client for the service, so that the client is charged by utilizing the authorization state for the service during automatic renewal.
As an aspect of embodiments herein, sending a query request including at least the customer's identity information and the business information to a third party platform further includes,
acquiring a unique identifier of the client on the third-party platform and a unique identifier corresponding to a service;
and sending a query request at least comprising the unique identifier of the third-party platform and the unique identifier corresponding to the service to the third-party platform.
In this step, the client communicates with the front-end device through the client terminal, and the client terminal generates context information during the communication, and the front-end device can obtain the unique identifier of the client on the third-party platform according to the context information.
When the third-party platform is a bank payment platform, the unique identifier of the third-party platform is a bank account number of the customer in the bank, and when the third-party platform is a payment platform such as a payment treasure or a WeChat, the unique identifier of the third-party platform is an account number of the customer in the platform. Each service has a unique corresponding identifier, which may be, for example, a specific numeric string or an alphanumeric string, and which is available in the head-end, generic, or core device.
After the query request is sent to the third-party platform, the third-party platform queries an authorization information table stored in an internal database thereof according to the unique identifier of the third-party platform in the query request and the unique identifier corresponding to the service, and the authorization information table stores the authorization state of the client to a certain service (or certain services). For example, if the third-party platform is a WeChat payment platform and the authorization status (permission) of customer A for service B is stored in the database of the platform, the payment platform can automatically make a continuous secret-free payment for service B of customer A according to the request.
As an aspect of this embodiment, if the authorization status is a first status, performing a first electronic transaction with a third party platform according to the transaction information matching the first status further comprises,
performing client identity verification on the identity information of the client;
performing service verification on the service information;
and sending the transaction information matched with the first state and passing the customer identity verification and the service verification to the third-party platform for carrying out first electronic transaction.
In this step, the front-end device obtains the identity information of the client, and the universal device verifies the identity information of the client, wherein the identity information of the client can be verified in a password manner, or can be verified in a biometric manner, that is, the user can verify the identity in a fingerprint manner, a voiceprint manner, an iris manner, or can also verify the identity in an image recognition manner, for example, in a face recognition manner. The service verification may be requested by the general device to the core device for verification, for example, the core device verifies whether the service is an existing service, whether data of the service is incorrect, and the like.
The service verification of the service information means that the core device compares the service information transmitted from the general device with the service information in its own database, for example, whether the text parts of the two service information are consistent, whether the time is consistent, and whether the number (amount of money) appearing therein is consistent.
The transaction information matched with the first state means that when the authorization state is in different state types, the corresponding transaction information is different, in this embodiment, when the authorization status is the first status, the general device needs to send the status information of the authorization status (i.e. the first status), the service verification information (i.e. whether the service verification of the service passes), the service information (e.g. service number, service time, etc.), the identity information of the user (e.g. user name, mobile phone number, etc.), the temporary authorization code, and other transaction information to the third party platform for performing the first electronic transaction, the temporary authorization code is an authorization code which is valid within a preset time, and the electronic transaction system and the third-party platform can complete the appointed service transaction without the real-time confirmation of the client within the preset time according to the temporary authorization code. The third-party platform feeds back a first electronic transaction result (success or failure of the service transaction) corresponding to the service to the general device, and also feeds back the first electronic transaction result to the core device; the generic device then feeds back the first electronic transaction result to the front-end device, which can then be made to display to the customer.
As an aspect of this embodiment, if the authorization status is a second status, performing a second electronic transaction with a third party platform according to the transaction information matching the second status further comprises,
performing client identity verification on the identity information of the client;
after the client identity is verified, deleting the temporary authorization code and the authorization state corresponding to the service;
and sending the transaction information matched with the second state to the third-party platform for second electronic transaction.
In this step, the front-end device obtains the identity information of the client, and the universal device verifies the identity information of the client, wherein the identity information of the client can be verified in a password manner, or can be verified in a biometric manner, that is, the user can verify the identity in a fingerprint manner, a voiceprint manner, an iris manner, or can also verify the identity in an image recognition manner, for example, in a face recognition manner. After passing the verification, the general device sends the identity information, the service information and the authorization state of the client to the service device, wherein the service information comprises information such as a service number, service time and the like.
The method comprises the steps that a service device requests a core device to delete an authorization state and a temporary authorization code of a client for corresponding service according to identity information and service information of the client transmitted by a general device, and after the core device deletes the authorization state and the temporary authorization code, the core device also sends a calling authorization request ID to the service device, wherein the authorization request ID is an authorization code which is valid for a longer time relative to the temporary authorization code, a third-party platform can generate a new temporary authorization code according to the authorization request ID within the valid time of the authorization request ID, and the electronic transaction system and the third-party platform can complete specified service transaction within the preset time of the new temporary authorization code without real-time confirmation of the client.
The step of sending the transaction information matched with the second state to the third-party platform for second electronic transaction further comprises the step of sending the transaction information matched with the second state, which comprises the identity information (user name, mobile phone number, unique identifier of the client on the third-party platform and the like), the authorization request ID, the service information and the like of the client to the third-party platform by the service device. The third-party platform carries out second electronic transaction according to the authorization request ID and the identity information of the client, feeds back a second electronic transaction result (namely authorization state, possibly including information of success or failure of authorization and the like) corresponding to the service and the updated temporary authorization code to the service device, feeds back the second electronic transaction result and the updated temporary authorization code to the core device for storage, feeds back the second electronic transaction result (authorization state) to the universal device by the core device, feeds back the second electronic transaction result (authorization state) to the front-end device by the universal device, and presents the second electronic transaction result (authorization state) to the client terminal for the client to view.
In the above steps, the authorization status generated by the second electronic transaction result is the result of whether the electronic transaction is successful or not, the authorization status of the client is the first status when the transaction is successful, the authorization status of the client is the third status when the transaction is failed, and when the client operates in the third-party platform, the authorization status can be independently operated by the third-party platform to change the authorization status into the second status.
As an aspect of this embodiment, if the authorization status is a third status, performing a third electronic transaction with a third party platform according to the transaction information matching the third status further comprises,
performing client identity verification on the identity information of the client;
and after the customer identity is verified, sending the transaction information matched with the third state to the third-party platform for carrying out third electronic transaction.
In this step, the front-end device obtains the identity information of the client, and the universal device verifies the identity information of the client, wherein the identity information of the client can be verified in a password manner, or can be verified in a biometric manner, that is, the user can verify the identity in a fingerprint manner, a voiceprint manner, an iris manner, or can also verify the identity in an image recognition manner, for example, in a face recognition manner.
Sending the transaction information matched with the third state to the third-party platform for third electronic transaction further comprises sending the obtained identity information of the customer and service information to a service device by the general device, wherein the service information comprises information such as a service number and service time of the customer. And the service device sends the transaction information which comprises the identity information (user name, mobile phone number and the like) of the client, the authorization permission of the client, the service information and the like and is matched with the third state to the third-party platform. The third party platform carries out third electronic transaction according to the identity information and the service information of the client, feeds back a third electronic transaction result (namely an authorization state, which may include information of success or failure of authorization and the like) corresponding to the service and a temporary authorization code to the service device, feeds back the third electronic transaction result, the temporary authorization code and an authorization request ID to the core device for storage, feeds back the third electronic transaction result (the authorization state) to the universal device, feeds back the third electronic transaction result (the authorization state) to the front-end device by the universal device, and presents the third electronic transaction result (the authorization state) to the client terminal for the client to view.
In the above steps, the authorization status generated by the third electronic transaction result is the result of whether the electronic transaction is successful or not, the authorization status of the client is the first status when the transaction is successful, the authorization status of the client is the third status when the transaction is failed, and when the client operates in the third-party platform, the authorization status can be independently operated by the third-party platform to change the authorization status into the second status. The temporary authorization code is used for carrying out first electronic transaction when the authorization state is the first state, and the authorization request ID is used for carrying out second electronic transaction when the authorization state is the second state.
As an aspect of embodiments herein, further comprising, in the first electronic transaction,
sending transaction information including the temporary authorization code and the service information to the third-party platform;
and receiving a first electronic transaction result of the transaction result aiming at the service, which is fed back by the third-party platform.
In this step, the general device forms transaction information with the temporary authorization code, the service information, the service verification information, and the like, and sends the transaction information to the third party platform, where the third party platform may obtain the customer identity information through matching the temporary authorization code, or the service information includes the customer identity information, and the third party platform completes a transaction for the service, for example, a transaction for a payment service, according to the transaction information.
As an aspect of embodiments herein, further comprising, in the second electronic transaction,
sending transaction information including an authorization request ID and service information to the third-party platform;
and receiving the updated temporary authorization code for the service, which is fed back by the third-party platform.
In this step, the service device obtains the authorization request ID from the core device, and forms transaction information in combination with the certificate of the service device, the customer identity information, the service information, and the like, and sends the transaction information to the third party platform, and the third party platform generates an updated temporary authorization code for the service according to the authorization request ID and other transaction information, and feeds back the updated temporary authorization code to the service device and the core device.
As an aspect of embodiments herein, further comprising, in the third electronic transaction,
obtaining authorization permission of a client for a service;
sending transaction information including the authorization permission for the service and service information to the third party platform;
and receiving a temporary authorization code and an authorization request ID (identity) for the service, which are fed back by the third-party platform.
In this step, the front-end device obtains the authorization permission of the client through a web page or an APP, for example, by explicitly prompting the client for information such as a target service, authorization time, and usage range of the authorization permission, and obtaining information such as "allow", "disallow", and the like input by the client to obtain the authorization permission of the client. The front-end device transmits the authorization permission to a service device, the service device sends transaction information consisting of a certificate of the service device, the authorization permission, the service information and the like to a third-party platform, and the third-party platform generates a temporary authorization code and an authorization request ID aiming at the service according to the authorization permission of the client and other transaction information, wherein the third-party platform can obtain the identity information of the client according to the authorization permission analysis of the client or the service information carries the identity information of the client.
By the method of the embodiment, the transaction information matched with the authorization state can be organized according to the authorization state of the client to carry out corresponding electronic transaction, so that the electronic transaction cannot be carried out due to the change of the authorization state, the execution efficiency of the electronic transaction is enhanced, the complicated operation of the client is avoided, the time of the client is saved, and the use experience of the client is enhanced.
Fig. 3 is a schematic structural diagram of an electronic transaction system according to an embodiment of the present disclosure, in this embodiment, the system in fig. 1 is subdivided in a functional partitioning manner, each of the functional units may be formed by one or several devices, all the functional units may be integrated in one computer or may be respectively disposed in multiple computers, and specifically, the method includes:
a client identity information obtaining unit 301, configured to obtain identity information of a client;
a service information obtaining unit 302, configured to obtain service information of the client;
a query unit 303, configured to send a query request including at least the identity information of the client and the service information to a third-party platform, so that the third-party platform matches the identity information of the client and the service information to obtain an authorization state of the client for the service;
a receiving unit 304, configured to receive an authorization status fed back by the third-party platform;
the first processing unit 305, if the authorization status is a first status, performing a first electronic transaction with a third party platform according to the transaction information matched with the first status;
the second processing unit 306, if the authorization status is a second status, performing a second electronic transaction with a third party platform according to the transaction information matched with the second status;
and a third processing unit 307, performing a third electronic transaction with a third party platform according to the transaction information matched with the third state if the authorization state is the third state.
As an aspect of the embodiments herein, the client identity information obtaining unit is further configured to obtain the identity information of the client according to a context of the client.
As an aspect of the embodiments herein, please refer to fig. 4, which is a detailed diagram illustrating a structure of the electronic trading system of the embodiments herein, the querying unit 303 further includes,
an identifier obtaining module 3031, configured to obtain a unique identifier of the client on the third-party platform and a unique identifier corresponding to a service;
the querying unit 303 further sends a query request at least including the unique identifier of the third party platform and the unique identifier corresponding to the service to the third party platform.
As an aspect of the embodiments herein, the first processing unit 305 further includes,
the client identity verification module 3051 is configured to perform client identity verification on the identity information of the client;
the service verification module 3052 is configured to perform service verification on the service information;
and the first transaction information sending module 3053, configured to send the transaction information, which is matched with the first state and passes through the client identity authentication and the service authentication, to the third party platform to perform the first electronic transaction.
As an aspect of the embodiments herein, the second processing unit 306 further includes,
a client authentication module 3061, configured to perform client authentication on the identity information of the client;
a deletion module 3062, configured to delete the authorization status after the client authentication is passed;
and a second transaction information sending module 3063, configured to send the transaction information matched with the second state to the third party platform for a second electronic transaction.
As an aspect of the embodiments herein, the third processing unit 307 further comprises,
the client identity authentication module 3071 is used for performing client identity authentication on the identity information of the client;
and the third transaction information sending module 3072 is configured to send the transaction information matched with the third state to the third party platform for a third electronic transaction after the customer identity authentication is passed.
As an aspect of this embodiment, the first transaction information sending module 3053 is further configured to send the transaction information including the temporary authorization code and the service information to the third party platform;
the receiving unit 304 is further configured to receive a first electronic transaction result of the transaction result for the service, which is fed back by the third party platform.
As an aspect of this embodiment, the second transaction information sending module 3063 is further configured to send transaction information including an authorization request ID and service information to the third party platform;
the receiving unit 304 is further configured to receive the updated temporary authorization code for the service, which is fed back by the third-party platform.
As an aspect of the embodiments herein, further includes an authorization license obtaining unit 308, configured to obtain an authorization license of the client for the service;
the third transaction information sending module 3072 is further configured to send transaction information including the authorization permission for the service and the service information to the third party platform;
the receiving unit 304 is further configured to receive the temporary authorization code and the authorization request ID for the service, which are fed back by the third-party platform.
The client authentication module 3051, the client authentication module 3061, and the client authentication module 3071 may be the same module, and the functional modules are shared by the three processing units.
Through the system of the embodiment, the corresponding electronic transaction can be carried out according to the transaction information matched with the authorization state organized according to the authorization state of the client, so that the electronic transaction cannot be carried out due to the change of the authorization state, the execution efficiency of the electronic transaction is enhanced, the complicated operation of the client is avoided, the time of the client is saved, and the use experience of the client is enhanced.
As shown in fig. 5, which is a data flow diagram for querying an authorization status of a client in this embodiment, in the embodiment of this figure, a process that a client queries the authorization status of the client through a front-end device, a core device, a service device, and a third-party platform is described in detail, in a service scenario in which the client initiates an electronic transaction of a certain service, the client may initiate an electronic transaction request of the service to the front-end device through a webpage or an APP of the client, and query an authorization status of the client for the service in the process of the electronic transaction request; or in a service scene such as automatic renewal, the system automatically initiates an electronic transaction according to the time period of the electronic service, and automatically initiates an automatic renewal for a certain service on the system side instead of actively initiating by the client, and the authorization state of the client for the service can be obtained through the following process in the electronic transaction process. Of course, in some embodiments, the authorization status for a service may also be the authorization status of the client, and a specific service is not considered.
Step 501, the front-end device obtains identity information of a client through a client.
In this step, the client may be an Application (APP) running on a mobile phone or a tablet computer, or may also be an interface in a Web (Web) mode, and obtain, through the application or the Web, identity information of the client, such as a name of the client, a mobile phone number, information about a service currently being processed (including a unique identifier of the service, service data, service time, and the like), payment information, and the like, and also obtain, from the context of the application or the Web, a unique identifier of the client on a third-party platform, such as a user name, an identity number, an age, and income of the third-party platform.
In other embodiments, the core device or the service device may start acquiring the identity information of the client according to a comparison between the service cycle time of the client and the current time, and start the process of acquiring the identity information of the user if the current time matches the service cycle time of the client.
Step 502, the front-end device sends the client identity information and the corresponding service information to the core device.
In this step, the service information may be determined by the application program or the hierarchy of the web page or the triggering of the function module where the client is located, for example, after the customer clicks to confirm the purchase, the front-end device may analyze the current service on the page where the button for confirming the purchase is located or the service module to which the button belongs, and obtain the relevant information of the service, where the service information may include information such as a service number, a service validation time, and a service amount.
In this step, the core device also checks whether the service information received from the front-end device is legal or not, for example, whether the service information is falsified or not, whether an illegal behavior caused by the fact that the age of the client is too small or too large exists or whether an illegal behavior caused by the fact that the living city of the client does not conform to the city specified in the service exists or not, according to the service information stored in the database of the core device.
In step 503, the core device sends the authenticated client identity information and the corresponding service information to the service device.
In this step, the core device verifies the service information through the above steps, and then sends the service information and the client identity information that meet the service standard to the service device.
Step 504, after the service device completes the client identity information and the service information, it sends a query request to the third party platform.
In this step, the service device may further verify the validity of the service information, store the payment means in the service information, and search for other client identity information or service information required by each database configuration third-party platform.
And 505, the third-party platform feeds back the authorization state to the service device.
In this step, the third party platform queries, according to the received client identity information and service information, an authorization status of the client matching the client information for the service matching the service information, that is, an authorization status of the client for the service is stored in a database of the third party platform, where a unique identifier of the client in the third party platform, such as a user name, a mobile phone number, or a specific character string, is used to compare with a client authorization status table stored in the database, where the table may be as shown in table 1:
TABLE 1
Customer unique identifier Service unique identifier Authorization status
Wx_0981025 ZJ_12u1u989 1
Wx_0981025 ZJ_12u1u988 0
In table 1, the unique identifier of the client is the unique identifier of the client in the third-party platform, and the unique identifiers of the client in other third-party platforms may be different, and may be found by matching through the client identification number in the client identification information, or directly found by matching through the third-party platform unique identifier in the client identification information. The service number (service unique identifier) in the service information may also be matched to the authorization status information of the client for the service in the table above, for example, the same client has different authorization statuses for different services, wherein authorization status 0 represents unauthorized, 1 represents authorized, and 2 represents de-authorized.
Step 506, the third party platform feeds back the authorization status to the core device.
In this step, the core device saves the authorization state of the client for the service.
And step 507, the core device feeds back the authorization state to the front-end device.
In this step, the core device determines according to the authorization status, and sends the page links corresponding to different authorization statuses to the front-end device.
Step 508, the front-end device instructs the client to display the authorization status of the service and the corresponding page link.
Through the embodiment, the authorization state of the client for the current service can be obtained, and the client can enter a page to be processed next.
Fig. 6 is a data flow diagram of a first authorization state in this embodiment, where a processing flow when the authorization state is the first state is described in this embodiment, specifically including:
step 601, the front-end device sends the authorization status and the client identity information to the general device.
In this step, the front-end device sends the authorization status and the client identity information to the general device through the page link according to the click operation of the client at the client, and verifies the client identity information in the general device, where the client identity information may be verified in a password manner, or may be verified in a biometric manner, that is, the user performs identity verification in a fingerprint manner, a voiceprint manner, an iris manner, or may also perform verification in an image recognition manner, for example, in a face recognition manner.
In step 602, the generic device sends the authorization status and the service information to the core device.
In this step, the generic device sends the service information and the client identity information that pass the client identity authentication to the core device, where the service information is a service transaction that is automatically initiated according to the client operating the client or the periodic service before the aforementioned step 501, the core device performs the service authentication for the service information, and compares the service information transmitted from the generic device with the service information in its own database, for example, whether the text portions of the two service information are consistent, whether the time is consistent, and whether the numbers (money amounts) appearing therein are consistent.
Step 603, the core device feeds back the service verification result to the general device.
In this step, the core device feeds back the verification result of the service verification, i.e., pass/fail, to the general device. The core device also sends a temporary authorization code for the service of the client to the general device, where each service of the client corresponds to one temporary authorization code, and the temporary authorization code is stored in the core device, and how the core device obtains the temporary authorization code and the authorization request ID will be described later.
In other embodiments, if the generic device stores the temporary authorization code, the core device does not send the temporary authorization code to the generic device in this step.
In step 604, the generic device forms transaction information and sends it to the third party platform.
In this step, the universal device may form transaction information from information such as the authorization status, the service verification result, the service information, the customer identity information, the temporary authorization code, and the like, and send the transaction information to the third party platform for completing the service transaction. Wherein, the third party platform can complete the service transaction according to the transaction information, for example, the service transaction is a payment transaction, the third party platform can obtain a deduction account number and a collection account number according to the service information, judge whether the payment transaction is legal or not according to the service verification result, the unique identifier of the client on the third-party platform can be obtained according to the client identity information, and the unique identifier of the client on the third-party platform and the service unique identifier in the service information, whether the deducting party (i.e. the client) who pays the service authorizes the service, whether the authorization information stored by the third-party platform is consistent with the authorization state in the transaction information, whether the temporary authorization code stored by the third-party platform is consistent with the temporary authorization code in the transaction information, if the judgment is consistent, deducting money, and if one item is inconsistent, refusing to execute the service.
In other embodiments, the third party platform may complete the service transaction only according to the temporary authorization code and the service information in the transaction information, that is, only the temporary authorization code and the service information need to be included in the transaction information.
Step 605, the third party platform feeds back the service transaction result to the general device and the core device.
In this step, the third party platform completes the business transaction according to the transaction information and generates a business transaction result, wherein the business transaction result comprises a result of success or failure of the business transaction.
And 606, the general device feeds back the service transaction result to the front-end device.
In step 607, the front-end device feeds back the service transaction result to the client.
In this step, the front-end device displays a prompt message of success or failure of the service transaction to the client.
By the method of the embodiment, when the authorization state is the first state, the business transaction issued by the client is completed through the transaction information matched with the first state.
Fig. 7 is a data flow diagram of a second authorization state in the embodiment of the present disclosure, and in this embodiment, a processing flow when the authorization state is the second state is described, which specifically includes:
in step 701, the front-end device sends the authorization status and the client identity information to the generic device.
In this step, the front-end device sends the authorization status and the client identity information to the general device through the page link according to the click operation of the client at the client, and verifies the client identity information in the general device, where the client identity information may be verified in a password manner, or may be verified in a biometric manner, that is, the user performs identity verification in a fingerprint manner, a voiceprint manner, an iris manner, or may also perform verification in an image recognition manner, for example, in a face recognition manner.
Step 702, the generic device sends the client identity information and the service information to the service device.
In this step, the identity information and the service information of the client are similar to those in the foregoing embodiment, and are not described again.
The service device searches an authorization state matched with the identity information of the client according to the identity information and the service information, and the authorization state is a second state in this embodiment, so that the service device generates a request for requesting to delete authorization, the request for requesting to delete authorization includes the identity information and the service information of the client, and thus the core device can find out a corresponding authorization state and a temporary authorization code according to the identity information and the service information of the client, wherein the temporary authorization code is an authorization code of the client for the service, the authorization code is valid within a certain time, and a third-party platform can perform operations allowed by client authorization, such as money deduction, money transfer and the like, on an account of the client according to the temporary authorization code.
In step 703, the service device sends a request for deleting the authorization to the core device.
In this step, the second state is an invalid authorization state, and if the authorization states of the second states in the core device are not deleted in time, service flow logic is disturbed, normal service operation is affected, and a problem that a client cannot authorize the service, even the client identity information in the client identity information and the client identity information in the third-party platform authorization information do not correspond to each other, which causes a problem that the third-party platform service is disturbed or even wrong. Therefore, in this step, the service device requests the core device to delete the authorization status in the second state, so that the above problem can be solved.
In step 704, the core device feeds back the authorization status deletion result to the service device.
In this step, the core device deletes the authorization status and deletes the temporary authorization code for the service of the client according to the matching of the client identity information and the service information to the corresponding authorization status information. Then, the core device calls an authorization request ID stored corresponding to the temporary authorization code, the authorization request ID is received in the client authorization process, and the third-party platform can generate a new temporary authorization code through the authorization request ID.
Step 705, the service device sends transaction information to the third party platform.
In this step, the service device sends the transaction information formed by the customer identity information, the authorization request ID, the service information and the like to the third-party platform so as to perform re-authorization transaction with the third-party platform.
And step 706, the third-party platform feeds back the re-authorization transaction result and the updated temporary authorization code to the core device and the service device.
In this step, the third party platform finds the existing authorization information in the database according to the client identity information and the service information in the transaction information, the authorization state at this time is the second state, verifies the validity of the authorization request ID, for example, verifies whether the authorization request ID meets the data format requirement, whether the authorization request ID is within the valid time range, whether the authorization request ID is consistent with the authorization request ID of the user for the service stored in the database, and the like, generates an updated temporary authorization code according to the valid authorization request ID, and re-authorizes the transaction result, for example, the re-authorizes the transaction result as successful or failed. And feeding back the re-authorization transaction result and the updated temporary authorization code to the service device. The third party platform will also save the updated temporary authorization code in the database.
In the above steps, the service device obtains the updated temporary authorization code, and can directly use the updated temporary authorization code to form transaction information to perform service transaction with the third-party platform when the next service transaction is processed, so as to complete the service transaction instruction of the client.
And step 707, the core device feeds back the re-authorization transaction result to the general device.
And step 708, the general device feeds back the service transaction result to the front-end device.
And step 709, the front-end device feeds back the service transaction result to the client.
In this step, the front-end device displays a prompt message indicating that the re-authorization transaction is successful or failed to the client.
By the method of the embodiment, different electronic transactions can be carried out according to various authorization states, and the business transaction instruction of the customer is finally completed.
Fig. 8 is a data flow diagram of a third authorization state in the embodiment of the present disclosure, and in this embodiment, a processing flow when the authorization state is the third state is described, which specifically includes:
step 801, the front-end device sends the client identity information to the generic device.
In this step, the front-end device sends the client identity information to the general device through the page link according to the click operation of the client on the client, for example, the client identity information may include information such as the client's identity card number, the mobile phone number, and the unique identifier of the client on the third-party platform, and the client identity information is verified in the general device, and the client identity information may be verified in a password manner, or may be verified in a biometric manner, that is, the user performs identity verification in a fingerprint manner, a voiceprint manner, an iris manner, or may also perform verification in an image recognition manner, for example, verification in a face recognition manner.
Step 802, the generic device sends the client identity information and the service information to the service device.
In this step, the identity information and the service information of the client are similar to those in the foregoing embodiment, and are not described again.
Step 803, the service device sends the transaction information to the third party platform.
In this step, the service device sends the transaction information formed by the customer identity information, the service information and the like to the third-party platform so as to perform authorized transaction with the third-party platform.
The workflow of the authorization request is further included in this step, which can be seen in the flow chart of the authorization transaction herein shown in fig. 9, which includes:
step 901, obtaining the access permission of the client.
In this step, corresponding to the above steps 801 to 803, a key indicating whether or not authorization is granted is displayed on the page of the client, and when the client confirms that the key is clicked, the client grants authorization to the service on behalf of the client, and the access permission of the client is transmitted to the service device via the front-end device and the general-purpose device.
Step 902, the service device requests authorization information from the third party platform.
In this step, the service device sends the private certificate and the access permission of the client to the third party platform, so as to request the third party platform to give the authorization information of the service.
In step 903, the third party platform verifies the validity of the private certificate and the access permission of the service device, and if the verification is valid, sends authorization information to the service device, where the authorization information includes an authorization request ID and a temporary authorization code, and other information such as scope (i.e., service for which the authorization is directed, time of the authorization, geographic location or area where the authorization is valid, etc.).
Wherein a temporary authorization code and an authorization request ID are stored in the core device.
And 904, performing service transaction to the third-party platform by using the authorization information.
In this step, referring to the service transaction process shown in fig. 6, in a certain period of time after the obtaining of the client authorization information, the universal device performs service transaction with the third party platform by using the temporary authorization code and the service information.
Step 905, the third party platform completes the business transaction according to the authorization information.
In this step, the third party platform does not need to obtain other authorization and real-time confirmation of the customer again, and can complete business transactions such as payment transactions, deduction transactions, remittance transactions and the like according to the authorization information.
And step 804, the third-party platform feeds back the authorization transaction result and part of authorization information to the service device.
In this step, the third party platform feeds back the authorization transaction result, i.e., the success or failure result, to the service device, and feeds back part of the authorization information, i.e., the temporary authorization code, to the service device.
Step 805, the third party platform feeds back the authorization transaction result and the authorization information to the core device.
In this step, the third party platform feeds back the result of the authorized transaction, i.e., the result of success or failure, to the core device, and feeds back the authorization information, i.e., the temporary authorization code and the authorization request ID, to the core device for storage.
At step 806, the core device feeds back the authorized transaction result to the front-end device.
In step 807, the front-end device feeds back the authorized transaction result to the client.
By the method of the embodiment, different electronic transactions can be carried out according to various authorization states, and the authorization transaction instruction of the client is finally completed.
As fig. 10 is a schematic structural diagram of a computing device in this embodiment, an electronic transaction system in this embodiment may be the computing device in this embodiment, or each functional unit and module in the electronic transaction system may also be the computing device in this embodiment, and execute the method in this embodiment. Computing device 1002 may include one or more processing devices 1004, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. Computing device 1002 may also include any storage resources 1006 for storing any kind of information, such as code, settings, data, and the like. For example, and without limitation, storage resources 1006 may include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any storage resource may use any technology to store information. Further, any storage resource may provide volatile or non-volatile reservation of information. Further, any storage resources may represent fixed or removable components of computing device 1002. In one case, when the processing device 1004 executes associated instructions stored in any storage resource or combination of storage resources, the computing device 1002 can perform any of the operations of the associated instructions. Computing device 1002 also includes one or more drive mechanisms 1008, such as a hard disk drive mechanism, an optical disk drive mechanism, or the like, for interacting with any storage resource.
Computing device 1002 may also include input/output module 1010(I/O) for receiving various inputs (via input device 1012) and for providing various outputs (via output device 1014)). One particular output mechanism may include a presentation device 1016 and an associated Graphical User Interface (GUI) 1018. In other embodiments, input/output module 1010(I/O), input device 1012, and output device 1014 may also not be included, but merely as a computing device in a network. Computing device 1002 may also include one or more network interfaces 1020 for exchanging data with other devices via one or more communication links 1022. One or more communication buses 1024 couple the above-described components together.
Communication link 1022 may be implemented in any manner, such as over a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. Communications link 1022 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
Embodiments herein also provide a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring identity information of a client;
inquiring the authorization state of the client according to the identity information of the client;
if the authorization state is a first state, performing a first electronic transaction with a third-party platform according to transaction information matched with the first state;
if the authorization state is a second state, performing second electronic transaction with a third-party platform according to transaction information matched with the second state;
and if the authorization state is a third state, performing third electronic transaction with a third-party platform according to the transaction information matched with the third state.
The computer device provided by the embodiment can also implement the methods in fig. 2, 5-9.
Corresponding to the methods in fig. 2, 5-9, the embodiments herein also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps of the above-described method.
Embodiments herein also provide computer readable instructions, wherein when executed by a processor, a program thereof causes the processor to perform the methods as shown in fig. 2, 5-9.
It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.
It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments herein.
In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The principles and embodiments of this document are explained herein using specific examples, which are presented only to aid in understanding the methods and their core concepts; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.

Claims (10)

1. An electronic transaction method, comprising,
acquiring identity information of a client and service information of the client;
sending a query request at least comprising the identity information of the client and the service information to a third-party platform so that the third-party platform matches the identity information of the client and the service information to obtain the authorization state of the client for the service;
receiving the authorization state fed back by the third-party platform;
if the authorization state is a first state, performing a first electronic transaction with the third-party platform according to the transaction information matched with the first state;
if the authorization state is a second state, performing second electronic transaction with a third-party platform according to transaction information matched with the second state;
and if the authorization state is a third state, performing third electronic transaction with a third-party platform according to the transaction information matched with the third state.
2. The method of claim 1, wherein conducting a first electronic transaction with a third party platform based on transaction information matching a first status if the authorization status is the first status further comprises,
performing client identity verification on the identity information of the client;
performing service verification on the service information;
and sending the transaction information matched with the first state and passing the customer identity verification and the service verification to the third-party platform for carrying out first electronic transaction.
3. The method of claim 1, wherein conducting a second electronic transaction with a third party platform based on transaction information matching a second status if the authorization status is the second status further comprises,
performing client identity verification on the identity information of the client;
after the client identity is verified, deleting the temporary authorization code and the authorization state corresponding to the service;
and sending the transaction information matched with the second state to the third-party platform for second electronic transaction.
4. The method of claim 1, wherein conducting a third electronic transaction with a third party platform based on transaction information matching a third status if the authorization status is the third status further comprises,
performing client identity verification on the identity information of the client;
and after the customer identity is verified, sending the transaction information matched with the third state to the third-party platform for carrying out third electronic transaction.
5. The method of claim 2, further comprising in the first electronic transaction,
sending transaction information including the temporary authorization code and the service information to the third-party platform;
and receiving a first electronic transaction result of the transaction result aiming at the service, which is fed back by the third-party platform.
6. The method of claim 3, further comprising in the second electronic transaction,
sending transaction information including an authorization request ID and service information to the third-party platform;
and receiving the updated temporary authorization code for the service, which is fed back by the third-party platform.
7. The method of claim 4, further comprising in the third electronic transaction,
obtaining the authorization permission of the client for the service;
sending transaction information including the authorization permission for the service and service information to the third party platform;
and receiving a temporary authorization code and an authorization request ID (identity) for the service, which are fed back by the third-party platform.
8. An electronic transaction system, comprising,
the client identity information acquisition unit is used for acquiring the identity information of the client;
a service information obtaining unit, configured to obtain service information of the client;
the query unit is used for sending a query request at least comprising the identity information of the client and the service information to a third-party platform so as to enable the third-party platform to match the identity information of the client and the service information to obtain the authorization state of the client for the service;
the receiving unit is used for receiving the authorization state fed back by the third-party platform;
the first processing unit is used for carrying out first electronic transaction with a third-party platform according to the transaction information matched with the first state if the authorization state is the first state;
the second processing unit is used for carrying out second electronic transaction with a third-party platform according to the transaction information matched with the second state if the authorization state is the second state;
and the third processing unit is used for carrying out third electronic transaction with a third-party platform according to the transaction information matched with the third state if the authorization state is the third state.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of the preceding claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method of any of claims 1-7.
CN202010640823.6A 2020-07-06 2020-07-06 Electronic transaction method, system and storage medium Pending CN111815446A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010640823.6A CN111815446A (en) 2020-07-06 2020-07-06 Electronic transaction method, system and storage medium
CN202110244037.9A CN112819635B (en) 2020-07-06 2021-03-05 Electronic transaction method, system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010640823.6A CN111815446A (en) 2020-07-06 2020-07-06 Electronic transaction method, system and storage medium

Publications (1)

Publication Number Publication Date
CN111815446A true CN111815446A (en) 2020-10-23

Family

ID=72841576

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202010640823.6A Pending CN111815446A (en) 2020-07-06 2020-07-06 Electronic transaction method, system and storage medium
CN202110244037.9A Active CN112819635B (en) 2020-07-06 2021-03-05 Electronic transaction method, system and storage medium

Family Applications After (1)

Application Number Title Priority Date Filing Date
CN202110244037.9A Active CN112819635B (en) 2020-07-06 2021-03-05 Electronic transaction method, system and storage medium

Country Status (1)

Country Link
CN (2) CN111815446A (en)

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2199942C (en) * 1994-09-16 2007-08-21 Lee H. Stein Computerized payment system for purchasing information products by electronic transfer on the internet
TWI275037B (en) * 2001-12-04 2007-03-01 Gary Leung System and method for facilitating electronic financial transactions using a mobile telecommunication device
CA2577271A1 (en) * 2004-08-25 2006-03-09 Mastercard International Incorporated Method and system for automated payment authorization and settlement
CN101051372A (en) * 2006-04-06 2007-10-10 北京易富金川科技有限公司 Method for safety verifying financial business information in electronic business
UA101469C2 (en) * 2006-08-01 2013-04-10 К'Юпей Холдінгс Лімітед Transaction authorization system and method of use thereof
US10853855B2 (en) * 2007-05-20 2020-12-01 Michael Sasha John Systems and methods for automatic and transparent client authentication and online transaction verification
US8249893B1 (en) * 2012-04-05 2012-08-21 Stoneeagle Services, Inc. Automated service provider payment method
US10096008B2 (en) * 2012-09-10 2018-10-09 Mastercard International Incorporated Methods and systems for processing electronic disbursements
US20150058220A1 (en) * 2013-08-26 2015-02-26 Cellco Partnership (D/B/A Verizon Wireless) Payment pre-authorization
US20150134518A1 (en) * 2013-11-14 2015-05-14 Google Inc. Pre-authorized online checkout
CN105099688B (en) * 2014-05-15 2018-12-21 阿里巴巴集团控股有限公司 A kind of operating method of electronic account, the methods of exhibiting and device for paying the page
US10698902B2 (en) * 2017-10-04 2020-06-30 The Toronto-Dominion Bank Data management device, communication system and methods for tagging data in a data table and triggering automated actions
WO2019068129A1 (en) * 2017-10-06 2019-04-11 Axis IP Pty Ltd System and method for generating a payment schedule for direct or recurring payments
CN110956539A (en) * 2019-11-28 2020-04-03 中国银行股份有限公司 Information processing method, device and system

Also Published As

Publication number Publication date
CN112819635B (en) 2023-10-27
CN112819635A (en) 2021-05-18

Similar Documents

Publication Publication Date Title
US10762503B2 (en) Method, device and system for online payment
US20200051074A1 (en) Method for approving use of card by using blockchain-based token id and server using method
US20210287225A1 (en) Method, device and system for information verification
EP3520009B1 (en) Systems and methods for biometric identity authentication
JP2002245243A (en) Private and secure financial transaction system and method
US11636488B2 (en) System for managing personal identifiers and financial instrument use
US10489565B2 (en) Compromise alert and reissuance
US9785949B2 (en) Customer communication analysis tool
WO2021211983A1 (en) Systems, methods, and non-transitory computer-readable media for secure biometrically-enhanced data exchanges and data storage
US20140358704A1 (en) Secured point-of-sale transactions
KR20210039920A (en) Mobile communication terminal for personal authentification, personal authentification system and personal authentification method using the mobile communication terminal
US20140358778A1 (en) Multi-level know your customer (kyc) data collection and verification
US20160132890A1 (en) Point of transaction device with multi-factor authentication
JP2020166601A (en) Mediation server, program, and information processing method
CN112819635B (en) Electronic transaction method, system and storage medium
US20150347518A1 (en) Associate communication analysis tool
US20210185036A1 (en) Secure authentication system
US11475446B2 (en) System, methods and computer program products for identity authentication for electronic payment transactions
US20200364722A1 (en) Biometric payment processing that configures payment processing for a determined merchant of record
US10216830B2 (en) Multicomputer processing of client device request data using centralized event orchestrator and link discovery engine
CN111930535A (en) Application function calling method and device, computer equipment and storage medium
KR20160076580A (en) Loan-based mobile instant loan services linked through the Internet, the Web service method
WO2018209623A1 (en) Systems, devices, and methods for performing verification of communications received from one or more computing devices
KR101354887B1 (en) The system which supports a authentication process of a user who using a non-facing service
KR20160031445A (en) An existing customer Easy loans Easy loan application and mobile services using the same 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
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20201023

WD01 Invention patent application deemed withdrawn after publication