CN112884469A - Payment method, device and system - Google Patents
Payment method, device and system Download PDFInfo
- Publication number
- CN112884469A CN112884469A CN202110283727.5A CN202110283727A CN112884469A CN 112884469 A CN112884469 A CN 112884469A CN 202110283727 A CN202110283727 A CN 202110283727A CN 112884469 A CN112884469 A CN 112884469A
- Authority
- CN
- China
- Prior art keywords
- payment
- financial
- user
- information
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 238000012545 processing Methods 0.000 claims abstract description 68
- 238000013475 authorization Methods 0.000 claims abstract description 34
- 238000004590 computer program Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 abstract description 21
- 238000005516 engineering process Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 39
- 238000010586 diagram Methods 0.000 description 18
- 238000012546 transfer Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000006855 networking Effects 0.000 description 3
- 239000002994 raw material Substances 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000004148 unit process Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/108—Remote banking, e.g. home banking
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present disclosure provides a payment method, which can be used in the fields of financial technology, including: sending registration information of a non-financial user to a financial client so that the financial client generates authentication information aiming at the registration information, wherein the authentication information is stored in a bank server; and sending a payment request to the bank server so that the bank server carries out payment processing according to the payment request and the authentication information. According to the online account moving permission authorization method and device, the existing online account moving permission of the enterprise is split and then authorized, and the capital safety risk existing in the payment process of the enterprise is reduced from the system level. The present disclosure also provides a payment apparatus and system, an electronic device, and a computer-readable storage medium.
Description
Technical Field
The disclosure relates to the technical field of financial technology, in particular to a payment method, device and system.
Background
Under the prior art background, because the online payment of enterprises needs the enterprises to hold the U shield people (generally being the enterprise finance) to insert the shield and check the signature, along with the online transformation of enterprise operation and purchase, the payment mode under the limitation of the prior art causes obstacles to the online purchase of enterprise management, especially for large and medium enterprises with perfect financial systems, the online payment of the purchase management faces the problem of payment flow interruption or employee payment pad, and some enterprises submit the U shield for use by the purchase management, so that the safety risk of the capital of the public account easily appears.
Disclosure of Invention
Technical problem to be solved
In view of the above problems, the present disclosure provides a payment method, device and system, which are used to at least partially solve the technical problems that the conventional payment method is prone to payment process interruption, high in capital security risk, and the like.
(II) technical scheme
One aspect of the present disclosure provides a payment method, including: sending registration information of a non-financial user to a financial client so that the financial client generates authentication information aiming at the registration information, wherein the authentication information is stored in a bank server; and sending a payment request to the bank server so that the bank server carries out payment processing according to the payment request and the authentication information.
Further, sending the payment request to the bank server includes: calling a payment certificate, wherein the payment certificate is a certificate for payment settlement of a bank; and sending a payment request to the bank server, wherein the payment request comprises payment certificates and transaction information so as to enable the bank server to carry out payment processing.
Further, sending the registration information of the non-financial user to the financial client comprises: submitting registration information to a bank server so that the bank server can identify the registration information; and after the identification is passed, the bank server sends the registration information to the financial client.
Another aspect of the present disclosure provides a payment method, including: acquiring registration information sent by a non-financial client, and generating authentication information aiming at the registration information, wherein the authentication information is stored in a bank server; and according to the authentication information, the bank server carries out payment processing when receiving a payment request of the non-financial user.
Further, acquiring the registration information sent by the non-financial client comprises: and acquiring registration information sent by the non-financial client, authenticating, and binding the relationship with the non-financial user.
Further, after acquiring the registration information sent by the non-financial client, the method further comprises: and issuing payment authority for the non-financial user or approving the payment authority applied by the non-financial user.
In yet another aspect, the present disclosure provides a payment method, including: storing authentication information, wherein the authentication information is generated by the financial client according to registration information sent by the non-financial client; and acquiring a payment request sent by a non-financial user, and performing payment processing according to the payment request and the authentication information.
Further, storing the authentication information includes: acquiring registration information sent by a non-financial client, and identifying the identity of the registration information; sending the registration information to a financial client, the financial client generating authentication information for the registration information; and acquiring and storing the authentication information.
Further, obtaining the payment request sent by the non-financial user comprises: acquiring a payment request sent by a non-financial client, and verifying the identity information of a non-financial user; and obtaining payment voucher information and transaction information, and verifying the payment authority of the non-financial user.
Further, the payment processing of the payment request and the authentication information includes: and deducting funds according to the payment request and the authentication information, and remitting the funds to a specified account according to the payment request.
The present disclosure also provides in one aspect a payment device, comprising: the non-financial client is used for sending registration information of a non-financial user to the financial client so as to enable the financial client to generate authentication information aiming at the registration information, and the authentication information is stored in the bank server; sending a payment request to a bank server so that the bank server carries out payment processing according to the payment request and the authentication information; the financial client is used for acquiring registration information sent by the non-financial client; the bank server is used for storing the authentication information; the system is used for acquiring a payment request sent by a non-financial user and performing payment processing.
Yet another aspect of the present disclosure provides a payment system, including: the system comprises a user management module, a financial client and a user management module, wherein the user management module is used for receiving registration information of a non-financial user and sending the registration information to the financial client so that the financial client generates authentication information aiming at the registration information; the payment authorization module is used for applying for payment authority by the non-financial user and issuing the payment authority for the non-financial user by the financial client; the payment authentication module is used for verifying the identity information and the payment authority of the non-financial user; the transaction receiving module is used for identifying transaction information; and the accounting processing module is used for deducting funds according to the payment request and the authentication information and remitting the funds to a specified account according to the payment request.
Yet another aspect of the present disclosure provides an electronic device, including: a processor; a memory storing a computer executable program which, when executed by the processor, causes the processor to perform the payment method as described above.
A further aspect of the disclosure provides a computer-readable storage medium on which a computer program is stored, characterized in that the program, when executed by a processor, implements a payment method as described above.
(III) advantageous effects
According to the payment method, the device and the system provided by the embodiment of the disclosure, on one hand, the existing online account moving permission is split and then authorized, and the payment can be completed by directly using the enterprise settlement account fund when the enterprise non-financial user carries out online transaction and purchase, so that the problem of long clearing path in the traditional payment method of the non-financial user is solved, and the payment efficiency is effectively improved; on the other hand, the non-financial users are subjected to real-name registration, are bound with the enterprise relationship, and then control the fund security risk in the enterprise payment process from the system level in a payment authorization mode, so that the security in the payment settlement business process is improved.
Drawings
FIG. 1 schematically illustrates an exemplary system architecture for a payment method according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a payment method according to an embodiment of the disclosure;
FIG. 3 is a diagram schematically illustrating an interaction process between a client and a bank server according to an embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow diagram of a payment method according to another embodiment of the disclosure;
FIG. 5 schematically illustrates a flow diagram of a payment method according to yet another embodiment of the disclosure;
FIG. 6 schematically illustrates a flow diagram for a bank server making a payment according to a payment request in an embodiment of the disclosure;
FIG. 7 schematically illustrates a block diagram of various modules in an enterprise payment system, in accordance with an embodiment of the present disclosure;
FIG. 8 schematically illustrates a cell structure diagram of a subscriber management module according to an embodiment of the disclosure;
FIG. 9 schematically illustrates a block diagram of elements of a payment authorization module according to an embodiment of the present disclosure;
FIG. 10 schematically illustrates a block diagram of elements of a payment authentication module according to an embodiment of the present disclosure;
FIG. 11 schematically illustrates a unit structure diagram of a transaction receipt module according to an embodiment of the disclosure;
fig. 12 schematically shows a unit structure diagram of an accounting processing module according to an embodiment of the present disclosure;
FIG. 13 schematically illustrates a full flow diagram of a method for online payment processing for an enterprise in accordance with an embodiment of the disclosure;
FIG. 14 schematically shows a block diagram of a computer system according to an embodiment of the disclosure.
Detailed Description
For the purpose of promoting a better understanding of the objects, aspects and advantages of the present disclosure, reference is made to the following detailed description taken in conjunction with the accompanying drawings.
The embodiment of the disclosure provides an online payment processing method and system for an enterprise, which set payment authority for a user by binding the relationship between the user and the enterprise finance, provides an online enterprise payment solution for systematic management, complete authorization and safe payment of enterprise full-scale employees, effectively solves the pain points of original certificate transfer, contribution staff payment pad, long payment process and unsafe account fund in online purchasing and finance, and controls the fund safety risk in the enterprise payment process from the system level.
Fig. 1 schematically illustrates an exemplary system architecture 100 for a payment method 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, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 101, 102, 103 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 server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background 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 webpage, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the payment method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the system for payment provided by the embodiments of the present disclosure may be generally disposed in the server 105. The payment method provided by the embodiments of the present disclosure may also be performed by a server or a cluster of servers different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the system for payment provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Fig. 2 schematically illustrates a flow chart of a payment method according to an embodiment of the disclosure.
And S11, sending the registration information of the non-financial user to the financial client so as to enable the financial client to generate authentication information aiming at the registration information, wherein the authentication information is stored in the bank server.
In step S11, the non-financial users are typically financial personnel who have a demand for payment within the enterprise, such as a purchase manager, who directly uses the enterprise account funds to make online payments. The traditional purchasing process of purchasing and conducting comprises the processes of applying for, charging the money of the conducting staff, transmitting the original certificate, auditing, financial payment and the like, and the time consumption is long; some enterprises submit the U shield to be used by purchasing and conducting, and the risk of safety of public account funds is easy to occur. Therefore, the method for splitting and re-authorizing the existing online account-moving permission of the enterprise is provided, so that non-financial personnel with payment requirements can also enjoy part of the payment permission, and can directly use the enterprise settlement account funds to complete payment when online transaction and purchase are carried out.
Firstly, an enterprise needs to register on a bank payment client to obtain a unique ID of the enterprise or a unique U shield ID after applying for the U shield; secondly, the non-financial users need to register on corresponding clients of the bank, perform real-name authentication, associate with the enterprise through enterprise ID, U shield ID or basic positioning of the enterprise, and submit application information. And after receiving the application information, the client sends the information to the enterprise financial client for authentication, and after the enterprise financial is confirmed, the non-financial user and the enterprise relationship are bound. The enterprise finance can further issue payment authority for the user, or approve the payment authority applied by the non-financial user, wherein the payment authority not only comprises payment amount, but also comprises information such as valid period, payment range and the like, and the user can obtain the corresponding payment authority.
And S12, sending a payment request to the bank server so that the bank server can carry out payment processing according to the payment request and the authentication information.
The non-financial user can log in the bank payment client to inquire the payment authority range enjoyed by the bank payment client, and the client can compare the login information with the registration information during login to perform login authentication. The non-financial users can submit payment applications to a bank payment system in modes of bank account transfer, code scanning payment or payment by showing payment codes and the like in the payment authority, and the system judges whether the payment application information is consistent with the preset payment authority range of the non-financial users or not and carries out payment authentication; if the payment account is matched with the bank account, payment account transfer is carried out, information of the payment authority range is updated, the whole payment process is completed, and a drawing of an interaction process between the client and the bank server is shown in fig. 3. The method disclosed by the invention solves the problem that the purchase and management face the interruption of the payment process or the payment pad of staff when online payment is carried out, and reduces the safety risk of public account funds.
On the basis of the above embodiment, sending the payment request to the bank server includes: calling a payment certificate, wherein the payment certificate is a certificate for payment settlement of a bank; and sending a payment request to the bank server, wherein the payment request comprises payment certificates and transaction information so as to enable the bank server to carry out payment processing.
The payment voucher is a voucher for payment settlement of a bank and has a settlement function. The non-financial users can directly use the enterprise settlement account funds to complete payment by means of the payment voucher, and the problems of complex approval process and long application period of the traditional mode are solved. And the bank server can carry out deduction and entry of funds according to the payment voucher and the transaction information.
On the basis of the above embodiment, sending registration information of the non-financial user to the financial client includes: submitting registration information to a bank server so that the bank server can identify the registration information; and after the identification is passed, the bank server sends the registration information to the financial client.
The registration and real-name authentication process of the non-financial user comprises the following steps: and (4) the user enters the client, the client establishes connection with the server, the socket file is opened, and the connection is successful after the establishment. The client submits a registration request to the server through the socket, and submits personal information such as mobile phone numbers, names, certificate types, certificate numbers, validity periods and the like. After submitting the request, the client transmits the request to the server through the HTTP protocol. The server carries out transaction processing and transmits a processing result back to the client. The non-financial user fills the information and sends the information back to the client, the server calls public security networking check to check and authenticate the real name information of the client, and after the authentication is passed, the client writes the information into the database and the registration is successful.
After the non-financial user is successfully registered, the bank server sends the registration information to the financial client, the enterprise financial staff can log in the special client, check the information of the registration staff through the server, and operate and bind the user and the enterprise information.
Fig. 4 schematically illustrates a flow diagram of a payment method according to another embodiment of the present disclosure.
S21, acquiring the registration information sent by the non-financial client, and generating authentication information aiming at the registration information, wherein the authentication information is stored in the bank server; and S22, making the bank server perform payment processing when receiving the payment request of the non-financial user according to the authentication information.
And the financial staff logs in the special client, checks the information of the registered staff through the server, and operates and binds the information of the user and the enterprise. After receiving real-name registration sent by a non-financial user, registering a related identity authentication and management entity, recording user identity details, sending enterprise authentication application information of the real-name user to an enterprise for authentication, binding the real-name user and the enterprise after the authentication is passed, storing the bound real-name user and the enterprise in a bank server, and providing an identity security authentication basis for transaction processing of a subsequent authorization and authentication module.
On the basis of the above embodiment, acquiring the registration information sent by the non-financial client includes: and acquiring registration information sent by the non-financial client, authenticating, and binding the relationship with the non-financial user.
The financial staff logs in the client, receives the user transaction application sent by the server, applies for the identity of the visiting user staff and other related information, the financial staff makes a decision after the server sends the information to the financial staff client, whether the relationship with the non-financial user is bound or not is judged, the feedback information is sent back to the server, and the server sends the feedback information to the non-financial staff client.
On the basis of the above embodiment, after acquiring the registration information sent by the non-financial client, the method further includes: and issuing payment authority for the non-financial user or approving the payment authority applied by the non-financial user.
The payment authority can be different payment authority ranges set according to different roles of the non-financial user, for example, the payment authority is set according to the payment amount involved in different posts, raw material purchasing is mainly large amount payment, the payment authority is correspondingly large, administrative purchasing is mainly small amount payment, and the payment authority is correspondingly small; the payment object range of the non-financial user can be set, for example, the payment object of raw material purchasing is a raw material supplier, and the payment object of administrative purchasing is a shopping website such as Taobao and Jingdong; the effective payment period of the non-financial users can be set, for example, the effective payment period can be a temporary effective payment period of one month, or a long effective payment period of one year, and when the effective payment period is exceeded, the system can automatically recognize and stop the transaction, and the payment cannot be completed.
It should be noted that here, the finance may issue a payment authority for a non-financial user, or the non-financial user applies for the payment authority online and approves the finance. Based on role authorization and authority setting, enterprise finance actively issues payment authority for a company by specifying authorized persons, setting a range of a payee, delineating a payment amount range and other payment information; or the non-financial user applies for the payment authority on line by reporting the payment amount, the payee and other information, and provides an authority judgment basis for the payment of the payment voucher by the subsequent handling role. And the enterprise finance approves the payment authority applied by the handling user, and after approval is passed, the user can carry out a payment process under the payment authority. When the payment is carried out by the handling user, the system can compare the payment application information with the authority set by the enterprise finance, if the comparison is successful, the payment process is started, and if the comparison is not successful, the payment is stopped.
On the basis of the above embodiment, acquiring the registration information sent by the non-financial client includes: and modifying, maintaining and terminating the payment authority of the non-financial user, and performing dynamic management.
After payment authority information issued by the enterprise finance is received, the payment authority is modified and maintained on the basis of the existing information, and the full life cycle management of abolishment is stopped. The corporate finance can adjust the information of the payment authority, the payment object range, the payment valid period and the like according to the change of the work role of the user, and can terminate the abolishment of the payment authority and the like at any time. After part of the payment authority is issued to the purchasing and handling department of the enterprise in advance, the purchasing and handling department can directly use the enterprise settlement account fund for payment, and the enterprise finance mainly carries out corresponding management and maintenance work on the sub-authority of the payment authority.
Fig. 5 schematically illustrates a flow diagram of a payment method according to yet another embodiment of the present disclosure.
S31, storing the authentication information generated by the financial client based on the registration information sent by the non-financial client.
And the bank server receives the registration information of the non-financial user, stores the authentication information sent by the financial client after the financial client passes the authentication, and provides a permission judgment basis for the subsequent payment process.
And S32, obtaining the payment request sent by the non-financial user, and performing payment processing according to the payment request and the authentication information.
After receiving a payment request of a non-financial user, the bank server verifies whether the payment request accords with the preset authority setting, and if so, deducts and remits funds; if not, the transaction is terminated.
On the basis of the above embodiment, storing the authentication information includes: acquiring registration information sent by a non-financial client, and identifying the identity of the registration information; sending the registration information to a financial client, the financial client generating authentication information for the registration information; and acquiring and storing the authentication information.
And the non-financial user sends the registration information to the bank server, and the server performs transaction processing and transmits a processing result back to the client. The user fills the information and sends the information back to the client, the server calls public security networking check to check and authenticate the real name information of the client, and after the authentication is passed, the client writes the information into the database, and the registration is successful. The server sends the registration information to the financial client, the enterprise financial staff logs in the special client, the server checks the registration staff information, operates and binds the user and enterprise information, and sends the authentication information to the bank server, and the bank server stores the authentication information.
On the basis of the above embodiment, acquiring the payment request sent by the non-financial user includes: acquiring a payment request sent by a non-financial client, and verifying the identity information of a non-financial user; and obtaining payment voucher information and transaction information, and verifying the payment authority of the non-financial user.
Obtaining the payment of a non-financial user, carrying out payment authentication on the user, and judging whether the payment request is matched with the payment authority of the user; if so, carrying out fund deduction and merchant posting to complete online payment; otherwise, the transaction is terminated, see FIG. 6. Specifically, a non-financial user sends a payment request to a server through a client, the server receives and identifies a transaction instruction, the authority of the user is compared with a set authority, and a feedback result is returned to the client for payment authentication. It should be noted that the payment authentication performed on the user specifically includes: when a user logs in, whether the login information of the user is consistent with the registration information is confirmed; and when the user submits the payment application, confirming whether the payment application information of the user is consistent with the payment authority. The payment authentication comprises login authentication and payment authentication, the login authentication comprises the steps of transmitting information into the server to be compared with the registration information in the database when an office or financial login client is executed, and returning the comparison result (correct or wrong) to the client; the payment authentication comprises the steps that a handling user sends a handling application to a server through a client, the server compares the authority of the user with the set authority, and a feedback result is returned to the client.
On the basis of the above embodiment, performing payment processing according to the payment request and the authentication information includes: and deducting funds according to the payment request and the authentication information, and remitting the funds to a specified account according to the payment request.
If the conditions are met, recording transaction details, carrying out fund deduction and then transmitting fund processing information back to the server, and after receiving the information of the fund deduction and deduction unit, sending an remittance instruction to the server for fund transmission to complete online payment; if the payment condition is not met, the transaction is terminated, and the information of payment failure is returned. The step of performing fund deduction and merchant posting specifically comprises the following steps: and after the transaction processing is finished, deducting the fund amount of the enterprise account, and remitting the fund amount to the merchant account appointed in the transaction instruction according to the payment plan. After receiving the command of the transaction processing unit, the client carries out fund deduction and then transmits fund processing information back to the server; after receiving the transaction processing unit instruction transmitted by the server and receiving the information of the fund deduction and marking unit, the client sends an remittance instruction to transmit to the server for fund transmission.
Obtaining the payment request sent by the non-financial user further comprises obtaining a transaction instruction: identifying a transaction instruction, and performing transaction processing on the transaction instruction meeting the conditions; wherein the transaction processing includes recording transaction details, identifying and formulating a payment plan. The server receives the transaction instruction transmitted by the platform partner and transmits the instruction to the transaction processing unit in a reserved mode, and after the transaction processing unit receives the transaction identification instruction, the transaction processing unit records transaction details in the server, identifies and formulates a payment plan and sends the payment plan to the client.
Another embodiment of the present disclosure provides a payment apparatus, including: the non-financial client is used for sending registration information of a non-financial user to the financial client so as to enable the financial client to generate authentication information aiming at the registration information, and the authentication information is stored in the bank server; sending a payment request to a bank server so that the bank server carries out payment processing according to the payment request and the authentication information; the financial client is used for acquiring registration information sent by the non-financial client; the bank server is used for storing the authentication information; the system is used for acquiring a payment request sent by a non-financial user and performing payment processing.
Referring to fig. 3, a diagram of an interaction process between the client and the bank server is shown, and the detailed process is specifically described in the payment method and is not described herein again.
Another embodiment of the present disclosure provides a payment system, please refer to fig. 7, including: the system comprises a user management module 1, a financial client and a user management module, wherein the user management module is used for receiving registration information of a non-financial user and sending the registration information to the financial client so that the financial client generates authentication information aiming at the registration information; the payment authorization module 2 is used for applying for payment authority by the non-financial user and issuing the payment authority for the non-financial user by the financial client; the payment authentication module 3 is used for verifying the identity information and the payment authority of the non-financial user; the transaction receiving module 4 is used for identifying transaction information; and the accounting processing module 5 is used for deducting funds according to the payment request and the authentication information, and remitting the funds to a specified account according to the payment request.
Fig. 7 is a block diagram schematically illustrating the structure of each module in the payment system, and the present disclosure adopts a novel online payment user, authorization and authentication mode for enterprises. Before the online purchasing transaction occurs, the relationship between the user and the enterprise is bound through a developed real-name registration mechanism; and completely agreeing with enterprise management and authorization management rules through user role and authority setting; when online purchasing behavior occurs, the purchasing management can use the payment amount which is approved in advance by finance to complete payment, and can conveniently complete payment authentication through human face, fingerprint, static password and other modes.
The user management module 1 is used for receiving registration information of a non-financial user and sending the registration information to the financial client so that the financial client generates authentication information aiming at the registration information. The user management module 1 is composed of a user registration unit 11, an enterprise authentication unit 12 and a role authorization unit 13, please refer to fig. 8.
1) User registration unit 11
The user registration unit 11 is mainly used for receiving user registration and real-name authentication, establishing a basis of an enterprise mobile payment user identity identification authentication system, storing user registration information, and transmitting the user information after the real-name authentication to the enterprise authentication unit 12 for further processing.
2) Enterprise authentication unit 12
The enterprise authentication unit 12 is mainly used for registering a related identity authentication and management entity after receiving the user real-name registration sent by the user registration unit 11, recording user identity details, sending enterprise authentication application information of the real-name user to an enterprise for authentication, binding the real-name user with the enterprise after the authentication is passed, and providing an identity security authentication basis for transaction processing of a subsequent authorization and authentication module.
3) Character authorization unit 13
The role authorization unit 13 is mainly used for setting role authority for the real-name user after receiving the real-name user and the enterprise binding authentication of the enterprise authentication unit 12, and providing a basis for subsequent payment and transaction authentication.
The payment authorization module 2 is used for applying for payment authority by the non-financial user and issuing the payment authority for the non-financial user by the financial client; the user applies for payment authority on line, which comprises payee information and payment amount information and provides authority judgment basis for setting payment authority for the user in enterprise finance; the enterprise finance sets payment information for the user, wherein the payment information comprises a payee range and a payment amount range, and the payment authority is issued. The payment authorization module 2 is composed of a financial authorization unit 21, an application unit 22 and a rights management unit 23, please refer to fig. 9.
1) Financial authorization unit 21
The main role of the financial authorization unit 21 is that, on the basis of the role and authority setting of the role management unit 13, a user of financial management authority actively issues payment authority for a business by specifying payment information such as an authorized person, setting a payee range, and defining a payment amount range. Or the payment authority applied by the handling user is approved, and an authority judgment basis is provided for the payment of the payment voucher used by the subsequent handling role.
2) Application execution unit 22
The application unit 22 is mainly used for the application authority user to apply for the payment authority on line by reporting the payment amount, the payee and other information on the basis of the role and authority setting of the role management unit 13, so as to provide the authority judgment basis for the subsequent role to pay by using the payment voucher.
3) Rights management unit 23
The authority management unit 23 is mainly used for sending the final feedback information of the financial authorization unit to the financial staff client for modification after receiving the authority information of the payment certificate issued by the financial authorization unit 21, and performing modification maintenance and full-life cycle management of terminating revocation on the payment authority on the basis of the existing information.
And the payment authentication module 3 is used for verifying the identity information and the payment authority of the non-financial user. When the user logs in, the method is used for confirming whether the login information of the user is consistent with the registration information; and when the user submits the payment application, the payment application information is used for confirming whether the payment application information of the user is consistent with the payment authority.
The payment authentication module 3 is composed of a login authentication unit 31 and a payment authentication unit 32, please refer to fig. 10.
1) Login authentication unit 31
The login authentication unit 31 is mainly used for identifying and authenticating the identity of the financial management authority role or the handling authority role during login, and login is performed to the system for relevant operations by using the user identity data of the user registration unit.
2) Payment authentication unit 32
The payment authentication unit 32 is mainly used for paying by using a payment certificate in the authority range by an authority handling user on the basis of the role authorization unit 13, and the authority handling user verifies whether the identity and the payment application of the user conform to the authority range preset by an enterprise.
The purchase and management can use the payment amount that financial affairs approved in advance to accomplish payment to conveniently accomplish payment authentication through modes such as people's face & fingerprint + static password, use the payment authentication mode that corresponds to accomplish payment authentication according to actual payment amount, see table 1:
TABLE 1
The transaction receiving module 4 is used for identifying transaction information, including identifying transaction instructions and processing the transaction instructions meeting the conditions; wherein the transaction processing includes recording transaction details, identifying and formulating a payment plan.
The transaction receiving module 4 is composed of a transaction identification unit 41 and a transaction processing unit 42, please refer to fig. 11.
1) Transaction identification unit 41
The transaction identification unit 41 is mainly used for receiving and identifying the transaction instruction transmitted by the platform partner and transmitting the eligible reservation payment instruction to the transaction processing unit 42 for further processing.
2) Transaction processing unit 42
The transaction processing unit 42 is mainly used for registering related transaction entities, recording transaction details, identifying and making payment plans and providing index guidance for transaction processing of subsequent account processing modules after receiving transaction instructions sent by the transaction identification unit 41.
And the accounting processing module is used for deducting funds according to the payment request and the authentication information and remitting the funds to a specified account according to the payment request. The accounting processing module 5 is composed of a fund deduction unit 51 and a merchant posting unit 52, please refer to fig. 12.
1) Capital deduction and marking unit 51
The fund deduction unit 51 is mainly used for completing the positioning of the public settlement account and deduction of funds through the host after receiving the instruction of the transaction processing unit 42, and returning fund processing state information to the transaction processing unit 42.
2) Merchant posting unit 52
The main function of the merchant account posting unit 52 is to complete information interaction with the fund deducting unit 51 after receiving the payment confirmation instruction from the transaction processing unit 42 to confirm that funds have been deducted from the payer settlement account, and remit the funds to the merchant account specified in the instruction according to the fund remitting instruction initiated by the transaction processing unit 42.
Fig. 13 is a specific embodiment of the online payment method for an enterprise according to the present disclosure, schematically illustrating a workflow diagram of mobile payment authorization, authentication, and payment for an enterprise according to the present disclosure. The specific process is illustrated as follows:
step 701: and the user registers login information, performs public security face real-name authentication, and stores and records the login user name and the binding mobile phone number of the client.
Step 702: and the user registration real-name information enters the enterprise authentication unit for processing, and the real-name user information is bound with the enterprise.
Step 703: the role authorization unit processes and stores the role and authority information of the user.
Step 704: for the enterprise financial management authority user, step 705 is entered, and the financial authorization unit authorizes the payment amount and manages the authority of a certain right-of-office user through a payment authorization module; for non-corporate financial management authorized users, step 711 is entered into the system using the payment credentials within their authorization by logging in the authentication unit.
Step 705: and the financial authorization unit is used for carrying out payment amount authorization and authority management on a certain right-handed user, or the right-handed application unit is used for applying payment amount authorization for the login user.
Step 706: and issuing a payment certificate for the enterprise handling user through the financial authorization unit.
Step 707: the issued payment vouchers are managed and maintained by a rights management unit.
Step 711: and authenticating the login authority of the login handling authority user through the login authentication unit.
Step 712: and the administrative authority user inquires the available payment certificate in the authority through the authority management unit.
Step 713: and the office authority user calls the payment voucher in the authority to pay through the modes of code scanning, transfer remittance and the like.
Step 714: the transaction processing unit processes the received transaction information.
Step 715: and matching and judging the transaction initiated by the handling user and the payment authority thereof through the payment authentication unit.
Step 716: and the fund collection and transfer unit deducts the fund of the public settlement account according to the instruction of the transaction processing unit and enters the account for the payee through the merchant account-entering unit.
Step 717: and updating the full life cycle state of the payment certificate through the authority management unit.
To facilitate an understanding of the present disclosure, another specific embodiment of an online payment processing method for a business is set forth below.
And S1, real-name registration of the office user and association binding with the enterprise are carried out, and the financial staff authorizes the office staff.
S101, submitting personal real-name information to register a user by a handling user at a client, carrying out public security networking check to finish real-name authentication, positioning an enterprise needing to be associated and bound through a U shield ID or an enterprise basic, sending registration information to an enterprise server by a client program, and pushing the registration information to the enterprise needing to be bound;
s102, checking the registered binding relationship with the handling user by a financial management worker through a client;
s103, the financial management personnel user submits financial authorization at the client and sets authorization information such as payment range, amount upper limit, validity period and the like for the handling user;
and S104, the financial management personnel check the authorized information through the client and dynamically manage the authorized information.
And S2, the operator pays by using the payment authority.
S201, a manager logs in a client to inquire available payment authority information under the name;
s202, the merchant two-dimensional code is scanned in a handling mode or a payment two-dimensional code is presented to the merchant;
s203, the system requires the user to pay and authenticate according to the amount of the order;
s204, after the authentication is passed, the payment is successful, and the system updates the information such as the available balance of the payment authority.
The online account moving authority of the existing enterprise can be split and then authorized, the enterprise settlement account fund can be directly used for completing payment when the enterprise deals with online transaction and purchase, the problem of money-charging pain of the enterprise handling is effectively solved, the fund safety risk existing in the enterprise payment process is controlled from the system level, and the online transaction and payment flow of the enterprise is smoothed.
Fig. 14 schematically shows a block diagram of an electronic device according to another embodiment of the present disclosure.
As shown in fig. 14, electronic device 800 includes a processor 810, a computer-readable storage medium 820. The electronic device 800 may perform a method according to an embodiment of the disclosure.
In particular, processor 810 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 810 may also include on-board memory for caching purposes. Processor 810 may be a single processing unit or a plurality of processing units for performing different actions of a method flow according to embodiments of the disclosure.
Computer-readable storage medium 820 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 820 may include a computer program 821, which computer program 821 may include code/computer-executable instructions that, when executed by the processor 810, cause the processor 810 to perform a method flow according to an embodiment of the present disclosure and any variations thereof.
The computer program 821 may be configured with, for example, computer program code comprising computer program modules. For example, in an example embodiment, code in computer program 821 may include one or more program modules, including for example 821A, modules 821B, … …. It should be noted that the division and number of the modules are not fixed, and those skilled in the art can use suitable program modules or program module combinations according to actual situations, and when the program modules are executed by the processor 810, the processor 810 can execute the method flow according to the embodiment of the disclosure and any variation thereof.
The present disclosure also provides a computer-readable storage medium, which may be included in the device/system described in the above embodiments, or may exist separately without being assembled into the device/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the 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 (15)
1. A payment method, comprising:
sending registration information of a non-financial user to a financial client so that the financial client generates authentication information aiming at the registration information, wherein the authentication information is stored in a bank server;
and sending a payment request to a bank server so that the bank server carries out payment processing according to the payment request and the authentication information.
2. A payment method as recited in claim 1, wherein said sending a payment request to a bank server comprises:
calling a payment certificate, wherein the payment certificate is a certificate for payment settlement of a bank;
and sending a payment request to a bank server, wherein the payment request comprises the payment certificate and the transaction information so as to enable the bank server to carry out payment processing.
3. A payment method as recited in claim 1, wherein sending registration information for the non-financial user to the financial client comprises:
submitting registration information to the bank server so that the bank server can identify the registration information; and after the identification is passed, the bank server sends the registration information to the financial client.
4. A payment method, comprising:
acquiring registration information sent by a non-financial client, and generating authentication information aiming at the registration information, wherein the authentication information is stored in a bank server;
and according to the authentication information, the bank server carries out payment processing when receiving a payment request of a non-financial user.
5. A payment method as recited in claim 4, wherein the obtaining registration information sent by the non-financial client comprises:
and acquiring registration information sent by a non-financial client, authenticating, and binding the relationship with the non-financial user.
6. A payment method as recited in claim 5, wherein obtaining registration information sent by the non-financial client further comprises:
and issuing payment authority for the non-financial user or approving the payment authority applied by the non-financial user.
7. A payment method as recited in claim 6, wherein the obtaining registration information sent by the non-financial client comprises:
and modifying, maintaining and stopping the payment authority of the non-financial user, and performing dynamic management.
8. A payment method, comprising:
storing authentication information, wherein the authentication information is generated by a financial client according to registration information sent by a non-financial client;
and acquiring a payment request sent by a non-financial user, and performing payment processing according to the payment request and the authentication information.
9. A payment method as recited in claim 8, wherein the storing authentication information comprises:
acquiring registration information sent by a non-financial client, and identifying the identity of the registration information;
sending the registration information to the financial client, the financial client generating authentication information for the registration information;
and acquiring and storing the authentication information.
10. A payment method as claimed in claim 8, wherein said obtaining a payment request sent by a non-financial user comprises:
acquiring a payment request sent by a non-financial client, and verifying the identity information of the non-financial user;
and obtaining payment voucher information and transaction information, and verifying the payment authority of the non-financial user.
11. The payment method of claim 10, wherein the processing payment according to the payment request and the authentication information comprises:
and deducting funds according to the payment request and the authentication information, and remitting the funds to a specified account according to the payment request.
12. A payment device, comprising:
the non-financial client is used for sending registration information of a non-financial user to the financial client so as to enable the financial client to generate authentication information aiming at the registration information, and the authentication information is stored in the bank server; sending a payment request to a bank server so that the bank server carries out payment processing according to the payment request and authentication information;
the financial client is used for acquiring registration information sent by the non-financial client;
the bank server is used for storing the authentication information; the payment processing system is used for acquiring the payment request sent by the non-financial user and performing payment processing.
13. A payment system, comprising:
the system comprises a user management module, a financial client and a user management module, wherein the user management module is used for receiving registration information of a non-financial user and sending the registration information to the financial client so that the financial client generates authentication information aiming at the registration information;
the payment authorization module is used for applying for payment authority by the non-financial user and issuing the payment authority for the non-financial user by the financial client;
the payment authentication module is used for verifying the identity information and the payment authority of the non-financial user;
the transaction receiving module is used for identifying transaction information;
and the accounting processing module is used for deducting funds according to the payment request and the authentication information and remitting the funds to a specified account according to the payment request.
14. An electronic device, comprising:
a processor;
a memory storing a computer executable program which, when executed by the processor, causes the processor to perform a payment method as claimed in any one of claims 1 to 11.
15. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out a payment method as set forth in any one of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110283727.5A CN112884469A (en) | 2021-03-16 | 2021-03-16 | Payment method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110283727.5A CN112884469A (en) | 2021-03-16 | 2021-03-16 | Payment method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112884469A true CN112884469A (en) | 2021-06-01 |
Family
ID=76040923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110283727.5A Pending CN112884469A (en) | 2021-03-16 | 2021-03-16 | Payment method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112884469A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113706045A (en) * | 2021-09-02 | 2021-11-26 | 工银科技有限公司 | Fund payment method, apparatus, device, medium and program product |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016173043A1 (en) * | 2015-04-30 | 2016-11-03 | 深圳市银信网银科技有限公司 | Payment system based on shared funds-management server, and method, device and server therefor |
| WO2017012447A1 (en) * | 2015-07-20 | 2017-01-26 | 中商交在线（北京）科技发展有限公司 | Payment processing server, payment system, and payment method |
| CN107026815A (en) * | 2016-01-29 | 2017-08-08 | 华为技术有限公司 | A kind of payment transaction processing method, paying server, relevant device and system |
| CN109544159A (en) * | 2018-11-12 | 2019-03-29 | 东莞市大易产业链服务有限公司 | A kind of method of quick authority to pay |
| CN111222965A (en) * | 2018-11-25 | 2020-06-02 | 吴三湖 | Client financial reimbursement management method |
| CN111614642A (en) * | 2016-01-22 | 2020-09-01 | 阿里巴巴集团控股有限公司 | Method, device and system for registration authentication |
| CN112132565A (en) * | 2020-11-24 | 2020-12-25 | 支付宝(杭州)信息技术有限公司 | Payment method and device, electronic equipment and storage medium |
-
2021
- 2021-03-16 CN CN202110283727.5A patent/CN112884469A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016173043A1 (en) * | 2015-04-30 | 2016-11-03 | 深圳市银信网银科技有限公司 | Payment system based on shared funds-management server, and method, device and server therefor |
| WO2017012447A1 (en) * | 2015-07-20 | 2017-01-26 | 中商交在线（北京）科技发展有限公司 | Payment processing server, payment system, and payment method |
| CN111614642A (en) * | 2016-01-22 | 2020-09-01 | 阿里巴巴集团控股有限公司 | Method, device and system for registration authentication |
| CN107026815A (en) * | 2016-01-29 | 2017-08-08 | 华为技术有限公司 | A kind of payment transaction processing method, paying server, relevant device and system |
| CN109544159A (en) * | 2018-11-12 | 2019-03-29 | 东莞市大易产业链服务有限公司 | A kind of method of quick authority to pay |
| CN111222965A (en) * | 2018-11-25 | 2020-06-02 | 吴三湖 | Client financial reimbursement management method |
| CN112132565A (en) * | 2020-11-24 | 2020-12-25 | 支付宝(杭州)信息技术有限公司 | Payment method and device, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113706045A (en) * | 2021-09-02 | 2021-11-26 | 工银科技有限公司 | Fund payment method, apparatus, device, medium and program product |
| CN113706045B (en) * | 2021-09-02 | 2024-05-10 | 工银科技有限公司 | Funds payment method, apparatus, device, medium and program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240029067A1 (en) | Systems and methods for secure provisioning of access to tiered databases | |
| US20200320525A1 (en) | Systems and methods for facilitating account verification over a network | |
| US20200349557A1 (en) | Stored-value card system | |
| US8682753B2 (en) | System and method to consolidate and update a user's financial account information | |
| US20160180302A1 (en) | System and method for processing multiple recurring payments | |
| CN109493038B (en) | Preposition system and method with compulsory notarization function applied to financial industry | |
| CN108369700A (en) | Mobile-payment system | |
| CN103186860A (en) | Electronic payment system based on cloud data processing technology | |
| US20210350454A1 (en) | Method and system for obtaining credit | |
| US10558956B2 (en) | Device and method for facilitating financial transactions | |
| KR20120046571A (en) | System and method for managing mobile gift certificate | |
| EP4038564A1 (en) | Device-based transaction authorization | |
| TW201643789A (en) | Security for electronic transactions and user authentication | |
| WO2022139347A1 (en) | Operating computer for payment, payment system, and payment method | |
| CN112884469A (en) | Payment method, device and system | |
| JP7399672B2 (en) | financial institution system | |
| JP2017510874A (en) | Credit provisioning system and method | |
| KR20130083050A (en) | Banking payment agency system using a virtual account and controlling method therefor | |
| KR20110129735A (en) | The internet loan system where the quick loan is possible | |
| CN113450204A (en) | Enterprise client multi-enterprise account query method and device | |
| KR20110095762A (en) | System and method for providing on-line personal credit loan | |
| US11907801B2 (en) | System for encoding resource access credential in barcode | |
| US9697532B2 (en) | Integrated platform employee transaction processing for buy your own device (BYOD) | |
| KR102234918B1 (en) | method for paying purchase price using mobile telecommunication subscriber information for nonmember | |
| KR20120037436A (en) | Method for on-off line loan service and financial server for the same |
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 |