Debt confirmation method applied to consumer debt system
By electronically managing banks' bad debts through the consumer debt system, the problem of banks recovering bad debts has been solved, and debtors have been able to independently confirm and remove their credit records, thus promoting social and economic development.
Patent Information
- Application Number
- CN202511329946.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-17
- Publication Date
- 2025-12-23
AI Technical Summary
Banks have difficulty recovering bad debts through traditional means, which leads to debtors becoming defaulters and making it difficult to remove their records from the credit reporting system.
The consumer debt system receives and stores personal debt information from banks' bad debts, classifying it into signed and unsigned states. After user account verification, debt data is displayed, and after signing confirmation, the signed document is uploaded and saved, realizing the electronic management and confirmation of debt data.
Debtors can identify and eliminate bad debts owed to banks, helping banks recover bad debts, remove records of dishonest judgment debtors, and promote social and economic development.
Smart Images

Figure CN121190184A_ABST
Abstract
Description
[TECHNICAL FIELD]
[0001] The present application relates to a debt confirmation method applied to a debt consumption system. [BACKGROUND]
[0002] Under the background of further development of market economy, various debts occur frequently, especially some bank debts become bad debts, and it is difficult for banks to recover debts through traditional channels. At the same time, the bad debtors of banks will be recorded as dishonest persons in the credit investigation system, and the dishonest persons will be restricted in consumption, and the general dishonest persons also cannot repay the debts to eliminate the record of dishonest persons in the credit investigation system.
[0003] For example, the application 202111304448.9 discloses a system and method for debt elimination through consumption, wherein the system specifically discloses a user unit, a server and a data updating unit, and the method includes the following steps: S1: the user registers as a consumer, a merchant, a debtor and a creditor through an APP; S2: activate the consumption system; S3: activate the debt elimination system. The contradictions between the debtor and the creditor and the contradictions between the consumer and the merchant are organically unified and coordinated and transformed into a cooperative relationship, and the debts are converted into points and participated in the consumption behavior, and interact with each other. In the above patent scheme, the creditor and the debtor are set, and new debts will be generated between the creditor and the debtor, which will increase the debtor's own debts, and the debtor cannot confirm the bank bad account personal debt, which is easy to generate non-self debts, so that the debtor cannot repay the bank bad account debt to eliminate the record of dishonest persons. [SUMMARY]
[0004] The present application overcomes the shortcomings of the prior art and provides a debt confirmation method applied to a debt consumption system.
[0005] To achieve the above purpose, the following technical solutions are adopted:
[0006] A debt confirmation method applied to a debt consumption system, characterized in that it comprises
[0007] In the first stage, the debt data request is received, the user account information is obtained by analysis, all associated debt data is queried and fed back according to the user account information, and the debt data includes signed confirmation debt data and unsigned confirmation debt data;
[0008] In the second stage, the unsigned confirmation debt data in the debt data is queried, and the signed file is submitted after signature confirmation;
[0009] In the third stage, the signed file is saved after being received, a signed success response is fed back, and a prompt is given.
[0010] The debt confirmation method applied to a consumer debt system as described above is characterized by: including, before the first stage, a...
[0011] S0. Receive and store personal debt information from multiple bank bad debts, and store multiple commodity inventory information, with commodity prices not exceeding the prices of similar commodities on mainstream sales platforms.
[0012] The debt confirmation method applied to the consumer debt system as described above is characterized by: the first stage including...
[0013] S1. Trigger the debt confirmation instruction in the mini-program client;
[0014] S2. The mini-program client sends a request to the PHP backend server to obtain debt data.
[0015] The S3 and PHP backend servers parse and obtain user account information.
[0016] S4, the PHP backend server queries the database for debt records based on the user account signal;
[0017] S5. The database returns all debt data associated with this user account;
[0018] The S6 and PHP backend servers send all debt data back to the mini-program client.
[0019] S7. The mini-program client displays all debt data associated with the user account.
[0020] The debt confirmation method applied to the consumer debt system as described above is characterized in that: in S2, the mini-program client also sends login credential information associated with the user account to the PHP backend server; in S3, the PHP backend server verifies the validity of the login credential information before parsing the user account information.
[0021] The debt confirmation method applied to the consumer debt system as described above is characterized in that: in S6, the PHP backend server classifies the debt data into signed and confirmed debt data and unsigned and confirmed debt data according to the signing status, and feeds it back to the mini-program client; in S7, the mini-program client displays the list of signed and confirmed debt data and the list of unsigned and confirmed debt data.
[0022] The debt confirmation method applied to the consumer debt system as described above is characterized in that: the second stage includes...
[0023] S8. Select any debt data record in the list of unsigned and unconfirmed debt data displayed in the mini-program client, and click the sign button;
[0024] S9. The mini-program client displays the debt relief agreement details for this debt;
[0025] S10. Click the signature button in the mini-program client to enter the signature confirmation process;
[0026] S11. The signature skateboard component is brought up in the mini-program client;
[0027] S12. Write your signature on the signature skateboard component in the mini-program client;
[0028] S13. Click the signature confirmation button in the mini-program client to submit the signed confirmation document and associated user account information to the PHP backend server.
[0029] The debt confirmation method applied to the consumer debt system as described above is characterized in that: the third stage includes...
[0030] S14. The mini-program client will convert the signed confirmation document into an image file;
[0031] S15. The mini-program client sends a signed confirmation image and associated user account information to the PHP backend server.
[0032] S16. The PHP backend server sends the signed confirmation image and associated user account information to the outside world for storage.
[0033] S17. After storage, return the file storage path information to the PHP backend server;
[0034] S18. The PHP backend server sends the debt data update instruction and the file storage path information of the debt signing document to the database.
[0035] S19. The database updates the debt data status to "signed and confirmed" and stores the file storage path information of the signed debt document, and returns the update operation result to the PHP backend server;
[0036] S20. The PHP backend server returns a successful signing response to the mini-program client.
[0037] S21. The mini-program client displays a success message;
[0038] S22. The mini-program client updates and displays the debt signing status as "signing confirmed".
[0039] The debt confirmation method applied to the consumer debt system as described above is characterized in that: in S14, the mini-program client converts the signed confirmation document into a PNG format image file.
[0040] The debt confirmation method applied to the consumer debt system as described above is characterized in that: in S15, the PHP backend server sends a signed confirmation image and associated user account information to the file storage server; in S16, the file storage server stores the information and returns the file storage path information to the PHP backend server.
[0041] The debt confirmation method applied to the consumer debt system as described above is characterized in that: in S22, the mini-program client updates the debt signing status in the unsigned debt confirmation data list to the signed confirmation status.
[0042] The beneficial effects of this invention are:
[0043] This invention provides a consumer debt repayment system that advances personal debts owed to banks. It acquires and pre-stores information on these debts in a database. After a user's account is matched with their personal debts, the debt is repaid through the system. The system automatically categorizes debt data into signed and unsigned categories based on their status, allowing debtors to track the ownership status of all their debts. It also updates the database and the mini-program client with debt status information in real time, achieving dual-status management. Furthermore, the system verifies login credentials and links user accounts to debt data for verification, improving the accuracy of debt data association. After signing a confirmation document for unsigned debt data, the system uploads and saves the signed confirmation document, its storage path, and the signing time, ensuring data integrity. This system allows debtors to confirm all their personal debts owed to banks, facilitating future debt repayment through shopping and consumption. This helps banks recover bad debts and also helps users repay their debts, thereby removing them from the list of defaulters. [Image Description]
[0044] Fig. 1 This is a flowchart of the method of the present invention;
[0045] Fig. 2 This is a system structure diagram of the present invention. [Detailed Implementation]
[0046] The technical solutions in the embodiments of the present invention will now be clearly and completely described in conjunction with the accompanying drawings.
[0047] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of the components in a specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly. Furthermore, descriptions involving "preferred," "second-best," etc., in this invention are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "preferred" or "second-best" may explicitly or implicitly include at least one of those features.
[0048] like Figs. 1-2 As shown, a debt confirmation method applied to a consumer debt system includes:
[0049] S0. Receives and stores personal debt information on multiple bank bad debts, as well as inventory information on multiple commodities, with commodity prices not exceeding those of similar commodities on mainstream sales platforms. This allows debtors to resolve bank bad debts through consumption after logging into their accounts, achieving the function of debt relief through consumption. This eliminates negative personal credit records, greatly promoting debtors' continued debt repayment, while also helping banks recover bad debt claims and promoting social and economic development.
[0050] The first phase involves receiving a request to retrieve debt data, parsing it to obtain user account information, and then querying and returning all associated debt data based on that information. This debt data includes both signed and unsigned confirmed debt data. Specifically, it includes...
[0051] S1. Trigger the debt confirmation instruction in the mini-program client, specifically by navigating to the "My Debts" page in the mini-program client;
[0052] S2. The mini-program client sends a request to the PHP backend server to obtain debt data. The mini-program client also sends login credential information associated with the user account to the PHP backend server.
[0053] S3, the PHP backend server parses the user account information. Before parsing the user account information, the PHP backend server verifies the validity of the login credentials.
[0054] S4, the PHP backend server queries the database for debt records based on the user account signal;
[0055] S5. The database returns all debt data associated with this user account;
[0056] The S6 and PHP backend servers send all debt data to the mini-program client. Specifically, the PHP backend servers categorize debt data into signed and confirmed debt data and unsigned and confirmed debt data based on their signing status, and then send this data to the mini-program client.
[0057] S7. The mini-program client displays all debt data associated with the user account; specifically, the mini-program client displays a list of signed and confirmed debt data and a list of unsigned and unconfirmed debt data.
[0058] The second stage involves querying the debt data for unsigned and unconfirmed debt data, and submitting the signed documents after confirmation.
[0059] S8. Select any debt data record in the list of unsigned and unconfirmed debt data displayed in the mini-program client, and click the sign button;
[0060] S9. The mini-program client displays the debt relief agreement details for this debt;
[0061] S10. Click the signature button in the mini-program client to enter the signature confirmation process;
[0062] S11. The signature skateboard component is brought up in the mini-program client;
[0063] S12. Write your signature on the signature skateboard component in the mini-program client;
[0064] S13. Click the signature confirmation button in the mini-program client to submit the signed confirmation document and associated user account information to the PHP backend server.
[0065] The third stage involves receiving and saving the signed documents, receiving a successful signing response and notification, specifically including:
[0066] S14. The mini-program client will convert the signed confirmation document into an image file; specifically, the mini-program client will convert the signed confirmation document into a PNG image file.
[0067] S15. The mini-program client sends a signed confirmation image and associated user account information to the PHP backend server; specifically, the PHP backend server sends the signed confirmation image and associated user account information to the file storage server.
[0068] S16. The PHP backend server sends the signed confirmation image and associated user account information to the outside world for storage; specifically, after storing the information, the file storage server returns the file storage path information to the PHP backend server.
[0069] S17. After storage, return the file storage path information to the PHP backend server;
[0070] S18. The PHP backend server sends the debt data update instruction and the file storage path information of the debt signing document to the database.
[0071] S19. The database updates the debt data status to "signed and confirmed" and stores the file storage path information of the signed debt document, and returns the update operation result to the PHP backend server;
[0072] S20. The PHP backend server returns a successful signing response to the mini-program client.
[0073] S21. The mini-program client displays a success message;
[0074] S22. The mini-program client updates and displays the debt signing status as signed and confirmed; specifically, the mini-program client updates the debt signing status in the list of unsigned and unconfirmed debts to signed and confirmed status.
[0075] like Fig. 2 As shown, the system in this case includes:
[0076] User client devices, such as smart devices like mobile phones and tablets, include processors, memory, and touch screens, as well as network interfaces, operating systems, and WeChat mini-program runtime environments. They are used to provide user interfaces (UIs), render the "My Debts" page and signature canvas, receive user input, send requests to the backend, and receive responses.
[0077] The PHP backend server includes a high-performance multi-core CPU, RAM, and solid-state drive (SSD), as well as a software environment with a network interface card (NIC) running Apache / Nginx+PHP. It is used to execute core business logic, process HTTP requests (including token verification), interact with databases and file systems, perform data classification and processing, and generate responses.
[0078] The database includes a high-performance CPU, large-capacity RAM and RAID disk array, as well as a network interface card (NIC) running a MySQL relational database management system, used to store, manage and provide user data and debt records (including fields such as ID, status, and signature file path).
[0079] The file storage server includes a large-capacity hard disk array, a network interface card (NIC), and software that runs file system and object storage services. It is used to persistently store user-uploaded signed image files (PNG format) and return the file path for the PHP backend server to record.
[0080] Network infrastructure, including routers and switches, as well as firewalls and Internet Service Provider (ISP) connections, provides secure and reliable LAN and WAN data connection channels between various hardware components.
[0081] like Figs. 1-2 As shown, the data flow of the connection relationships between various hardware components in this system includes:
[0082] The data flow between the user's client device's mini-program client and the PHP backend server via the Internet / Network includes: step S2, in which the mini-program client sends a request to the PHP backend server to obtain debt data, carrying the Token login credentials; step S15, in which the mini-program client uploads the signature confirmation image and the associated user account form data; and step S20, in which the PHP backend server returns a signature success response to the mini-program client.
[0083] The data flow between the PHP backend server and the database via a LAN / private network includes: step S4, in which the PHP backend server sends an SQL query carrying user account information to the database; step S5, in which the database returns a set of all debt data records associated with the user account; step S18, in which the PHP backend server sends an SQL Update to the database to update the debt status and signature path; and step S19, in which the database returns the update operation result to the PHP backend server, such as success or failure.
[0084] The data flow between the PHP backend server and the file storage server via a LAN / private network includes step S16, in which the PHP backend server writes the received signed image file data to the storage directory of the file storage server; and step S17, in which the file storage server returns file storage path information to the PHP backend server.
[0085] The data flow between the user's client device's mini-program client and the file storage server is as follows: the user's signed confirmation file data is transferred through the PHP backend server and finally stored on the file storage server.
[0086] The data flow between all components and the network infrastructure is such that all hardware components are connected to the network infrastructure via wired or wireless means to achieve interconnection; firewalls are typically deployed between the application server and the Internet to ensure security.
[0087] This case utilizes automated data classification, secure identity authentication, standardized document processing, and reliable storage mechanisms to achieve fully electronic processing from debt data display to handwritten signature collection, document conversion, and storage, ensuring the validity of the signing process, data integrity, and a smooth user experience.
[0088] The above are merely preferred embodiments of the present invention and do not limit the patent scope of the present invention. All equivalent structural transformations made using the contents of the present invention's specification and drawings under the inventive concept of the present invention, or direct or indirect applications in other related technical fields, are included within the patent protection scope of the present invention.
Claims
1. A debt confirmation method applied to a consumer debt system, characterized in that: Including The first stage involves receiving requests to obtain debt data, parsing the user account information, and querying and returning all associated debt data based on the user account information. The debt data includes both signed and unsigned debt data. The second stage involves querying the debt data for unsigned and unconfirmed debt data, and submitting the signed documents after confirmation. The third stage involves receiving and saving the signed document, and receiving a successful signing response and notification.
2. The debt confirmation method applied to a consumer debt system according to claim 1, characterized in that: The first phase also includes S0. Receive and store personal debt information from multiple bank bad debts, and store multiple commodity inventory information, with commodity prices not exceeding the prices of similar commodities on mainstream sales platforms.
3. The debt confirmation method applied to a consumer debt system according to claim 1, characterized in that: The first phase includes: S1. Trigger the debt confirmation instruction in the mini-program client; S2. The mini-program client sends a request to the PHP backend server to obtain debt data. The S3 and PHP backend servers parse and obtain user account information. S4, the PHP backend server queries the database for debt records based on the user account signal; S5. The database returns all debt data associated with this user account; The S6 and PHP backend servers send all debt data back to the mini-program client. S7. The mini-program client displays all debt data associated with the user account.
4. The debt confirmation method applied to a consumer debt system according to claim 3, characterized in that: In S2, the mini-program client also sends login credential information associated with the user account to the PHP backend server; in S3, the PHP backend server verifies the validity of the login credential information before parsing the user account information.
5. The debt confirmation method applied to a consumer debt system according to claim 3, characterized in that: In S6, the PHP backend server categorizes debt data into signed and unsigned confirmed debt data based on the signing status and sends the results to the mini-program client; in S7, the mini-program client displays the lists of signed and unsigned confirmed debt data.
6. The debt confirmation method applied to a consumer debt system according to claim 5, characterized in that: The second phase includes: S8. Select any debt data record in the list of unsigned and unconfirmed debt data displayed in the mini-program client, and click the sign button; S9. The mini-program client displays the debt relief agreement details for this debt; S10. Click the signature button in the mini-program client to enter the signature confirmation process; S11. The signature skateboard component is brought up in the mini-program client; S12. Write your signature on the signature skateboard component in the mini-program client; S13. Click the signature confirmation button in the mini-program client to submit the signed confirmation document and associated user account information to the PHP backend server.
7. The debt confirmation method applied to a consumer debt system according to claim 6, characterized in that: The third stage includes: S14. The mini-program client will convert the signed confirmation document into an image file; S15. The mini-program client sends a signed confirmation image and associated user account information to the PHP backend server. S16. The PHP backend server sends the signed confirmation image and associated user account information to the outside world for storage. S17. After storage, return the file storage path information to the PHP backend server; S18. The PHP backend server sends the debt data update instruction and the file storage path information of the debt signing document to the database. S19. The database updates the debt data status to "signed and confirmed" and stores the file storage path information of the signed debt document, and returns the update operation result to the PHP backend server; S20. The PHP backend server returns a successful signing response to the mini-program client. S21. The mini-program client displays a success message; S22. The mini-program client updates and displays the debt signing status as "signing confirmed".
8. The debt confirmation method applied to a consumer debt system according to claim 7, characterized in that: The S14 mini-program client will convert the signed confirmation document into a PNG image file.
9. The debt confirmation method applied to a consumer debt system according to claim 7, characterized in that: In S15, the PHP backend server sends a signed confirmation image and associated user account information to the file storage server; in S16, the file storage server returns the file storage path information to the PHP backend server after storing the file.
10. A debt confirmation method applied to a consumer debt system according to claim 7, characterized in that: In the S22 mini-program client update, the debt signing status in the unsigned and unconfirmed debt data list is now marked as signed and confirmed.
Citation Information
Patent Citations
System and method for debt removal through consumption
CN114004657A