Automatic refund method and device, electronic equipment and storage medium

Abstract

The invention provides an automatic refund method and device, electronic equipment and a storage medium, and the method comprises the steps: generating an automatic refund instruction for each sold parking package when the sold parking package exceeds the preset service life of the parking package; obtaining performance data of the parking package in response to the automatic refund instruction; determining a refund amount based on the package cancel-after-verification record; if the verification record does not exist in the service life, the refund amount is the full amount; if there is a verification record within the service life, calculating a refund amount based on refund rule information of the parking package; and executing an automatic refund operation to return the refund amount to the target account. According to the embodiment of the invention, the method helps to improve the user experience.

Description

Technical Field

[0001] This application relates to the field of smart parking technology, and more specifically, to an automatic refund method, device, electronic device, and storage medium. Background Technology

[0002] With the increasing prevalence of smart parking platforms in cities, various parking packages (such as single-use packages, time-limited packages, and monthly passes) have become important service products to improve user parking convenience and cost-effectiveness. Users who pre-purchase a package can enjoy discounts on a certain number of parking visits or durations at designated parking lots within the validity period. To ensure service quality and user rights, users are allowed a refund for unused packages after their expiration.

[0003] The inventors discovered significant shortcomings in existing technologies for processing refunds of parking packages. Currently, the industry commonly employs a passive refund process that relies on user-initiated actions: when a package expires unused, the user must recall and manually submit a refund request. Upon receiving the request, the platform manually creates a work order, which is then submitted to the parking lot operator to verify the vehicle's usage history before customer service personnel conduct the final review and manually process the refund. This approach is essentially a backend processing model highly dependent on manual intervention and multi-party collaboration, thus degrading the user's shopping experience.

[0004] Therefore, a solution is needed. Summary of the Invention

[0005] In view of this, embodiments of this application provide an automatic refund method, apparatus, electronic device, and storage medium to solve the problems of low efficiency, high cost, and poor user experience caused by the reliance on manual application and manual review in the parking package refund process in the prior art.

[0006] In a first aspect, embodiments of this application provide an automatic refund method, the method comprising: For each parking package sold, when it is detected that the preset usage period of the parking package has been exceeded, an automatic refund instruction is generated; In response to the automatic refund instruction, the fulfillment data of the parking package is obtained; the fulfillment data includes at least the package cancellation records; The refund amount is determined based on the package redemption record; if there is no redemption record within the usage period, the refund amount is the full amount; if there is a redemption record within the usage period, the refund amount is calculated based on the refund rules information of the parking package. Perform an automatic refund to return the refund amount to the target account.

[0007] In one feasible implementation, when the parking package also includes bound target vehicle information and / or target parking lot information, obtaining the fulfillment data of the parking package further includes: Obtain the parking records of the target vehicle within the target parking lot during the specified usage period; The method further includes: If the parking record matches the package redemption record, the package redemption record is determined to be valid; otherwise, the package redemption record that does not match the parking record is deleted.

[0008] In one feasible implementation, the automatic refund operation includes: Send the refund amount for the parking package to the management terminal; Based on the refund amount reported by the management terminal, execute the automatic refund operation.

[0009] In one feasible implementation, when it is detected that the preset usage period of the parking package has exceeded, an automatic refund instruction is generated, including: If the current time has exceeded the expiration time of the parking package's usage period, an automatic refund instruction is generated; or, When a preset time point is reached, the parking package database is scanned to identify parking packages that have exceeded their validity period, and an automatic refund instruction is generated.

[0010] In one feasible implementation, the automatic refund operation to return the refund amount to the target account includes: Execute the automatic refund operation to return the refund amount to the original account; or, According to the instructions from the original account, the refund amount will be returned to the designated account.

[0011] In one feasible implementation, before detecting that the preset usage period of the parking package has expired, the method further includes: In response to receiving an order for a parking package from a user account, an automatic refund verification task is generated for the parking package; the automatic refund verification task is used to monitor whether the current time has exceeded the preset usage period of the parking package.

[0012] In one feasible implementation, the method further includes: Upon completion of the refund operation, a refund information is sent to the user terminal; the refund information includes at least one of the following: the refund information of the parking package, the refund amount, the calculation rules for the refund amount, and the time when the refund is credited to the account.

[0013] Secondly, embodiments of this application also provide an automatic refund device, the device comprising: The instruction generation module is used to generate an automatic refund instruction for each parking package sold when it is detected that the preset usage period of the parking package has been exceeded. The data acquisition module is used to acquire the fulfillment data of the parking package in response to the automatic refund instruction; the fulfillment data includes at least the package cancellation records; The amount determination module is used to determine the refund amount based on the package redemption records; if there are no redemption records within the usage period, the refund amount is the full amount; if there are redemption records within the usage period, the refund amount is calculated based on the refund rule information of the parking package. An automatic refund module is used to perform automatic refund operations to return the refund amount to the target account.

[0014] In one feasible implementation, when the parking package also includes bound target vehicle information and / or target parking lot information, obtaining the fulfillment data of the parking package further includes: Obtain the parking records of the target vehicle within the target parking lot during the specified usage period; The device further includes: The verification module is used to determine that the package redemption record is valid when the parking record is consistent with the package redemption record; otherwise, it deletes the package redemption record that is inconsistent with the parking record.

[0015] In one feasible implementation, the automatic refund module, when performing an automatic refund operation, is configured to: Send the refund amount for the parking package to the management terminal; Based on the refund amount reported by the management terminal, execute the automatic refund operation.

[0016] In one feasible implementation, the instruction generation module is used to generate an automatic refund instruction when it detects that the preset usage period of the parking package has exceeded, including: If the current time has exceeded the expiration time of the parking package's usage period, an automatic refund instruction is generated; or, When a preset time point is reached, the parking package database is scanned to identify parking packages that have exceeded their validity period, and an automatic refund instruction is generated.

[0017] In one feasible implementation, the automatic refund module is used to perform an automatic refund operation to return the refund amount to the target account, for the following purposes: Execute the automatic refund operation to return the refund amount to the original account; or, According to the instructions from the original account, the refund amount will be returned to the designated account.

[0018] In one feasible implementation, the device further includes: The verification module is used to generate an automatic refund verification task for the parking package in response to receiving an order for the parking package from a user account before detecting that the preset usage period of the parking package has been exceeded; the automatic refund verification task is used to monitor whether the preset usage period of the parking package has been exceeded at the current time.

[0019] In one feasible implementation, the device further includes: The notification module is used to send refund information to the user terminal in response to the completion of the refund operation; the refund information includes at least one of the following: the refund information of the parking package, the refund amount, the calculation rules of the refund amount, and the time when the refund arrives.

[0020] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the automatic refund method as described in any one of the first aspects.

[0021] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the automatic refund method as described in any one of the first aspects.

[0022] This application provides an automatic refund method, apparatus, electronic device, and storage medium. By automatically monitoring whether a parking package has exceeded its preset usage period, it proactively generates a refund instruction at the expiration date, changing the passive mode of the prior art that requires manual application from the user. In response to this refund instruction, it further automatically acquires and makes decisions based on the performance data bound to the package (especially package redemption records). When the package redemption record indicates that the package has not been used, a full refund is issued; when the package redemption record indicates that the package has been partially used, a partial refund is issued according to the parking package's refund rules. This operation requires no manual intervention.

[0023] Through the above methods, the embodiments of this application can achieve the effect of "changing the refund process from passive and manually driven to active and automatically executed".

[0024] Compared with the lengthy process in the prior art that relies entirely on user initiation and requires subsequent manual work order processing, parking lot verification, and customer service review, the embodiments of this application can solve the problems of "low processing efficiency, high operating costs, and poor user experience caused by passive processes and high dependence on manual labor", which helps to improve the user experience.

[0025] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0026] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 A flowchart of an automatic refund method provided in an embodiment of this application is shown.

[0028] Figure 2 A flowchart of another automatic refund method provided by an embodiment of this application is shown.

[0029] Figure 3 A schematic diagram of an automatic refund device provided in an embodiment of this application is shown.

[0030] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0032] With the deepening of smart parking services, parking packages, as a convenient prepaid consumption model, have been widely adopted. Users can enjoy discounted parking services during specific time periods by purchasing parking packages. The basic business logic is to promote efficient resource utilization and enhance user loyalty. To achieve a closed-loop service model, providing a refund mechanism for unfulfilled packages has become an industry standard. This not only reflects the platform's commitment to service but is also a crucial step in building user trust.

[0033] In current industry practice, the complexity of determining the fulfillment status of a service package—which involves data collaboration across multiple systems, including order records, parking lot entry and exit data, and package verification vouchers—has led to a fixed model for traditional refund processing that relies on manual review. Specifically, after a package expires, the platform waits for the user to submit an application, then initiates a cross-departmental manual verification process: operations staff retrieve parking records from the parking lot, customer service staff verify the verification vouchers, and finance staff ultimately execute the refund. This design essentially transforms the data collaboration problem between systems into a manual task, which, while controlling risk, introduces significant efficiency bottlenecks.

[0034] This processing model has exposed a series of structural problems in actual operation. From the perspective of user experience, the entire process shifts the burden of data verification to the user—users not only need to remember their refund rights, but also need to manually initiate complex applications. This dual burden of cognition and operation seriously weakens the user experience of the package products.

[0035] In view of the above problems, this application provides an automatic refund method, apparatus, electronic device and storage medium, which are described below through embodiments.

[0036] To facilitate understanding of this embodiment, a detailed description of an automatic refund method disclosed in this application embodiment will be provided first. For example... Figure 1 As shown, it includes the following steps: Step 101: For each parking package sold, when it is detected that the preset usage period of the parking package has been exceeded, an automatic refund instruction is generated.

[0037] This step uses a proactive monitoring mechanism to identify the natural end time of the parking package order lifecycle and generate instructions to drive subsequent processes based on this.

[0038] The "monitoring" behavior here refers to the continuous or periodic comparison of the "usage period" time condition. For example, this can be achieved by periodically scanning all active parking package orders and comparing their recorded "usage period" expiration time with the current time; alternatively, a timed trigger mechanism can be preset for each order at creation, automatically activating when the "usage period" expires. Regardless of the specific implementation method used, or other equivalent technical means, the goal is to accurately capture the "parking package has exceeded the preset usage period" status event without any external manual triggering.

[0039] Once the aforementioned monitoring confirms that the "expiration date" condition is met, this step immediately "generates an automatic refund instruction." This instruction can manifest as an internal message containing a specific order identifier, a new task created in the task queue, or a flag set in the program logic. Generating this automatic refund instruction signifies the formal initiation of an automated processing flow aimed at refunding that specific parking package order.

[0040] This step shifts the triggering condition for refund processing from an external event that relies on the user's active submission of an application to an internal event that relies on the order's own time attributes meeting certain conditions. This shift ensures that all eligible orders are promptly and comprehensively included in the processing flow, providing a crucial technical foundation for achieving the service effect of "platform-initiated refunds, seamless user experience."

[0041] Step 102: In response to the automatic refund instruction, obtain the fulfillment data of the parking package; the fulfillment data includes at least the package cancellation record.

[0042] Automatic refund instructions typically include information to uniquely identify the parking package order, such as an order number.

[0043] After triggering the automatic refund instruction, the system enters the preparation phase for intelligent judgment. By acquiring performance data, it collects a chain of evidence that objectively and accurately reflects whether the parking package was actually used within its usage period and the extent of that use. Here, "performance data" is a general term referring to all electronic records related to verifying the usage status of the package. This includes at least "package redemption records," which typically refer to the one-time usage mark or deduction record made by the system when the vehicle leaves the premises to offset fees. This clearly proves that the package was activated at a specific point in time.

[0044] There are various ways to obtain fulfillment data. For example, when the fulfillment data only contains the redemption records for the parking package, these records may already be stored in association with the order information and can be read directly; alternatively, a query can be initiated to the corresponding redemption record database based on the order identifier (such as the order number). The scope of the data obtained should be precisely associated with the order itself to ensure the relevance and efficiency of data retrieval and avoid interference from irrelevant data.

[0045] This step transforms the abstract question of "whether to refund" into a logical judgment based on specific, verifiable electronic data. It establishes an automated link from the "order due date" event to the "evidence collection" action, providing the necessary input for subsequent data-driven automated decision-making, replacing manual verification, and improving verification efficiency.

[0046] Step 103: Determine the refund amount based on the package redemption record; if there is no redemption record within the usage period, the refund amount is the full amount; if there is a redemption record within the usage period, calculate the refund amount based on the refund rule information of the parking package.

[0047] First, the system will check the package redemption records to determine whether the user has used this parking package, and then take different refund measures depending on the situation, including the following two measures: Measure 1: Full Refund for Unused Packages: If no redemption record is found within the entire validity period of the parking package, it is considered "unused." This proves that the user paid the fee but did not receive any service. In this case, the refund amount will be automatically set equal to the full order fee initially paid by the user, ensuring that the user's rights are not compromised.

[0048] Measure 2: If the package has already been used, the refund amount will be calculated according to the pre-defined refund rules of the parking package: If there is at least one redemption record within the validity period, the package is considered "used." In this case, the user is not entitled to a full refund. Instead, the pre-defined refund rules for the package will be retrieved (e.g., "deduct X yuan for each use, then refund proportionally based on the remaining days" or "deduct a fixed handling fee of Y yuan"). Based on these rules and the specific data of the package's redemption records (such as the number of uses and the time of use), a calculation will be performed to arrive at the final refund amount.

[0049] Step 104: Perform an automatic refund operation to return the refund amount to the target account.

[0050] After the refund amount is determined in step 103, the refund operation is initiated and executed. This refund operation will return the refund amount to the target account through the financial link connected to the original payment channel.

[0051] In one feasible implementation, the automatic refund operation to return the refund amount to the target account includes: Execute an automatic refund operation to return the refund amount to the original account; or, according to the instructions from the original account, return the refund amount to the designated account.

[0052] In other words, the target account is usually the original account, that is, the user's original payment account, thus achieving a "return to the original payment method." This is a safe, convenient, and user-friendly refund method. Alternatively, according to preset user instructions or business rules, the refund amount can be returned to another account designated by the user, i.e., the aforementioned designated account.

[0053] This application provides an automatic refund method, apparatus, electronic device, and storage medium. By automatically monitoring whether a parking package has exceeded its preset usage period, it proactively generates a refund instruction at the expiration date, changing the passive mode of the prior art that requires manual application from the user. In response to this refund instruction, it further automatically acquires and makes decisions based on the performance data bound to the package (especially package redemption records). When the package redemption record indicates that the package has not been used, a full refund is issued; when the package redemption record indicates that the package has been partially used, a partial refund is issued according to the parking package's refund rules. This operation requires no manual intervention.

[0054] Through the above methods, the embodiments of this application can achieve the effect of "changing the refund process from passive and manually driven to active and automatically executed".

[0055] Compared with the lengthy process in the prior art that relies entirely on user initiation and requires subsequent manual work order processing, parking lot verification, and customer service review, the embodiments of this application can solve the problems of "low processing efficiency, high operating costs, and poor user experience caused by passive processes and high dependence on manual labor", which helps to improve the user experience.

[0056] The following provides a feasible implementation plan to further clarify how to more comprehensively and reliably obtain and determine the "performance data" upon which the package performance status depends. This embodiment enhances the robustness and accuracy of the automated determination process by introducing diversified "parking records" as supplementary evidence and cross-validating them with the core "package cancellation records".

[0057] That is, when the parking package also includes the bound target vehicle information and / or target parking lot information, obtaining the fulfillment data of the parking package also includes: Obtain the parking records of the target vehicle within the target parking lot during the specified usage period.

[0058] The composition of "performance data" has been expanded. In addition to "package redemption records" that directly represent package consumption, "parking records" generated by the target vehicle within applicable parking lots during the package's validity period have been further included. Here, "parking records" is a general term that can encompass various data sources, such as: electronic logs automatically generated by parking lot gate systems or geomagnetic sensors; vehicle passage evidence generated through video recognition processing; information entered by parking lot management personnel; or vehicle passage data shared from third-party parking platforms. These data, after standardization, collectively constitute a set of parking records used for cross-validation.

[0059] The purpose of introducing parking records is to build a more complete data verification system: First, when the verification record is temporarily missing, it can serve as a supplementary basis to ensure the robustness of the judgment process; second, it can achieve mutual verification with the verification record, enhancing the accuracy of status judgment; third, it can adapt to parking management environments with different levels of automation, thereby improving the applicability and practicality of this method.

[0060] Based on this, this embodiment also includes a key data verification step: If the parking record matches the package redemption record, the package redemption record is determined to be valid; otherwise, the package redemption record that does not match the parking record is deleted.

[0061] In other words, each "package redemption record" is automatically compared with all "parking records" for the same vehicle in the same parking lot within the usage period. The purpose of the comparison is to confirm whether the redemption occurred within a real and complete parking event time period. For example, a valid redemption should occur when the time of occurrence matches the entry to exit time of a parking record.

[0062] When a comparison reveals a parking record that perfectly matches the time and location of a reimbursement record, the reimbursement record is deemed "valid." This means it has passed automated verification and can serve as a reliable basis for calculating the used credit limit. This step essentially links and verifies discrete behavioral data (reimbursement) with continuous process data (parking).

[0063] Conversely, if a reimbursement record cannot be linked to any valid parking record, it is considered "inconsistent" and an anomaly. To maintain the data integrity of the entire automated decision-making process and prevent misjudgments due to data errors (such as accidental operations or phantom reimbursements caused by system malfunctions), this embodiment employs automated correction measures, namely, deleting such unverifiable anomaly reimbursement records. This design ensures that the data involved in subsequent decisions is clean and reliable, fundamentally improving the accuracy and security of automated refund judgments, and is a key technological implementation that replaces the "authentication" step in manual review.

[0064] In one feasible implementation, the method further includes: If the target vehicle has a single-payment parking record within the usage period, and the target parking record meets the usage conditions of the parking package, then it is determined whether the automatic cancellation conditions are met. If so, an automatic cancellation operation is performed, and the single-payment fee is refunded to the target account.

[0065] This embodiment expands the application scenarios and intelligence level of the automatic refund method, providing an automated remedial mechanism for users' "enjoyed but not yet enjoyed" rights. The method aims to identify and handle a specific situation: within the package's usage period, a user has incurred a single parking expense that meets the package's usage conditions, but did not use the parking package for fee reduction, instead paying the single-use fee separately.

[0066] When a "target parking record" that meets the above description is detected, the operation is not executed directly. Instead, it first "determines whether the automatic cancellation conditions are met." This "determination" process provides diverse design space for the implementation method, and its specific logic can be flexibly set according to business strategies, user preferences, or data analysis results.

[0067] The decision-making logic can be based on a variety of possible rules or conditions. For example, in one implementation, the platform can provide users with preset preference options, allowing users to pre-authorize whether to perform automatic redemption and refund in such cases. In another implementation, the decision-making conditions can be based on preset, simple business rules, such as automatic execution as long as there is available credit in the package and the parking record fully meets the usage conditions. Furthermore, in a more intelligent implementation, the decision can rely on an analysis model of the user's historical behavior patterns. For example, by analyzing the frequency and habits of the user's past use of the package, it can infer whether the current "unredeemed" behavior was due to negligence or intentional selection, and decide whether to initiate automatic redemption accordingly, thereby improving the user experience.

[0068] When the current situation is determined to meet the "automatic cancellation conditions," subsequent automated processing is triggered. This processing includes two consecutive technical actions: First, "execute the automatic cancellation operation," which means associating this parking record with a package cancellation record in the background to complete the correction of the performance data; then, "refund the single payment fee to the target account" to compensate the user's rights in the form of a cash refund.

[0069] Through the above methods, the embodiments of this application can not only handle the static scenario of "unused upon expiration", but also proactively intervene and optimize the dynamic scenario of "misuse within the expiration period". Through configurable and flexible judgment logic and automated execution process, it achieves more refined and proactive protection of user rights, reflecting the technical idea of ​​service evolution from "responding to requests" to "anticipating needs".

[0070] It is important to note that the establishment and execution of the aforementioned automatic refund and automatic cancellation conditions are typically based on the user's informed consent to ensure service compliance and protect user rights. In actual business deployment, the relevant terms of service can be clearly and explicitly presented to users at key stages of the parking package ordering process.

[0071] Specifically, during the process of a user purchasing a parking package through an application or web interface, the system will present the user with a complete service agreement, including rules for "automatic cancellation and optimized refunds." This agreement clearly states that within the package's usage period, if the system detects a parking record where the user's vehicle meets the package's usage conditions but the package was not used, and a single parking fee has already been paid, the system may automatically cancel the package and refund the fee according to established rules. Users need to actively read (e.g., by checking the "I have read and agree" option) and explicitly accept these terms before successfully completing the package purchase. Alternatively, the system may obtain the user's authorization through other means.

[0072] In a feasible implementation plan, such as Figure 2 As shown, the automatic refund process includes: Step 201: Send the refund amount of the parking package to the management terminal.

[0073] In the automated refund process, after the system completes the analysis and calculation of the package fulfillment data and determines the final refund amount, it does not immediately execute the payment. Instead, it needs to first transmit the data to a designated management terminal. The management terminal typically refers to the back-end system or management interface used by the parking lot operator, property management company, or platform customer service.

[0074] The purpose of this step is to make refund decisions transparent and controllable. The information sent to the management terminal typically includes not only the refund amount itself, but also key context such as the package order identifier and the basis for the refund determination (e.g., "unused" or "used and deducted XX yuan"). This allows administrators to confirm, review, or, if necessary, manually intervene in the automatic determination before the refund is actually executed, thereby improving efficiency while retaining ultimate oversight of the business.

[0075] Step 202: Execute an automatic refund operation based on the refund amount reported by the management terminal.

[0076] This step is triggered upon receiving confirmation or modification instructions from the management terminal regarding the reported refund amount. Its core function is to transform the final refund decision, after manual review, into a real fund refund transaction. This step strictly follows the confirmed amount from the management terminal, refunding the corresponding funds to the target account through the payment channel, thus completing the final closed loop from decision-making to fund return.

[0077] This design achieves a secure combination of automated processes and human oversight. It not only retains the efficiency of automatic system calculations but also provides a flexible entry point for handling complex or disputed situations by introducing a confirmation step at the management terminal, ultimately ensuring the accuracy and compliance of refund procedures.

[0078] In one feasible implementation, when it is detected that the preset usage period of the parking package has been exceeded, an automatic refund instruction is generated, including the following two methods: Method 1: If the current time has exceeded the expiration time of the parking package, an automatic refund instruction will be generated.

[0079] One approach is a real-time triggering method, which relies on real-time monitoring of the status of individual parking packages. It continuously compares the current time with the preset expiration date of each parking package. When the system detects that the current time has exceeded the expiration date of a particular package, it determines that the package has expired and immediately generates an automatic refund instruction for that specific package. This method offers immediate response and is suitable for scenarios with high requirements for timely refunds.

[0080] Alternatively, in method two, when a preset time node is reached, the parking package database is scanned, parking packages that have exceeded their usage period are identified from the database, and an automatic refund instruction is generated.

[0081] This method is a batch-triggered approach, employing a scheduled task mechanism. At a preset, specific time point (which can be periodic or non-periodic), a batch processing task is initiated. This task scans the entire parking package database, identifying all packages with expiration dates earlier than the current scan time through a single query. Subsequently, the system generates individual automatic refund instructions for each of these expired packages. This method is highly efficient, has controllable system load, and is suitable for scenarios requiring centralized processing of a large number of orders.

[0082] Both methods can be used independently or in combination, together forming a reliable automated chain from the "package expired" event to the "initiate refund" instruction.

[0083] In one feasible implementation, before detecting that the preset usage period of the parking package has expired, the method further includes: In response to receiving an order for a parking package from a user account, an automatic refund verification task is generated for the parking package; the automatic refund verification task is used to monitor whether the current time has exceeded the preset usage period of the parking package.

[0084] This step is the initialization and pre-deployment mechanism for the automated refund process. Its core lies in planning and setting up potential refund verification work in advance, at the time of order creation, thereby laying the timeline foundation for the entire automated process.

[0085] In other words, when a user account successfully subscribes to a parking package and the system generates a valid order, a creation operation called "Automatic Refund Verification Task" is triggered synchronously. This task is not executed immediately, but is generated and registered with the scheduling system as a future-oriented, planned task to be triggered. This task is essentially a listener or timed trigger carrying the core parameters of the order (especially its "preset usage period" expiration time).

[0086] This automated refund verification task continuously or periodically (e.g., through system scheduled tasks) compares the current system time with the expiration date recorded in the order. Thus, at a precise future point in time, when the condition "expiration date has passed" is detected, the refund instruction generation process described above is automatically triggered.

[0087] By introducing this step, fully automated planning is achieved from the very beginning of the order lifecycle. It transforms the monitoring of refund timing from a passive, post-expiration batch scan into a proactive, order-specific, and precise countdown monitoring system. This not only improves the timeliness and reliability of process triggering but also ensures that no order is missed.

[0088] In one feasible implementation, the method further includes: Upon completion of the refund operation, a refund information is sent to the user terminal; the refund information includes at least one of the following: the refund information of the parking package, the refund amount, the calculation rules for the refund amount, and the time when the refund is credited to the account.

[0089] After the core refund process is completed in an automated workflow, the results are proactively communicated to users, thus building a trustworthy and perceptible service experience.

[0090] This step is automatically triggered by the "refund operation completed" event. Once the refund instruction is successfully processed (e.g., the payment gateway returns a success callback), the system immediately or later initiates a notification process to "send refund information to the user's terminal." This "refund information" is a structured data packet designed to answer any questions the user may have.

[0091] The refund information contains content in multiple dimensions. Among them, the "refund information" itself can be a general status statement, such as "Your package refund has been initiated". The "refund amount" is the core financial data, directly informing the user of the actual amount to be returned. The "calculation rule of the refund amount" is used to explain how this amount is obtained, for example, stating whether it is a "full refund" or "refunded according to the proportion of the remaining 7 times based on 3 times already used", which enhances the transparency and fairness of the process. The "time of refund arrival" provides a clear expectation, informing the user when the funds will be returned to their payment account and alleviating the anxiety of waiting. These information items can be sent individually or in combination.

[0092] The technical implementation of this step usually involves calling internal or external message services and delivering them to users through one or more channels such as text messages, application push notifications, and in-site messages. Its introduction has transformed the entire automated refund process from a purely "background silent process" into a complete, "beginning-to-end" user-perceivable service. It not only fulfills the obligation of notification, avoiding user inquiries or complaints that may be caused by information opacity, but more importantly, it actively transforms a cost-optimization operation (the platform saves labor) into a positive service touchpoint that enhances user satisfaction and brand trust.

[0093] The following combines a specific application scenario to elaborate on the complete execution process of the embodiments of this application in detail. This embodiment aims to clearly demonstrate the automated closed-loop from order generation to refund completion, but should not be construed as any limitation on the protection scope of the present invention.

[0094] Implementation scenario: Suppose the car owner paid 100 yuan through the application on October 1, 2025, and successfully purchased a "daytime weekly pass" parking package. This package stipulates that the usage period is from 00:00 on October 1, 2025 to 24:00 on October 7, 2025; within this usage period, between 10:00 and 16:00 every day, the license plate "粤XXXXX" can enjoy free parking services at the designated "A Parking Lot".

[0095] Then the execution process of the embodiments of this application is as follows: The first step: Order creation and monitoring task initialization: When the user's payment is successful, the system automatically generates a parking package order record. This record at least includes the order ID, license plate number "粤XXXXX", package type "daytime weekly pass", payment amount of 100 yuan, start and end time of the usage period, applicable parking lot "A Parking Lot", and the initial order status (such as "in effect").

[0096] Meanwhile, in response to the creation of this order, the system generates an "automatic refund verification task" bound to it. The core logic of this task is set as follows: continuously monitor the system time to determine whether it has exceeded the end point of the "usage period" preset for this order (i.e., after 24:00 on October 7, 2025). In this embodiment, this task can be carried by a background scheduling service that runs every day at early morning (e.g., 00:05), and batch scans all expired orders on the same day.

[0097] Step 2: Trigger automatic refund instruction and performance status verification upon expiration: At 00:05 on the early morning of October 8, 2025, the scheduling service starts scanning. When it is monitored that the cut-off time of the "usage period" of the above order (24:00 on October 7) has been exceeded by the current time, the system immediately automatically generates an automatic refund instruction for this order.

[0098] In response to this automatic refund instruction, the system automatically starts the verification process. First, based on the license plate number "Yue XX XXX" in the order and the applicable parking lot "A Parking Lot", the system queries all parking records (i.e., vehicle entry and exit logs) generated by this vehicle at "A Parking Lot" from October 1 to October 7, 2025. Secondly, in these parking records, the system further retrieves whether there is a "package verification record" associated with the order ID, that is, to determine whether this package has been actually used to offset parking fees. This process is completed through automatic query and correlation analysis of multi-source data without any manual intervention.

[0099] Step 3: Intelligent determination and decision-making: After the verification process is completed, the system makes an automatic determination based on the obtained "parking records" and "package verification records". In this scenario, the verification result shows that within the usage period of the package, the number of parking records of the bound vehicle "Yue XX XXX" at "A Parking Lot" is 0, and there is no relevant package verification record. Based on this, the system intelligently determines that this parking package has "not been used at all" within the usage period, meeting the preset condition of "automatic full refund".

[0100] Step 4: Execution of automatic refund: Based on the determination result of "not used at all", the system automatically calls the standard refund application programming interface (API) provided by the payment gateway, and passes parameters such as the order number and refund amount (100 yuan) to this interface to initiate a refund request for the original payment path. After the payment gateway processes this request, it will call back the notification of successful transaction to this system.

[0101] Step 5: Result notification and service closed-loop: After the system receives the callback of successful refund returned by the payment gateway, it first updates the status of this order to "expired automatic refund" to indicate the end of the process.

[0102] Immediately afterwards, the system automatically invokes the message notification service to generate a successful refund notice containing key information, which is sent to the user via SMS or application push. An example of the notice content is as follows: "Dear customer, the daily weekly parking package you purchased (order number: XXX) has expired. After system verification, your vehicle (license plate number: Yue XX) did not use this package at Parking Lot A during the usage period (October 1st - 7th). According to the service commitment of the 'Assured Purchase' parking package, 100 yuan has been refunded to your payment account (target account) via the original route, and it is expected to arrive within 24 hours. Thank you for your support."

[0103] Thus, from order expiration monitoring, automatic verification, intelligent determination to refund execution and user notification, a complete and unattended automatic refund service loop is successfully achieved.

[0104] This embodiment demonstrates the entire process of a user obtaining an automatic refund from purchasing the "daily weekly card", without the user having to make any applications or operations. This method effectively solves the problems of cumbersome processes, poor experience, and high operating costs caused by users having to actively apply and undergo manual refund reviews in the traditional mode, truly achieving the technical effect of "the platform takes the initiative to refund, and users enjoy it without feeling it", significantly enhancing user satisfaction and the intelligent level of platform services.

[0105] Based on the same technical concept, an embodiment of this application also provides an automatic refund device, as Figure 3 shown, the device includes: An instruction generation module 301, configured to generate an automatic refund instruction for each sold parking package when it is detected that the preset usage period of the parking package has been exceeded.

[0106] A data acquisition module 302, configured to obtain the performance data of the parking package in response to the automatic refund instruction; the performance data at least includes package verification records.

[0107] An amount determination module 303, configured to determine the refund amount based on the package verification records; if there are no verification records within the usage period, the refund amount is the full amount; if there are verification records within the usage period, the refund amount is calculated based on the refund rule information of the parking package.

[0108] An automatic refund module 304, configured to perform an automatic refund operation to refund the refund amount to the target account.

[0109] In a feasible implementation, when the parking package also includes bound target vehicle information and / or target parking lot information, obtaining the performance data of the parking package further includes: Obtain the parking records of the target vehicle within the target parking lot during the specified usage period.

[0110] The device further includes: The verification module is used to determine that the package redemption record is valid when the parking record is consistent with the package redemption record; otherwise, it deletes the package redemption record that is inconsistent with the parking record.

[0111] In one feasible implementation, the automatic refund module, when performing an automatic refund operation, is configured to: Send the refund amount for the parking package to the management terminal.

[0112] Based on the refund amount reported by the management terminal, execute the automatic refund operation.

[0113] In one feasible implementation, the instruction generation module is used to generate an automatic refund instruction when it detects that the preset usage period of the parking package has exceeded, including: If the current time has exceeded the expiration time of the parking package, an automatic refund instruction is generated; or, when a preset time node is reached, the parking package database is scanned, parking packages that have exceeded their expiration time are identified from the database, and an automatic refund instruction is generated.

[0114] In one feasible implementation, the automatic refund module is used to perform an automatic refund operation to return the refund amount to the target account, for the following purposes: Execute an automatic refund operation to return the refund amount to the original account; or, according to the instructions from the original account, return the refund amount to the designated account.

[0115] In one feasible implementation, the device further includes: The verification module is used to generate an automatic refund verification task for the parking package in response to receiving an order for the parking package from a user account before detecting that the preset usage period of the parking package has been exceeded; the automatic refund verification task is used to monitor whether the preset usage period of the parking package has been exceeded at the current time.

[0116] In one feasible implementation, the device further includes: The notification module is used to send refund information to the user terminal in response to the completion of the refund operation; the refund information includes at least one of the following: the refund information of the parking package, the refund amount, the calculation rules of the refund amount, and the time when the refund arrives.

[0117] Figure 4A schematic diagram of an electronic device provided in this application embodiment includes: a processor 401, a storage medium 402, and a bus 403. The storage medium 402 stores machine-readable instructions executable by the processor 401. When the electronic device runs the automatic refund method as described in the embodiment, the processor 401 communicates with the storage medium 402 via the bus 403, and the processor 401 executes the machine-readable instructions to perform the steps as described in the embodiment.

[0118] In this embodiment, the storage medium 402 may also execute other machine-readable instructions to perform other methods as described in the embodiment. For details on the specific execution steps and principles, please refer to the description of the embodiment, which will not be repeated here.

[0119] This application also provides a computer-readable storage medium storing a computer program that is executed by a processor to perform the steps as described in the embodiments.

[0120] In this embodiment, the computer program, when run by the processor, can also execute other machine-readable instructions to perform other methods as described in the embodiments. For details on the specific execution steps and principles, please refer to the description of the embodiments, which will not be repeated here.

[0121] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interface; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0122] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0123] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0124] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0125] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An automatic refund method, characterized in that, The method includes: For each parking package sold, when it is detected that the preset usage period of the parking package has been exceeded, an automatic refund instruction is generated; In response to the automatic refund instruction, the fulfillment data of the parking package is obtained; the fulfillment data includes at least the package cancellation records; The refund amount is determined based on the package redemption record; if there is no redemption record within the usage period, the refund amount is the full amount; if there is a redemption record within the usage period, the refund amount is calculated based on the refund rules information of the parking package. Perform an automatic refund to return the refund amount to the target account.

2. The method according to claim 1, characterized in that, When the parking package also includes the bound target vehicle information and / or target parking lot information, obtaining the fulfillment data of the parking package further includes: Obtain the parking records of the target vehicle within the target parking lot during the specified usage period; The method further includes: If the parking record matches the package redemption record, the package redemption record is determined to be valid; otherwise, the package redemption record that does not match the parking record is deleted.

3. The method according to claim 1, characterized in that, The automatic refund operation includes: Send the refund amount for the parking package to the management terminal; Based on the refund amount reported by the management terminal, execute the automatic refund operation.

4. The method according to claim 3, characterized in that, When it is detected that the preset usage period of the parking package has been exceeded, an automatic refund instruction is generated, including: If the current time has exceeded the expiration time of the parking package's usage period, an automatic refund instruction is generated; or, When a preset time point is reached, the parking package database is scanned to identify parking packages that have exceeded their validity period, and an automatic refund instruction is generated.

5. The method according to claim 1, characterized in that, The automatic refund operation, which returns the refund amount to the target account, includes: Execute the automatic refund operation to return the refund amount to the original account; or, According to the instructions from the original account, the refund amount will be returned to the designated account.

6. The method according to claim 1, characterized in that, Before detecting that the preset usage period of the parking package has expired, the method further includes: In response to receiving an order for a parking package from a user account, an automatic refund verification task is generated for the parking package; the automatic refund verification task is used to monitor whether the current time has exceeded the preset usage period of the parking package.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Upon completion of the refund operation, a refund information is sent to the user terminal; the refund information includes at least one of the following: the refund information of the parking package, the refund amount, the calculation rules for the refund amount, and the time when the refund is credited to the account.

8. An automatic refund device, characterized in that, The device includes: The instruction generation module is used to generate an automatic refund instruction for each parking package sold when it is detected that the preset usage period of the parking package has been exceeded. The data acquisition module is used to acquire the fulfillment data of the parking package in response to the automatic refund instruction; the fulfillment data includes at least the package cancellation records; The amount determination module is used to determine the refund amount based on the package redemption records; if there are no redemption records within the usage period, the refund amount is the full amount; if there are redemption records within the usage period, the refund amount is calculated based on the refund rule information of the parking package. An automatic refund module is used to perform automatic refund operations to return the refund amount to the target account.

9. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is in operation, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the automatic refund method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the automatic refund method as described in any one of claims 1 to 7.

Images