Account access methods, devices, computer equipment and media for ride-hailing platforms

By uniformly acquiring transaction requests and automatically creating accounts, making credit limit changes and generating operation logs, the problem of inconsistent access processes and expansion difficulties in the account system of ride-hailing platforms has been solved, achieving traceability of account operations and improving system collaboration efficiency.

CN123118089APending Publication Date: 2026-11-17BEIJING BAIJU YIXING TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611104179.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-23
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing ride-hailing platform account system manages each entity's account independently, resulting in inconsistent access processes, low access efficiency, difficulty in expanding when adding new business types, difficulty for upstream systems to obtain account change results in real time, and difficulty in tracing the operation process.

Method used

By uniformly acquiring transaction requests, storing transaction vouchers, and obtaining account configuration rules, the system automatically creates target accounts, changes credit limits, generates operation logs, and pushes them to upstream and downstream systems, thus achieving an atomic closed loop of account creation, credit limit adjustment, and log recording.

Benefits of technology

It achieves traceability of account operations and flexible adaptation driven by configuration, avoids the problem of hard-coded expansion, improves system collaboration efficiency, ensures that upstream and downstream are aware of account change status in real time, and eliminates information silos.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123118089A_ABST
    Figure CN123118089A_ABST
Patent Text Reader

Abstract

This invention relates to the field of ride-hailing technology, and discloses a method, apparatus, computer equipment, and medium for account access in ride-hailing platforms. The method includes: obtaining an account activity request, wherein the account activity request includes a target business, an account activity voucher, and account activity parameters corresponding to the target business; responding to the account activity request, storing the account activity voucher, and obtaining the account configuration rules corresponding to the target business, wherein the account activity voucher is used to record the process information of this account activity; creating a target account corresponding to the target business according to the account configuration rules, and changing the credit limit of the resources in the target account using the account activity parameters to obtain the change result, and generating an operation log for the target account based on the change result; and pushing the operation log to upstream and downstream related business systems. This invention solves the problems of inconsistent processes, cumbersome operations, and difficulty for upstream systems to obtain real-time account change results when different business systems access the account system in existing ride-hailing platforms.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of ride-hailing technology, specifically to account access methods, devices, computer equipment, and media for ride-hailing platforms. Background Technology

[0002] With the rapid development of computer and network technologies, the business scenarios of ride-hailing systems are becoming increasingly complex, leading to a growing demand for data resource management involving multiple stakeholders, including platforms, drivers, and service providers. In the ride-hailing model, the account system needs to manage the account information, transaction records, and data flow of these multiple stakeholders to support data consistency in core business processes such as clearing and settlement, driver withdrawals, and order payments. However, existing account systems typically manage accounts for different stakeholders separately, with each account having its own independent tables and services, creating data silos. Upstream business systems need to call different account interfaces to complete integration, and the system lacks unified management of data flow, making it difficult to coordinate information flow and data flow.

[0003] The shortcomings and drawbacks of existing technologies are as follows: when different business systems access accounts, they need to manually handle operations such as account creation and account limit changes, resulting in inconsistent access processes and low access efficiency; when adding new business types, multiple parts of system code need to be modified, making expansion difficult; at the same time, upstream systems have difficulty obtaining account change results in real time, and the operation process is also difficult to trace. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a method, apparatus, computer equipment and medium for accessing accounts on ride-hailing platforms, in order to solve the problems of inconsistent processes, cumbersome operations and difficulty for upstream systems to obtain account change results in real time when different business systems access the account system in existing ride-hailing platforms.

[0005] In a first aspect, embodiments of the present invention provide a method for account access on a ride-hailing platform, the method comprising: Obtain an account activity request, wherein the account activity request includes a target business, an account activity voucher, and account activity parameters corresponding to the target business; In response to the transaction request, the transaction voucher is stored, and the account configuration rules corresponding to the target business are obtained, wherein the transaction voucher is used to record the process information of this transaction. Create a target account corresponding to the target business according to the account configuration rules, and use the transaction parameters to change the limit of the resources in the target account to obtain the change result. At the same time, generate the operation log of the target account based on the change result. The operation logs are pushed to relevant upstream and downstream business systems.

[0006] Furthermore, obtaining the account configuration rules corresponding to the target service includes: Obtain the service identifier corresponding to the target service; The ride-hailing account type corresponding to the current transaction is determined based on the business identifier of the target business. Obtain the account configuration rules corresponding to the ride-hailing account type.

[0007] Furthermore, creating the target account corresponding to the target business according to the account configuration rules includes: Parse the account configuration rules and extract the key fields required for account creation to adapt to the target business, as well as the corresponding validation logic for the key fields; Obtain the basic parameters that match the key field, and use the verification logic to verify the basic parameters; If the basic parameters pass the verification, the basic parameters are assembled to obtain the account initialization data; or, if the basic parameters fail the verification, the basic parameters are adjusted according to the preset correction rules, and the corrected parameters are integrated and assembled to obtain the account initialization data. Create the target account based on the account initialization data.

[0008] Furthermore, the step of using the transaction parameters to change the limit of resources in the target account to obtain the change result includes: Obtain the credit limit change parameters from the aforementioned transaction parameters; Obtain the available resource quota in the target account, and compare the quota change parameters with the available resource quota to determine whether the quota adjustment complies with the change rules; If the change rules are met, the available resource quota is updated according to the quota change parameters to obtain the latest resource quota data; The available resource quota and change details of the target account before and after this quota update are integrated to generate the resource quota change result of the target account.

[0009] Furthermore, the method also includes: If the change does not meet the change rules, the limit change parameters and the account information of the target account will be packaged into an abnormal change task, and the task level of the abnormal change task will be determined according to the priority of the ride-hailing business. Based on the task level, a matching supplementary quota is retrieved from cross-account resources; The supplementary quota is used to correct the quota change parameters to obtain the corrected quota change parameters, and then associated with the task level and the supplementary quota to generate a retryable pending change task order.

[0010] Furthermore, the method also includes: Based on the task level carried by the pending change task order, match the corresponding retry cycle and execution weight; Poll the pending change task list according to the retry cycle, re-initiate the quota change process, and allocate processing resources according to the execution weight during the quota change process. If the task fails to execute after a preset number of retries, the pending change task is marked as abnormal, and an abnormal alarm message is sent.

[0011] Furthermore, pushing the operation logs to upstream and downstream related business systems includes: Obtain at least one upstream or downstream related business system associated with the target business; Based on the business attributes of the relevant business systems, the corresponding differentiated notification content template is invoked; Extract key information related to resource quota changes from the operation log, fill the key information into the corresponding differentiated notification content template, and obtain the notification information; The notification information is pushed to the relevant business systems.

[0012] Secondly, embodiments of the present invention provide an account access device for a ride-hailing platform, the device comprising: The acquisition module is used to acquire transaction requests, wherein the transaction request includes the target business, the transaction voucher, and the transaction parameters corresponding to the target business; The response module is used to respond to the transaction request, store the transaction voucher, and obtain the account configuration rules corresponding to the target business, wherein the transaction voucher is used to record the process information of this transaction. The processing module is used to create a target account corresponding to the target business according to the account configuration rules, and to change the limit of the resources in the target account using the transaction parameters to obtain the change result. At the same time, it generates the operation log of the target account based on the change result. The push module is used to generate notification information based on the operation log and push the notification information to upstream and downstream related business systems.

[0013] Thirdly, embodiments of the present invention provide a computer device, including: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the method described in the first aspect or any corresponding embodiment thereof.

[0014] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing computer instructions that cause a computer to perform the method described in the first aspect or any of its corresponding embodiments.

[0015] The method provided in this application has the following beneficial effects: The method provided in this application can accurately identify the type of business to be accessed and its operational intent by uniformly acquiring a transaction request containing the target business, transaction voucher, and corresponding transaction parameters, laying the foundation for subsequent automated processing. By immediately storing the transaction voucher and obtaining the account configuration rules corresponding to the target business after responding to the transaction request, the traceability of the operation process and the flexible adaptation of configuration-driven processes are achieved, avoiding the expansion problems caused by hard coding. By automatically creating the target account according to the account configuration rules and changing the credit limit of the resources in the account using the transaction parameters, and generating operation logs based on the change results, an atomic closed loop of account creation, credit limit adjustment, and log recording is achieved, and the entire process can be completed without the intervention of the upstream system. By pushing the operation logs to relevant upstream and downstream business systems, it is ensured that each business node can know the account change status in real time, effectively eliminating information silos and improving system collaboration efficiency. Attached Figure Description

[0016] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating an account access method for a ride-hailing platform according to some embodiments of the present invention; Figure 2 This is a schematic diagram of a ride-hailing account structure according to some embodiments of the present invention; Figure 3 This is a schematic diagram of the architecture of a ride-hailing platform account access system according to some embodiments of the present invention; Figure 4 This is a structural block diagram of an account access device for a ride-hailing platform according to an embodiment of the present invention; Figure 5 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] According to embodiments of the present invention, a method, apparatus, computer device, and medium for accessing accounts on a ride-hailing platform are provided. It should be noted that the steps shown in the flowcharts in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0020] This embodiment provides a method for account access on a ride-hailing platform. Figure 1 This is a flowchart of an account access method for a ride-hailing platform according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps: Step S101: Obtain the transaction request, wherein the transaction request includes the target transaction, the transaction voucher, and the transaction parameters corresponding to the target transaction.

[0021] In this embodiment, the transaction request is an operation instruction initiated by the upstream business system to trigger an account limit change; the target business is used to identify the specific business scenario to which the current transaction belongs (such as order payment, driver settlement, etc.); the transaction voucher is the unique process identifier for this transaction, used to record the flow status, operation time and execution result of the entire transaction process, which is convenient for subsequent tracking and retry; the transaction parameters contain the specific data fields required to execute this limit change, such as account subject information, account type, changed limit value, scenario code, event code, etc.

[0022] First, a unified transaction interface is exposed through a standardized access layer. Upstream business systems assemble request messages according to a predefined transaction protocol and send them to the account core service. Upon receiving the transaction request, the access layer performs a preliminary check on its integrity, including verifying whether the target business field is empty, whether the transaction voucher has been submitted repeatedly (to prevent idempotency issues), and whether the transaction parameters contain the necessary account entity identifier and changed limit value. If the verification passes, the request is parsed into an internally recognizable data structure, and the target business identifier is extracted so that subsequent steps can dynamically match the corresponding account configuration rules based on this identifier. Furthermore, the transaction voucher is only received and temporarily stored in this step, not immediately persisted, but uniformly stored, thus ensuring the atomicity and traceability of the transaction process. Through this standardized request acquisition method, upstream businesses do not need to concern themselves with the underlying account creation logic and limit change details; they only need to transmit the necessary information according to the protocol to complete the transaction initiation.

[0023] Step S102: Respond to the transaction request, store the transaction voucher, and obtain the account configuration rules corresponding to the target business. The transaction voucher is used to record the process information of this transaction.

[0024] In this embodiment, upon receiving a transaction request, the account core service first responds to the request, confirming that the request format is valid, the target business is identifiable, and the transaction parameters are complete. Before formally processing the transaction logic, the system extracts the transaction voucher and performs atomic persistent storage operations. Specifically, the system uses the unique identifier of the transaction voucher (such as voucher ID) as the primary key, writes the voucher and its associated request context (including the target business, the hash value of the transaction parameters, the receiving timestamp, the current status, etc.) into a dedicated transaction voucher table, and sets the initial status to "pending processing". To ensure the idempotency of the transaction, a distributed lock check is performed based on the voucher ID before writing: if the same voucher ID already exists and the status is not "finally failed", a duplicate request prompt is returned directly to prevent the same transaction from being executed multiple times; if it does not exist, the writing is successful. Simultaneously, the storage operation is incorporated into the same local transaction or distributed transaction framework as subsequent configuration rule acquisition, account creation, and other processes, ensuring that once the transaction voucher is successfully stored, subsequent processes are traceable. In addition, a preset validity period (e.g., 24 hours) is set for each transaction record, which is used by a scheduled task to scan for expired and incomplete records and trigger a retry mechanism. This reactive storage method not only achieves traceability of the transaction process, but also provides a reliable data foundation for subsequent asynchronous compensation and anomaly recovery.

[0025] In this embodiment of the application, obtaining the account configuration rules corresponding to the target service includes: Step A1: Obtain the business identifier corresponding to the target business.

[0026] Specifically, the target business field is extracted from the parsed and temporarily stored transaction request data structure. This field is filled in according to a unified coding standard when the upstream system constructs the request, such as using a hierarchical naming rule "business domain_business scenario_sub-scenario". After extracting the target business, its format is first validated, including checking whether it is empty, whether the length is within the preset range, and whether the characters belong to the allowed character set (such as uppercase letters, numbers, and underscores). After the validation passes, the target business is used as input to call the business identifier mapping service. This service internally maintains a mapping table between businesses and identifiers, which supports dynamic hot reloading and can be updated without restarting the service. The mapping service returns the corresponding unique business identifier based on the target business (for example, mapping "driver reward distribution" to "DRIVER_INCENTIVE"). If the target business does not exist in the mapping table, the new business automatic registration process is triggered: the business domain is parsed according to the naming rule of the target business, a default identifier is generated and persisted to the mapping table, and marked as "pending configuration". The complete account configuration rules are then supplemented by the backend management interface. In this way, not only is the business identifier obtained, but the ability to dynamically adapt to new businesses is also achieved, avoiding the scalability issues caused by hard coding.

[0027] Step A2: Determine the ride-hailing account type corresponding to the current transaction based on the business identifier of the target business.

[0028] Specifically, the business identifier is a unique code or string corresponding to the target business, used to quickly retrieve and match the account type, transaction scenario, event and payment configuration rules bound to the business in the account configuration rule base; the ride-hailing account type refers to the account classification corresponding to different entities involved in the operation of the ride-hailing platform, such as driver account, platform account, channel merchant account, SaaS service provider account, etc. Each account type has an independent account model, quota management rules and operation permissions.

[0029] Using a business identifier as input, the system invokes an account type matching engine. This engine internally maintains a dynamic mapping table between business identifiers and ride-hailing account types, which supports real-time updates based on the configuration center. The engine first performs an exact match query in the mapping table based on the business identifier. If a match is successful, the corresponding account type is returned directly. If a match fails, a rule-based learning matching mechanism is triggered: the engine parses the naming structure of the business identifier (e.g., the business identifier "DRIVER_INCENTIVE" contains the prefix "DRIVER"), compares the similarity of this prefix with the keyword database for account types, automatically recommends the most likely account type (e.g., "driver account"), and records the matching result for manual confirmation before it is fixed in the mapping table. Simultaneously, the system also verifies whether the account entity information carried in the current transaction parameters is compatible with the matched account type. For example, if the account type corresponding to the business identifier is "driver account," but the entity type passed in the transaction parameters is "platform," a conflict is flagged and an exception message is returned. Through this multi-level matching and verification mechanism, the mapping from business identifiers to account types can be accurately completed without manual intervention, laying the foundation for subsequent acquisition of account configuration rules.

[0030] Step A3: Obtain the account configuration rules corresponding to the ride-hailing account type.

[0031] Specifically, account configuration rules refer to a set of structured configuration information predefined for a specific ride-hailing account type, used to guide behaviors such as automatic account creation, credit limit changes, and payment channel integration; specifically, it may include account subject configuration (such as the type of subject to which the account belongs), transaction scenario configuration (such as settlement, driver cash withdrawal, and other business scenarios), transaction event configuration (such as order payment, order refund, and other sub-events), and payment configuration (payment account, payment channel information, etc.).

[0032] like Figure 2 As shown, a ride-hailing account consists of four core components: account category, account holder, balance information, and payment information. The account category corresponds to the account classification of different entities in the operation of the ride-hailing platform. The account holder identifies the owner of the account. The balance information records the available resource quota of the account. The payment information includes configuration data such as payment account and payment channel.

[0033] like Figure 3As shown, the ride-hailing platform account access system is divided into three layers: the top layer is the standard access layer, which provides transaction access and data query functions; the middle layer is the core account service layer, which includes an account configuration module, a transaction service module, a callback notification module, and a payment channel proxy module, respectively implementing account configuration parsing, transaction voucher saving, account creation and balance update, business callback notification, and payment / transfer proxy functions; the bottom layer is the data and payment support layer, which manages account information, transaction vouchers, account transaction records, and other data through the account storage module, and connects to different payment channels through the payment middle platform to achieve unified management of payment capabilities.

[0034] Using the ride-hailing account type as the primary key, the system calls the configuration center service to retrieve account configuration rules matching that account type. The configuration center employs a multi-level caching strategy (local cache + remote cache) to improve read performance. First, it checks the cache for a corresponding configuration rule snapshot based on the account type. If a match is found, it returns the snapshot directly. If not, it loads all configuration items associated with that account type from persistent storage (such as a configuration database or configuration management table). During loading, the completeness and validity of the configuration rules are verified, such as checking for missing account principal configurations, matching transaction scenarios with transaction events, and the availability of payment channels. If the verification passes, the rule set is stored in the cache with a reasonable expiration time. If the verification fails (e.g., payment configuration for an account type is missing but the transaction requires a fund transfer), automatic completion is performed based on the default configuration template, and an incomplete configuration log is recorded for maintenance personnel to follow up. Furthermore, account configuration rules support version management and retrieve the currently effective version number to determine if a rule refresh is necessary later. By dynamically obtaining configuration rules in this way, the account processing logic and business rules are completely decoupled. When adding new business or adjusting rules, there is no need to modify the code; only the configuration needs to be updated to take effect.

[0035] Step S103: Create a target account corresponding to the target business according to the account configuration rules, and use the transaction parameters to change the limit of the resources in the target account to obtain the change result. At the same time, generate the operation log of the target account based on the change result.

[0036] In this embodiment of the application, creating a target account corresponding to the target business according to the account configuration rules includes: Step B1: Parse the account configuration rules and extract the key fields required for account creation to adapt to the target business, as well as the corresponding validation logic for the key fields.

[0037] Specifically, key fields refer to the attribute fields necessary for creating the target account, such as account subject identifiers (e.g., driver ID, platform ID), account type code, initial credit limit, account status, creation timestamp, etc.; validation logic refers to the predefined legality verification rules for each key field, used to ensure that the input basic parameters meet the requirements for account creation, such as non-empty validation, format validation (e.g., mobile phone number regular expression, ID format), value range validation (e.g., the initial credit limit cannot be negative), and correlation validation (e.g., the subject identifier must exist in the system), etc.

[0038] The system receives account configuration rules (usually structured data in JSON or YAML format). First, it performs syntax and integrity parsing on the rules, deserializing them into an in-memory configuration object model. Then, it identifies and extracts a sub-configuration section specifically for account creation from the configuration object model. This sub-configuration section explicitly lists all key field names required to create the target account, along with the corresponding validation logic expression for each field. During extraction, key fields are dynamically trimmed or supplemented based on the type of the target business: for example, if the target business is "driver reward distribution," the key fields required for account creation include driver ID, mobile phone number, and initial reward amount; if the target business is "driver settlement," additional fields such as bank card number and binding time need to be extracted. Simultaneously, contextual metadata, such as the field's data type, whether it is required, and default value, is attached to each key field. After extraction, these key fields and their corresponding validation logic are assembled into an ordered field-rule mapping table for subsequent sequential parameter validation. With this parsing and extraction method, the account creation logic is entirely configuration-driven. When adding any account type or adjusting field requirements, only the configuration rules need to be modified, without changing the core code, which greatly improves the system's scalability and maintainability.

[0039] Step B2: Obtain the basic parameters that match the key fields, and use the validation logic to validate the basic parameters.

[0040] Specifically, basic parameters refer to the specific data values ​​corresponding to key fields extracted from the transaction parameters carried in the transaction request, such as the specific value "D12345" corresponding to the driver ID field. Validation logic consists of predefined validity rules (such as NOT NULL, regular expressions, and value range) for each key field. Using a field-rule mapping table as input, each key field is traversed, and basic parameter values ​​matching the field name are extracted from the transaction parameters. Fuzzy matching and alias mapping of field names are supported during extraction (e.g., the key field "driverId" may correspond to "driver_id" or "driverID" in the transaction parameters). For each key field, the corresponding validation logic is obtained, and the basic parameter values ​​are validated one by one. During the validation process, multiple checks are performed sequentially: first, NOT NULL validation is performed; if a field is marked as required but the basic parameter is empty, a missing error is recorded; second, format validation is performed, such as regular expression matching; finally, business logic validation is performed, such as checking whether the driver ID actually exists in the user center. If all fields pass validation, the validation is successful. If any field fails validation, the process does not terminate immediately. Instead, all failure information is collected, and an attempt is made to repair the field according to preset correction rules (such as automatically filling in default values ​​and automatically converting formats). After repair, validation is performed again. If the validation still fails, a clear validation error report is returned. This centralized validation and automatic correction mechanism ensures the accuracy and completeness of the basic parameters upon which subsequent account creation depends.

[0041] Step B3: If the basic parameters pass the verification, the basic parameters are assembled to obtain the account initialization data; or, if the basic parameters fail the verification, the basic parameters are adjusted according to the preset correction rules, and the corrected parameters are integrated and assembled to obtain the account initialization data.

[0042] Specifically, account initialization data refers to the complete data structure required to create the target account, including the account's basic attributes (such as account ID, account type, entity identifier, initial limit, status, creation time, etc.) and metadata information. This data will be directly used to perform the account creation operation. Preset correction rules refer to the automatic repair strategies that are pre-set for the basic parameters that fail to be validated. For example, they can supplement the default values ​​for missing required fields, standardize and transform data with incorrect format (such as removing spaces from mobile phone numbers), and set boundary values ​​for values ​​that are out of range.

[0043] If all validations pass, the assembly process begins directly: the set of validated basic parameters is merged with fixed fields in the account configuration rules (such as account type, default status "normal", creation timestamp, etc.), and data is transformed according to the field mapping relationship of the target account table structure to finally generate a complete account initialization data object. If some fields fail validation, the process does not terminate directly, but instead, an automatic correction module is activated: for each field that fails validation, a correction operation is performed according to the preset correction rule corresponding to that field (which can be defined in the configuration rules). For example, for missing required fields, if a default value is configured, it is automatically filled; for incorrectly formatted strings, a standardized cleaning function (such as trim, removing spaces) is attempted; for values ​​outside the range, they are set as boundary values. After correction, the corrected basic parameters are merged with the parameters that did not fail, and a simplified validation is performed again (only checking whether the basic requirements are met after correction). If it passes, the corrected complete parameter set is assembled to generate account initialization data, and the correction operation log is recorded. If the requirements are still not met after correction, an exception is thrown and the process terminates. This fault-tolerant design of "verification-correction-assembly" significantly improves the success rate of account creation and reduces account operation failures caused by minor anomalies in upstream parameters.

[0044] Step B4: Create the target account based on the account initialization data.

[0045] Specifically, the target account refers to the final account instance to be created or operated on in this transaction. In a ride-hailing platform, this could be a driver account, platform account, channel partner account, etc. Each target account has a unique account identifier and complete account attributes. First, a globally unique account ID is generated based on the account type and subject identifier in the account initialization data (using either the Snowflake algorithm or a database sequence). Then, a database transaction is initiated, and an insert operation is performed in the account master table, writing fields such as account ID, account type, subject identifier, initial credit limit, status, and creation time. Before insertion, a final deduplication check is performed: a query is conducted based on the combination of subject identifier and account type to see if the account already exists. If it already exists, the existing account information is returned directly (idempotent processing), and the account is not created again. After successful insertion, associated metadata (such as phone number, registration source, etc.) is also written to the account extended table. At the same time, an account creation log is recorded, including snapshots of the status before and after creation. The entire creation operation and subsequent credit limit change operations are included in the same distributed transaction to ensure atomicity: if the account is created successfully but the subsequent credit limit change fails, the created account is deleted or marked as invalid according to the transaction rollback strategy. Finally, the successfully created target account object (containing information such as account ID, account type, and initial credit limit) is returned for use in subsequent credit limit change steps. This transactional account creation method ensures the consistency and reliability of account data and avoids the retention of dirty data.

[0046] In this embodiment of the application, the limit of resources in the target account is changed using the transaction parameters to obtain the change result, including the following two cases: Scenario 1: Obtain the credit limit change parameters from the transaction parameters; obtain the available resource limit in the target account, and compare the credit limit change parameters with the available resource limit to determine whether the current credit limit adjustment complies with the change rules; if it complies with the change rules, update the available resource limit according to the credit limit change parameters to obtain the latest resource limit data; integrate the available resource limit and change details of the target account before and after this credit limit update to generate the target account resource limit change result.

[0047] It should be noted that the quota change parameters refer to the specific data extracted from the transaction parameters that describes the adjustment of the resource quota, including the direction of change (increase or decrease), the change value, and the reason for the change; the available resource quota refers to the current actual available resource balance of the target account, such as the remaining reward quota in the driver's account; the change rules refer to the preset legality conditions for the quota change, such as "the available quota after deduction cannot be negative" or "the quota increase in a single transaction cannot exceed the upper limit"; the change result refers to the record generated after the quota change operation is completed, which includes information such as the quota before the change, the quota after the change, the change value, and the change status (success / failure).

[0048] Specifically, the process begins by extracting the credit limit change parameters from the transaction parameters, including the change value (e.g., +50 or -20) and the change type. Next, the target account is queried to obtain its current available resource credit limit. Then, the credit limit change parameters are compared with the available resource credit limit, and the validity of the credit limit adjustment is determined according to preset change rules. For example, if the change rule requires that "the credit limit after deduction must not be less than 0," and the current available credit limit is 30, requesting a deduction of 50 is considered non-compliant; conversely, a deduction of 20 is compliant. If the change rule is met, a credit limit update operation is executed in the database transaction: the available resource credit limit is atomically added or subtracted based on the change parameters, and the credit limit field of the target account is updated. After a successful update, a complete detail of the change is recorded, including a snapshot of the credit limit before the change, a snapshot of the credit limit after the change, the change value, the change timestamp, the transaction voucher ID, etc., and this information is encapsulated as the target account resource credit limit change result. This change result will serve as the core data source for subsequent operation log generation. This atomic processing method of verifying before updating ensures the legality of the quota change operation and the consistency of the data, avoiding abnormal situations such as over-deduction.

[0049] As an example, suppose the target account is a driver's account with a current available resource quota of 100. The quota change parameter in the transaction request is "+50" (increase by 50). The change value +50 is extracted, and the current available quota is 100. The change rule allows any increase (no upper limit), so it is determined to meet the rule. The update is executed: new quota = 100 + 50 = 150, updating the account quota field to 150. The change result is then generated: quota before change 100, quota after change 150, change value +50, status successful. If another request has a quota change parameter of "-80" (deduct 80), the current quota is 100. The rule requires that the quota after deduction ≥ 0, 100 - 80 = 20 ≥ 0, which meets the rule. The updated quota is 20, and the change result record shows successful deduction. If a request is made to deduct 120, then 100 - 120 = -20 < 0, which is determined to not meet the rule. Case one is not applicable, and it will proceed to case two.

[0050] Scenario 2: Obtain the credit limit change parameters from the transaction parameters; obtain the available resource credit in the target account and compare the credit limit change parameters with the available resource credit to determine whether the current credit limit adjustment complies with the change rules; if it does not comply with the change rules, encapsulate the credit limit change parameters and the target account's account information into an abnormal change task, and determine the task level of the abnormal change task based on the priority of the ride-hailing business; retrieve the matching supplementary credit from cross-account resources based on the task level; use the supplementary credit to correct the credit limit change parameters to obtain the corrected credit limit change parameters, and associate the task level and supplementary credit to generate a retryable pending change task order.

[0051] It should be noted that an abnormal change task refers to a task object encapsulated with the original credit limit change parameters and target account information when the credit limit change does not comply with the change rules. This object is used to trigger subsequent correction and retry processes. Ride-hailing business priority is a pre-classified importance level based on business type (such as driver withdrawal, order settlement, emergency compensation, etc.) used to differentiate the handling of abnormal tasks. Cross-account resources refer to the available credit limit resources in other accounts or public backup pools within the ride-hailing platform (such as platform backup fund accounts, risk buffer accounts, etc.). Supplementary credit is a value retrieved from cross-account resources to make up for the current account's insufficient credit limit. A pending change task order is a task document generated after correction, containing corrected credit limit change parameters, task level, supplementary credit, and other information, and supporting a retry mechanism.

[0052] Specifically, the system first extracts the credit limit change parameters from the transaction parameters and obtains the current available resource limit of the target account. Based on the change rules, it determines that the credit limit adjustment does not comply (e.g., the requested deduction exceeds the current available limit). Instead of directly rejecting the transaction, an exception handling process is initiated: the original credit limit change parameters and the target account's account information (account ID, account type, entity identifier, etc.) are encapsulated into an exception change task. Then, based on the target business type of the transaction, the corresponding task level (e.g., high, medium, and low) is obtained from the preset business priority configuration table. Based on the task level, the cross-account resource scheduling module is invoked: for high-priority transactions (e.g., driver emergency withdrawals), the system retrieves a supplementary credit limit matching the difference from a highly reliable cross-account resource pool (e.g., the platform's reserve fund account); for low-priority transactions, it may retrieve from a general resource pool or use a downgraded processing method. After obtaining the supplementary credit limit, the original credit limit change parameters are modified using this supplementary credit limit. For example, if the original request was to deduct 100 but the available credit limit is only 30, resulting in a difference of 70, the modified change parameters become: deduct 30 (actually available), and 70 is transferred from cross-account resources to the target account before the deduction is executed; or, 100 is directly deducted while simultaneously supplementing 70 from cross-account resources to the target account. After modification, the modified credit limit change parameters, task level, and supplementary credit limit source are associated to generate a pending change task order. This task order is persistently stored and marked as "pending retry." Finally, this task order is periodically retried. This exception handling mechanism automatically allocates resources and retryes tasks when the credit limit is insufficient, significantly improving the success rate of account transactions and avoiding business interruptions caused by temporary credit limit shortages.

[0053] As an example, suppose a driver's account currently has an available resource limit of 30. A withdrawal request is initiated, with a limit change parameter of "-100" (deducting 100). The change rule requires the deducted limit to be ≥0; 30-100=-70<0, which does not meet the rule. The system encapsulates the limit change parameter -100 and account information (account ID "ACC_123", account type "driver account") into an abnormal change task. Based on the "high" priority of the target business "driver withdrawal", a supplementary limit of 70 is retrieved from the platform's reserve fund account across accounts. The corrected solution: first, 70 is transferred from the reserve fund account to the driver's account, making the driver's account limit 100, then the 100 is deducted, ultimately reducing the driver's account limit to 0. A pending change task order is generated, recording the corrected parameters (source of the supplementary limit of 70 from the reserve fund account, corrected operation sequence), the task level is set to "high", and it is added to the retry queue. Subsequently, it will be retried and executed according to the high priority and short retry cycle.

[0054] In this embodiment, the operation log refers to an immutable log entry used to completely record the entire process of this account resource limit change. This log includes core data from the change result, as well as contextual information such as associated account information, target business identifier, and trigger source. It serves as a crucial basis for subsequent auditing, tracing, notification, and problem investigation. After the limit change operation is completed (whether it's a direct successful update in scenario one, or a successful retry or marked as an anomaly in scenario two), the operation log generation process is immediately triggered. First, the following information is collected from the current change execution context: basic information of the target account (account ID, account type, entity identifier), limit snapshot before the change, limit snapshot after the change, changed value, change result status (success / failure / partial success), reason for failure (if any), transaction voucher ID, target business identifier, original limit change parameters in the transaction request, and system timestamps for the start and end of the change. Then, the above information is assembled according to a preset log structure to generate a structured operation log object (e.g., JSON format). During the assembly process, a globally unique log ID is generated for each log entry (e.g., generated using the Snowflake algorithm), and the log version number and log creation time are automatically filled in. Subsequently, the operation log objects are persisted to a dedicated account operation log table, typically indexed by account ID and creation time for fast retrieval. The persistence operation and the account limit update operation are usually placed within the same database transaction to ensure consistency between limit changes and log records. If log writing fails, the entire transaction is rolled back to prevent situations where changes occur without logs. Furthermore, the operation logs are synchronously written to an offline data warehouse or search engine (such as Elasticsearch) for subsequent global auditing, statistical analysis, and issue tracing. The generated and persisted operation logs serve as a data source for distribution to upstream and downstream related business systems. This mechanism of synchronously generating operation logs with change results achieves end-to-end traceability, auditability, and reproducibility for every account limit change.

[0055] In this application embodiment, for case two, the method further includes: Step C1: Match the corresponding retry cycle and execution weight according to the task level carried in the change task order to be processed.

[0056] Specifically, the pending change task order is the task document generated in scenario two, which includes the corrected quota change parameters, task level, supplementary quota, and other information, and supports a retry mechanism; the task level is the importance level of the abnormal change task based on the priority of ride-hailing business (such as high, medium, and low levels); the retry period refers to the time interval between two retries (such as high-priority tasks retrying once every 5 seconds, and low-priority tasks retrying once every 60 seconds); the execution weight refers to the proportion of processing resources allocated to different task levels (such as high-priority tasks occupying 60% of the retry thread pool resources, medium-priority tasks occupying 30%, and low-priority tasks occupying 10%).

[0057] Upon receiving the pending change task list generated in scenario two, the task level field (e.g., "High", "Medium", "Low") is extracted. Then, the retry policy configuration center is invoked, which maintains a mapping table between task level, retry period, and execution weight. Based on the task level, the corresponding retry period (e.g., 5 seconds for high, 30 seconds for medium, and 120 seconds for low) and execution weight (e.g., 0.6 for high, 0.3 for medium, and 0.1 for low) are matched. After matching, these parameters are dynamically bound to the pending change task list, updating the "retry period" and "execution weight" fields in the task list, and changing the task list's status from "Pending Correction" to "Pending Retry." Simultaneously, the version number of the task level mapping is recorded for smooth migration during subsequent policy changes. Furthermore, task lists are submitted to different delay queues based on task level: high-level tasks go to the high-priority queue, and low-level tasks go to the low-priority queue. Queue consumers allocate processing threads according to execution weight. This hierarchical strategy ensures that high-priority services receive more frequent retry opportunities and more computing resources, thereby completing quota changes as quickly as possible.

[0058] Step C2: Poll the pending change task orders according to the retry cycle, re-initiate the quota change process, and allocate processing resources according to the execution weight during the quota change process.

[0059] Specifically, a background scheduler is launched, which continuously monitors pending change orders in queues of different priorities. The scheduler retrieves each order according to its assigned retry cycle, at the designated retry time (e.g., 5 seconds after the order was enqueued). After retrieval, based on the order's execution weight, a corresponding number of processing resources are requested from the global retry thread pool; for example, high-weight tasks can obtain more thread slots or longer CPU time slices. After resource allocation, the quota change process is re-initiated: the current available resource quota of the target account is read again, combined with the corrected quota change parameters in the order, and a verification and update operation similar to that in scenario one is performed. If this execution is successful, the order status is marked as "completed," and a change result is generated; if the execution fails (e.g., cross-account resources are not yet available or the account is locked), the order remains in the queue, awaiting the next retry cycle. Simultaneously, the number of attempts, timestamps, and reasons for failure are recorded for subsequent analysis and rate limiting. This polling and retry mechanism, which allocates resources based on weights, can efficiently handle a large number of abnormal tasks and avoid resource contention between low-priority tasks and high-priority tasks.

[0060] Step C3: If the execution still fails after a preset number of retries, the pending change task is marked as abnormal, and an abnormal alarm message is pushed.

[0061] Specifically, the preset number of attempts is the maximum retry limit configured by the system for each task level (e.g., 10 retries for high priority, 5 retries for medium priority, and 3 retries for low priority); the abnormal alarm information is used to notify maintenance personnel or request manual intervention from upstream systems, and includes key fields such as task order ID, target account information, reason for failure, and number of retries.

[0062] After each failed retry, the "Number of Retryes" counter for the task order is incremented and compared with the preset maximum number of retries corresponding to the task level. When the number of retries reaches or exceeds the preset number (e.g., 10 consecutive retries all fail), the task order is determined to be unable to complete automatically through retries. At this time, the task order is marked as "abnormal" (e.g., status code "FAILED_AFTER_RETRIES") and locked to prevent the scheduler from polling it again. Simultaneously, the alarm module is immediately triggered: based on the target business information and account information carried by the task order, an abnormal alarm message is constructed, which includes the task level, total number of retries, the final reason for failure (e.g., "target account frozen" or "cross-account resource pool exhausted"), and the task order creation time. The alarm message is pushed to relevant operations and maintenance personnel or upstream system managers through preset notification channels (e.g., robots, emails, SMS, or monitoring system interfaces). In addition, abnormal task orders are archived in the failed task table for manual investigation and intervention (e.g., replenishing quotas or repairing account data). This failure limit and proactive alert mechanism avoids the waste of resources caused by infinite retries and ensures that abnormal situations can be detected and resolved in a timely manner.

[0063] Step S104: Push the operation log to the relevant upstream and downstream business systems.

[0064] In this embodiment of the application, pushing operation logs to upstream and downstream related business systems includes: Step D1: Obtain at least one upstream or downstream related business system associated with the target business.

[0065] Specifically, upstream and downstream related business systems refer to business systems that have data dependencies or process connections with the current target business of account changes. Upstream systems are usually the systems that initiate account change requests (such as driver services and order services), while downstream systems are the systems that need to perform subsequent processing based on the account change results (such as clearing and settlement systems, message centers, risk control systems, etc.).

[0066] First, the target business identifier (e.g., "driver reward distribution") is extracted from the operation log. Then, the dependency configuration center is invoked, which pre-maintains a table of subscription relationships between each target business and its upstream and downstream business systems. A query is performed based on the target business identifier to obtain a list of all related business systems associated with that business, including each system's unique identifier (e.g., service name), call address, notification method (HTTP callback, RPC, message queue, etc.), and notification trigger conditions (e.g., notifying only successful results or notifying even failed results). Simultaneously, dynamic filtering is performed: based on the result status of the current quota change (success / failure / abnormal) and contextual information such as the magnitude of the changed value, systems that do not require notification are removed (e.g., small changes do not notify the audit system). After obtaining the final system list, it is temporarily stored in memory and sorted by priority (e.g., high-priority core systems are notified first). This configuration-based dependency retrieval method decouples the notification target from the business logic; adding or adjusting related systems only requires modifying the configuration, without changing the code.

[0067] Step D2: Based on the business attributes of the relevant business systems, call the corresponding differentiated notification content template.

[0068] Specifically, business attributes refer to the characteristic descriptions of each relevant business system, including system type (such as synchronous HTTP interface, asynchronous message queue, RPC service), data format preference (JSON, XML, Protobuf), authentication method (Token, signature), required field set, etc.; differentiated notification content templates are message structure templates predefined according to different business attributes. The templates specify the fixed format of the message, required field placeholders, optional fields, and default values.

[0069] The process iterates through each relevant business system, retrieving its business attributes for each system. It then invokes the template management service, using the business attribute as a composite key (e.g., "system type + data format") to query the corresponding differentiated notification content template. Templates are stored in a semi-structured format (e.g., JSON Schema or Freemarker templates), containing static fields and dynamic placeholders (e.g., ${accountId}, ${changeAmount}, ${timestamp}). For systems supporting multiple notification methods, templates further differentiate between success and failure templates. After loading the retrieved templates into memory, the system dynamically adapts them to its specific requirements: for example, some systems need to convert timestamps to millisecond-level Unix timestamps, while others require nested additional signature header fields. This template-based differentiated design ensures that notification content adapts to the interface specifications of different systems, reducing the complexity of upstream systems parsing notifications.

[0070] Step D3: Extract key information related to resource quota changes from the operation log, fill the key information into the corresponding differentiated notification content template, and obtain the notification information.

[0071] Specifically, firstly, all fields are parsed from the operation log object, and a key-value mapping (Map) is established, with the key being the field name (such as "accountId", "oldBalance", "newBalance", "changeAmount", "timestamp", etc.). Then, for each system to be notified and its corresponding template, a population operation is performed: all placeholders in the template are traversed, and the corresponding value is searched for in the above mapping. If found, it is replaced; otherwise, the default value defined in the template or the value is left blank. During the population process, necessary data type conversions (such as converting the timestamp from string to Long) and business encoding conversions (such as converting the account type enumeration to the integer encoding agreed upon by the target system) are performed. After population, the generated notification message undergoes final verification: it checks whether required fields are not empty and whether the signature placeholder has been correctly calculated (such as calling the signature service to generate and replace the signature). After successful verification, the notification message for each system is encapsulated into an independent message object, ready to be sent. This template population mechanism achieves automated conversion from operation logs to multi-format notification messages, avoiding the need to write repetitive conversion code for each system.

[0072] Step D4: Push notification information to relevant business systems.

[0073] Specifically, based on the communication method in the business attributes of each relevant business system, the corresponding push adapter is invoked. For HTTP-type systems, the adapter constructs a POST request, sets the correct Content-Type (e.g., application / json) and authentication header (e.g., Token or signature), and sends the notification information, while setting the timeout (e.g., 3 seconds) and the number of retries (e.g., 1 time). For RPC-type systems, the adapter obtains the target address through service discovery and initiates a synchronous call. For message queue-type systems, the adapter serializes the notification information and delivers it to the specified Topic. During the push process, the result of each push (success / failure / timeout) is recorded. For failed pushes, they are written to a failure retry table, and a background scheduled task retryes them according to an exponential backoff strategy (up to 3 times). If the retry still fails, an alarm log is recorded but the main process is not affected. Asynchronous push mode is also supported: multiple notification tasks are submitted to a thread pool for parallel execution to avoid blocking the main thread. After the push is completed, the "Notification Status" field in the operation log is updated to mark the list of notified systems. This multi-protocol adaptation and asynchronous push mechanism ensures the reliability and efficiency of notifications while reducing intrusion into downstream systems.

[0074] This embodiment also provides an account access device for a ride-hailing platform, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0075] This embodiment provides an account access device for a ride-hailing platform, such as... Figure 4 As shown, it includes: The acquisition module 41 is used to acquire the transaction request, wherein the transaction request includes the target business, the transaction voucher and the transaction parameters corresponding to the target business; The response module 42 is used to respond to the transaction request, store the transaction voucher, and obtain the account configuration rules corresponding to the target business. The transaction voucher is used to record the process information of this transaction. Processing module 43 is used to create a target account corresponding to the target business according to the account configuration rules, and use the transaction parameters to change the limit of the resources in the target account to obtain the change result. At the same time, it generates the operation log of the target account based on the change result. The push module 44 is used to generate notification information based on the operation log and push the notification information to upstream and downstream related business systems.

[0076] In this embodiment of the application, the response module 42 is specifically used to obtain the business identifier corresponding to the target business; determine the ride-hailing account type corresponding to the current transaction based on the business identifier of the target business; and obtain the account configuration rules corresponding to the ride-hailing account type.

[0077] In this embodiment, the processing module 43 is specifically used to parse the account configuration rules, extract the key fields required for account creation to adapt to the target business and the corresponding verification logic of the key fields; obtain the basic parameters that match the key fields, and use the verification logic to verify the basic parameters; if the basic parameters pass the verification, the basic parameters are assembled to obtain account initialization data; or, if the basic parameters fail the verification, the basic parameters are adjusted according to the preset correction rules, and the corrected parameters are integrated and assembled to obtain account initialization data; and the target account is created based on the account initialization data.

[0078] In this embodiment of the application, the processing module 43 is specifically used to obtain the limit change parameters from the transaction parameters; obtain the available resource limit in the target account, and compare the limit change parameters with the available resource limit to determine whether the current limit adjustment complies with the change rules; if it complies with the change rules, update the available resource limit according to the limit change parameters to obtain the latest resource limit data; integrate the available resource limit and change details of the target account before and after the current limit update to generate the target account resource limit change result.

[0079] In this embodiment of the application, the device further includes: a correction module, used to encapsulate the quota change parameters and the account information of the target account into an abnormal change task if the change rules are not met, and determine the task level of the abnormal change task based on the priority of the ride-hailing business; retrieve a matching supplementary quota from cross-account resources based on the task level; correct the quota change parameters using the supplementary quota to obtain the corrected quota change parameters, and associate the task level and the supplementary quota to generate a retryable pending change task order.

[0080] In this embodiment of the application, the device further includes: a matching module, used to match the corresponding retry cycle and execution weight according to the task level carried by the change task order to be processed; poll the change task order to be processed according to the retry cycle, re-initiate the quota change process, and allocate processing resources according to the execution weight during the quota change process; if the execution still fails after a preset number of consecutive retries, the change task order to be processed is marked as abnormal and an abnormal alarm message is pushed.

[0081] In this embodiment, the push module 44 is specifically used to obtain at least one upstream and downstream related business system associated with the target business; call the corresponding differentiated notification content template according to the business attributes of the related business system; extract key information related to resource quota changes from the operation log, fill the key information into the corresponding differentiated notification content template to obtain notification information; and push the notification information to the related business system.

[0082] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 5As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system).

[0083] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0084] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0085] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device as shown by a landing page for an app. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, which can be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0086] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0087] The computer device also includes a communication interface 30 for communicating with other devices or communication networks.

[0088] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0089] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for account access on a ride-hailing platform, characterized in that, The method includes: Obtain an account activity request, wherein the account activity request includes a target business, an account activity voucher, and account activity parameters corresponding to the target business; In response to the transaction request, the transaction voucher is stored, and the account configuration rules corresponding to the target business are obtained, wherein the transaction voucher is used to record the process information of this transaction. Create a target account corresponding to the target business according to the account configuration rules, and use the transaction parameters to change the limit of the resources in the target account to obtain the change result. At the same time, generate the operation log of the target account based on the change result. The operation logs are pushed to relevant upstream and downstream business systems.

2. The method according to claim 1, characterized in that, The step of obtaining the account configuration rules corresponding to the target service includes: Obtain the service identifier corresponding to the target service; The ride-hailing account type corresponding to the current transaction is determined based on the business identifier of the target business. Obtain the account configuration rules corresponding to the ride-hailing account type.

3. The method according to claim 1, characterized in that, Creating the target account corresponding to the target service according to the account configuration rules includes: Parse the account configuration rules and extract the key fields required for account creation to adapt to the target business, as well as the corresponding validation logic for the key fields; Obtain the basic parameters that match the key field, and use the verification logic to verify the basic parameters; If the basic parameters pass the verification, the basic parameters are assembled to obtain the account initialization data; or, if the basic parameters fail the verification, the basic parameters are adjusted according to the preset correction rules, and the corrected parameters are integrated and assembled to obtain the account initialization data. Create the target account based on the account initialization data.

4. The method according to claim 1, characterized in that, The step of using the transaction parameters to change the limit of resources in the target account and obtaining the change result includes: Obtain the credit limit change parameters from the aforementioned transaction parameters; Obtain the available resource quota in the target account, and compare the quota change parameters with the available resource quota to determine whether the quota adjustment complies with the change rules; If the change rules are met, the available resource quota is updated according to the quota change parameters to obtain the latest resource quota data; The available resource quota and change details of the target account before and after this quota update are integrated to generate the resource quota change result of the target account.

5. The method according to claim 4, characterized in that, The method further includes: If the change does not meet the change rules, the limit change parameters and the account information of the target account will be packaged into an abnormal change task, and the task level of the abnormal change task will be determined according to the priority of the ride-hailing business. Based on the task level, a matching supplementary quota is retrieved from cross-account resources; The supplementary quota is used to correct the quota change parameters to obtain the corrected quota change parameters, and then associated with the task level and the supplementary quota to generate a retryable pending change task order.

6. The method according to claim 5, characterized in that, The method further includes: Based on the task level carried by the pending change task order, match the corresponding retry cycle and execution weight; Poll the pending change task list according to the retry cycle, re-initiate the quota change process, and allocate processing resources according to the execution weight during the quota change process. If the task fails to execute after a preset number of retries, the pending change task is marked as abnormal, and an abnormal alarm message is sent.

7. The method according to claim 1, characterized in that, The process of pushing the operation logs to upstream and downstream related business systems includes: Obtain at least one upstream or downstream related business system associated with the target business; Based on the business attributes of the relevant business systems, the corresponding differentiated notification content template is invoked; Extract key information related to resource quota changes from the operation log, fill the key information into the corresponding differentiated notification content template, and obtain the notification information; The notification information is pushed to the relevant business systems.

8. An account access device for a ride-hailing platform, characterized in that, The device includes: The acquisition module is used to acquire transaction requests, wherein the transaction request includes the target business, the transaction voucher, and the transaction parameters corresponding to the target business; The response module is used to respond to the transaction request, store the transaction voucher, and obtain the account configuration rules corresponding to the target business, wherein the transaction voucher is used to record the process information of this transaction. The processing module is used to create a target account corresponding to the target business according to the account configuration rules, and to change the limit of the resources in the target account using the transaction parameters to obtain the change result. At the same time, it generates the operation log of the target account based on the change result. The push module is used to generate notification information based on the operation log and push the notification information to upstream and downstream related business systems.

9. A computer device, characterized in that, include: A memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, the processor executing the computer instructions to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to perform the method of any one of claims 1 to 7.