WO2020006902A1 - 批量支付方法、装置、计算机设备和存储介质 - Google Patents

批量支付方法、装置、计算机设备和存储介质 Download PDF

Info

Publication number
WO2020006902A1
WO2020006902A1 PCT/CN2018/108416 CN2018108416W WO2020006902A1 WO 2020006902 A1 WO2020006902 A1 WO 2020006902A1 CN 2018108416 W CN2018108416 W CN 2018108416W WO 2020006902 A1 WO2020006902 A1 WO 2020006902A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
enterprise
task
bank
end machine
Prior art date
Application number
PCT/CN2018/108416
Other languages
English (en)
French (fr)
Inventor
刘建
宁之孟
魏尧东
金明
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020006902A1 publication Critical patent/WO2020006902A1/zh

Links

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/102—Bill distribution or payments
    • 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/105—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems involving programming of a portable memory device, e.g. IC cards, "electronic purses"

Definitions

  • the present application relates to the field of computers, and in particular, to a batch payment method, device, computer device, and storage medium.
  • the main purpose of this application is to provide a batch payment method, device, computer equipment and storage medium for quickly completing batch payment.
  • this application proposes a batch payment method, which uses an enterprise-end front-end machine set on an enterprise side to perform financial data interaction with a bank.
  • the enterprise-end front-end machine is provided with multiple UKey interfaces, and the enterprise
  • the front-end processor corresponds to a plurality of the UKey interfaces and is configured to complete financial data interaction with multiple bank-end front-end processors of different types of banks; the method includes:
  • a plurality of the payment tasks are respectively sent to a bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine to complete batch payments.
  • the present application also provides a batch payment device, which uses an enterprise-side front-end machine set on the enterprise side to interact with financial data.
  • the enterprise-side front-end machine is provided with multiple UKey interfaces, and the enterprise-side front-end machine corresponds to A plurality of the UKey interfaces are configured to complete financial data interaction with a plurality of bank-side front-end processors of different types of banks; the device includes:
  • An obtaining unit configured to obtain multiple payment account information and at least one receiving account information
  • a establishing unit configured to establish a payment correspondence relationship between the payment account information and the receiving account information, and payment information
  • a generating unit configured to generate multiple payment tasks according to the payment correspondence relationship and payment information
  • a payment unit is configured to send a plurality of the payment tasks to a bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine to complete batch payments.
  • the present application further provides a computer device including a memory and a processor, where the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, implements the steps of any of the foregoing methods.
  • the present application also provides a computer non-volatile readable storage medium having computer-readable instructions stored thereon, which are executed by a processor to implement the steps of the method according to any one of the foregoing.
  • the enterprise-end front-end machine can perform bank-enterprise direct connection functions with a plurality of different types of banks
  • multiple UKey interfaces are set on the enterprise-side front-end machine.
  • the operation is performed directly to realize batch payment, which greatly saves the workload of financial staff and improves the efficiency of transfers.
  • FIG. 1 is a schematic flowchart of a batch payment method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of step S4 in the batch payment method according to an embodiment of the present application.
  • FIG. 3 is a schematic block diagram of a structure of a batch payment device according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a payment unit according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a computer device according to an embodiment of the present application.
  • an embodiment of the present application provides a batch payment method.
  • Financial data is exchanged with a bank by an enterprise-side front-end machine set on an enterprise side.
  • the enterprise-side front-end machine is provided with multiple UKey interfaces.
  • the enterprise The front end processor corresponds to a plurality of the UKey interfaces and is configured to complete financial data interaction with a plurality of different bank end front processors.
  • the above-mentioned enterprise-side front-end machine refers to the front-end machine set on the enterprise side, and is an intermediate device when the enterprise-side financial system is directly connected with the bank-bank-enterprise.
  • the foregoing enterprise-side front-end machine is configured to complete data interaction with a plurality of different types of bank-side front-end machines.
  • the configuration process is that when an enterprise-side front-end machine is installed, the enterprise-side front-end machine has an administrator interface. Enter the specified configuration information in the preset interface.
  • the configuration information includes the enterprise ID, the enterprise front-end processor number, the bank server IP, the bank port, the bank-enterprise direct connection number of the bank, and the bank-end front-end processor version number.
  • Banks and other corporate financial systems and banks complete the necessary parameters for direct bank-enterprise integration, and configure the number of threads to configure multi-threaded tasks; then send the configuration results to the application corresponding to the enterprise front-end processor server. That is, configure the bank-enterprise direct account number and related information that are applied for.
  • each bank-enterprise direct account When an enterprise needs to log in to each bank-enterprise direct account to obtain data (transaction data, query data, etc.) in its corresponding bank, it only needs to be in the enterprise.
  • the corresponding UKey (a small storage device directly connected to the computer via USB, with password verification function, and reliable and high speed) can be inserted into the front-end machine, which can realize an enterprise-side front-end machine and a number of different types of banks.
  • the front-end of the enterprise can easily obtain the account information, transaction flow information, and balance information of each bank-enterprise direct account of the enterprise, and can perform related operations such as payment, collection, and transfer.
  • the above major banks refer to different banks.
  • ICBC and China Construction Bank belong to two different major banks, that is, banks using different front-end processors are considered to be different major banks.
  • the above method includes steps:
  • the payment account information refers to the account information corresponding to the bank where the enterprise side opens the direct bank-enterprise connection.
  • the account information generally includes the bank name, account information, etc .; the aforementioned receiving account information is not required to be the account information corresponding to the bank where the enterprise opens the bank-enterprise direct link.
  • the multiple payment account information refers to two or more payment account information; the at least one receiving account information refers to one or more receiving account information.
  • the above-mentioned payment correspondence relationship refers to a correspondence relationship in which a payment account is transferred to which receiving account.
  • one payment account may correspond to multiple payment accounts, and similarly, one payment account may correspond to multiple payment accounts.
  • the above payment information may include specific transfer amount information, transfer reason remark information, prompt information (receipt of short payment, payment short message), and the like.
  • the above-mentioned establishment of the payment correspondence relationship between the payment account information and the collection account information, and the process of payment information include multiple situations. The first is: receiving a manual command from the financial staff at the enterprise side to implement the connection, specifically The above financial system provides a configuration interface.
  • the financial staff configures the payment account information in the payment account information column, the payment account information in the payment account information column, and then configures different payment information according to the transfer requirements.
  • the second type is: Set the completed configuration information (the configuration information includes specific payment account information and payment account information, as well as payment information, etc., specifically, which payment account information corresponds to which payment account information corresponds in advance, and the corresponding Payment information, etc.), the configuration information is automatically configured to the payment account column and the receiving account column according to a preset time. For example, the enterprise side needs to set the specified amount of the a bank account, the specified amount of the b bank account, and the c bank every day.
  • the specified amount of the account is collected into the d bank account, where a bank account , B bank accounts, c bank accounts for different categories of banks, it can be configured to automatically reach the transfer time may be automatically configured without financial staff for processing.
  • the above payment task is a payment task generated according to the correspondence between the payment account and the receiving account, and payment information, such as generating the payment task of the a bank account (payment account) to the d bank account (receiving account), b The payment task from the bank account (payment account) to the d bank account (receiving account), the payment task from the c bank account (payment account) to the d bank account (receiving account), and so on.
  • the plurality of payment tasks are respectively sent to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine to complete batch payment.
  • step S4 there are multiple UKey interfaces preset on the front-end of the enterprise side, that is, multiple UKeys can be inserted.
  • the corresponding bank account can be used to perform transfers, inquiries, etc., and In the case of transferring funds from multiple different bank accounts, there is no need to switch logins, etc., and operations can be performed directly to achieve batch payments, which greatly saves the workload of financial staff and improves the efficiency of transfers.
  • different payment tasks are sent to the bank-end front-end machine corresponding to different payment accounts through the same enterprise-end front-end machine to send the payment task to the service system of the corresponding bank to complete the payment task.
  • the foregoing multiple sending payment tasks are respectively sent to the bank-side front-end machine corresponding to the payment account through the enterprise-side front-end machine to complete step S4 of batch payment.
  • the foregoing multiple sending payment tasks are respectively sent to the bank-side front-end machine corresponding to the payment account through the enterprise-side front-end machine to complete step S4 of batch payment.
  • the payment task is not directly sent to the enterprise-side front-end machine, but is sent to the application server corresponding to the enterprise-side front-end machine.
  • the application server refers to the first server that provides the enterprise-side front-end machine to the enterprise.
  • the three-party application server serves as the management background of the enterprise-side front-end machine.
  • the tasks issued by the enterprise will first enter the above application server, and then the application server will send the enterprise-side front-end machine.
  • the above task ID is only an identifier, and the identifier uniquely corresponds to the payment task.
  • the task ID does not have a task content, so as to prevent the packets of the payment task from being directly placed on the enterprise-side front-end processor, which affects the enterprise-side front-end processor.
  • the preset cache queue generally includes a transaction cache queue and a query cache queue. Different cache queues store task IDs of corresponding attributes, and correspondingly set a transaction thread pool and a query thread pool.
  • the front end of the enterprise When the front end of the enterprise obtains the task ID, it first determines the attributes of the task ID.
  • the attributes include transaction attributes and query attributes. Because the task ID belongs to the transaction class, it is placed in the transaction cache queue.
  • the tasks in the two cache queues are sorted according to priority. Each task will be set with a type identifier. The type identifier is divided into 1-8 levels. If it is 1, the highest level, which represents emergency tasks.
  • Priority processing can be based on presets. Pre-set rules, according to the specific request attached to the corresponding priority level, for example, the level of payment is higher than the level of query bank flow.
  • the task types are the same, they are sorted according to the task generation time.
  • the task ID fed back by the front-end server of the enterprise refers to that if the thread pool corresponding to the cache queue is free, the task is obtained from the cache queue, and because only the task ID is in the cache queue at this time,
  • the enterprise front end will return the task ID to the above application server.
  • the application server will generate or call the corresponding payment task according to the returned task ID, and then the payment task will be sent to the enterprise front end to facilitate the enterprise front end. Forward the payment task to the bank front-end machine.
  • the payment task obtained by the application server according to each of the task IDs is sent to the bank-side front-end machine through the enterprise-side front-end machine to complete the corresponding payment task.
  • the payment task is for a bank account (payment account) that needs to transfer money out
  • the payment task will include the number of the bank-side front-end processor corresponding to the payment account and the corresponding bank server IP. These information are all configured and sent to the application server corresponding to the enterprise-end front-end processor when the enterprise-end front-end processor is installed. The above application server will automatically write these information into the message according to the request of the task ID, so that the front end of the enterprise side connects to the corresponding front end of the bank.
  • the above-mentioned enterprise-side front-end machine After receiving the payment task, the above-mentioned enterprise-side front-end machine will parse out the required information first, such as the number of the bank-side front-end machine, the corresponding bank server IP, and then send the payment task to the corresponding bank front-end machine accurately. , The bank front-end machine then forwards it to the bank server to complete the corresponding payment action.
  • the method before the step of sending a plurality of the payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine, to complete the batch payment S4, the method includes:
  • the identifiers corresponding to the types of banks of the UKey devices inserted in each UKey interface are collected, and then the identifiers are compared with the identifiers representing various types of banks configured when the front-end processor of the enterprise is configured.
  • the collected logos fully cover the logos representing various types of banks configured when the enterprise-end front end is configured, then it is determined that UKey devices corresponding to various types of banks are inserted into the enterprise-end front end. Otherwise, the uncovered
  • the bank type corresponding to the identification is extracted and sent to the relevant personnel of the enterprise to report the alarm.
  • the relevant personnel of the enterprise can take corresponding measures to re-insert the UKey device that has forgotten to be inserted or the insertion place is loose, resulting in poor contact of the UKey device.
  • the method before the step of sending a plurality of the payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine, to complete the batch payment S4, the method includes:
  • the method for obtaining the balance information of the payment account includes: sending, through an application server, a plurality of balance query task IDs corresponding to the balance query tasks of the payment account to the enterprise-end front-end machine, wherein the enterprise The front-end processor stores a plurality of the balance query task IDs into a preset cache queue; when the balance query task IDs in the cache queue turn, the enterprise-end front-end processor feedbacks the balance query task IDs to the application server
  • the application server obtains the corresponding balance inquiry task message according to the balance inquiry task ID, and sends it again to the enterprise front end machine; and then the enterprise side front end machine sends the balance inquiry task message to the corresponding bank end Front-end machine, the bank-end front-end machine sends the balance inquiry task message to the corresponding bank server for balance inquiry, and returns the balance information to the financial system in the original way.
  • step S412 if the balance information of a payment account is less than the amount to be transferred, an alarm is issued to remind the financial staff of the enterprise that there is a problem with the transfer. You can send an email, text message, pop-up window, sound / light Wait for one or more combinations. .
  • the batch payment method further includes:
  • the enterprise-side front-end unit and application server should be online for a long time, but because it is an electronic product, it will inevitably be caused by failure or upgrade. At this time, the enterprise-side front-end unit and the application server may be disconnected. To detect the connection status of the two. When the connection between the two fails, an alarm message needs to be issued. Sending out alarm information includes sending information such as emails to relevant personnel of the enterprise, and / or to relevant personnel of third parties that provide enterprise-side front-end processors.
  • the batch payment method further includes:
  • the application server and the enterprise-end front end use the block input output (BIO) synchronous blocking mode for a long connection to complete task interaction.
  • BIO block input output
  • Different payment tasks cannot be performed at the same time, so they need to be performed in accordance with the order of instructions.
  • One instruction can be executed before the next instruction can be executed. It cannot be executed asynchronously, so the BIO synchronous blocking mode is used in this application to make the application server and the enterprise front-end processor long. connection.
  • the batch payment method further includes:
  • Protocol Buffers It is a lightweight and efficient structured data storage format, which can be used for serialization of structured data, or serialization. It is very suitable for data storage or RPC data exchange format. Language-independent, platform-independent, and extensible serialization structure data format that can be used in communication protocols, data storage, etc., simply The main advantages of Protobuf are: simple and fast. This application uses GOOGLE's Protocol Buffers for serialization, which can improve the efficiency of message packaging and sending.
  • the enterprise-end front-end machine can perform direct bank-enterprise functions with a plurality of different types of banks
  • multiple UKey interfaces are set on the enterprise-side front-end machine to ensure the integrity of each bank account. Normal use; when the corresponding UKey is inserted, you can use the corresponding bank account for transfers, inquiries, etc., and in the case of multiple different bank accounts for transfers, you can directly operate without switching logins, etc.
  • the batch payment greatly saves the workload of financial staff and improves the efficiency of transfers.
  • an embodiment of the present application further provides a batch payment device, which is characterized in that an enterprise-side front-end machine set on an enterprise side performs financial data interaction with a bank side, and the enterprise-side front-end machine is provided with multiple UKeys. Interface, the enterprise-end front-end processor corresponding to a plurality of the UKey interfaces is configured to complete financial data interaction with a plurality of different bank-end front-end processors.
  • the above-mentioned enterprise-side front-end machine refers to the front-end machine set on the enterprise side, and is an intermediate device when the enterprise-side financial system is directly connected with the bank-bank-enterprise.
  • the foregoing enterprise-side front-end machine is configured to complete data interaction with a plurality of different types of bank-side front-end machines.
  • the configuration process is that when an enterprise-side front-end machine is installed, the enterprise-side front-end machine has an administrator interface. Enter the specified configuration information in the preset interface.
  • the configuration information includes the enterprise ID, the enterprise front-end processor number, the bank server IP, the bank port, the bank-enterprise direct connection number of the bank, and the bank-end front-end processor version number.
  • Banks and other corporate financial systems and banks complete the necessary parameters for direct bank-enterprise integration, and configure the number of threads to configure multi-threaded tasks; then send the configuration results to the application corresponding to the enterprise front-end processor server. That is, configure the bank-enterprise direct account number and related information that are applied for.
  • each bank-enterprise direct account When an enterprise needs to log in to each bank-enterprise direct account to obtain data (transaction data, query data, etc.) in its corresponding bank, it only needs to be in the enterprise.
  • the corresponding UKey (a small storage device directly connected to the computer via USB, with password verification function, and reliable and high speed) can be inserted into the front-end machine, which can realize an enterprise-side front-end machine and a number of different types of banks.
  • the front-end of the enterprise can easily obtain the account information, transaction flow information, and balance information of each bank-enterprise direct account of the enterprise, and can perform related operations such as payment, collection, and transfer.
  • the above major banks refer to different banks.
  • ICBC and China Construction Bank belong to two different major banks, that is, banks using different front-end processors are considered to be different major banks.
  • the above devices include:
  • the obtaining unit 10 is configured to obtain multiple payment account information and at least one payment account information.
  • the payment account information refers to account information corresponding to a bank that is directly connected between a bank and an enterprise on the enterprise side.
  • the account information generally includes the bank name, account information, etc .; the aforementioned receiving account information is not required to be the account information corresponding to the bank where the enterprise opens the bank-enterprise direct link.
  • the multiple payment account information refers to two or more payment account information; the at least one receiving account information refers to one or more receiving account information.
  • a establishing unit 20 configured to establish a payment correspondence relationship between the payment account information and the receiving account information, and payment information
  • a generating unit 30 is configured to generate multiple payment tasks according to the payment correspondence relationship and payment information.
  • the aforementioned payment correspondence relationship refers to a correspondence relationship in which a payment account is transferred to which receiving account.
  • one payment account may correspond to multiple payment accounts, and similarly, one payment account may correspond to multiple payment accounts.
  • the above payment information may include specific transfer amount information, transfer reason remark information, prompt information (receipt of short payment, payment short message), and the like.
  • the above-mentioned establishment of the payment correspondence relationship between the payment account information and the collection account information, and the process of payment information include multiple situations. The first is: receiving a manual command from the financial staff at the enterprise side to implement the connection, specifically The above financial system provides a configuration interface.
  • the financial staff configures the payment account information in the payment account information column, the payment account information in the payment account information column, and then configures different payment information according to the transfer requirements.
  • the second type is: Set the completed configuration information (the configuration information includes specific payment account information and payment account information, as well as payment information, etc., specifically, which payment account information corresponds to which payment account information corresponds in advance, and the corresponding Payment information, etc.), the configuration information is automatically configured to the payment account column and the receiving account column according to a preset time. For example, the enterprise side needs to set the specified amount of the a bank account, the specified amount of the b bank account, and the c bank every day.
  • the specified amount of the account is collected into the d bank account, where a bank account , B bank accounts, c bank accounts for different categories of banks, it can be configured to automatically reach the transfer time may be automatically configured without financial staff for processing.
  • the above payment task is a payment task generated according to the correspondence between the payment account and the receiving account, and payment information, such as generating the payment task of the a bank account (payment account) to the d bank account (receiving account), b The payment task from the bank account (payment account) to the d bank account (receiving account), the payment task from the c bank account (payment account) to the d bank account (receiving account), and so on.
  • the payment unit 40 is configured to send a plurality of the payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine to complete batch payment.
  • the payment unit 40 there are multiple UKey interfaces preset on the front-end of the enterprise side, that is, multiple UKeys can be inserted. After the corresponding UKey is inserted, the corresponding bank account can be used for transfers, inquiries, etc. Moreover, in the case of transferring funds from multiple different bank accounts, there is no need to switch logins, etc., and operations can be performed directly, thereby realizing batch payment, which greatly saves the workload of financial staff and improves the transfer efficiency. In this application, different payment tasks are sent to the bank-end front-end machine corresponding to different payment accounts through the same enterprise-end front-end machine to send the payment task to the service system of the corresponding bank to complete the payment task.
  • the payment unit 40 includes:
  • a sending module 41 is configured to send a plurality of the payment tasks to an application server corresponding to the enterprise-end front-end processor, and generate a task ID of each of the payment tasks through the application server;
  • a forwarding module 42 is configured to send each of the task IDs to the enterprise-end front end machine through the application server, wherein the enterprise-side front end machine stores the task ID in a preset cache queue ;
  • the payment task is not directly sent to the enterprise-side front-end machine, but is sent to the application server corresponding to the enterprise-side front-end machine.
  • the application server refers to providing the enterprise-side front-end to the enterprise.
  • the third-party application server of the computer serves as the management background of the enterprise-side front-end machine.
  • Tasks issued by the enterprise first enter the above application server, and then the application server sends the enterprise-side front-end machine.
  • the above task ID is only an identifier, and the identifier uniquely corresponds to the payment task.
  • the task ID does not have a task content, so as to prevent the packets of the payment task from being directly placed on the enterprise-side front-end processor, which affects the enterprise-side front-end processor.
  • the enterprise-end front-end unit of this application can be connected to multiple bank-side front-end units, there will be many different tasks, and the packets of various tasks will be directly stacked in the front-end unit's cache, which will greatly reduce The operation efficiency of the front end of the enterprise side even crashed.
  • the preset cache queue generally includes a transaction cache queue and a query cache queue.
  • Different cache queues store task IDs of corresponding attributes, and correspondingly set a transaction thread pool and a query thread pool.
  • the front end of the enterprise obtains the task ID, it first determines the attributes of the task ID.
  • the attributes include transaction attributes and query attributes. Because the task ID belongs to the transaction class, it is placed in the transaction cache queue.
  • the tasks in the two cache queues are sorted according to priority. Each task will be set with a type identifier. The type identifier is divided into 1-8 levels. If it is 1, the highest level, which represents emergency tasks.
  • Priority processing can be based on presets. Pre-set rules, according to the specific request attached to the corresponding priority level, for example, the level of payment is higher than the level of query bank flow.
  • the task types are the same, they are sorted according to the task generation time.
  • An obtaining module 43 is configured to receive a task ID fed back by the enterprise-end front-end machine through the application server, and use the application server to obtain a corresponding payment task according to the task ID and send the payment task to the enterprise-end front-end machine.
  • the task ID fed back by the enterprise-end front-end processor refers to that if there is idle in the thread pool corresponding to the cache queue, the task is obtained from the cache queue, and because only the task ID is in the cache queue at this time, Therefore, the enterprise front end will return the task ID to the application server, and the application server will generate or call the corresponding payment task according to the returned task ID, and then the payment task will be sent to the enterprise front end to facilitate the enterprise front end.
  • the machine forwards the payment task to the bank front-end machine.
  • a payment module 44 is configured to send the payment task obtained by the application server according to each of the task IDs to the bank-side front-end machine through the enterprise-side front-end machine to complete the corresponding payment task.
  • the payment task because the payment task is for a bank account (payment account) that requires external transfer, the payment task will include the number of the bank front-end machine corresponding to the payment account and the corresponding bank server. IP and other information are all configured and sent to the application server corresponding to the enterprise-end front-end processor when the enterprise-end front-end processor is installed. The above application server will automatically write these information into the message according to the request of the task ID, so that the front end of the enterprise side connects to the corresponding front end of the bank.
  • the above-mentioned enterprise-side front-end machine After receiving the payment task, the above-mentioned enterprise-side front-end machine will parse out the required information first, such as the number of the bank-side front-end machine, the corresponding bank server IP, and then send the payment task to the corresponding bank front-end machine accurately. , The bank front-end machine then forwards it to the bank server to complete the corresponding payment action.
  • the batch payment device further includes:
  • a judging unit configured to judge whether a UKey device corresponding to various types of banks is inserted into the front end of the enterprise
  • the first alarm unit is configured to alarm if UKey devices corresponding to various types of banks are not plugged into the enterprise-end front-end machine.
  • the identifiers corresponding to the types of banks of the UKey devices inserted in each UKey interface are collected, and then the identifiers are compared with the identifiers representing various types of banks configured when the front-end processor of the enterprise is configured, If the collected logos fully cover the logos representing the various types of banks configured when the enterprise-end front end is configured, it is determined that UKey devices corresponding to various types of banks are inserted into the enterprise-end front end, otherwise, they will not be covered.
  • the type of bank corresponding to the ID is extracted and sent to the relevant personnel of the enterprise to report the alarm.
  • the relevant personnel of the enterprise can take corresponding measures to re-insert the UKey device that has forgotten to be inserted or the insertion place is loose, resulting in poor contact of the UKey device. Etc. to ensure the interaction between the business and the banks.
  • the batch payment device further includes:
  • a balance inquiry unit is used to obtain balance information of each payment account.
  • the method for obtaining balance information of a payment account includes: sending, through an application server, a balance inquiry task ID corresponding to a plurality of balance inquiry tasks of the payment account to the enterprise-end front-end machine, wherein the The front end of the enterprise stores multiple balance query task IDs into a preset cache queue. When the balance query task ID in the cache queue is turned on, the front end of the enterprise feedbacks the balance query task ID to the application.
  • a server an application server obtains a corresponding balance inquiry task message according to the balance inquiry task ID, and sends it again to the enterprise-end front-end machine; and then the enterprise-side front-end machine sends the balance inquiry task message to the corresponding bank Front-end processor, the bank-end front-processor sends the balance inquiry task message to the corresponding bank server for balance inquiry, and feeds back the balance information to the financial system.
  • a second alarm unit is configured to issue an alarm if the balance information is less than the amount to be transferred.
  • the second alarm unit if the balance information of a payment account is less than the amount to be transferred, an alarm is issued to remind the financial staff of the enterprise that there is a problem with the transfer, and you can send an email, text message, pop-up window, or sound / Light and other combinations. .
  • the batch payment device further includes:
  • the connection detection unit is used to determine the connection status of the application server and the enterprise-end front-end processor. If the connection status is disconnected, an alarm message is issued.
  • connection detection unit the enterprise-side front-end unit and the application server should be online for a long time, but because it is an electronic product, it will inevitably be caused by failure or upgrade. At this time, the enterprise-side front-end unit and the application server may lose the connection.
  • Heartbeat detection is used to detect the connection status of the two. When the connection between the two fails, an alarm message needs to be issued.
  • Sending out alarm information includes sending information such as emails to relevant personnel of the enterprise, and / or to relevant personnel of third parties that provide enterprise-side front-end processors.
  • the batch payment device further includes:
  • the BIO synchronization blocking unit is configured to control the application server to send a payment task to the enterprise-end front-end processor through the BIO synchronization blocking mode.
  • the application server and the enterprise-end front end use the block input output (BIO) synchronous blocking mode for a long connection to complete task interaction.
  • BIO block input output
  • Different payment tasks cannot be performed at the same time, so they need to be performed in accordance with the order of instructions.
  • One instruction can be executed before the next instruction can be executed. It cannot be executed asynchronously, so the BIO synchronous blocking mode is used in this application to make the application server and the enterprise front-end processor long connection.
  • the above-mentioned batch payment device further includes:
  • a serialization unit is configured to serialize tasks using Protocol Buffers when the tasks are mutually sent by the application server and the enterprise-end front-end processor.
  • Protocol Buffers It is a lightweight and efficient structured data storage format, which can be used for serialization of structured data, or serialization. It is very suitable for data storage or RPC data exchange format. Language-independent, platform-independent, and extensible serialization structure data format that can be used in communication protocols, data storage, etc., simply The main advantages of Protobuf are: simple and fast. This application uses GOOGLE's Protocol Buffers for serialization, which can improve the efficiency of message packaging and sending.
  • the enterprise-end front-end machine can perform bank-enterprise direct connection functions with a plurality of different types of banks, multiple UKey interfaces are set on the enterprise-side front-end machine to ensure the Normal use; when the corresponding UKey is inserted, you can use the corresponding bank account for transfers, inquiries, etc., and in the case of multiple different bank accounts for transfers, you can directly operate without switching logins, etc.
  • the batch payment greatly saves the workload of financial staff and improves the efficiency of transfers.
  • an embodiment of the present application further provides a computer device.
  • the computer device may be a server, and its internal structure may be as shown in FIG.
  • the computer device includes a processor, a memory, a network interface, and a database connected through a system bus.
  • the computer design processor is used to provide computing and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium stores an operating system, computer-readable instructions, and a database.
  • the memory provides an environment for operating systems and computer-readable instructions in a non-volatile storage medium.
  • the database of the computer equipment is used to store batch payment method programs and the like.
  • the network interface of the computer device is used to communicate with an external terminal through a network connection.
  • the computer-readable instructions are executed by a processor to implement a batch payment method.
  • the processor executes the batch payment method and uses the enterprise-side front-end machine set on the enterprise side to exchange financial data with the bank side.
  • the enterprise-side front-end machine is provided with multiple UKey interfaces, and the enterprise-side front-end machine corresponds to multiple Each of the UKey interfaces is configured to complete financial data interaction with a plurality of bank-end front-end processors of different types of banks; the method includes: obtaining a plurality of payment account information and at least one receiving account information; establishing the Payment correspondence between payment account information and the receiving account information, and payment information; generating multiple payment tasks based on the payment correspondence and payment information; and dividing the plurality of payment tasks by the enterprise-end front-end machine And sending it to a bank-end front end corresponding to the payment account to complete a batch payment.
  • the step of sending multiple payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine, respectively, to complete the batch payment step includes: Sending the payment task to an application server corresponding to the front-end server of the enterprise, and generating a task ID of each of the payment tasks through the application server; and sending each of the task ID to the front of the enterprise through the application server Machine installation, wherein the enterprise-end front-end machine stores the task ID in a preset cache queue; receiving the task ID fed back by the enterprise-side front-end machine through the application server, and using the application
  • the server obtains the corresponding payment task according to the feedback task ID and sends the payment task to the enterprise-side front-end processor; and sends the payment task obtained by the application server according to each of the task IDs to the enterprise-side front-end processor through the enterprise-side front-end processor.
  • the bank front-end machine is described to complete the corresponding payment task.
  • the method before sending the plurality of payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine, to complete the batch payment, the method includes: Describes whether UKey devices corresponding to various types of banks are plugged into the front end of the enterprise; if not, an alarm is issued.
  • the method before sending the multiple payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-side front-end machine, to complete the batch payment step S4, the method includes: The balance information of each payment account; if the balance information is less than the amount to be transferred, an alarm is issued.
  • the above-mentioned batch payment method further includes: judging a connection status of the application server and the enterprise-end front-end processor; if the connection status is disconnected, sending out an alarm message.
  • the above-mentioned batch payment method further includes: controlling the application server to send a payment task to the enterprise-end front-end machine through a BIO synchronization blocking mode.
  • the above-mentioned batch payment method further includes: when using the application server and the enterprise-end front-end processor to send tasks to each other, adopting Protocol for the tasks Buffers are serialized.
  • FIG. 5 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied.
  • the enterprise-end front-end can perform bank-enterprise direct connection functions with a plurality of different types of banks
  • multiple UKey interfaces are set on the enterprise-end front-end to ensure the normality of each bank account. Use; After inserting the corresponding UKey, you can use the corresponding bank account for transfers, inquiries, etc., and in the case of multiple different bank accounts for transfers, you can directly operate without switching logins, etc., and realize batches. Payment greatly saves the workload of financial staff and improves the efficiency of transfers.
  • An embodiment of the present application further provides a computer non-volatile readable storage medium, which stores computer-readable instructions.
  • a batch payment method is implemented, and an enterprise set by an enterprise is used.
  • the front-end processor performs financial data interaction with the bank.
  • the enterprise-end front-end processor is provided with multiple UKey interfaces.
  • the enterprise-end front-end processor is configured to correspond to multiple UKey interfaces and can be configured with multiple different bank types.
  • a bank-end front-end processor completes financial data interaction; the method includes: acquiring multiple payment account information and at least one receiving account information; establishing a payment correspondence relationship between the payment account information and the receiving account information, And payment information; generating a plurality of payment tasks according to the payment correspondence and payment information; and sending the plurality of payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-side front-end machine, To complete a batch payment.
  • the enterprise-end front-end machine can perform direct bank-enterprise functions with multiple different types of banks
  • multiple UKey interfaces are set on the enterprise-end front-end machine to ensure the normal use of each bank account; when After inserting the corresponding UKey, you can use the corresponding bank account to perform transfers and inquiries, and in the case of multiple different bank accounts, you can directly perform operations without switching logins, etc., and then realize batch payments, greatly This saves the workload of financial staff and improves the efficiency of transfers.
  • the step of sending multiple payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine, respectively, to complete the batch payment step includes: Sending the payment task to an application server corresponding to the front-end server of the enterprise, and generating a task ID of each of the payment tasks through the application server; and sending each of the task ID to the front of the enterprise through the application server Machine installation, wherein the enterprise-end front-end machine stores the task ID in a preset cache queue; receiving the task ID fed back by the enterprise-side front-end machine through the application server, and using the application
  • the server obtains the corresponding payment task according to the feedback task ID and sends the payment task to the enterprise-side front-end processor; and sends the payment task obtained by the application server according to each of the task IDs to the enterprise-side front-end processor through the enterprise-side front-end processor.
  • the bank front-end machine is described to complete the corresponding payment task.
  • the method before sending the plurality of payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-end front-end machine, to complete the batch payment, the method includes: Describes whether UKey devices corresponding to various types of banks are plugged into the front end of the enterprise; if not, an alarm is issued.
  • the method before sending the multiple payment tasks to the bank-side front-end machine corresponding to the payment account through the enterprise-side front-end machine, to complete the batch payment step S4, the method includes: The balance information of each payment account; if the balance information is less than the amount to be transferred, an alarm is issued.
  • the above-mentioned batch payment method further includes: judging a connection status of the application server and the enterprise-end front-end processor; if the connection status is disconnected, sending out an alarm message.
  • the above-mentioned batch payment method further includes: controlling the application server to send a payment task to the enterprise-end front-end machine through a BIO synchronization blocking mode.
  • the above-mentioned batch payment method further includes: when using the application server and the enterprise-end front-end processor to send tasks to each other, adopting Protocol for the tasks Buffers are serialized.
  • Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory can include random access memory (RAM) or external cache memory.
  • RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual-speed data rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种批量支付方法、装置、计算机设备和存储介质，包括获取多个支付账户信息，以及至少一个收款账户信息（S1）；建立支付账户信息与收款账户信息的支付对应关系，以及支付信息（S2）；根据支付对应关系和支付信息生成多个支付任务（S3）；通过企业端前置机将多个支付任务分别发送给与支付账户对应的银行端前置机，以完成批量支付（S4）。

Description

批量支付方法、装置、计算机设备和存储介质
本申请要求于2018年7月2日提交中国专利局、申请号为2018107086707，申请名称为“批量支付方法、装置、计算机设备和存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及到计算机领域，特别是涉及到一种批量支付方法、装置、计算机设备和存储介质。
 背景技术
传统支付方法中，当需要企业端使用多个支付账户给其它的账户转钱时，需要登录不同的支付账户，登录哪一个支付账户后，需要选择对应的企业端前置机，并插入对应的UKey，操作繁琐。
 技术问题
本申请的主要目的为提供一种快速完成批量支付的批量支付方法、装置、计算机设备和存储介质。
 技术解决方案
为了实现上述发明目的，本申请提出一种批量支付方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
获取多个支付账户信息，以及至少一个收款账户信息；
建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
根据所述支付对应关系和支付信息生成多个支付任务；
通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
本申请还提供一种批量支付装置，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述装置，包括：
获取单元，用于获取多个支付账户信息，以及至少一个收款账户信息；
建立单元，用于建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
生成单元，用于根据所述支付对应关系和支付信息生成多个支付任务；
支付单元，用于通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
本申请还提供一种计算机设备，包括存储器和处理器，所述存储器存储有计算机可读指令，所述处理器执行所述计算机可读指令时实现上述任一项所述方法的步骤。
本申请还提供一种计算机非易失性可读存储介质，其上存储有计算机可读指令，所述计算机可读指令被处理器执行时实现上述任一项所述的方法的步骤。
 有益效果
本申请的批量支付方法、装置、计算机设备和存储介质，因为企业端前置机能够与多个不同种类的银行进行银企直联功能，所以在企业端前置机上设置了多个UKey接口，以保证各个银行账户的正常使用；当插入对应的UKey之后，既可以使用对应的银行账户进行转账、查询等工作，而且在多个不同的银行账户进行转账的情况下，无需切换登录等，可以直接进行操作，进而实现批量支付，大大地节约了财务人员的工作量，以及提高转账效率。
 附图说明
图1 为本申请一实施例的批量支付方法的流程示意图；
图2 为本申请一实施例的上述批量支付方法中步骤S4的流程示意图；
图3 为本申请一实施例的批量支付装置的结构示意框图；
图4 为本申请一实施例的支付单元的结构示意框图；
图5 为本申请一实施例的计算机设备的结构示意框图。
 本发明的最佳实施方式
参照图1，本申请实施例提供一种批量支付方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互。
上述的企业端前置机是指设置在企业端的前置机，是企业端财务系统与银行端进行银企直联时的中间设备。上述企业端前置机被配置为可以与多个不同银行种类的银行端前置机完成数据交互，配置过程为，当企业安装企业端前置机时，企业端前置机有一个管理员界面，在预设的界面内输入指定的配置信息，该配置信息包括企业ID、企业端前置机编号、银行服务器IP、银行端口、银行的银企直联编号、银行端前置机的版本号，银行大类等企业财务系统与银行完成银企直联的必要参数，还会配置线程数大小配置等，以实现多线程任务的处理；然后将配置结果发送给企业端前置机对应的应用服务器。也就是，配置申请通过的银企直联的账号及其相关信息，当企业需要登录各银企直联的账户获取在其对应银行的数据时（交易数据、查询数据等），只需要在企业端前置机上插入对应的UKey（一种通过USB直接与计算机相连、具有密码验证功能、可靠高速的小型存储设备）即可，实现一个企业端前置机与多个不同类银行的银行端前置机连接，企业统一集中管理用户的银行UKey，无需做银行的切换操作。通过企业端前置机可以方便地获取企业的每个银企直联账户的账户信息、交易流水信息、余额信息，并且可以进行相关的支付、归集、调拨等相关操作。上述银行大类是指不同的银行，比如工商银行与建设银行属于两个不同的银行大类等，即使用不同前置机的银行被认为是不同的银行大类。
上述方法，包括步骤：
S1、获取多个支付账户信息，以及至少一个收款账户信息；
在上述步骤S1中，上述支付账户信息是指企业端开启银企直联的银行对应的账户信息。账户信息一般包括银行名字、账号信息等；上述收款账户信息则不规定是企业端开启银企直联的银行对应的账户信息。上述多个支付账户信息是指两个或两个以上的支付账户信息；上述至少一个收款账户信息是指有一个或一个以上的收款账户信息。
S2、建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
S3、根据所述支付对应关系和支付信息生成多个支付任务；
在上述步骤S2和S3中，上述的支付对应关系是指，哪一个支付账户向哪一个收款账户进行转账的对应关系。在一个实施例中，一个支付账户可以对应多个收款账户，同样的，一个收款账户可以对应多个支付账户。上述支付信息可以包括具体的转账金额信息、转账原因备注信息、提示信息（收款短息、付款短信）等。上述建立所设所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息的过程，包括多种情况，第一种为：接收企业端的财务人员的手动命令实现连接，具体地，上述财务系统提供一个配置界面，财务人员在支付账户信息一列配置支付账户信息，在收款账户信息一列配置收款账户信息，然后根据转账要求配置不同的支付信息等；第二种为：预设配置完成的配置信息（该配置信息包括具体的支付账户信息和收款账户信息、以及支付信息等，具体地，事先配置好哪一个支付账户信息对应哪一个收款账户信息对应，以及对应的支付信息等），按照预设的时间自动将配置信息配置到支付账户一列和收款账户一列等，比如，企业端每天都需要将a银行账户的指定金额、b银行账户的指定金额、c银行账户的指定金额归集到d银行账户中，其中a银行账户、b银行账户、c银行账户为不同大类银行，则可以自动进行配置，到达转账时间既可以自动配置，无需财务人员进行处理。上述支付任务，即为根据支付账户与收款账户的对应关系，支付信息等生成的支付任务，如生成上述a银行账户（支付账户）向d银行账户（收款账户）的支付任务，上述b银行账户（支付账户）向d银行账户（收款账户）的支付任务，上述c银行账户（支付账户）向d银行账户（收款账户）的支付任务等。
S4、通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
在上述步骤S4中，上述企业端前置机上面预设有多个UKey接口，即可以插入多个UKey，当插入对应的UKey之后，既可以使用对应的银行账户进行转账、查询等工作，而且在多个不同的银行账户进行转账的情况下，无需切换登录等，可以直接进行操作，进而实现批量支付，大大地节约了财务人员的工作量，以及提高转账效率。本申请中，即为将不同的支付任务通过同一个企业端前置机发送给对应不同支付账户的银行端前置机，以将支付任务发送给对应银行的服务系统完成支付任务。
参照图2，在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4，包括：
S41、将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；
S42、通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；
在上述步骤S41和S42中，支付任务并不是直接发送给企业端前置机，而是发送给企业端前置机对应的应用服务器，该应用服务器是指给企业提供企业端前置机的第三方的应用服务器，其作为企业端前置机的管理后台，企业发布的任务会先进入到上述应用服务器，然后由应用服务器发送给企业端前置机。上述的任务ID只是一个标识，该标识唯一对应所述一个支付任务，任务ID并没有任务内容，以防止将支付任务的报文直接放到企业端前置机中，影响企业端前置机的运行空间，而降低其运行速度。因为本申请的企业端前置机可以连接多个银行端前置机，所以各种不同的任务会较多，直接将各种任务的报文堆积到前置机的缓存中，会大大地降低企业端前置机的运行效率，甚至崩溃。本申请中，只放入任务ID，则大大地降低了企业端前置机的缓存空间的要求，提高运行环境质量。本实施例中，预设的缓存队列一般包括交易缓存队列和查询缓存队列，不同的缓存队列存放对应属性的任务ID，对应的设置交易线程池和查询线程池。企业端前置机在获取到任务ID时，先判断所述任务ID的属性，其中属性包括交易属性、查询属性，因为任务ID属于交易类，则放入到交易缓存队列中。两个缓存队列中的任务按优先级进行排序，每个任务会设置有一个类型标识，类型标识分为1-8个级别，为1的话等级最高，代表紧急任务，优先处理，可以根据预设预设规则，根据具体请求附加对应的优先级别，比如，支付的级别高于查询银行流水的级别等。当任务类型相同时，则按照任务生成时间进行排序。
S43、通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述任务ID获取对应的支付任务发送给所述企业端前置机。
在上述步骤S43中，上述企业端前置机反馈的任务ID是指，对应上述缓存队列的线程池中有空闲，则到缓存队列中获取任务，又因为此时缓存队列中只是任务ID，所以企业端前置机会将任务ID返回给上述应用服务器，应用服务器会根据该返回的任务ID生成或调取对应的支付任务，然后该支付任务发送企业端前置机，以便于企业端前置机将支付任务转发给银行端前置机。
S44、通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
在上述步骤S44中，因为上述支付任务是针对需要向外转账的银行账户（支付账户）的，那么支付任务中会包含有该支付账户对应的银行端前置机的编号、对应的银行服务器IP等，这些信息都是在安装企业端前置机时配置好并发给企业端前置机对应的应用服务器中的信息。上述应用服务器会根据任务ID的请求自动将这些信息写入到报文中，以便于企业端前置机连接对应的银行端前置机。上述企业端前置机接收到支付任务后，会先解析出需要的信息，如银行端前置机的编号、对应的银行服务器IP等，然后将支付任务准确地发送给对应的银行前置机，银行前置机再转发给银行服务器，以完成对应的支付动作。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4之前，包括：
S401、判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
S402、若否，则报警。
在上述步骤S401和S402中，采集各UKey接口插入的UKey设备的对应其银行种类的标识，然后将所述标识与配置企业端前置机时配置的代表各类银行的标识进行比对，如果采集到的各标识全面覆盖配置企业端前置机时配置的代表各类银行的标识时，则判定企业端前置机上插入各对应各种类银行的UKey设备，否者，将未被覆盖的标识对应的银行种类提取出来，并发送给企业的相关人员以报警，此时企业的相关人员可以进行相应的处理，将忘记插入的UKey设备或插入处松动而导致UKey设备接触不良的重新插入等，以保证企业与各银行之间的交互。本申请中，还可以判断获取到的UKey设备的标识与配置企业端前置机时配置的代表各类银行的标识（不重复）的数量是否相同，因为一个银行只会发一个UKey给企业，所以当数量相同时候，基本可以判定企业端前置机上插入对应各种类银行的UKey设备，此种判断方法虽然存在缺陷，但是判断速度会更快。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4之前，包括：
S411、获取各支付账户的余额信息。
在上述步骤S411中，获取支付账户的余额信息的方法包括：通过应用服务器向所述企业端前置机发送多个所述支付账户的余额查询任务对应的余额查询任务ID，其中，所述企业端前置机将多个所述余额查询任务ID存入到预设的缓存队列中；当轮到缓存队列中的余额查询任务ID时，企业端前置机将余额查询任务ID反馈给应用服务器，应用服务器根据所述余额查询任务ID获取对应的余额查询任务报文，并再次发给所述企业端前置机；然后由企业端前置机将余额查询任务报文发送给对应的银行端前置机，银行端前置机将余额查询任务报文发送给对应的银行服务器进行余额查询，并将余额信息原路反馈到财务系统。
S412、若所述余额信息小于待转账金额，则发出报警。
在上述步骤S412中，如果某个支付账户的余额信息小于其待转账金额，则发出报警，以提示企业端的财务人员，该笔转账存在问题，可以以发邮件、短信、弹窗、声/光等一种或多种结合的方式进行。。
在一个实施例中，上述批量支付方法还包括：
判断应用服务器与企业端前置机的连接状态，若连接状态为断开，则发出警报信息。
本步骤中，企业端前置机和应用服务器应该长期在线，但是因为是电子产品，难免会出现故障或者升级等处理，此时企业端前置机与应用服务器可能断掉连接，那么通过心跳检测的方式检测两者的连接状态，当两者连接失败，则需要发出警报信息。发出警报信息包括，发送邮件等信息给企业的相关人员，和/或发送给提供企业端前置机的第三方的相关人员等。
在一个实施例中，上述批量支付方法，还包括：
控制所述应用服务器通过BIO同步阻塞模式向所述企业端前置机发送支付任务。
因为向企业端前置机发送的任务或接收的任务可能是连续的，所以使用长连接的方式监听服务，使每个操作完后都不断开，下次处理时直接发送数据包就可以，不用建立TCP（Transmission Control Protocol 传输控制协议）连接，以保持处理任务的效率。本实施例中，应用服务器与企业端前置机采用BIO（block input output）同步阻塞模式进行长连接，以完成任务交互。不同的支付任务不能够同时进行，所以需要按照指令顺序进行，一个指令执行完才能执行下一个指令，不能异步执行，所以本申请中采用BIO同步阻塞模式使应用服务器与企业端前置机进行长连接。
在一个实施例中，上述批量支付方法，还包括：：
通过所述应用服务器与所述企业端前置机相互发送的任务时，对所述任务采用Protocol Buffers进行序列化。
Protocol Buffers 是一种轻便高效的结构化数据存储格式，可以用于结构化数据串行化，或者说序列化。它很适合做数据存储或 RPC 数据交换格式。可用于通讯协议、数据存储等领域的语言无关、平台无关、可扩展的序列化结构数据格式，简单说来 Protobuf 的主要优点就是：简单，快。本申请采用GOOGLE（谷歌）的Protocol Buffers进行序列化，可以提高报文封装和发送的效率。
本申请实施例的批量支付方法，因为企业端前置机能够与多个不同种类的银行进行银企直联功能，所以在企业端前置机上设置了多个UKey接口，以保证各个银行账户的正常使用；当插入对应的UKey之后，既可以使用对应的银行账户进行转账、查询等工作，而且在多个不同的银行账户进行转账的情况下，无需切换登录等，可以直接进行操作，进而实现批量支付，大大地节约了财务人员的工作量，以及提高转账效率。
参照图3，本申请实施例中还一种批量支付装置，其特征在于，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互。
上述的企业端前置机是指设置在企业端的前置机，是企业端财务系统与银行端进行银企直联时的中间设备。上述企业端前置机被配置为可以与多个不同银行种类的银行端前置机完成数据交互，配置过程为，当企业安装企业端前置机时，企业端前置机有一个管理员界面，在预设的界面内输入指定的配置信息，该配置信息包括企业ID、企业端前置机编号、银行服务器IP、银行端口、银行的银企直联编号、银行端前置机的版本号，银行大类等企业财务系统与银行完成银企直联的必要参数，还会配置线程数大小配置等，以实现多线程任务的处理；然后将配置结果发送给企业端前置机对应的应用服务器。也就是，配置申请通过的银企直联的账号及其相关信息，当企业需要登录各银企直联的账户获取在其对应银行的数据时（交易数据、查询数据等），只需要在企业端前置机上插入对应的UKey（一种通过USB直接与计算机相连、具有密码验证功能、可靠高速的小型存储设备）即可，实现一个企业端前置机与多个不同类银行的银行端前置机连接，企业统一集中管理用户的银行UKey，无需做银行的切换操作。通过企业端前置机可以方便地获取企业的每个银企直联账户的账户信息、交易流水信息、余额信息，并且可以进行相关的支付、归集、调拨等相关操作。上述银行大类是指不同的银行，比如工商银行与建设银行属于两个不同的银行大类等，即使用不同前置机的银行被认为是不同的银行大类。
上述装置，包括：
获取单元10，用于获取多个支付账户信息，以及至少一个收款账户信息。
在上述获取单元10中，上述支付账户信息是指企业端开启银企直联的银行对应的账户信息。账户信息一般包括银行名字、账号信息等；上述收款账户信息则不规定是企业端开启银企直联的银行对应的账户信息。上述多个支付账户信息是指两个或两个以上的支付账户信息；上述至少一个收款账户信息是指有一个或一个以上的收款账户信息。
建立单元20，用于建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
生成单元30，用于根据所述支付对应关系和支付信息生成多个支付任务。
在上述建立单元20和生成单元30中，上述的支付对应关系是指，哪一个支付账户向哪一个收款账户进行转账的对应关系。在一个实施例中，一个支付账户可以对应多个收款账户，同样的，一个收款账户可以对应多个支付账户。上述支付信息可以包括具体的转账金额信息、转账原因备注信息、提示信息（收款短息、付款短信）等。上述建立所设所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息的过程，包括多种情况，第一种为：接收企业端的财务人员的手动命令实现连接，具体地，上述财务系统提供一个配置界面，财务人员在支付账户信息一列配置支付账户信息，在收款账户信息一列配置收款账户信息，然后根据转账要求配置不同的支付信息等；第二种为：预设配置完成的配置信息（该配置信息包括具体的支付账户信息和收款账户信息、以及支付信息等，具体地，事先配置好哪一个支付账户信息对应哪一个收款账户信息对应，以及对应的支付信息等），按照预设的时间自动将配置信息配置到支付账户一列和收款账户一列等，比如，企业端每天都需要将a银行账户的指定金额、b银行账户的指定金额、c银行账户的指定金额归集到d银行账户中，其中a银行账户、b银行账户、c银行账户为不同大类银行，则可以自动进行配置，到达转账时间既可以自动配置，无需财务人员进行处理。上述支付任务，即为根据支付账户与收款账户的对应关系，支付信息等生成的支付任务，如生成上述a银行账户（支付账户）向d银行账户（收款账户）的支付任务，上述b银行账户（支付账户）向d银行账户（收款账户）的支付任务，上述c银行账户（支付账户）向d银行账户（收款账户）的支付任务等。
支付单元40，用于通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
在上述支付单元40中，上述企业端前置机上面预设有多个UKey接口，即可以插入多个UKey，当插入对应的UKey之后，既可以使用对应的银行账户进行转账、查询等工作，而且在多个不同的银行账户进行转账的情况下，无需切换登录等，可以直接进行操作，进而实现批量支付，大大地节约了财务人员的工作量，以及提高转账效率。本申请中，即为将不同的支付任务通过同一个企业端前置机发送给对应不同支付账户的银行端前置机，以将支付任务发送给对应银行的服务系统完成支付任务。
参照图4，在一个实施例中，上述支付单元40，包括：
发送模块41，用于将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；
转发模块42，用于通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；
在上述发送模块41和转发模块42中，支付任务并不是直接发送给企业端前置机，而是发送给企业端前置机对应的应用服务器，该应用服务器是指给企业提供企业端前置机的第三方的应用服务器，其作为企业端前置机的管理后台，企业发布的任务会先进入到上述应用服务器，然后由应用服务器发送给企业端前置机。上述的任务ID只是一个标识，该标识唯一对应所述一个支付任务，任务ID并没有任务内容，以防止将支付任务的报文直接放到企业端前置机中，影响企业端前置机的运行空间，而降低其运行速度。因为本申请的企业端前置机可以连接多个银行端前置机，所以各种不同的任务会较多，直接将各种任务的报文堆积到前置机的缓存中，会大大地降低企业端前置机的运行效率，甚至崩溃。本申请中，只放入任务ID，则大大地降低了企业端前置机的缓存空间的要求，提高运行环境质量。本实施例中，预设的缓存队列一般包括交易缓存队列和查询缓存队列，不同的缓存队列存放对应属性的任务ID，对应的设置交易线程池和查询线程池。企业端前置机在获取到任务ID时，先判断所述任务ID的属性，其中属性包括交易属性、查询属性，因为任务ID属于交易类，则放入到交易缓存队列中。两个缓存队列中的任务按优先级进行排序，每个任务会设置有一个类型标识，类型标识分为1-8个级别，为1的话等级最高，代表紧急任务，优先处理，可以根据预设预设规则，根据具体请求附加对应的优先级别，比如，支付的级别高于查询银行流水的级别等。当任务类型相同时，则按照任务生成时间进行排序。
获取模块43，用于通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述任务ID获取对应的支付任务发送给所述企业端前置机。
在上述获取模块43中，上述企业端前置机反馈的任务ID是指，对应上述缓存队列的线程池中有空闲，则到缓存队列中获取任务，又因为此时缓存队列中只是任务ID，所以企业端前置机会将任务ID返回给上述应用服务器，应用服务器会根据该返回的任务ID生成或调取对应的支付任务，然后该支付任务发送企业端前置机，以便于企业端前置机将支付任务转发给银行端前置机。
支付模块44，用于通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
在上述支付模块44中，因为上述支付任务是针对需要向外转账的银行账户（支付账户）的，那么支付任务中会包含有该支付账户对应的银行端前置机的编号、对应的银行服务器IP等，这些信息都是在安装企业端前置机时配置好并发给企业端前置机对应的应用服务器中的信息。上述应用服务器会根据任务ID的请求自动将这些信息写入到报文中，以便于企业端前置机连接对应的银行端前置机。上述企业端前置机接收到支付任务后，会先解析出需要的信息，如银行端前置机的编号、对应的银行服务器IP等，然后将支付任务准确地发送给对应的银行前置机，银行前置机再转发给银行服务器，以完成对应的支付动作。
在一个实施例中，上述批量支付装置，还包括：
判断单元，用于判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
第一报警单元，用于若所述企业端前置机上未插入对应各种类银行的UKey设备，则报警。
在上述判断单元和报警单元中，采集各UKey接口插入的UKey设备的对应其银行种类的标识，然后将所述标识与配置企业端前置机时配置的代表各类银行的标识进行比对，如果采集到的各标识全面覆盖配置企业端前置机时配置的代表各类银行的标识时，则判定企业端前置机上插入各对应各种类银行的UKey设备，否者，将未被覆盖的标识对应的银行种类提取出来，并发送给企业的相关人员以报警，此时企业的相关人员可以进行相应的处理，将忘记插入的UKey设备或插入处松动而导致UKey设备接触不良的重新插入等，以保证企业与各银行之间的交互。本申请中，还可以判断获取到的UKey设备的标识与配置企业端前置机时配置的代表各类银行的标识（不重复）的数量是否相同，因为一个银行只会发一个UKey给企业，所以当数量相同时候，基本可以判定企业端前置机上插入对应各种类银行的UKey设备，此种判断方法虽然存在缺陷，但是判断速度会更快。
在一个实施例中，上述批量支付装置，还包括：
余额查询单元，用于获取各支付账户的余额信息。
在上述余额查询单元中，获取支付账户的余额信息的方法包括：通过应用服务器向所述企业端前置机发送多个所述支付账户的余额查询任务对应的余额查询任务ID，其中，所述企业端前置机将多个所述余额查询任务ID存入到预设的缓存队列中；当轮到缓存队列中的余额查询任务ID时，企业端前置机将余额查询任务ID反馈给应用服务器，应用服务器根据所述余额查询任务ID获取对应的余额查询任务报文，并再次发给所述企业端前置机；然后由企业端前置机将余额查询任务报文发送给对应的银行端前置机，银行端前置机将余额查询任务报文发送给对应的银行服务器进行余额查询，并将余额信息原路反馈到财务系统。
第二报警单元，用于若所述余额信息小于待转账金额，则发出报警。
在上述第二报警单元中，如果某个支付账户的余额信息小于其待转账金额，则发出报警，以提示企业端的财务人员，该笔转账存在问题，可以以发邮件、短信、弹窗、声/光等一种或多种结合的方式进行。。
在一个实施例中，上述批量支付装置还包括：
连接检测单元，用于判断应用服务器与企业端前置机的连接状态，若连接状态为断开，则发出警报信息。
在上述连接检测单元中，企业端前置机和应用服务器应该长期在线，但是因为是电子产品，难免会出现故障或者升级等处理，此时企业端前置机与应用服务器可能断掉连接，那么通过心跳检测的方式检测两者的连接状态，当两者连接失败，则需要发出警报信息。发出警报信息包括，发送邮件等信息给企业的相关人员，和/或发送给提供企业端前置机的第三方的相关人员等。
在一个实施例中，上述批量支付装置，还包括：
BIO同步阻塞单元，用于控制所述应用服务器通过BIO同步阻塞模式向所述企业端前置机发送支付任务。
因为向企业端前置机发送的任务或接收的任务可能是连续的，所以使用长连接的方式监听服务，使每个操作完后都不断开，下次处理时直接发送数据包就可以，不用建立TCP（Transmission Control Protocol 传输控制协议）连接，以保持处理任务的效率。本实施例中，应用服务器与企业端前置机采用BIO（block input output）同步阻塞模式进行长连接，以完成任务交互。不同的支付任务不能够同时进行，所以需要按照指令顺序进行，一个指令执行完才能执行下一个指令，不能异步执行，所以本申请中采用BIO同步阻塞模式使应用服务器与企业端前置机进行长连接。
在一个实施例中，上述批量支付装置，还包括：：
序列化单元，用于通过所述应用服务器与所述企业端前置机相互发送的任务时，对所述任务采用Protocol Buffers进行序列化。
Protocol Buffers 是一种轻便高效的结构化数据存储格式，可以用于结构化数据串行化，或者说序列化。它很适合做数据存储或 RPC 数据交换格式。可用于通讯协议、数据存储等领域的语言无关、平台无关、可扩展的序列化结构数据格式，简单说来 Protobuf 的主要优点就是：简单，快。本申请采用GOOGLE（谷歌）的Protocol Buffers进行序列化，可以提高报文封装和发送的效率。
本申请实施例的批量支付装置，因为企业端前置机能够与多个不同种类的银行进行银企直联功能，所以在企业端前置机上设置了多个UKey接口，以保证各个银行账户的正常使用；当插入对应的UKey之后，既可以使用对应的银行账户进行转账、查询等工作，而且在多个不同的银行账户进行转账的情况下，无需切换登录等，可以直接进行操作，进而实现批量支付，大大地节约了财务人员的工作量，以及提高转账效率。
参照图5，本申请实施例中还提供一种计算机设备，该计算机设备可以是服务器，其内部结构可以如图5所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口和数据库。其中，该计算机设计的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机可读指令和数据库。该内存器为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。该计算机设备的数据库用于存储批量支付方法程序等。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读指令被处理器执行时以实现一种批量支付方法。
上述处理器执行上述批量支付方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：获取多个支付账户信息，以及至少一个收款账户信息；建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；根据所述支付对应关系和支付信息生成多个支付任务；通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤，包括：将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述反馈的任务ID获取对应的支付任务发送给所述企业端前置机；通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤之前，包括：判断所述企业端前置机上是否插入对应各种类银行的UKey设备；若否，则报警。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4之前，包括：获取各支付账户的余额信息；若所述余额信息小于待转账金额，则发出报警。
在一个实施例中，上述批量支付方法还包括：判断应用服务器与企业端前置机的连接状态；若连接状态为断开，则发出警报信息。
在一个实施例中，上述批量支付方法还包括：控制所述应用服务器通过BIO同步阻塞模式向所述企业端前置机发送支付任务。
在一个实施例中，上述批量支付方法还包括：通过所述应用服务器与所述企业端前置机相互发送的任务时，对所述任务采用Protocol Buffers进行序列化。
本领域技术人员可以理解，图5中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定。
本申请实施例的计算机设备，因为企业端前置机能够与多个不同种类的银行进行银企直联功能，所以在企业端前置机上设置了多个UKey接口，以保证各个银行账户的正常使用；当插入对应的UKey之后，既可以使用对应的银行账户进行转账、查询等工作，而且在多个不同的银行账户进行转账的情况下，无需切换登录等，可以直接进行操作，进而实现批量支付，大大地节约了财务人员的工作量，以及提高转账效率。
本申请一实施例还提供一种计算机非易失性可读存储介质，其上存储有计算机可读指令，计算机可读指令被处理器执行时实现一种批量支付方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：获取多个支付账户信息，以及至少一个收款账户信息；建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；根据所述支付对应关系和支付信息生成多个支付任务；通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
上述批量支付方法，因为企业端前置机能够与多个不同种类的银行进行银企直联功能，所以在企业端前置机上设置了多个UKey接口，以保证各个银行账户的正常使用；当插入对应的UKey之后，既可以使用对应的银行账户进行转账、查询等工作，而且在多个不同的银行账户进行转账的情况下，无需切换登录等，可以直接进行操作，进而实现批量支付，大大地节约了财务人员的工作量，以及提高转账效率。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤，包括：将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述反馈的任务ID获取对应的支付任务发送给所述企业端前置机；通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤之前，包括：判断所述企业端前置机上是否插入对应各种类银行的UKey设备；若否，则报警。
在一个实施例中，上述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4之前，包括：获取各支付账户的余额信息；若所述余额信息小于待转账金额，则发出报警。
在一个实施例中，上述批量支付方法还包括：判断应用服务器与企业端前置机的连接状态；若连接状态为断开，则发出警报信息。
在一个实施例中，上述批量支付方法还包括：控制所述应用服务器通过BIO同步阻塞模式向所述企业端前置机发送支付任务。
在一个实施例中，上述批量支付方法还包括：通过所述应用服务器与所述企业端前置机相互发送的任务时，对所述任务采用Protocol Buffers进行序列化。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的和实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可以包括只读存储器（ROM）、可编程ROM（PROM）、电可编程ROM（EPROM）、电可擦除可编程ROM（EEPROM）或闪存。易失性存储器可包括随机存取存储器（RAM）或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM（SRAM）、动态RAM（DRAM）、同步DRAM（SDRAM）、双速据率SDRAM（SSRSDRAM）、增强型SDRAM（ESDRAM）、同步链路（Synchlink）DRAM（SLDRAM）、存储器总线（Rambus）直接RAM（RDRAM）、直接存储器总线动态RAM（DRDRAM）、以及存储器总线动态RAM（RDRAM）等。
以上所述仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种批量支付方法，其特征在于，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
    获取多个支付账户信息，以及至少一个收款账户信息；
    建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
    根据所述支付对应关系和支付信息生成多个支付任务；
    通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
  2. 根据权利要求1所述的批量支付方法，其特征在于，所述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤，包括：
    将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；
    通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；
    通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述任务ID获取对应的支付任务发送给所述企业端前置机；
    通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
  3. 根据权利要求1所述的批量支付方法，其特征在于，通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤之前，包括：
    判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
    若否，则报警。
  4. 根据权利要求1所述的批量支付方法，其特征在于，所述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4之前，包括：
    获取各支付账户的余额信息；
    若所述余额信息小于待转账金额，则发出报警。
  5. 根据权利要求1所述的批量支付方法，其特征在于，所述方法还包括：
    判断应用服务器与企业端前置机的连接状态；
    若连接状态为断开，则发出警报信息。
  6. 根据权利要求2所述的批量支付方法，其特征在于，所述方法还包括：
    控制所述应用服务器通过BIO同步阻塞模式向所述企业端前置机发送支付任务。
  7. 根据权利要求1所述的批量支付方法，其特征在于，所述方法还包括：
    通过所述应用服务器与所述企业端前置机相互发送的任务时，对所述任务采用Protocol Buffers进行序列化。
  8. 一种批量支付装置，其特征在于，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述装置，包括：
    获取单元，用于获取多个支付账户信息，以及至少一个收款账户信息；
    建立单元，用于建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
    生成单元，用于根据所述支付对应关系和支付信息生成多个支付任务；
    支付单元，用于通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
  9. 根据权利要求8所述的批量支付装置，其特征在于，所述支付单元，包括：
    发送模块，用于将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；
    转发模块，用于通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；
    获取模块，用于通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述任务ID获取对应的支付任务发送给所述企业端前置机；
    支付模块，用于通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
  10. 根据权利要求8所述的批量支付装置，其特征在于，所述批量支付装置，还包括：
    判断单元，用于判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
    第一报警单元，用于若所述企业端前置机上未插入对应各种类银行的UKey设备，则报警。
  11. 根据权利要求8所述的批量支付装置，其特征在于，所述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4之前，包括：
    余额查询单元，用于获取各支付账户的余额信息；
    第二报警单元，用于若所述余额信息小于待转账金额，则发出报警。
  12. 根据权利要求8所述的批量支付装置，其特征在于，所述批量支付装置还包括：
    连接检测单元，用于判断应用服务器与企业端前置机的连接状态，若连接状态为断开，则发出警报信息。
  13. 根据权利要求9所述的批量支付装置，其特征在于，所述批量支付装置，还包括：
    BIO同步阻塞单元，用于控制所述应用服务器通过BIO同步阻塞模式向所述企业端前置机发送支付任务。
  14. 根据权利要求8所述的批量支付装置，其特征在于，所述批量支付装置，还包括：：
    序列化单元，用于通过所述应用服务器与所述企业端前置机相互发送的任务时，对所述任务采用Protocol Buffers进行序列化。
  15. 一种计算机设备，包括存储器和处理器，所述存储器存储有计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现批量支付方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
    获取多个支付账户信息，以及至少一个收款账户信息；
    建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
    根据所述支付对应关系和支付信息生成多个支付任务；
    通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
  16. 根据权利要求15所述的计算机设备，其特征在于，所述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤，包括：
    将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；
    通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；
    通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述任务ID获取对应的支付任务发送给所述企业端前置机；
    通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
  17. 根据权利要求15所述的计算机设备，其特征在于，通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤之前，包括：
    判断所述企业端前置机上是否插入对应各种类银行的UKey设备；
    若否，则报警。
  18. 根据权利要求15所述的计算机设备，其特征在于，所述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤S4之前，包括：
    获取各支付账户的余额信息；
    若所述余额信息小于待转账金额，则发出报警。
  19. 一种计算机非易失性可读存储介质，其上存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现权利批量支付方法，利用企业端设置的企业端前置机与银行端进行财务数据交互，所述企业端前置机上设置有多个UKey接口，所述企业端前置机对应多个所述UKey接口被配置为可以与多个不同银行种类的银行端前置机完成财务数据交互；所述方法，包括：
    获取多个支付账户信息，以及至少一个收款账户信息；
    建立所述支付账户信息与所述收款账户信息的支付对应关系，以及支付信息；
    根据所述支付对应关系和支付信息生成多个支付任务；
    通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付。
  20. 根据权利要求19所述的计算机非易失性可读存储介质，其特征在于，所述通过所述企业端前置机将多个所述支付任务分别发送给与所述支付账户对应的银行端前置机，以完成批量支付的步骤，包括：
    将多个所述支付任务发送给所述企业端前置机对应的应用服务器，并通过应用服务器生成各所述支付任务的任务ID；
    通过所述应用服务器将各所述任务ID发送给所述企业端前置机，其中，所述企业端前置机将所述任务ID存入到预设的缓存队列中；
    通过所述应用服务器接收所述企业端前置机反馈的任务ID，并利用所述应用服务器根据所述任务ID获取对应的支付任务发送给所述企业端前置机；
    通过所述企业端前置机分别将所述应用服务器根据各所述任务ID获取的支付任务发送给所述银行端前置机，以完成对应的支付任务。
PCT/CN2018/108416 2018-07-02 2018-09-28 批量支付方法、装置、计算机设备和存储介质 WO2020006902A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810708670.7 2018-07-02
CN201810708670.7A CN109165935A (zh) 2018-07-02 2018-07-02 批量支付方法、装置、计算机设备和存储介质

Publications (1)

Publication Number Publication Date
WO2020006902A1 true WO2020006902A1 (zh) 2020-01-09

Family

ID=64897538

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/108416 WO2020006902A1 (zh) 2018-07-02 2018-09-28 批量支付方法、装置、计算机设备和存储介质

Country Status (2)

Country Link
CN (1) CN109165935A (zh)
WO (1) WO2020006902A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110111209A (zh) * 2019-05-05 2019-08-09 泰康保险集团股份有限公司 支付通知业务的处理方法、装置及可读存储介质
CN110659891A (zh) * 2019-09-29 2020-01-07 浪潮软件集团有限公司 一种多订单并发大数据量在线付款的方法
CN111612447A (zh) * 2020-05-29 2020-09-01 远光软件股份有限公司 一种批量电子支付的方法、装置、存储介质和电子设备
CN112785285B (zh) * 2021-01-21 2024-03-01 深圳乐信软件技术有限公司 多银行支付方法、系统、服务器和存储介质
CN113393228A (zh) * 2021-06-21 2021-09-14 中国工商银行股份有限公司 电子转账方法、系统、电子设备、存储介质及程序产品

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101996368A (zh) * 2009-08-21 2011-03-30 阿里巴巴集团控股有限公司 一种跨银行批量付款方法及系统
CN103413244A (zh) * 2013-07-29 2013-11-27 北京握奇数据系统有限公司 一种移动安全金融终端和金融交易方法
CN104573547A (zh) * 2014-10-21 2015-04-29 江苏通付盾信息科技有限公司 一种信息交互的安全防范体系及其操作实现方法
WO2016019535A1 (zh) * 2014-08-06 2016-02-11 深圳市银信网银科技有限公司 一种邮箱支付方法及邮箱支付系统
CN108171027A (zh) * 2018-01-29 2018-06-15 深圳平安综合金融服务有限公司 网银登录方法、装置、计算机设备和存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101262645A (zh) * 2008-03-14 2008-09-10 北京汇德佳信息技术有限公司 基于无线pda的移动生产监控系统
US8606705B2 (en) * 2009-02-13 2013-12-10 Bank Of America Corporation Systems, methods and computer program products for managing payment processes in a comprehensive payment hub system
CN102521778A (zh) * 2011-12-08 2012-06-27 携程计算机技术（上海）有限公司 企业与银行直接进行财务数据交互的系统
CN103345420B (zh) * 2013-06-03 2017-12-22 百度在线网络技术（北京）有限公司 批量调用api接口的方法、系统和装置
CN107544853A (zh) * 2017-08-23 2018-01-05 万惠投资管理有限公司 一种与银行进行交互重试的方法和系统
CN107516204A (zh) * 2017-08-31 2017-12-26 四川长虹电器股份有限公司 互联网银企对接系统及对接方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101996368A (zh) * 2009-08-21 2011-03-30 阿里巴巴集团控股有限公司 一种跨银行批量付款方法及系统
CN103413244A (zh) * 2013-07-29 2013-11-27 北京握奇数据系统有限公司 一种移动安全金融终端和金融交易方法
WO2016019535A1 (zh) * 2014-08-06 2016-02-11 深圳市银信网银科技有限公司 一种邮箱支付方法及邮箱支付系统
CN104573547A (zh) * 2014-10-21 2015-04-29 江苏通付盾信息科技有限公司 一种信息交互的安全防范体系及其操作实现方法
CN108171027A (zh) * 2018-01-29 2018-06-15 深圳平安综合金融服务有限公司 网银登录方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
CN109165935A (zh) 2019-01-08

Similar Documents

Publication Publication Date Title
WO2020006902A1 (zh) 批量支付方法、装置、计算机设备和存储介质
WO2020006903A1 (zh) 财务数据交互方法、装置、计算机设备和存储介质
WO2016101599A1 (zh) 业务流程管理的通知服务处理的方法及业务流程管理引擎
US20090199210A1 (en) Transaction management in a web service messaging environment
CN110413424B (zh) 可配置的第三方消息回调方法、装置、服务器和存储介质
US9961125B2 (en) Messaging API over HTTP protocol to establish context for data exchange
WO2020006895A1 (zh) 对账方法、装置、计算机设备和存储介质
WO2009030130A1 (fr) Procédé et système de transmission de données
US10523667B2 (en) Framework for executing operations on systems
US20180026959A1 (en) Preventing Unauthorized Access to Secured Information Systems Using Tokenized Authentication Techniques
WO2020006896A1 (zh) 余额监控方法、装置、计算机设备和存储介质
CN111935177B (zh) 一种业务控制方法及装置
WO2020006893A1 (zh) 回单获取方法、装置、计算机设备和存储介质
WO2020258653A1 (zh) 一种跨节点的数据处理方法及装置
CN112148394A (zh) 一种分布式事务协调方法、装置及电子设备
CN112163026A (zh) 一种用于整合多类技术应用数据的多源异构接口管控方法
WO2020006901A1 (zh) 资金归集方法、装置、计算机设备和存储介质
CN116170234B (zh) 一种基于虚拟账号认证的单点登录方法和系统
WO2011143967A1 (zh) 一种图形化用户界面实现系统和方法
WO2020006904A1 (zh) 财务调拨方法、装置、计算机设备和存储介质
US20230291726A1 (en) System and method for providing multi factor authorization to rdp services through a zero trust cloud environment
CN115643271A (zh) 一种云上多应用数据同步方法、装置、服务器及介质
CN110381143A (zh) 作业提交执行方法、装置、设备及计算机存储介质
CN115086311A (zh) 一种基于云服务总线的企业跨系统服务的管理系统
CN112668998B (zh) 流程实现方法、装置、系统、电子设备和可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18925386

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18925386

Country of ref document: EP

Kind code of ref document: A1