Staged payment implementation method and system based on user order

Abstract

The invention discloses a staged payment implementation method and system based on a user order, and the method comprises the following steps: recording a payment mode selected by a user, and storing the payment behavior of the user in a cache; reporting the payment behavior data to a server regularly, and clearing payment behavior data cache; the server receives and analyzes the payment behavior data and stores the data; the background service performs staging processing on the order according to the created staging payment rule; and according to the staging information of the order, the payment condition of the order is analyzed, an order state model is constructed, and a corresponding payment plan and a reminding notice are generated. According to the invention, based on detailed and dynamically updated order data, highly personalized payment management can be realized, and the management efficiency and the user satisfaction are significantly improved. The personalized payment plan not only optimizes the payment experience of the user, but also increases the fund circulation efficiency of the platform and the loyalty of the user, makes the fund management more accurate, and effectively improves the use efficiency and recovery rate of the fund.

Description

Technical Field

[0001] The present invention relates to the fields of e-commerce and financial technology, and in particular to a method and system for implementing installment payment based on user orders. Background Art

[0002] In the current e-commerce environment, user needs are diversified, and payment methods are becoming more diversified and personalized. The traditional full payment model may bring certain financial pressure to users for some large-value goods or services. In order to alleviate this pressure, it is particularly important to provide a flexible installment payment method. Existing installment payment methods are mostly concentrated in online payment, while offline payment methods are relatively rare.

[0003] In response to this situation, this paper proposes a method for implementing order installment payment that supports two payment modes: offline payment code and sales QR code. Summary of the invention

[0004] In order to solve the problems existing in the prior art, the present invention provides a method and system for implementing installment payment based on user orders, which has the advantages of automatically processing installment payments, providing enterprises with in-depth financial insights and optimizing user payment experience. The method implements the installment payment function of the order by analyzing the user's purchase history and credit data, so that users can flexibly manage payments according to their own financial conditions. In addition, the system can also provide personalized shopping suggestions and preferential activities by building user portraits, thereby improving user experience and increasing the sales efficiency of merchants.

[0005] To achieve the above object, the present invention adopts a method for implementing installment payment based on user orders, comprising the following steps:

[0006] S1. When a user browses a product and decides to purchase it, the system provides the option of installment payment. After the order is generated, the system instantly generates an offline payment code or sales QR code, and the user pays the deposit by scanning the code. After the payment is completed, the system automatically records the payment information and updates the order status to "deposit paid" to ensure that both parties are clear about the payment status.

[0007] S2. The system regularly collects order payment data from the database. The order payment data is first cleaned to remove all invalid and erroneous data entries. After that, the data is standardized using a special format conversion tool to ensure that all data meets the analysis requirements. The cleaned and standardized data is stored in relational and non-relational databases to provide support for subsequent data analysis and report generation.

[0008] S3. The system backend service uses machine learning algorithms to analyze the stored payment data, including but not limited to the frequency distribution of payment time, payment method preferences, and payment amount statistics. Based on the analysis results, the system uses predefined rules and algorithms to generate corresponding payment tags for each order. The generation and update of payment tags are dynamic to ensure that the latest trends in payment behavior can be reflected in real time.

[0009] S4. After paying the deposit, the user continues to pay the balance by scanning the offline payment code or sales QR code. After each successful payment of the balance, the system immediately captures the payment behavior and updates the order status to "balance paid", while recording the payment details. After the payment is successful, the system automatically sends a payment confirmation notification to the user to ensure that the user is clearly aware of his or her payment behavior.

[0010] S5. The system provides a user interface that allows users to check the payment status of their orders at any time, including the specific amount of the deposit and balance paid. At the same time, the system generates detailed payment record reports for the backend administrator, who uses these reports to analyze income, monitor payment behavior, and evaluate the overall performance of the installment payment system. The report generation function supports customized options.

[0011] Optionally, in some embodiments of the present invention, step S1 includes: defining the collection event name and the information to be reported, the server extracts information about the payment event triggered by the user, encrypts the information with RSA, and stores the encrypted information on the server.

[0012] Optionally, in some embodiments of the present invention, step S2 includes: the server side reports the payment behavior data recorded on the server to the application API interface in batches every 10 seconds. If the data reporting fails, it will enter the retry queue. If the user terminates the process, it will be re-reported the next time it enters. If the data reporting is successful, the encrypted data that has been reported will be cleaned up.

[0013] Optionally, in some embodiments of the present invention, step S3 includes: applying the API interface to receive data, verifying the data to prevent the interface from being attacked, decrypting the data if the verification passes, filtering the decrypted data again, and finally saving the payment behavior data in the order library.

[0014] Optionally, in some embodiments of the present invention, step S4 includes: the background service cleans, denoises, and converts the data, and then extracts the payment behavior labels of the deposit order and the final payment order from the processed data, and creates corresponding labels for the user.

[0015] Optionally, in some embodiments of the present invention, step S5 includes: building an order status model based on the payment behavior label, through the payment behavior and the user's order information, visually displaying the user's payment behavior label, and configuring display content and display rules for the label in the background by analyzing and understanding the user's payment preferences; when the user triggers a payment behavior, the filtered and sorted recommended label configuration content is displayed to the user in a user-friendly manner.

[0016] Optionally, in some embodiments of the present invention, the payment behavior includes the user browsing products, selecting a payment mode, submitting payment, and confirming the order.

[0017] On the other hand, the present invention provides an installment payment implementation system based on user orders, including a data collection module, a payment behavior label extraction module, an order status construction module and an application interface module; the data collection module is responsible for obtaining the user's payment behavior data from multiple data sources; the payment behavior label extraction module uses natural language processing and machine learning technology to process and analyze the user's payment behavior data and extract the payment behavior label; the order status construction module associates and integrates the extracted payment behavior label with the user's payment behavior to generate an order status; the application interface module allows other applications or services to access the system through an API to obtain order status data and perform related applications.

[0018] Optionally, in some embodiments of the present invention, the user's personal information includes the user's browsing of products, selection of payment mode, submission of payment and confirmation of order behaviors, as well as the user's non-privacy information.

[0019] Optionally, in some embodiments of the present invention, the order status building module configures display content and display rules for the tag, and when the user triggers a payment behavior, the filtered and sorted content of the recommended tag configuration is displayed to the user in a user-friendly manner.

[0020] The beneficial effects of the present invention are:

[0021] (1) By building accurate order status, the system can better understand the user's payment needs, capabilities, and preferences, thereby providing optimized payment plans, reminder notifications, and service experiences;

[0022] (2) Through the accurate classification and identification of payment behavior tags, the system can more accurately manage finances and assess user credit.

[0023] (3) Payment behavior tags can help the system segment and classify users and optimize resource allocation and service provision;

[0024] (4) Compared with the traditional order management method, the method based on user payment behavior is more accurate and dynamic. It can capture the user's payment changes and behavior patterns in real time, so as to better understand the user's needs and preferences. The system has broad application prospects in the fields of financial management, credit assessment, payment behavior analysis, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 The present invention is a flowchart of a method for implementing installment payment based on user orders according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0027] Based on the current offline payment methods, there is a lack of flexible installment payment methods, such as Figure 1 As shown, the present invention is a method for implementing installment payment based on user orders, comprising the following steps:

[0028] S1. Record the payment method selected by the user and save the user's payment behavior in the cache; the user chooses to pay in installments and pay a deposit. When the user browses the product and decides to buy it, the system provides the option of paying in installments. The user can choose this method when creating an order. After the order is generated, the system instantly generates an offline payment code or sales QR code, and the user can pay the deposit by scanning the code. This step is not only convenient for users, but also provides merchants with the immediacy of capital flow. After the payment is completed, the system automatically records the payment information and updates the order status to "deposit paid" to ensure that both parties are clear about the payment status.

[0029] S2. Regularly report payment behavior data to the server and clean up the payment behavior data cache; it is crucial to process the data generated after the user pays the deposit. The system regularly collects order payment data from the database, including payment time, amount, method and other information. The data is first cleaned to remove all invalid and erroneous data entries (such as duplicate payments, format errors, etc.). After that, a special format conversion tool is used to standardize the data to ensure that all data meets the analysis requirements. The cleaned and standardized data is stored in relational and non-relational databases to provide support for subsequent data analysis and report generation.

[0030] S3. The server receives and parses the payment behavior data and saves the data; analyzes the payment behavior and generates payment tags. The system backend service uses machine learning algorithms to conduct in-depth analysis on the stored payment data. The analysis includes but is not limited to the frequency distribution of payment time, payment method preferences, and payment amount statistics. Based on these analysis results, the system uses predefined rules and algorithms to generate corresponding payment tags for each order, such as "fast payment user", "prefer digital payment", etc. These tags help the system better understand user behavior and optimize the payment experience accordingly. The generation and update of payment tags are dynamic to ensure that the latest trends in payment behavior are reflected in real time.

[0031] S4. The backend service processes the order in installments according to the created installment payment rules; after paying the deposit, the user needs to continue to pay the balance by scanning the offline payment code or the sales QR code. After each successful payment of the balance, the system immediately captures the payment behavior and updates the order status to "balance paid", while recording the payment details, including the payment amount and time. After the payment is successful, the system will also automatically send a payment confirmation notification to the user to ensure that the user is clearly aware of his or her payment behavior and enhance the user experience.

[0032] S5. Analyze the payment status based on the order's installment information, build an order status model, and generate corresponding payment plans and reminder notifications. The system provides a user interface that allows users to check their order payment status at any time, including the specific amount of the deposit and balance paid. At the same time, the system generates detailed payment record reports for the backend administrator, who can use these reports to analyze revenue, monitor payment behavior, and evaluate the overall performance of the installment payment system. The report generation function supports customized options, such as selecting a specific time period, order type, or payment method for analysis to meet different management needs.

[0033] In this technical solution, when the user chooses the offline payment code or sales QR code payment method, the client will record the payment behavior and report it to the application API interface. The service will clean, denoise, convert the format of the reported data, and generate the corresponding installment payment tag for the order. Finally, based on the installment payment tag of the order, an order status model is established. The order status can be applied to scenarios such as financial management, user credit assessment, and payment behavior analysis. By combining the order status with specific business scenarios, more accurate financial monitoring and user payment experience optimization can be achieved.

[0034] In a further technical solution, the collection and payment behavior in step S1 includes:

[0035] Record the payment method selected by the user and save the user's payment behavior in the cache.

[0036] In this technical solution, it is necessary to define the collection event name and the information that needs to be reported, such as payment method, payment amount, order number. The client extracts information about the payment event triggered by the user, encrypts the information with RSA, and saves the encrypted information in the cache.

[0037] In a further technical solution, step S2 includes:

[0038] Report payment behavior data to the server regularly and clear the payment behavior data cache.

[0039] In this technical solution, because there may be a large number of payment behaviors, the client will report the payment behavior data to the application API interface every 10 seconds. If the data reporting fails, it will enter the retry queue. If the user terminates the process, it will be re-reported the next time it enters. If the data reporting is successful, the encrypted data reported will be cleaned up.

[0040] In a further technical solution, step S3 includes:

[0041] The server receives and parses the payment behavior data and saves the data.

[0042] In this technical solution, the API interface is used to receive data and verify the data to prevent the interface from being attacked. If the verification passes, the data is decrypted and the decrypted data is filtered again. Finally, the payment behavior data is saved in the order management system.

[0043] In a further technical solution, step S4 includes:

[0044] The backend service processes the order in installments according to the created installment payment rules.

[0045] In this technical solution, in order to improve the flexibility and applicability of payment, it is necessary to set up installments for orders through the service to ensure that the payment plan is accurate, consistent, complete, and in line with the user's payment ability, and then generate the corresponding installment payment plan from the processed data.

[0046] In a further technical solution, step S5 includes:

[0047] Based on the order's installment information, the user's payment behavior and order information, an order status model is built, and corresponding payment plans and reminder notifications are generated.

[0048] In this technical solution, based on the installment payment information of the order, the order status model is constructed through the user's payment history, order amount, payment method and other behaviors and order information, and the payment progress of the order is visualized. By analyzing and understanding the user's payment preferences, reminder content and reminder rules are configured for the order in the background. When the user triggers a payment behavior, the filtered and sorted reminder configuration content will be displayed to the user in a user-friendly manner.

[0049] The present invention also provides a system for constructing a more accurate order status by analyzing the user's payment behavior, and the system includes a data collection module, a payment behavior label extraction module, an order status construction module and an application interface module. The data collection module is responsible for obtaining the user's payment behavior data from multiple data sources, such as payment method, payment amount, order number, etc. The payment behavior label extraction module uses natural language processing and machine learning technology to process and analyze the original data and extract payment behavior labels, such as payment method, payment frequency, etc. The order status construction module associates and integrates the extracted payment behavior labels with the user's order information to generate an accurate status of the order. These statuses include detailed information such as the payment progress of the order, the remaining payment amount, and the estimated completion time, so as to better understand user needs and provide optimized payment experience and management. The application interface module allows other applications or services to access the system through an API to obtain order status data and perform related applications.

[0050] Through the above-mentioned user order-based installment payment implementation method and system of the present invention, based on detailed and dynamically updated order data, highly personalized payment management can be achieved, significantly improving management efficiency and user satisfaction. Personalized payment plans not only optimize the user's payment experience, but also increase the platform's capital circulation efficiency and user loyalty, while making capital management more accurate, effectively improving the efficiency and recovery rate of capital use.

[0051] In order to better illustrate the method and system for implementing installment payment based on user orders of the present invention, the following is a detailed description through specific embodiments. It should be noted that the following embodiments are only schematic illustrations of the present invention, and the protection scope of the present invention is not limited thereto.

[0052] Example:

[0053] like Figure 1 As shown, the present invention provides a method for implementing installment payment based on user orders, comprising the following steps:

[0054] S1. Record the payment method selected by the user and save the relevant information of the user's payment in the cache;

[0055] S2. Report the payment information data to the server regularly and clear the payment information data cache;

[0056] S3, the server receives and parses the payment information data and saves the data;

[0057] S4. The backend service processes the order in installments according to the created installment payment rules;

[0058] S5. Analyze the payment status according to the installment information of the order, build an order status model, and generate corresponding payment plans and reminder notifications.

[0059] In this embodiment, when the user chooses the offline payment code or sales QR code payment method, the client will record the payment information and report it to the application API interface. The service will clean, denoise, convert the format and other operations on the reported data to generate a corresponding installment payment plan for the order. Finally, based on the installment information of the order, an order status model is established. The order status can be applied to scenarios such as financial management, user credit assessment, and payment behavior analysis. By combining the order status with specific business scenarios, more accurate financial monitoring and user payment experience optimization can be achieved.

[0060] In another embodiment, step S1 comprises:

[0061] A1. Determine the payment method;

[0062] A2. Confirm and collect payment information;

[0063] A3. Cache payment data;

[0064] In this embodiment, it is necessary to define the collection event name and the information to be reported, such as payment method, payment amount, and order number. The client extracts information about the payment event triggered by the user, encrypts the information with RSA, and saves the encrypted information in the cache.

[0065] In another embodiment, step S2 comprises:

[0066] Report payment information data to the server regularly and clear the payment information data cache.

[0067] In this embodiment, because the payment information may be large, the client will report the payment information data to the application API interface every 10 seconds. If the data reporting fails, it will enter the retry queue. If the user terminates the process, it will be re-reported the next time it enters. If the data reporting is successful, the encrypted data reported will be cleaned up.

[0068] In another embodiment, step S3 comprises:

[0069] The server receives and parses the payment information data and saves the data.

[0070] In this embodiment, the application API interface receives data and verifies the data to prevent the interface from being attacked. If the verification passes, the data is decrypted and the decrypted data is filtered again, and finally the payment information data is saved in the order management system.

[0071] In another embodiment, step S4 comprises:

[0072] The backend service processes the order in installments according to the created installment payment rules.

[0073] In this embodiment, it is necessary to create a custom installment payment rule. Since the payment information data is relatively large, it is necessary to set a corresponding installment payment plan for the order through the service.

[0074] In another embodiment, step S5 comprises:

[0075] Based on the order's installment information, the user's payment behavior and order information, an order status model is built, and corresponding payment plans and reminder notifications are generated.

[0076] In this embodiment, according to the installment payment information of the order, through the user's payment history, order amount, payment method and other behaviors and order information, an order status model is constructed to visualize the payment progress of the order. By analyzing and understanding the user's payment preferences, reminder content and reminder rules are configured for the order in the background. When the user triggers a payment behavior, the filtered and sorted reminder configuration content is displayed to the user in a user-friendly manner. The payment progress of the order is visualized, that is, the order status model, and the display data is configured for the installment payment plan, that is, the payment plan and reminder notification are generated for the user.

[0077] The present invention also provides a system for constructing a more accurate order status by analyzing the user's payment behavior, the system comprising a data collection module, a payment behavior label extraction module, an order status construction module and an application interface module. The data collection module is responsible for obtaining the user's payment behavior data from multiple data sources, such as payment method, payment amount, order number, etc. The payment behavior label extraction module uses natural language processing and machine learning technology to process and analyze the raw data and extract payment behavior labels, such as payment method, payment frequency, etc.

[0078] The order status building module associates and integrates the extracted payment behavior tags with the user's order information to generate the precise status of the order. These statuses include detailed information such as the payment progress of the order, the remaining payment amount, and the estimated completion time, so as to better understand user needs and provide optimized payment experience and management. The application interface module allows other applications or services to access the system through APIs to obtain order status data and perform related applications.

[0079] The above-mentioned embodiments only express the specific implementation of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the scope of the present invention. It should be pointed out that, for ordinary technicians in this field, several variations and improvements can be made without departing from the concept of the present invention, which all belong to the protection scope of the present invention.

Claims

1. A method for implementing installment payment based on user orders, characterized in that: The following steps are involved: S1. When users browse products and decide to purchase, the system provides the option of installment payment. After the order is generated, the system immediately generates an offline payment code or sales QR code, and the user pays the deposit by scanning the code. After the payment is completed, the system automatically records the payment information and updates the order status to "deposit paid" to ensure that both parties are clear about the payment status. S2. The system regularly collects order payment data from the database. The order payment data is first cleaned to remove all invalid and erroneous data entries. After that, the data is standardized using a special format conversion tool to ensure that all data meets the analysis requirements. The cleaned and standardized data is stored in relational and non-relational databases to provide support for subsequent data analysis and report generation. S3. The system backend service uses machine learning algorithms to analyze the stored payment data, including but not limited to the frequency distribution of payment time, payment method preferences, and payment amount statistics. Based on the analysis results, the system uses predefined rules and algorithms to generate corresponding payment tags for each order. The generation and update of payment tags are dynamic to ensure that the latest trends in payment behavior can be reflected in real time. S4. After paying the deposit, the user continues to pay the balance by scanning the offline payment code or sales QR code. After each successful payment of the balance, the system immediately captures the payment behavior and updates the order status to "balance paid", while recording the payment details. After the payment is successful, the system automatically sends a payment confirmation notification to the user to ensure that the user is clearly aware of his or her payment behavior. S5. The system provides a user interface that allows users to check the payment status of their orders at any time, including the specific amount of the deposit and balance paid. At the same time, the system generates detailed payment record reports for the backend administrator, who uses these reports to analyze income, monitor payment behavior, and evaluate the overall performance of the installment payment system. The report generation function supports customized options.

2. A method for implementing installment payment based on user orders according to claim 1, characterized in that: Step S1 includes: defining the collection event name and the information to be reported, the server extracts information about the payment event triggered by the user, encrypts the information with RSA, and stores the encrypted information on the server.

3. A method for implementing installment payment based on user orders according to claim 1, characterized in that: Step S2 includes: the server reports the payment behavior data recorded on the server to the application API interface in batches every 10 seconds. If the data reporting fails, it will enter the retry queue. If the user terminates the process, it will be re-reported the next time it enters. If the data reporting is successful, the encrypted data reported will be cleaned up.

4. A method for implementing installment payment based on user orders according to claim 1, characterized in that: The step S3 includes: applying the API interface to receive the data, verifying the data to prevent the interface from being attacked, decrypting the data if the verification passes, filtering the decrypted data again, and finally saving the payment behavior data in the order library.

5. A method for implementing installment payment based on user orders according to claim 1, characterized in that: Step S4 includes: the backend service cleans, denoises, and converts the data, then extracts payment behavior labels for deposit orders and balance orders from the processed data, and creates corresponding labels for users.

6. A method for implementing installment payment based on user orders according to claim 1, characterized in that: Step S5 includes: building an order status model based on the payment behavior label, through the payment behavior and the user's order information, visually displaying the user's payment behavior label, configuring the display content and display rules for the label in the background by analyzing and understanding the user's payment preferences, and when the user triggers a payment behavior, the filtered and sorted recommended label configuration content is displayed to the user in a user-friendly manner.

7. A method for implementing installment payment based on user orders according to claim 6, characterized in that: Payment behavior includes users browsing products, selecting payment methods, submitting payments, and confirming orders.

8. A system for implementing installment payment based on user orders, characterized in that: It includes data collection module, payment behavior tag extraction module, order status construction module and application interface module; The data collection module is responsible for acquiring the user's payment behavior data from multiple data sources; The payment behavior label extraction module uses natural language processing and machine learning technology to process and analyze the user's payment behavior data and extract payment behavior labels; The order status building module associates and integrates the extracted payment behavior tag with the user's payment behavior to generate an order status; The application interface module allows other applications or services to access the system through the API to obtain order status data and perform related applications.

9. A system for implementing installment payment based on user orders according to claim 8, characterized in that: The user's personal information includes the user's browsing of products, selection of payment mode, submission of payment and confirmation of order, as well as the user's non-privacy information.

10. A system for implementing installment payment based on user orders according to claim 8, characterized in that: The order status building module configures display content and display rules for tags. When a user triggers a payment behavior, the filtered and sorted recommended tag configuration content is displayed to the user in a user-friendly manner.

Images