Method and system for automatic processing of transfer payment instructions based on a policy trigger mechanism

Abstract

This invention discloses an automated processing method and system for transfer payment instructions based on a strategy-triggered mechanism. This invention automates the processing of transfer payment instructions based on a strategy-triggered mechanism, specifically by automatically triggering the generation and submission of payment instructions upon approval. Compared to traditional manual processing of each transaction, this significantly improves processing timeliness and execution efficiency under large data volumes, avoiding fatigue errors and payment mistakes caused by frequent manual operations. Furthermore, compared to solutions relying on scheduled tasks and constantly running intelligent robots, this invention does not require additional software installation on the user's end or continuous occupation of system resources. Approval is immediate, eliminating polling delays, and payment results can be pushed to the user's end for real-time visualization. Therefore, it improves the timeliness and accuracy of payments while effectively reducing the impact on user terminal performance, thus comprehensively optimizing the user's operating experience and ease of use.

Description

Technical Field

[0001] This invention belongs to the field of automated payment technology, specifically relating to a method and system for automating transfer payment instructions based on a strategy-triggered mechanism. Background Technology

[0002] Currently, for direct bank-enterprise payment transactions, the general fund settlement system mainly adopts the following two methods for fund settlement and payment: the first is manual submission through the system one by one, that is, submission of operations through online payment instructions; the second is to use artificial intelligence robots to complete online payments by setting submission actions.

[0003] The aforementioned existing technologies have the following shortcomings: (1) When the amount of payment data is large, manual operation has poor processing timeliness and is prone to payment errors under frequent operation; (2) For intelligent robots, the computer used for payment needs to install intelligent robot software and keep the program running continuously. It is also necessary to set timed tasks for the program, which has the problem of untimely response. Furthermore, forcibly running the program for a long time will also affect the user's application experience.

[0004] Therefore, given the aforementioned shortcomings, how to provide an automated processing method for transfer payment instructions that can solve the problems of low efficiency in traditional manual processing and untimely response of intelligent robot solutions has become an urgent issue to be addressed. Summary of the Invention

[0005] The purpose of this invention is to provide an automated processing method and system for transfer payment instructions based on a strategy triggering mechanism, in order to solve the problems of low efficiency of manual processing and untimely response of intelligent robot solutions in the prior art.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: Firstly, a method for automating transfer payment instructions based on a policy-triggered mechanism is provided, including: Obtain the approval result of the electronic payment record settlement signature for the target payment task, and determine whether the approval result is approved; If so, a payment instruction is generated based on the electronic payment record settlement signature; The system obtains the automatic payment parameters configured on the payment user terminal corresponding to the target payment task in real time, and determines whether the automatic payment instruction submission function is enabled on the payment user terminal based on the automatic payment parameters. If so, the payment instruction is verified, and after the verification is successful, the payment instruction is sent to the payment platform so that the payment platform can transfer the funds for the target payment task according to the payment instruction and return the payment result corresponding to the target payment task. The payment result is sent to the payment user's terminal so that the payment user's terminal can visualize the payment result.

[0007] Based on the above-disclosed content, this invention automates the processing of transfer payment instructions using a strategy-triggered mechanism. Specifically, the generation and submission of payment instructions are automatically triggered upon approval. Compared to traditional manual transaction-by-transaction processing, this significantly improves processing timeliness and execution efficiency under large data volumes, avoiding fatigue errors and payment mistakes caused by frequent manual operations, and ensuring fund security. Furthermore, compared to solutions relying on scheduled tasks and constantly running intelligent robots, this invention does not require additional software installation on the user's end or continuous occupation of system resources. Approval is immediate, eliminating polling delays, and payment results are pushed to the user's end for real-time visualization. Therefore, this invention improves the timeliness and accuracy of payments while effectively reducing the impact on user terminal performance, thus comprehensively optimizing the user's operating experience and ease of use. Consequently, this invention is highly suitable for large-scale application and promotion.

[0008] In one possible design, the payment instruction includes the payment authorization data of the paying user and the business document information corresponding to the target payment task; The payment verification of the payment instruction includes: Based on the business document information, the payment business logic data is determined; The validity of the payment authorization data is verified, and after the validity verification passes, the business logic consistency of the payment business logic data is verified. After the business logic consistency verification passes, the payment instruction is sequentially subjected to data integrity verification and risk verification. Once the risk verification passes, the payment instruction is sent to the payment platform.

[0009] In one possible design, the payment authorization data includes: a user-authorized payment certificate and a user USB key, wherein validating the payment authorization data includes: Determine whether the user-authorized payment certificate is within its validity period; If so, determine whether the payment permissions of the user's U-shield meet the preset authorization permissions; If yes, the payment authorization data is deemed to have passed the validity check; otherwise, the payment instruction is intercepted, and an exception record containing the reason for failure is generated, which is then pushed to the manual intervention interface on the payment user's end.

[0010] In one possible design, the payment business logic data includes: settlement method and payment channel, wherein the business logic consistency check of the payment business logic data is: determining whether the settlement method and payment channel match; Data integrity verification is used to check whether the required fields in the payment instruction are complete and whether they meet the preset format requirements; Accordingly, risk verification of the payment instruction includes: Identify the payee information in the payment instruction; Based on the recipient information, determine whether the recipient is a high-risk user; If so, the risk verification is deemed to have failed, and the payment instruction is intercepted, along with an exception record containing the reason for the failure. This exception record is then pushed to the manual intervention interface on the payment user's end.

[0011] In one possible design, before sending the payment instruction to the payment platform, the method further includes: Obtain the business document information corresponding to the target payment task; Business attribute information is extracted from the business document information, and based on the business attribute information, the payment strategy corresponding to the target payment task is determined from a pre-set payment strategy library. The payment strategy and the payment instruction are then sent to the payment platform, so that the payment platform, upon receiving the payment instruction, triggers a payment operation to perform the transfer payment for the target payment task based on the payment strategy, and returns the payment result corresponding to the target payment task. The payment strategy library is configured with payment strategies corresponding to different business attributes.

[0012] In one possible design, the payment result includes: payment success, payment failure, and unsuccessful delivery, wherein sending the payment result to the payment user terminal includes: If the payment result is successful, the payment result will be sent to the payment success tab on the payment user's terminal. If the payment result is "not sent successfully" or "payment failed", the payment result will be sent to the payment failure tab on the payment user's terminal. If the payment result is "not sent successfully", the target payment task will also be pushed to the manual intervention processing interface on the payment user's terminal.

[0013] In one possible design, the payment result further includes: payment alert information returned by the payment platform, wherein sending the payment result to the payment user's terminal includes: Based on the payment warning information, the warning level is determined; If the warning level is Level 1, the payment result will be sent to the warning failure tab on the payment user's terminal, and the target payment task will be pushed to the manual intervention interface on the payment user's terminal. If the warning level is Level 2, the payment result will be sent to the payment failure tab on the payment user's terminal, and the target payment task will be pushed to the manual intervention interface on the payment user's terminal. The payment risk corresponding to Level 2 warning is higher than that corresponding to Level 1 warning.

[0014] Secondly, an automated processing system for transfer payment instructions based on a policy-triggered mechanism is provided, including: The signature approval unit is used to obtain the approval result of the electronic payment record settlement signature of the target payment task in real time, and to determine whether the approval result is approved. The payment instruction generation unit is used to generate a payment instruction based on the electronic payment record settlement signature when the signature approval unit determines that the approval result is approved; An automatic payment function detection unit is used to obtain the automatic payment parameters configured by the payment user terminal corresponding to the target payment task, and determine whether the payment user terminal has enabled the automatic submission function of transfer payment instructions based on the automatic payment parameters. An automatic payment unit is used to perform payment verification on the payment instruction when the automatic payment function detection unit determines that the payment user has enabled the automatic submission function of the transfer payment instruction. After the payment verification is passed, the payment instruction is sent to the payment platform so that the payment platform can perform the transfer payment of the target payment task according to the payment instruction and return the payment result corresponding to the target payment task. The payment feedback unit is used to send the payment result to the payment user terminal so that the payment user terminal can visualize the payment result.

[0015] Thirdly, an automated transfer payment instruction processing device based on a policy triggering mechanism is provided. Taking the device as an electronic device as an example, it includes a memory, a processor, and a transceiver that are connected in sequence. The memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program and execute the automated transfer payment instruction processing method based on the policy triggering mechanism as described in the first aspect or any possible design in the first aspect.

[0016] Fourthly, a storage medium is provided, on which instructions are stored, which, when executed on a computer, perform the automated processing method for transfer payment instructions based on the policy triggering mechanism described in the first aspect or any possible design of the first aspect.

[0017] Fifthly, a computer program product containing instructions is provided, which, when executed on a computer, causes the computer to perform the automated processing method for transfer payment instructions based on the policy triggering mechanism described in the first aspect or any possible design of the first aspect.

[0018] Beneficial effects: (1) This invention is based on a strategy-triggered mechanism to automate the processing of transfer payment instructions. That is, the generation and submission of payment instructions are automatically triggered by the approval result. In this way, compared with the traditional manual operation of each transaction, the processing timeliness and execution efficiency are significantly improved under the large amount of data, avoiding fatigue errors and payment errors caused by high-frequency manual operation, and ensuring the safety of funds. At the same time, compared with the solution of intelligent robots that rely on timed tasks and need to run continuously, this invention does not require the installation of additional software on the user end or continuous occupation of system resources. The response is immediate after approval, eliminating the polling delay problem, and the payment result can be pushed to the user end for visualization in real time. Based on this, the timeliness and accuracy of payment are improved, and the impact on the performance of the user terminal is effectively reduced, thereby comprehensively optimizing the user's operating experience and ease of use. Therefore, this invention is very suitable for large-scale application and promotion.

[0019] (2) The present invention has a payment verification step before the payment instruction is submitted, which can ensure the legality and compliance of the payment instruction. In this way, the system's automated processing replaces high-frequency manual operation, effectively eliminating the risks of payment account and amount errors caused by fatigue or negligence under frequent manual operation, and improving the accuracy and security of payment business.

[0020] (3) The present invention supports the classification display and automatic push function of payment results, and provides a flexible processing method of manual pre-review for failed transactions; thus, the convenience and flexibility of use are further improved. Attached Figure Description

[0021] Figure 1 A flowchart illustrating the steps of the automated processing method for transfer payment instructions based on a policy triggering mechanism provided in this embodiment of the invention; Figure 2 A flowchart of an automated processing method for transfer payment instructions based on a policy triggering mechanism provided in an embodiment of the present invention; Figure 3 This is a structural diagram of an automated transfer payment instruction processing system based on a strategy triggering mechanism provided in an embodiment of the present invention. Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the present invention will be briefly introduced below in conjunction with the accompanying drawings and descriptions of the embodiments or the prior art. Obviously, the following description of the structure of the accompanying drawings is only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. It should be noted that the description of these embodiments is for the purpose of helping to understand the present invention, but does not constitute a limitation of the present invention.

[0023] It should be understood that although the terms first, second, etc., may be used herein to describe various units, these units should not be limited by these terms. These terms are only used to distinguish one unit from another. For example, a first unit may be referred to as a second unit, and similarly, a second unit may be referred to as a first unit, without departing from the scope of the exemplary embodiments of the invention.

[0024] It should be understood that the term "and / or" that may appear in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, B exists alone, and A and B exist simultaneously. The term " / and" that may appear in this document describes another relationship between related objects, indicating that two relationships can exist. For example, A / and B can mean: A exists alone, and A and B exist alone. In addition, the character " / " that may appear in this document generally indicates that the related objects before and after it are in an "or" relationship.

[0025] Example: See Figure 1 As shown, the automated processing method for transfer payment instructions based on a policy triggering mechanism provided in the first aspect of this embodiment can be executed by a computer device with certain computing resources, including but not limited to a server. It is understood that the aforementioned execution subject does not constitute a limitation on the embodiments of this application. Accordingly, the operation steps of this method can be, but are not limited to, the steps S1 to S5 below.

[0026] S1. Obtain the approval result of the electronic payment record settlement signature for the target payment task, and determine whether the approval result is approved; in specific applications, the electronic payment record settlement signature may include, but is not limited to: the payment authorization data of the paying user, the business document information corresponding to the target payment task, and the payee information, that is, it contains all the information required for this payment; further, the payment authorization data may include, but is not limited to, the user's authorized payment certificate and the user's U-shield, and the business document information may include, but is not limited to, business attribute information, such as the payment unit, settlement method (such as different settlement types such as wire transfer, bill, and linked payment), payment channel (connected to different payment platforms or different payment channels), transaction amount, currency, and transaction type (such as purchase payment, salary payment, expense reimbursement, etc.).

[0027] Meanwhile, the approval result of the electronic payment record settlement signature can be sent from the payment user terminal to the running server of this method, thereby realizing the instant receipt of the approval result. After receiving the result, the payment instruction is automatically generated and submitted based on the approval result. In this way, all processing is completed instantly on the server side, and the response is immediate upon approval, eliminating the polling delay problem. The payment instruction generation process is shown in step S2 below.

[0028] S2. If so, a payment instruction is generated based on the electronic payment record settlement signature. In practice, the approval result is either approval or disapproval. If the approval is disapproved, the automated processing flow of this transfer payment instruction is terminated directly. Conversely, if the approval is approved, a payment instruction needs to be generated, which means converting the electronic payment record settlement signature into a payment instruction. This instruction contains the aforementioned payment authorization data, business document information, and payee information.

[0029] Thus, after generating the payment instruction, this embodiment also adds a judgment logic, namely, judging whether the "automatic submission of transfer payment instruction" service of the current payment user terminal is enabled, the process of which is shown in step S3 below.

[0030] S3. Obtain the automatic payment parameters configured on the payment client corresponding to the target payment task, and determine whether the payment client has enabled the automatic submission function for transfer payment instructions based on the automatic payment parameters; in this embodiment, the automatic payment parameters are the automatic submission parameters for transfer payment (see...). Figure 2 As shown in the figure, it is used to indicate whether the current payment client has enabled the automatic submission function of transfer payment instructions, that is, whether automatic submission of payment instructions is allowed; wherein, the automatic payment parameter can be pre-configured according to the unit's permissions, but is not limited to.

[0031] Optionally, the aforementioned automatic payment parameters can be identified using character identifiers. For example, the character "1" indicates that the automatic submission function for transfer payment instructions is enabled, and the character "0" indicates that the automatic submission function for transfer payment instructions is disabled. Based on this, if the current payment user's client has the automatic submission function for transfer payment instructions disabled, the payment instruction will be routed to the manual intervention stage on the payment user's client, thus reminding the user to manually submit the payment instruction. Conversely, when the automatic submission function for transfer payment instructions is enabled, the payment instruction will be automatically submitted (see...). Figure 2 As shown in the figure), the process is as shown in step S4 below.

[0032] S4. If so, the payment instruction is verified. After the verification is successful, the payment instruction is sent to the payment platform so that the payment platform can transfer funds for the target payment task according to the payment instruction and return the payment result corresponding to the target payment task. In specific applications, before submitting the payment, this embodiment supports multi-dimensional data-based reasonableness verification of the payment instruction (i.e., retaining the verification strategy for the payment instruction) to ensure the efficiency and accuracy of the payment operation, thereby significantly reducing the need for manual intervention and the potential error rate.

[0033] The payment verification process for payment instructions may include, but is not limited to, the steps S41 to S43 below.

[0034] S41. Based on the business document information, determine the payment business logic data; in specific implementation, the payment business logic data may include, but is not limited to, settlement method and payment channel; thus, after determining the payment business logic data, data validity and business logic consistency verification can be performed, the process of which is shown in step S42 below.

[0035] S42. The validity of the payment authorization data is verified, and after the validity verification passes, the business logic consistency of the payment business logic data is verified. In specific implementation, the validity verification mainly involves verifying the limited validity period of the user's authorized payment certificate and the user's U-shield permissions. That is, first, it is determined whether the user's authorized payment certificate is within its validity period; if so, it is determined whether the user's U-shield payment permissions meet the preset authorization permissions; if the preset authorization permissions are met, the payment authorization data is determined to have passed the validity verification; otherwise, if the user's authorized payment certificate is not within its validity period, and / or the user's U-shield payment permissions do not meet the preset authorization permissions, the payment instruction will be intercepted, and an exception record containing the reason for failure will be generated (such as the user's authorized certificate being expired or the user's U-shield payment permissions not meeting the preset authorization permissions). Finally, the exception record will be pushed to the manual intervention processing interface on the payment user's end for manual processing. In this way, the aforementioned validity verification can prevent payment instructions from being issued without authorization or with forged identities, ensuring the authenticity of "whoever approves, whoever authorizes".

[0036] After the validity check is completed, the business logic consistency check can be performed. The business logic consistency check determines whether the settlement method and payment channel match. For example, wire transfer cannot use the bill channel, and foreign currency payments cannot use the RMB clearing channel. In this way, the business logic consistency check can ensure that the payment path is correct, thereby avoiding payment failure or fund stagnation due to channel mismatch. Of course, if the business logic consistency check fails, an exception record containing the reason for the failure will be generated and pushed to the manual intervention interface on the payment user's end.

[0037] Thus, after completing the business logic consistency verification, data integrity verification and risk verification can be performed, as shown in step S43 below.

[0038] S43. After the business logic consistency verification passes, the payment instruction is sequentially subjected to data integrity verification and risk verification. If the risk verification passes, the payment instruction is sent to the payment platform. In specific implementation, for example, data integrity verification can be used, but is not limited to, to verify whether the required fields in the payment instruction are complete and conform to preset format requirements. Required fields can include, but are not limited to, the payee's account number, payment amount, payment purpose, etc., i.e., verifying whether the payee's account number has the preset number of digits, whether the amount is a number, and whether the payment purpose contains sensitive keywords (which can be matched based on a sensitive word database). If the data integrity verification fails, an abnormal record is generated and pushed to the manual intervention processing interface. Thus, this data integrity verification ensures that the data packet sent to the payment platform fully complies with the specifications of the bank-enterprise direct connection interface.

[0039] After passing data integrity verification, risk verification can be performed. Specifically, the risk verification process is as follows: First, the payee information in the payment instruction is identified; then, based on the payee information, it is determined whether the payee is a risk user, that is, whether the payee is an internal blacklist user and / or whether the payment amount exceeds the maximum payment amount; if the payee is a blacklist user and / or the payment amount exceeds the maximum payment amount, the payee is determined to be a risk user. In this case, the risk verification is deemed to have failed, thus the payment instruction is intercepted, and an abnormal record containing the reason for failure is generated and pushed to the manual intervention interface; of course, if the risk verification is passed, the payment instruction is submitted; in this way, through the aforementioned risk verification, regulatory and internal enterprise risk control requirements can be met, thereby intercepting high-risk transactions and reducing financial losses.

[0040] Through the aforementioned steps S41 to S43, this embodiment performs multi-dimensional data validation on the payment instruction before submission, ensuring the efficiency and accuracy of the payment operation, thereby significantly reducing the need for manual intervention and the potential error rate.

[0041] After payment verification is completed, payment can be automatically submitted. In this embodiment, the payment scope (i.e., payment strategy) can be configured within a unit range to achieve flexible configuration of the payment strategy corresponding to the automatically sent payment instruction. In this way, the optimal payment strategy can be determined for each payment instruction, and the process is as follows: First, obtain the business document information corresponding to the target payment task (obtained by parsing the payment instruction); then, extract business attribute information from the business document information, and determine the payment strategy corresponding to the target payment task from a pre-set payment strategy library based on the business attribute information; finally, extract the business attribute information from the business document information, and determine the payment strategy corresponding to the target payment task from a pre-set payment strategy library based on the business attribute information.

[0042] It should be noted that the payment strategy library is configured with payment strategies corresponding to different business attributes. Specifically, a payment strategy corresponds to attribute field values ​​such as "payment unit," "settlement method," "amount," and "currency." Therefore, after receiving the currently generated payment instruction, the library can filter out attribute field values ​​that match the business attribute information based on the business attribute information in the payment instruction. Then, the payment strategy corresponding to the matched attribute field value is used as the payment strategy corresponding to the currently generated payment instruction. The matched payment strategy, along with the payment instruction, can then be sent to the payment platform (such as a bank). Upon receiving the payment instruction, the payment platform will trigger a support operation and use the received payment strategy to complete the transfer payment for the target payment task, thereby returning the corresponding payment result. After receiving the payment result, the payment can be displayed, as shown in step S5 below.

[0043] S5. Send the payment result to the payment user terminal so that the payment user terminal can visualize the payment result; in specific implementation, the payment result may include, but is not limited to: payment success, payment failure, unsuccessful sending, and payment warning information returned by the payment platform; thus, this embodiment can classify and display the payment result in categories.

[0044] Among them, see Figure 2 As shown, if the payment result is successful, the payment result is sent to the payment success tab on the payment user's end; if the payment result is unsuccessful or the payment fails, the payment result is sent to the payment failure tab on the payment user's end. When the payment result is unsuccessful, the target payment task is also pushed to the manual intervention processing interface on the payment user's end for manual pre-review or re-payment.

[0045] See Figure 2 As shown, when the payment platform returns payment warning information, a payment warning needs to be issued. Specifically, the warning level is first determined based on the payment warning information. If the warning level is a Level 1 warning, the payment result is sent to the warning failure tab on the payment user's end, and the target payment task is pushed to the manual intervention processing interface on the payment user's end.

[0046] Similarly, if the warning level is level two, the payment result will be sent to the payment failure tab on the payment user's end, and the target payment task will be pushed to the manual intervention interface on the payment user's end. The payment risk corresponding to level two warning is higher than that corresponding to level one warning.

[0047] In practical applications, it's important to note that the payment platform will assess the risk of the payee based on the payee information in the payment instruction and its latest real-time database (such as bank or treasury credit records, account judicial freeze status, etc.), and return a corresponding warning level. If the payee's credit rating is lower than the preset level, a Level 1 warning will be returned (which can be understood as a medium-level warning; see [link to relevant documentation]). Figure 2 As shown in the image, if the recipient's account is under judicial freeze, the payment warning information returned will be a Level 2 warning (i.e., a high-level warning); then, it can be categorized and displayed according to different warning levels.

[0048] See Figure 2 As shown, when the warning level is Level 1, the payment result is recorded in the "Warning Failure" tab; when the warning level is Level 2, it is recorded in the "Payment Failure" tab. In both cases, the target payment task needs to be pushed to the manual intervention interface for review or re-payment. Of course, after manual intervention, if the intervention result is successful, the final payment result is recorded in the "Payment Success" tab; otherwise, if the payment still fails, it is recorded in the "Payment Failure" tab.

[0049] It's important to note that a tab refers to a specific tab or page on the payment settlement system's interface used by the user to centrally display payment instruction records with different payment statuses. Essentially, it's a status filter view. The settlement system interface typically has a horizontally arranged row of tabs (similar to browser tabs), including "All," "Not Sent," "Processing," "Payment Successful," and "Payment Failed." When a user clicks the "Payment Successful" tab, the list below only refreshes to display records corresponding to payment instructions with a successful status; records with other statuses are automatically filtered and hidden. This allows users to quickly view records corresponding to payment instructions with different statuses.

[0050] Thus, by categorizing and displaying payment results and automatically pushing them, and by providing a flexible approach of manual pre-screening for failed transactions, the ease of use and flexibility can be further improved.

[0051] Therefore, through the strategy-triggered mechanism-based automated processing method for transfer payment instructions described in detail in steps S1 to S5 above, this invention achieves fully automated processing of transfer payment instruction data by introducing a strategy channel and mechanism for automatically submitting payment instructions, significantly improving the processing efficiency and intelligence level of bank-enterprise direct payment business. Compared with the traditional method of manual submission of each transaction or relying on intelligent robots, this invention does not require additional robot software installation or continuous program operation, avoiding customer application experience problems caused by long-term program operation. Moreover, through intelligent system control and verification mechanisms, this solution achieves real-time response and automatic processing of payment instructions, greatly reducing the burden of manual operation and potential errors, effectively improving the efficiency and accuracy of payment operations. At the same time, this invention supports setting automatic execution of payment operations according to unit permissions (that is, flexibly configuring automatic payment parameters), and immediately starts the payment instruction submission process after approval. Combined with the classification display and automatic push function of payment results, it provides flexible handling methods for special cases, further improving the reliability and efficiency of the payment process. Thus, this invention significantly improves customer experience and payment efficiency while optimizing the payment process, providing strong technical support for the intelligent upgrade of bank-enterprise direct payment business.

[0052] like Figure 3 As shown, the second aspect of this embodiment provides a software system for implementing the automated processing system for transfer payment instructions based on a strategy triggering mechanism as described in the first aspect of the embodiment, comprising: The signature approval unit is used to obtain the approval result of the electronic payment record settlement signature of the target payment task in real time, and to determine whether the approval result is approved.

[0053] The payment instruction generation unit is used to generate a payment instruction based on the electronic payment record settlement signature when the signature approval unit determines that the approval result is approved.

[0054] The automatic payment function detection unit is used to obtain the automatic payment parameters configured by the payment user terminal corresponding to the target payment task, and determine whether the payment user terminal has enabled the automatic submission function of transfer payment instructions based on the automatic payment parameters.

[0055] An automatic payment unit is used to perform payment verification on the payment instruction when the automatic payment function detection unit determines that the payment user has enabled the automatic submission function of the transfer payment instruction. After the payment verification is passed, the payment instruction is sent to the payment platform so that the payment platform can perform the transfer payment for the target payment task according to the payment instruction and return the payment result corresponding to the target payment task.

[0056] The payment feedback unit is used to send the payment result to the payment user terminal so that the payment user terminal can visualize the payment result.

[0057] The working process, working details and technical effects of the system provided in this embodiment can be found in the first aspect of the embodiment, and will not be repeated here.

[0058] like Figure 4 As shown, the third aspect of this embodiment provides an automated processing device for transfer payment instructions based on a policy triggering mechanism. Taking the device as an electronic device as an example, it includes: a memory, a processor, and a transceiver that are connected in sequence. The memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program and execute the automated processing method for transfer payment instructions based on a policy triggering mechanism as described in the first aspect of the embodiment.

[0059] For specific examples, the memory may include, but is not limited to, random access memory (RAM), read-only memory (ROM), flash memory, first-in-first-out (FIFO) memory, and / or first-in-last-out (FILO) memory, etc.; specifically, the processor may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor may be implemented using at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), PLA (Programmable Logic Array). The processor may also include a main processor and a coprocessor. The main processor, also known as the CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state.

[0060] In some embodiments, the processor may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. For example, the processor may not be limited to microprocessors of the STM32F105 series, reduced instruction set computer (RISC) microprocessors, x86 architecture processors, or processors with integrated neural network processing units (NPUs). The transceiver may be, but is not limited to, a Wi-Fi transceiver, a Bluetooth transceiver, a General Packet Radio Service (GPRS) transceiver, a ZigBee transceiver (a low-power LAN protocol based on the IEEE 802.15.4 standard), a 3G transceiver, a 4G transceiver, and / or a 5G transceiver. Furthermore, the device may also include, but is not limited to, a power module, a display screen, and other necessary components.

[0061] The working process, working details and technical effects of the electronic device provided in this embodiment can be found in the first aspect of the embodiment, and will not be repeated here.

[0062] The fourth aspect of this embodiment provides a storage medium for storing instructions containing the automated processing method for transfer payment instructions based on the policy triggering mechanism described in the first aspect of the embodiment. That is, the storage medium stores instructions, and when the instructions are run on a computer, the automated processing method for transfer payment instructions based on the policy triggering mechanism described in the first aspect of the embodiment is executed.

[0063] The storage medium refers to a carrier for storing data, which may include, but is not limited to, floppy disks, optical disks, hard disks, flash memory, USB flash drives, and / or memory sticks. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

[0064] The working process, working details and technical effects of the storage medium provided in this embodiment can be found in the first aspect of the embodiment, and will not be repeated here.

[0065] The fifth aspect of this embodiment provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform the automated processing method for transfer payment instructions based on a policy triggering mechanism as described in the first aspect of this embodiment. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

[0066] Finally, it should be noted that the above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for automating the processing of transfer payment instructions based on a strategy-triggered mechanism, characterized in that, include: The system acquires the approval result of the electronic payment record settlement signature for the target payment task in real time and determines whether the approval result is approved. If so, a payment instruction is generated based on the electronic payment record settlement signature; Obtain the automatic payment parameters configured on the payment user terminal corresponding to the target payment task, and determine whether the automatic payment instruction submission function is enabled on the payment user terminal based on the automatic payment parameters. If so, the payment instruction is verified, and after the verification is successful, the payment instruction is sent to the payment platform so that the payment platform can transfer the funds for the target payment task according to the payment instruction and return the payment result corresponding to the target payment task. The payment result is sent to the payment user's terminal so that the payment user's terminal can visualize the payment result.

2. The method according to claim 1, characterized in that, The payment instruction contains the payment authorization data of the paying user and the business document information corresponding to the target payment task; The payment verification of the payment instruction includes: Based on the business document information, the payment business logic data is determined; The validity of the payment authorization data is verified, and after the validity verification passes, the business logic consistency of the payment business logic data is verified. After the business logic consistency verification passes, the payment instruction is sequentially subjected to data integrity verification and risk verification. Once the risk verification passes, the payment instruction is sent to the payment platform.

3. The method according to claim 2, characterized in that, The payment authorization data includes: a user-authorized payment certificate and a user U-shield, wherein the validity verification of the payment authorization data includes: Determine whether the user-authorized payment certificate is within its validity period; If so, determine whether the payment permissions of the user's U-shield meet the preset authorization permissions; If yes, the payment authorization data is deemed to have passed the validity check; otherwise, the payment instruction is intercepted, and an exception record containing the reason for failure is generated, which is then pushed to the manual intervention interface on the payment user's end.

4. The method according to claim 2, characterized in that, The payment business logic data includes: settlement method and payment channel, wherein the business logic consistency verification of the payment business logic data is: determining whether the settlement method and payment channel match; Data integrity verification is used to check whether the required fields in the payment instruction are complete and whether they meet the preset format requirements; Accordingly, risk verification of the payment instruction includes: Identify the payee information in the payment instruction; Based on the recipient information, determine whether the recipient is a high-risk user; If so, the risk verification is deemed to have failed, and the payment instruction is intercepted, along with an exception record containing the reason for the failure. This exception record is then pushed to the manual intervention interface on the payment user's end.

5. The method according to claim 1, characterized in that, Before sending the payment instruction to the payment platform, the method further includes: Obtain the business document information corresponding to the target payment task; Business attribute information is extracted from the business document information, and based on the business attribute information, the payment strategy corresponding to the target payment task is determined from a pre-set payment strategy library. The payment strategy and the payment instruction are then sent to the payment platform, so that the payment platform, upon receiving the payment instruction, triggers a payment operation to perform the transfer payment for the target payment task based on the payment strategy, and returns the payment result corresponding to the target payment task. The payment strategy library is configured with payment strategies corresponding to different business attributes.

6. The method according to claim 1, characterized in that, The payment result includes: payment successful, payment failed, and unsuccessful delivery. Sending the payment result to the payment user's terminal includes: If the payment result is successful, the payment result will be sent to the payment success tab on the payment user's terminal. If the payment result is "not sent successfully" or "payment failed", the payment result will be sent to the payment failure tab on the payment user's terminal. If the payment result is "not sent successfully", the target payment task will also be pushed to the manual intervention processing interface on the payment user's terminal.

7. The method according to claim 1, characterized in that, The payment result also includes: payment alert information returned by the payment platform, wherein sending the payment result to the payment user includes: Based on the payment warning information, the warning level is determined; If the warning level is Level 1, the payment result will be sent to the warning failure tab on the payment user's terminal, and the target payment task will be pushed to the manual intervention interface on the payment user's terminal. If the warning level is Level 2, the payment result will be sent to the payment failure tab on the payment user's terminal, and the target payment task will be pushed to the manual intervention interface on the payment user's terminal. The payment risk corresponding to Level 2 warning is higher than that corresponding to Level 1 warning.

8. An automated processing system for transfer payment instructions based on a strategy-triggered mechanism, characterized in that, include: The signature approval unit is used to obtain the approval result of the electronic payment record settlement signature of the target payment task in real time, and to determine whether the approval result is approved. The payment instruction generation unit is used to generate a payment instruction based on the electronic payment record settlement signature when the signature approval unit determines that the approval result is approved; An automatic payment function detection unit is used to obtain the automatic payment parameters configured by the payment user terminal corresponding to the target payment task, and determine whether the payment user terminal has enabled the automatic submission function of transfer payment instructions based on the automatic payment parameters. An automatic payment unit is used to perform payment verification on the payment instruction when the automatic payment function detection unit determines that the payment user has enabled the automatic submission function of the transfer payment instruction. After the payment verification is passed, the payment instruction is sent to the payment platform so that the payment platform can perform the transfer payment of the target payment task according to the payment instruction and return the payment result corresponding to the target payment task. The payment feedback unit is used to send the payment result to the payment user terminal so that the payment user terminal can visualize the payment result.

9. An electronic device, characterized in that, include: The system comprises a memory, a processor, and a transceiver connected in sequence, wherein the memory is used to store computer programs, the transceiver is used to send and receive messages, and the processor is used to read the computer programs and execute the automated processing method for transfer payment instructions based on a policy triggering mechanism as described in any one of claims 1 to 7.

10. A computer program product containing instructions, characterized in that, When the instruction is executed on the computer, it causes the computer to perform the automated processing method for transfer payment instructions based on the policy triggering mechanism as described in any one of claims 1 to 7.

Images