Transaction processing method and device, equipment, storage medium and computer program product

Abstract

The invention relates to a transaction processing method and device, equipment, a storage medium and a computer program product. The method comprises the following steps: displaying a dialogue interface with a virtual object on a login terminal of a target object; in response to transaction intention content input by the target object on the dialogue interface, displaying an intention understanding result of the virtual object on the transaction intention content, and displaying transaction authorization information for the transaction intention content; under the condition that the target object confirms the intention understanding result and triggers a confirmation operation for the transaction authorization information, the virtual object executes transaction processing according to the transaction intention content; and displaying a transaction processing result of the virtual object. By adopting the method, the transaction processing efficiency can be improved.

Description

Technical Field

[0001] This application relates to the field of artificial intelligence technology, and in particular to a method, apparatus, device, storage medium, and computer program product for transaction processing. Background Technology

[0002] Mobile search and electronic payments have become an integral part of users' daily lives. When searching for products, users typically need to consider their financial capacity and payment methods. Currently, online shopping activities can be managed and payment capabilities are available through the payment functions of e-commerce platforms and financial management applications. However, these functions are only available after the user has entered the purchase process. In other words, transaction processing still depends on the user's search and payment actions, making the transaction processing process redundant and requiring multiple user actions, thus reducing efficiency. Therefore, improving transaction processing efficiency remains a pressing issue that needs to be addressed. Summary of the Invention

[0003] Therefore, it is necessary to provide a transaction processing method, apparatus, device, storage medium, and computer program product that can improve the efficiency of transaction processing in order to address the above-mentioned technical problems.

[0004] Firstly, this application provides a method for transaction processing. The method includes:

[0005] On the target object's login terminal, a dialog interface for interacting with the virtual object is displayed;

[0006] In response to the target object entering transaction intent content in the dialog interface, the virtual object's understanding of the transaction intent content is displayed, and the transaction authorization information for the transaction intent content is displayed;

[0007] If the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information, the virtual object will execute the transaction processing according to the content of the transaction intent.

[0008] Displays the transaction processing results of the virtual object.

[0009] Secondly, this application also provides a transaction processing apparatus. The apparatus includes:

[0010] The dialog interface display module is used to display the dialog interface with the virtual object on the login terminal of the target object;

[0011] The information display module is used to respond to the target object's input of transaction intent content in the dialog interface, display the virtual object's understanding of the transaction intent content, and display the transaction authorization information for the transaction intent content;

[0012] The transaction processing module is used to allow the virtual object to perform transaction processing according to the transaction intent content when the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information.

[0013] The transaction processing result display module is used to display the transaction processing results of virtual objects.

[0014] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0015] On the target object's login terminal, a dialog interface for interacting with the virtual object is displayed;

[0016] In response to the target object entering transaction intent content in the dialog interface, the virtual object's understanding of the transaction intent content is displayed, and the transaction authorization information for the transaction intent content is displayed;

[0017] If the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information, the virtual object will execute the transaction processing according to the content of the transaction intent.

[0018] Displays the transaction processing results of the virtual object.

[0019] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0020] On the target object's login terminal, a dialog interface for interacting with the virtual object is displayed;

[0021] In response to the target object entering transaction intent content in the dialog interface, the virtual object's understanding of the transaction intent content is displayed, and the transaction authorization information for the transaction intent content is displayed;

[0022] If the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information, the virtual object will execute the transaction processing according to the content of the transaction intent.

[0023] Displays the transaction processing results of the virtual object.

[0024] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0025] On the target object's login terminal, a dialog interface for interacting with the virtual object is displayed;

[0026] In response to the target object entering transaction intent content in the dialog interface, the virtual object's understanding of the transaction intent content is displayed, and the transaction authorization information for the transaction intent content is displayed;

[0027] If the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information, the virtual object will execute the transaction processing according to the content of the transaction intent.

[0028] Displays the transaction processing results of the virtual object.

[0029] The aforementioned transaction processing method, apparatus, computer equipment, storage medium, and computer program product, on the target object's login terminal, displays a dialogue interface with a virtual object. In response to the target object inputting transaction intent content in the dialogue interface, the virtual object displays its understanding of the transaction intent content and transaction authorization information for that content. If the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information, the virtual object executes the transaction processing according to the transaction intent content, and finally displays the virtual object's transaction processing result. Through this transaction processing method, the target object's confirmation of the understanding of the intent ensures that the executed transaction processing conforms to the target object's required transaction intent content. In this case, the target object does not need to perform a search operation, and the transaction processing is automatically executed upon triggering the confirmation operation for the transaction authorization information. That is, the transaction processing process does not require the target object to perform search or payment operations, avoiding multiple redundant triggering operations before displaying the transaction processing result, thereby improving transaction processing efficiency. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 This is an application environment diagram of a transaction processing method in one embodiment;

[0032] Figure 2 This is a system architecture diagram of a transaction processing system in one embodiment;

[0033] Figure 3 This is a schematic diagram illustrating the data structure design and hash chain association mechanism between multiple verifiable digital credential data structures in one embodiment;

[0034] Figure 4 This is a flowchart illustrating a transaction processing method in one embodiment;

[0035] Figure 5 This is a schematic diagram of a dialogue interface with a virtual object in one embodiment.

[0036] Figure 6 This is a schematic diagram of a dialogue interface with a virtual object in another embodiment;

[0037] Figure 7 This is a schematic diagram of an interface in one embodiment that displays the transaction intent entered by the target object in the dialog interface.

[0038] Figure 8 This is a schematic diagram of an interface that displays the content of the transaction intent, the result of the intent understanding, and the transaction authorization information in a dialog interface, as shown in one embodiment.

[0039] Figure 9 This is a schematic diagram of an interface showing intent modification information based on the intent understanding result in one embodiment;

[0040] Figure 10 This is a schematic diagram of an interface where the intent understanding result is modified in one embodiment;

[0041] Figure 11 This is a timing flowchart for obtaining the intent understanding result and displaying entity parameters in one embodiment;

[0042] Figure 12 This is a schematic diagram of an interface displaying intent confirmation results and search progress in one embodiment;

[0043] Figure 13 This is a schematic diagram of the interface displaying the search progress in one embodiment;

[0044] Figure 14 A sequence flowchart for generating intent verification credentials in one embodiment;

[0045] Figure 15 This is a schematic diagram of an interface displaying the target transaction object and order information for the target transaction object in one embodiment;

[0046] Figure 16 This embodiment shows the target transaction object and a timing flowchart for the target transaction object;

[0047] Figure 17 This is a schematic diagram of an interface displaying verification progress and merchant confirmation information in one embodiment.

[0048] Figure 18 This is a schematic diagram of the interface displaying the verification results in one embodiment;

[0049] Figure 19This is a schematic diagram of an interface displaying the transaction processing results of a virtual object in one embodiment;

[0050] Figure 20 This is a schematic diagram of an interface displaying the transaction processing results of a virtual object in another embodiment;

[0051] Figure 21 This is a schematic diagram of an interface showing transaction processing details for a transaction processing result in one embodiment;

[0052] Figure 22 This is a flowchart illustrating a transaction processing method in another embodiment;

[0053] Figure 23 This is a schematic diagram of the timing flow for authorization in one embodiment;

[0054] Figure 24 This is a schematic diagram of the timing process for object search in one embodiment;

[0055] Figure 25 This is a schematic diagram of the timing flow of transaction authorization in one embodiment;

[0056] Figure 26 This is a schematic diagram of the timing process for generating payment verification credentials in one embodiment;

[0057] Figure 27 This is a schematic diagram of the timing process for payment authorization in one embodiment;

[0058] Figure 28 This is a schematic diagram of the complete timing process for payment authorization in one embodiment;

[0059] Figure 29 Here is a flowchart of a secure signature mechanism in one embodiment;

[0060] Figure 30 This is a schematic diagram of the complete process of a transaction processing method in one embodiment;

[0061] Figure 31 This is a structural block diagram of a transaction processing device in one embodiment;

[0062] Figure 32 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0063] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0064] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0065] Mobile search and electronic payment have become integral parts of users' daily lives. When searching for products, users typically need to consider their financial capacity and payment methods. Currently, online shopping activities can be managed and payment capabilities facilitated through e-commerce platform payment functions and financial management applications. For example, e-commerce platforms offer installment payment options, allowing users to choose to pay in installments when purchasing goods. Alternatively, bank credit card installment payment services require users to actively apply and usually meet certain credit limit requirements, meaning the installment payment process is completely separated from the search process. Some financial management applications offer budget settings, spending records, and financial analysis functions, but the financial management process is also separate from the search and payment processes. Therefore, the aforementioned functions are only available after the user has entered the purchase process. In other words, transaction processing still depends on the user's search and payment actions, making the transaction processing process redundant and requiring multiple user actions, thus reducing efficiency. Therefore, improving transaction processing efficiency remains a pressing issue that needs to be addressed.

[0066] This application provides a transaction processing method to improve transaction processing efficiency. The transaction processing method provided in this application can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104, or it can be located in the cloud or on another server.

[0067] Specifically, taking terminal 102 as an example, which is the login terminal of the target object requiring transaction processing, a dialogue interface with the virtual object is displayed on terminal 102 (i.e., the target object's login terminal). In response to the target object inputting transaction intent in the dialogue interface, the virtual object displays its understanding of the transaction intent and the transaction authorization information. Based on this, after the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information, the virtual object executes the transaction processing according to the transaction intent. Finally, terminal 102 displays the transaction processing result of the virtual object. Since the transaction processing does not require the target object to perform search or payment operations, multiple redundant triggering operations are avoided before displaying the transaction processing result, thereby improving the efficiency of transaction processing.

[0068] The terminal 102 can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. The server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The transaction processing method provided in this embodiment can be applied to various scenarios, including but not limited to shopping via mobile search and transaction processing via electronic payment, in scenarios requiring transaction processing for specific transaction points.

[0069] The following will introduce the relevant technical concepts involved in the transaction processing method in the embodiments of this application:

[0070] Artificial Intelligence Agent (AI Agent): An AI agent is an intelligent software entity capable of autonomously sensing user needs, understanding natural language instructions, planning execution steps, and completing specific tasks. In automated payment scenarios, an AI agent can represent the user in the entire process of product searching, price comparison, order placement, and payment.

[0071] Verifiable Digital Credentials (VDCs): A VDC is a tamper-proof, cryptographically signed digital object used to transmit trusted information between agents. VDCs are standardized data structures with uncontroversial, portable, and verifiable characteristics, thus serving as building blocks for transactions.

[0072] IntentMandate: IntentMandate is a verifiable digital credential used to capture a user's purchase intent and scope of authorization. This verifiable digital credential includes, but is not limited to, information such as the user's natural language purchase description, budget constraints, product category, and refundability requirements. This verifiable digital credential is generated after the user confirms the transaction, recording the user's authorization time and device information.

[0073] CartMandate: CartMandate is used to capture verifiable digital credentials that signify a user's final confirmation of specific cart contents. These verifiable digital credentials include, but are not limited to, detailed information such as the exact Stock Keeping Unit (SKU), product price, quantity, shipping address, and merchant signature. These credentials are generated after the user confirms the transaction and the merchant signs, ensuring a consistent understanding of the transaction between the ordering user and the merchant.

[0074] Payment Mandate: A payment mandate is a verifiable digital credential transmitted to the payment network and card issuer. This verifiable digital credential identifies the automated payment scenario involving the AI ​​agent. The aforementioned verifiable digital credential includes, but is not limited to, the hash value of the shopping cart authorization, payment method tokens, risk signals, and device information, for the payment network to conduct risk assessment.

[0075] User Confirmation Record: The user confirmation record is used to record complete information about the user's confirmation action, including but not limited to confirmation time, device information, Internet Protocol (IP) address, and user identity (ID). This record serves as evidence of user authorization and is stored together with the aforementioned verifiable digital credentials for subsequent dispute resolution and liability determination.

[0076] Session Identifier: The session identifier is used to associate multiple verifiable digital credentials in the same shopping process. In other words, the session ID links the intent authorization, shopping cart authorization, and payment authorization to form a complete transaction trail, which is easy to trace and detect.

[0077] Timestamp chain verification: Timestamp chain verification is a technical mechanism that embeds the hash value and timestamp of the preceding authorization into each layer of authorization to form an immutable chain of evidence. In other words, subsequent authorizations depend on the integrity of the preceding authorizations; tampering with any link will invalidate the entire chain of evidence.

[0078] As described above, an AI agent is an intelligent software entity capable of autonomously perceiving user needs, understanding natural language commands, planning execution steps, and completing specific tasks. Therefore, AI agents can be applied to automated payment scenarios. Users can express their purchase intentions to the AI ​​agent through natural language, and the AI ​​agent will automatically complete the payment processing flow, including product search, price comparison, merchant selection, order placement, and payment. However, when using an AI agent for payment processing, practical issues regarding authorization verification, authenticity confirmation, and accountability need to be considered. For authorization verification, it's necessary to consider whether the AI ​​agent has obtained authorization from the user for the purchase operation. Regarding authenticity confirmation, it's necessary to consider the possibility that large language models might misunderstand user needs, fabricate non-existent product information, or have discrepancies in price demands. How can merchants and payment systems determine whether the AI ​​agent's transaction and payment requests accurately reflect the user's true purchase intentions? Finally, regarding accountability, it's crucial to consider who should bear the responsibility for erroneous or abnormal transactions.

[0079] Therefore, the transaction processing method proposed in this application constructs a multi-layered authorization mechanism to generate verifiable digital credentials at three stages: user intent expression, merchant transaction confirmation, and payment execution. Hardware-level signatures and timestamp chain verification ensure the authenticity and non-repudiation of the authorization. Specifically, the multi-layered authorization mechanism separates user intent, shopping cart confirmation, and payment execution into three independent verifiable digital credentials. Each verifiable digital credential carries authorization information of different granularities, collectively forming a complete chain of authorization evidence. Intent authorization captures the user's ambiguous needs and authorization boundaries; shopping cart authorization determines specific goods and prices; and payment authorization transmits risk signals to the payment network, making user intent, shopping cart confirmation, and payment execution interconnected but functionally distinct.

[0080] Furthermore, this embodiment of the application also employs a user confirmation recording mechanism to fully record the context information of the confirmation operation when the user performs a confirmation operation. This context information includes, but is not limited to, confirmation time, device information, network information, and session information, forming an immutable operation log. The recorded context information is stored together with the corresponding verifiable digital credential as evidence of user authorization, ensuring the traceability of the operation.

[0081] By separating user intent, shopping cart confirmation, and payment execution into three independent verifiable digital credentials, a timestamp-based chained verification process is used. Each authorization level includes the hash value and timestamp of the preceding authorization, forming a one-way dependent chain of evidence. That is, shopping cart confirmation references the hash value of the verifiable digital credential of user intent, and payment execution references the hash value of the verifiable digital credential of shopping cart confirmation. Therefore, tampering with the verifiable digital credential at any stage will cause subsequent verification to fail, preventing issues such as post-event modification and selective disclosure.

[0082] The transaction processing system in the embodiments of this application is described in detail below, specifically as follows: Figure 2 The system architecture diagram of the transaction processing system shown is a five-layer architecture design. From user interaction to payment execution, a clear technical layer is formed. That is, the transaction processing system includes at least: user interaction layer 202, AI agent processing layer 204, VDC voucher management layer 206, payment execution layer 208, and external system 210.

[0083] The user interaction layer 202 is responsible for authorizing intent in scenarios where the target object is not present. The target object enters transaction intent content in the dialog interface displayed by the application to express the intention to purchase, and can leave after the target object triggers the operation based on the transaction authorization information. At this time, the transaction processing system records complete context information such as confirmation timestamp, device information, network environment, and session context to provide authorization evidence for dispute resolution. The AI ​​agent processing layer 204 is used to parse the transaction intent content entered by the target object based on a large language model, extract purchase intent parameters, and perform operations such as product search, price analysis, and personalized recommendations. It also identifies the target transaction object and generates a corresponding shopping cart for the target transaction object, and continuously checks the consistency between the target transaction object and the transaction intent content entered by the target object to ensure that the recommendation results are within the authorized scope.

[0084] Based on this, the VDC credential management layer 206 can sequentially generate three layers of verifiable digital credentials: intent verification credentials, transaction verification credentials, and payment verification credentials. These credentials all embed confirmation records and merchant signatures, forming an immutable chain of evidence through a hash chain mechanism. The intent verification credentials, transaction verification credentials, and payment verification credentials are stored locally and on the server, supporting historical queries, dispute resolution, and liability determination. Therefore, the payment execution layer 208 integrates the payment services and payment network capabilities provided by the application. It intelligently selects a payment method to generate a payment token, thereby verifying the signature of the payment verification credentials. Upon successful verification, the payment request for the target transaction object is forwarded to the payment network matched by the payment method. This allows the payment network to identify the AI ​​agent transaction identifier and apply differentiated risk control strategies, completing transaction authorization, clearing and settlement, and notifying the target object.

[0085] Considering the need to deliver the target transaction object to the target party, external system 210 provides transaction object and order fulfillment capabilities. This includes providing transaction object information queries and inventory / price queries through product services, and signing the contents of the generated shopping cart and generating an order through shopping cart services. This enables order services such as processing and delivery, logistics monitoring, and delivery confirmation after payment is completed for the target transaction object. Furthermore, VDC evidence chain analysis is used to determine liability in dispute resolution.

[0086] As described above, the intent verification credential, transaction verification credential, and payment verification credential are three layers of verifiable digital credentials generated sequentially. The following section introduces the data structure design and hash chain association mechanism of these verifiable digital credentials: Figure 3The diagram illustrates the data structure design and hash chain association mechanism among multiple verifiable digital credential data structures. The first layer of verifiable digital credentials is the intent verification credential, which is specifically a digital representation of the target object's transaction intent. Therefore, the credential fields of the intent verification credential include, but are not limited to: intent verification credential identifier (mandate_id), transaction intent content (natural_language), structured parameters (structured_params), authorization scope (authorization_scope), confirmation record (user_confirmation), generation timestamp (issued_at), and first hash value (Hash) (IntentMandate). The format of the intent verification credential identifier is "intent_<date>_<serial number>", and the intent verification credential identifier is a unique identifier for the intent verification credential. The transaction intent content is the content entered by the target object, such as, "I want to buy a dress suitable for summer, with a budget of around 300 yuan, in a fresh style." Structured parameters are obtained through semantic analysis of the transaction intent content, such as the transaction object category, season, style, and price range. Taking the transaction intent content "I want to buy a summer dress, budget around 300 yuan, with a fresh style" as an example, the transaction object category is "dress," the season is "summer," the style is "fresh," and the price range can be [200, 400]. The authorization range indicates the maximum amount of the transaction object and the automatic transaction threshold. The confirmation record represents the relevant confirmation information for the target object triggering the confirmation operation; therefore, the confirmation record includes, but is not limited to, confirmation time, device information, network information, and session information. The generation timestamp represents the generation time T1 of the first-layer verifiable digital credential (i.e., the intent verification credential). The first hash value is the SHA-256 hash value H1 generated based on the intent verification credential, specifically the unique fingerprint of the intent verification credential.

[0087] The second layer of verifiable digital credentials is the transaction verification credential, which is specifically used to lock the shopping cart contents generated by the target transaction object selected by the AI ​​agent. Therefore, the credential fields of the transaction verification credential include, but are not limited to: transaction verification credential identifier (mandate_id), hash chain link (linked_intent_mandate_hash), transaction object details (cart_contents), consistency automatic assessment (consistency_check), AI decision record (ai_decision_record), merchant private key RSA signature (merchant_signature), generation timestamp (system_generated_at), and second hash value (IntentMandate). The transaction verification credential identifier is a unique identifier for the transaction verification credential. The hash chain link is used to reference the SHA-256 hash value H1 (i.e., the first hash value) generated based on the intent verification credential to establish the first hash chain link. The transaction object details describe the object details of the target transaction object selected by the AI ​​agent, and the transaction object details include, but are not limited to, SKU, transaction object price, transaction object quantity, and transaction object delivery address. The system includes an automatic consistency assessment to evaluate transaction objects and obtain object evaluation scores, along with corresponding evaluation explanations. An AI decision record describes the process of identifying target transaction objects that match the transaction intent; therefore, the AI ​​decision record includes, but is not limited to, candidate transaction objects, object analysis criteria, comprehensive scores of candidate transaction objects, and the reasons for selecting target transaction objects. A merchant's private key RSA signature is used to commit to fulfilling orders for the target transaction object. A generation timestamp represents the generation time T2 of the second-layer verifiable digital credential (i.e., the transaction verification credential), and generation time T2 > generation time T1, meaning the generation time T2 of the transaction verification credential is later than the generation time T1 of the intent verification credential. The second hash value is the SHA-256 hash value H2, which includes the first hash value.

[0088] The third layer of verifiable digital credentials is the payment verification credential, which is specifically used to transmit payment authorization and AI scenario signals to the payment network. Therefore, the credential fields of the payment verification credential include, but are not limited to: payment verification credential identifier (mandate_id), hash chain link (linked_cart_mandate_hash), hash value reference (linked_intent_hash), payment method (payment_method), AI scenario signals (ai_agent_signals), risk signals (risk_signals), payment service signature (payment_service_signature), and generation timestamp (mandate_created_at). The payment verification credential identifier is a unique identifier for the payment verification credential. The hash chain link is used to reference the SHA-256 hash value H2 (i.e., the second hash value) generated based on the transaction verification credential to establish a second hash chain link. The hash value reference is specifically used to reference the first hash value to form a complete chain of evidence. The payment method represents the payment type and generates a single-use token. AI scenario signals include, but are not limited to, agent participation identifier, transaction pattern, and consistency score. Risk signals include, but are not limited to, device fingerprint, behavioral characteristics, and risk score. The payment service signature is the service signature obtained after successful payment. The generation timestamp represents the generation time T3 of the third-level verifiable digital credential (i.e., the payment verification credential), and the generation time T3 > the generation time T2, meaning that the generation time T3 of the payment verification credential will be later than the generation time T2 of the transaction verification credential.

[0089] Therefore, the transaction verification credential references the first hash value H1 generated by the intent verification credential. During verification, the first verification hash value H1' is recalculated, and it is determined whether the first verification hash value H1' is consistent with the first hash value H1. If they are consistent, the intent authorization verification passes. Conversely, if the first verification hash value H1' is not equal to the first hash value H1, the intent authorization verification passes, indicating that the intent authorization has been tampered with, and no further operation will be performed. The resulting payment verification credential can form a double verification by referencing the first hash value H1 generated by the intent verification credential and the second hash value H2 generated by the transaction verification credential. Furthermore, the forced incrementing of timestamps for generation times T1, T2, and T3 also prevents time reversal attacks. This ensures that any modification to any field in the intent verification credential, transaction verification credential, or payment verification credential will cause the hierarchical verification to fail, thus guaranteeing the integrity and immutability of the evidence chain.

[0090] The following examples illustrate how transaction processing is performed: In one exemplary embodiment, as shown... Figure 4As shown, a transaction processing method is provided, which is applied to... Figure 1 Taking terminal 102 as an example, it can be understood that this method can also be applied to a system including terminal 102 and server 104, and implemented through the interaction between terminal 102 and server 104. In this embodiment, the method includes steps 402 to 408. Wherein:

[0091] Step 402: On the target object's login terminal, a dialog interface with the virtual object is displayed.

[0092] Here, the target object refers to the transaction user who needs to have their transaction processed. The target object can be the user's login account in the shopping application, or it can be a login account in an application that provides shopping transaction services; there is no limitation here. The login terminal is the terminal on which the target object logs in to their account. Figure 1 Terminal 102 in the middle. Secondly, the virtual object is an AI agent, that is, the virtual object can represent the target object to perform payment process operations such as searching for transaction objects, comparing prices, placing orders and making payments according to the transaction intention.

[0093] Specifically, when the target object requires automated transaction processing, a dialog interface with the virtual object can be displayed on the target object's login terminal. This dialog interface can display an information input area for the target object to input content. Furthermore, the dialog interface can display multiple functional controls for payment processing, such as shopping, price comparison search, gift recommendation, and order record functions. Therefore, the dialog interface can also display separate functional controls for ordinary transactions, price comparison search, gift recommendation, and order record functions. For ease of understanding, as follows... Figure 5 The dialog interface shown is for interacting with a virtual object. The dialog interface displays an information input area 502 for the target object to input content, and multiple functional controls 504 for payment processing.

[0094] In practical applications, considering that virtual objects can provide automated payment processes, the dialogue interface can also display interactive information from the virtual object. This interactive information can be text messages instructing the target object to input their transaction intent. For example, the virtual object's interactive information could be: "Hello! I'm an automated shopping assistant. I can help you search for products, compare prices, place orders, and make payments. What do you want to buy? Just tell me!" In addition to the virtual object's interactive information, the dialogue interface can also display the target object's optional intent content. For example, the target object's optional intent content could be: "Buy me a pair of running shoes, budget around 500 yuan," "I want to buy a summer dress, a fresh style, around 300 yuan," and "Recommend me a high-performance Bluetooth headset." For ease of understanding, as... Figure 6 The diagram shows a dialogue interface with a virtual object. The interface displays interaction information 602 of the virtual object, as well as multiple optional intent contents 604 for the target object. It is understood that the foregoing examples are for illustrative purposes only, and the information and content displayed in the dialogue interface are not specifically limited here.

[0095] Step 404: In response to the target object inputting transaction intent content in the dialog interface, display the virtual object's understanding of the transaction intent content, and display the transaction authorization information for the transaction intent content.

[0096] The transaction intent content refers to the content input by the target object. Therefore, the transaction intent content can be text information representing the target object's transaction intent. Considering that the target object can directly represent its transaction intent through images or videos, the transaction intent content can also include voice information, image information, or video information representing the target object's transaction intent. Secondly, the intent understanding result is obtained through semantic analysis of the transaction intent content. Therefore, the intent understanding result can include entity parameters matching the intent entity. The intent entity matches the transaction intent content, and the entity parameters are specific descriptions of the intent entity. For example, if the target object inputs "I want to buy a dress suitable for summer, with a budget of around 300 yuan, in a fresh style," then the transaction intent content is: "I want to buy a dress suitable for summer, with a budget of around 300 yuan, in a fresh style." Based on this, the intent entities in the intent understanding result are the transaction object category, season, style, and price range, and the transaction object category is "dress," the season is "summer," the style is "fresh," and the price range can be [200, 400]. The transaction authorization information indicates that a confirmation operation is triggered on the transaction intent content. Therefore, the transaction authorization information can be text information, such as "authorize automatic purchase."

[0097] Specifically, based on the dialog interface displayed with the virtual object, the target object can input transaction intent content based on its real transaction intention. As described above, since the displayed dialog interface can show an information input area for the target object to input content, after the target object inputs transaction intent content in the information input area, the dialog interface will display the content of the target object's input transaction intent. For ease of understanding, as follows... Figure 7 As shown, the transaction intent content 702 entered by the target object in the dialog interface is displayed.

[0098] Furthermore, the AI ​​agent (i.e., the virtual object) responds to the target object's input of transaction intent content in the dialogue interface and sends a request to the large language model to understand the transaction intent content. The large language model then performs semantic analysis on the transaction intent content in response to the understanding request, thereby determining the intent understanding result, and feeds back the intent understanding result to the AI ​​agent. The AI ​​agent then feeds back the intent understanding result to the target object's login terminal. At this point, the target object's login terminal can display the intent understanding result and the transaction authorization information related to the transaction intent content. For ease of understanding, as follows... Figure 8 As shown, the dialog interface displays the transaction intent content 802 entered by the target object in the dialog interface, and can also display the intent understanding result 804 based on the transaction intent content, and the transaction authorization information 806 based on the intent understanding result. It can be understood that the display area of ​​the transaction authorization information based on the intent understanding result may be within the display area of ​​the intent understanding result, or it may not be within the display area of ​​the intent understanding result; this is not limited here.

[0099] Understandably, considering that in practical applications, the intent understanding results obtained from semantic analysis of transaction intent content may not match the actual transaction needs of the target object, the target object can modify the intent understanding results, that is, modify the entity parameters matched by each intent entity in the intent understanding results, to ensure the reliability of the intent understanding results. Therefore, in an exemplary optional embodiment, the transaction processing method further includes: displaying intent modification information for the intent understanding results when displaying the intent understanding results of the virtual object on the transaction intent content; displaying the entity parameters to be modified in the intent understanding results in response to a trigger operation on the intent modification information; and, in response to a modification confirmation operation, causing the virtual object to modify the entity parameters in the intent understanding results and displaying the modified intent understanding results.

[0100] Specifically, in response to the target object inputting transaction intent in the dialog interface, as described above, and displaying the virtual object's understanding of the transaction intent, it can also display intent modification information based on the intent understanding result. For ease of understanding, as follows... Figure 9 As shown, in addition to displaying the transaction intent content entered by the target object in the dialog interface, the intent understanding result based on the transaction intent content, and the transaction authorization information based on the intent understanding result, the intent modification information 902 based on the intent understanding result can also be displayed.

[0101] Based on this, if the target object believes that there is an intent understanding deviation in the entity parameters matched by each intent entity displayed in the intent understanding result, it can trigger an intent modification operation. This causes the login terminal to respond to the trigger operation on the intent modification information, displaying the entity parameters that need to be modified in the intent understanding result. The target object then modifies the entity parameters that need to be modified and triggers a modification confirmation operation after the modification is completed. This causes the virtual object to modify the entity parameters in the intent understanding result and display the modified intent understanding result. For ease of understanding, as follows... Figure 10 As shown, Figure 10 The intent modification information 1002 shown in section (A) triggers an operation based on the intent understanding result, which can display the following: Figure 10 The entity parameters that need to be modified in the intent understanding results shown in Part (B) can be adjusted as follows if the target object is specifically adjusted for the budget range, and after the modification confirmation operation is triggered after the modification is completed. Figure 10 The modified intent understanding result displayed in section (C) will still show the transaction authorization information for displaying the modified intent understanding result, compared to... Figure 10 The budget range for the intent understanding results shown in Part (A) is 200 to 400. Figure 10 The budget range in the revised intent understanding results shown in section (C) has been changed to 200 to 300.

[0102] As described above, the virtual object's understanding of the transaction intent content includes entity parameters matching the intent entities. The following describes how to obtain these entity parameters. In an exemplary embodiment, in response to the target object inputting transaction intent content in the dialog interface, the virtual object's understanding of the transaction intent content is displayed. This includes: in response to the target object inputting transaction intent content in the dialog interface, performing semantic analysis on the transaction intent content, identifying multiple intent entities in the transaction intent content, and the entity parameters matching each intent entity; and displaying the entity parameters matching each intent entity.

[0103] Intent entities are used to represent entity types across multiple intent dimensions. For example, taking the transaction intent content as "I want to buy a summer dress, with a budget of around 300 yuan, in a fresh and clean style," the multiple intent entities in the transaction intent content include: transaction object category, season, style, and price range. Entity parameters are specific descriptions of the intent entities. Based on the example where the multiple intent entities in the transaction intent content include: transaction object category, season, style, and price range, the specific entity parameters are: "dress" for the transaction object category, "summer" for the season, "fresh and clean" for the style, and [200, 400] for the price range.

[0104] Specifically, as described in the foregoing embodiments, based on the dialogue interface displayed with the virtual object, after the target object inputs transaction intent content in the information input area, the dialogue interface will display the target object's input transaction intent content. Based on this, the AI ​​agent (i.e., the virtual object) will respond to the target object's input of transaction intent content in the dialogue interface and send an understanding request for the transaction intent content to the large language model. The large language model, in response to the understanding request, specifically performs semantic analysis on the transaction intent content, identifying multiple intent entities within the transaction intent content, as well as the entity parameters matching each intent entity. In other words, the large language model analyzes and identifies multiple intent entities within the transaction intent content, and then generates structured parameters from the transaction intent content according to the intent entities to obtain the entity parameters matching each intent entity.

[0105] To facilitate understanding, let's take the transaction intent as an example again: "I want to buy a dress suitable for summer, with a budget of around 300 yuan, in a fresh and clean style." The large language model analyzes the transaction intent and identifies multiple intent entities as "transaction object category, season, style, and price range." It extracts "dress" from the transaction intent based on the transaction object category, "summer" from the transaction intent based on the season, "fresh and clean" from the transaction intent based on the style, and generates a price range [200, 400] based on "around 300 yuan" in the transaction intent. This yields the structured parameters: {category:"dress", season:"summer", style:"fresh and clean", price range: [200, 400]}. From these structured parameters, we can obtain the entity parameter "dress" for the transaction object category, "summer" for the season, "fresh and clean" for the style, and [200, 400] for the price range.

[0106] Furthermore, in response to a request to understand transaction intent content, the large language model performs semantic analysis on the transaction intent content, identifies multiple intent entities within it, and the entity parameters matching each intent entity. Then, it feeds back these multiple intent entities and their matching entity parameters to the AI ​​agent. The AI ​​agent then sends the matching entity parameters to the target object's login terminal, thereby displaying the matching entity parameters for each intent entity on the login terminal. For better understanding, please refer to [link to previous text]. Figure 8 The dialog interface shown is in Figure 8 The dialog interface shown displays the intent understanding results for the transaction intent content, and the intent understanding results specifically include multiple intent entities, as well as the entity parameters matched for each intent entity.

[0107] As mentioned above, semantic analysis of transaction intent is not performed through virtual objects, but rather requires the virtual objects to send understanding requests for the transaction intent to the large language model. In practical applications, after obtaining the entity parameters matching each intent entity, an intent authorization data structure needs to be created based on these parameters. Only after creating this data structure can the login terminal display the entity parameters matching each intent entity. The following describes the process of semantic analysis using the login terminal, virtual objects, and the large language model to obtain intent understanding results and display entity parameters. Figure 11As shown, the target object inputs transaction intent content on the login terminal, causing the virtual object to respond to the transaction intent content and send an understanding request for the transaction intent content to the large language model. The large language model responds to the understanding request by performing semantic analysis on the transaction intent content, identifying multiple intent entities and the entity parameters matching each intent entity. Then, the large language model feeds back structured parameters including the entity parameters matching each intent entity to the virtual object. Based on the received structured parameters, the virtual object requests the generation of an intent verification credential from the verifiable digital credential generator, and the request carries the structured parameters including the entity parameters matching each intent entity. Based on this, the verifiable digital credential generator creates an intent authorization data structure according to the entity parameters matching each intent entity and returns a draft of the intent verification credential to the virtual object. At this point, the virtual object feeds back the intent understanding result and the transaction authorization information based on the intent understanding result to the target object's login terminal, so that the login terminal displays the intent understanding result and the transaction authorization information based on the intent understanding result.

[0108] Step 406: If the target object confirms the understanding of the intent and triggers a confirmation operation for the transaction authorization information, the virtual object executes the transaction processing according to the content of the transaction intent.

[0109] The confirmation operation for transaction authorization information can be any of the following: a click operation, a voice confirmation operation, or a swipe operation. No specific limitations are placed on the method of confirmation. Specifically, when the target object confirms the intent understanding result and triggers a confirmation operation for the transaction authorization information matching the determined intent understanding result, the virtual object executes the transaction processing according to the transaction intent content confirmed by the target object. That is, the virtual object sequentially generates an intent verification certificate, a transaction verification certificate, and a payment verification certificate according to the transaction intent content confirmed by the target object. During the sequential generation of these verification certificates, a target transaction object matching the transaction intent content is also identified. After the intent verification certificate, transaction verification certificate, and payment verification certificate are verified successfully, the transaction processing is specifically executed for the target transaction object.

[0110] Since the virtual object generates intent verification credentials, transaction verification credentials, and payment verification credentials sequentially during the transaction processing according to the transaction intent content, and also determines the target transaction object, the transaction processing progress can be displayed to the target object during the generation of verification credentials and the determination of the target transaction object. In an exemplary optional embodiment, the transaction processing method further includes: displaying the transaction processing progress during the transaction processing executed by the virtual object according to the transaction intent content. The transaction processing progress includes, but is not limited to: intent confirmation result for the transaction intent content, search progress for the transaction intent content, the determined target transaction object, order information for the target transaction object, verification progress, and payment progress. Furthermore, since the execution of transaction processing includes multiple sequential transaction processing steps, the transaction processing progress corresponding to each transaction processing step is also displayed sequentially. The following describes the display prerequisites and specific display interfaces for different transaction processing progress levels:

[0111] In an exemplary optional embodiment, the transaction processing method further includes: after generating the intent verification credential, displaying the intent confirmation result for the transaction intent content and the search progress for the transaction intent content on the target object's login terminal.

[0112] Specifically, when the target object confirms the intent understanding result and triggers a confirmation operation for the transaction authorization information, the context information of the target object triggering the confirmation operation will be recorded. Then, an intent verification credential will be generated based on the context information and the transaction intent content. The aforementioned context information includes, but is not limited to, confirmation time, device information, network information, session information, etc. In the process of generating the intent verification credential, it is necessary to obtain the operation information of the confirmation operation for the transaction authorization information and embed the operation information into the obtained intent authorization data structure to obtain the intent verification credential. After generating the intent verification credential, to ensure that the target object can more directly confirm the transaction processing progress, the intent confirmation result for the transaction intent content can be displayed on the target object's login terminal, meaning that the intent confirmation result is now "intent confirmation complete."

[0113] Furthermore, during the transaction processing, after generating the intent verification credential, it is necessary to determine the target transaction object that matches the transaction intent content based on the intent verification credential. In other words, during the process of determining the target transaction object that matches the transaction intent content, to ensure that the target object can more directly confirm the transaction processing progress, the search progress for the transaction intent content can also be displayed on the target object's login terminal. The search progress for the transaction intent content may include, but is not limited to: the number of candidate transaction objects obtained, the progress percentage for different search dimensions (e.g., the search progress of the search scope, the search progress of the filtering conditions, and the overall score progress), etc.

[0114] For ease of understanding, such as Figure 12 The displayed intent confirmation results and search progress indicate that the intent confirmation has been completed in the intent confirmation result 1202 when the target object confirms the intent understanding result and triggers the confirmation operation for transaction authorization information. Then, in the process of determining the target transaction object that matches the transaction intent content, the search progress 1204 for the transaction intent content will also be displayed. Through the search progress 1204, it can be seen that the search scope "summer dress" and the filter conditions "fresh style & 200-400 yuan" have been completed. At this time, 8 products that meet the conditions have been found and are being comprehensively rated, and the comprehensive rating progress is "65%".

[0115] In practical applications, it can also display the percentage of search progress, search waiting time, and waiting information for steps that have not yet been executed in the process of identifying the target transaction object, etc., for ease of understanding, such as Figure 13 The displayed interface, during the process of determining the target transaction object that matches the transaction intent, can also display waiting information 1302 for intelligent decision matching, waiting information 1304 for automatic shopping cart generation authorization, the percentage of search progress 1306, and the search waiting time 1308. Furthermore, the search progress for the transaction intent in this embodiment may include, but is not limited to: intent authorization completed → autonomous product search (in progress) → intelligent decision (waiting) → automatic shopping cart generation authorization (waiting) → automatic payment completion (waiting). It is understood that the foregoing examples are for understanding this solution and do not specifically limit the search progress for the transaction intent.

[0116] As explained above, the generation of intent verification credentials involves the virtual object requesting the verifiable digital credential generator based on the received structured parameters. This means that generating the intent verification credentials and displaying the intent confirmation result and search progress require interaction between the verifiable digital credential generator, the virtual object, and the login terminal. This will be discussed below. Figure 14As shown, after generating an intent verification certificate according to the transaction intent content, the verifiable digital certificate generator can also store the generated intent verification certificate in the certificate storage system. The target object's login terminal can display the intent understanding result and the transaction authorization information based on the intent understanding result. When the target object triggers a confirmation operation on the transaction authorization information, the virtual object responds to the confirmation operation and requests the intent verification certificate from the certificate storage system. The certificate storage system then returns the intent verification certificate to the virtual object. Through the intent verification certificate, the virtual object can determine that the target object has confirmed the intent authorization, meaning the obtained intent understanding result matches the target object's transaction intent. At this point, the intent confirmation result based on the transaction intent content can be displayed on the target object's login terminal.

[0117] Based on this, the virtual object then requests the object search system to search for transaction objects that match the transaction intent content. During the process of the object search system searching for transaction objects according to the transaction intent content, the search progress can also be displayed on the target object's login terminal to reflect the progress of finding transaction objects that match the transaction intent content. It can be understood that before the object search system returns candidate transaction objects, the displayed search progress for the transaction intent content may indicate that the search for candidate transaction objects is in progress. After the object search system returns candidate transaction objects, the virtual object will then perform object analysis on the candidate transaction objects that match the transaction intent content through multiple transaction dimensions to determine the target transaction object. Therefore, the displayed search progress for the transaction intent content at this point can be seen from the object analysis across multiple transaction dimensions. Thus, the displayed search progress for the transaction intent content is continuous and should not be viewed as a single, incomplete process. Figure 14 The displayed sequence of the search progress for the transaction intent content is shown as a specific display sequence limitation.

[0118] As described above, the process of searching for transaction objects that match the transaction intent can display corresponding results and progress. After the target transaction object is found, the corresponding results and information should also be fed back. This is described below: In an exemplary optional embodiment, the transaction processing method further includes: after determining the target transaction object, displaying the target transaction object and the order information for the target transaction object on the login terminal of the target object.

[0119] Specifically, after receiving multiple candidate transaction objects from the object search system, the virtual object performs object analysis on each candidate object across multiple transaction dimensions to obtain a comprehensive score. It then selects the candidate transaction object with the highest comprehensive score as the target transaction object that matches the transaction intent. Therefore, after the virtual object identifies the target transaction object, it will be displayed on the target object's login terminal. Furthermore, after the virtual object identifies the target transaction object, it will automatically generate a shopping cart based on the target transaction object to obtain order information for that target transaction object; thus, the target object's login terminal can also display this order information.

[0120] For ease of understanding, such as Figure 15 As shown, after the virtual object identifies the target transaction object, it displays the target transaction object 1502 and the order information 1504 for the target transaction object. Considering that displaying the intent confirmation result and search progress requires interaction between the verifiable digital voucher generator, the virtual object, and the login terminal, the process of identifying the target transaction object also requires interaction between the virtual object and the login terminal. For ease of understanding, based on... Figure 14 The timing sequence shown will be further explained, such as... Figure 16 As shown, after the object search system returns candidate transaction objects, the virtual object will analyze the candidate transaction objects that match the transaction intent through multiple transaction dimensions to determine the target transaction object, and automatically generate a shopping cart based on the target transaction object to obtain the order information for the target transaction object. At this time, the login terminal of the target object can display the target transaction object and the order information for the target transaction object.

[0121] In practical applications, after identifying the target transaction object and generating order information for the target transaction object, it is necessary to verify the identified target transaction object to ensure that the identified target transaction object truly meets the target object's intentions and needs. During the verification process, progress feedback can also be provided to the target object by displaying relevant information. This is described in detail below: In an exemplary optional embodiment, the transaction processing method further includes: displaying the verification progress on the target object's login terminal during the verification process; and displaying the payment progress for the target transaction object on the target object's login terminal if the target transaction object passes verification.

[0122] Specifically, during the verification process for the target transaction object, the verification progress can also be displayed on the target object's login terminal. For ease of understanding, as follows... Figure 17 The verification progress of the target transaction object is displayed at 1702 on the target object's login terminal, and in... Figure 17 The system also displays merchant confirmation information for the merchant to which the target transaction object belongs. It is understandable that during the verification process for the target transaction object, other information that can be displayed on the login terminal may also exist; the specific information displayed can be based on the verification process and is not limited here.

[0123] Furthermore, after verification of the target transaction party, payment will be processed for that party. At this point, the payment progress will be displayed on the target party's login terminal. For ease of understanding, as follows... Figure 18 The login terminal for the target transaction displays verification result 1802, indicating that "the shopping cart contents are completely consistent with the user's intent." Payment progress 1804 can also be displayed. Since the verification of the target transaction is successful, a corresponding transaction verification credential is generated, and the generation information 1806 for the transaction verification credential can also be displayed. It is understandable that after successful verification of the target transaction, other information can be displayed on the login terminal; the specific information displayed can be based on the verification result and is not limited here.

[0124] Step 408: Display the transaction processing result of the virtual object.

[0125] The transaction processing result can be either successful or failed. Specifically, if the intent verification credential, transaction verification credential, and payment verification credential are generated sequentially, and each credential is verified in turn, the transaction processing result is successful. Conversely, if any one of the three verification credentials fails, the transaction processing result is failed.

[0126] Secondly, the displayed transaction processing results include, but are not limited to: payment information for the target transaction object, transaction processing summary information of the virtual object executing transaction processing according to the transaction intent, and multi-level authorization credential generation process information. Payment information includes, at a minimum, the payment amount for the target transaction object, the payment method for the target transaction object, the payment order number, the payment time, and the recipient for the target transaction object. The transaction processing summary information includes, at a minimum, the number of candidate transaction objects found, the overall score of the selected target transaction object, and the transaction object name of the selected target transaction object. The multi-level authorization credential generation process information includes, the timestamp and generation method for generating the intent verification credential, the timestamp and generation method for generating the transaction verification credential, and the timestamp and generation method for generating the payment verification credential.

[0127] Specifically, the transaction processing result of the virtual object is displayed on the login terminal of the target object. This application considers the scenario where transaction processing can be performed automatically without the target object operating the login terminal. Therefore, the display of the virtual object's transaction processing result should also consider the scenarios where the target object exits the dialog interface after entering transaction intent, or remains in the dialog interface without performing any operation. In the case where the target object remains in the dialog interface without performing any operation, similar to the aforementioned embodiments, the transaction processing progress can be continuously displayed on the dialog interface as the virtual object executes the transaction processing according to the transaction intent. After obtaining the virtual object's transaction processing result, the target object's login terminal can then display the virtual object's transaction processing result. For ease of understanding, as follows... Figure 19 As shown, the transaction processing result of the virtual object is displayed on the login terminal of the target object, and the transaction processing result specifically includes: payment information 1902 for the target transaction object, transaction processing summary information 1904 of the virtual object executing transaction processing according to the transaction intent content, and multi-level authorization certificate generation process information 1906.

[0128] The following describes how to display the transaction processing result of a virtual object to the target object when exiting the dialog interface: In an exemplary embodiment, displaying the transaction processing result of a virtual object specifically includes: when the virtual object exits the dialog interface while performing transaction processing according to the transaction intent, displaying a transaction processing notification on the login terminal; and displaying the transaction processing result of the virtual object in response to the interactive operation triggered by the transaction processing notification.

[0129] Interactive operations include, but are not limited to, click operations, voice confirmation operations, and swipe operations, etc., which are not limited here. Specifically, during the process of the virtual object executing the transaction according to the transaction intent, if the target object exits the dialog interface by triggering an exit operation for the dialog interface, and if the virtual object receives the transaction processing result, a transaction processing notification will be pushed to the target object's login terminal so that the transaction processing notification is displayed on the login terminal. After the target object confirms the completion of the transaction through the transaction processing notification, it can trigger the corresponding interactive operation on the transaction processing notification, at which point the virtual object's transaction processing result will be displayed. For ease of understanding, as follows: Figure 20 As shown, in Figure 20 The transaction processing notification shown in section (A) will be displayed automatically after triggering an interactive action to display the transaction processing notification. Figure 20 The transaction processing results of the virtual object are shown in Part (B).

[0130] In practical applications, when the transaction processing result is a transaction failure, the target object may need to view the details of the reason for the failure. Conversely, when the transaction processing result is a transaction success, the target object may also believe that the target transaction object does not meet the actual needs, and in this case, it is also necessary to view the details of the transaction processing result. This will be described in detail below: In an exemplary optional embodiment, the transaction processing method further includes: in response to the operation of viewing the details of the transaction processing result, displaying the transaction processing details of the transaction processing result.

[0131] The transaction processing details indicate detailed information in the transaction processing flow that generates the transaction processing result. These details include at least: the target transaction object's order information, the authorization credential chain for the intent verification credential, transaction verification credential, and payment verification credential, which determines whether the verification credential was actively triggered by the target object or automatically generated by the virtual object. Specifically, after displaying the transaction processing result of the virtual object, a details viewing operation can be triggered to display the transaction processing details for the login terminal. For ease of understanding, as follows... Figure 21 As shown, the transaction processing details for the transaction processing result are displayed, and the transaction processing details specifically include the order information 2102 of the target transaction object and the authorization credential chain 2104 for the intent verification credential, transaction verification credential and payment verification credential.

[0132] pass Figure 21It is known that the target object can view the complete content of the authorization certificate for the transaction processing result of the virtual object. Each layer of authorization certificate clearly indicates the generation method and generation time, and the transaction processing details may also include a details storage control and an appeal control. The target object can store the displayed transaction processing details by triggering the details storage control. If the target object has questions about the transaction processing result, it can trigger the appeal control to initiate a dispute appeal against the transaction order matching the generated transaction processing result. Since the transaction processing details include an authorization certificate chain, the authorization certificate chain can be used to determine whether there is a verification error that caused the problem. For example, if the intended verification certificate is inconsistent with the transaction verification certificate, but the authorization certificate chain shows that the verification passed, it means that an error occurred during the verification by the virtual object, and the responsibility for the problem can be determined to be the virtual object. If the merchant fails to fulfill the transaction order matching the target transaction object, the responsibility for the problem may lie with the merchant to which the target transaction object belongs. If the authorization certificate chain is complete and consistent, and the verification result is correct, then the responsibility for the problem may lie with the target object due to an erroneous operation. Since transaction processing details can indicate detailed information in the transaction processing flow that generates the transaction processing result, a clear problem can be identified based on the transaction processing details when transaction processing problems occur. This not only ensures the reliability of transaction processing but also the reliability of the responsibility allocation when problems occur.

[0133] It is understood that the foregoing examples are for the purpose of understanding this solution and should not be construed as specific limitations on this solution.

[0134] In the above transaction processing method, confirming the intent understanding result by the target object can ensure that the executed transaction processing meets the transaction intent content required by the target object. At this time, the target object does not need to perform a search operation, and the transaction processing is automatically executed when the confirmation operation for transaction authorization information is triggered. That is, the transaction processing does not require the target object to perform a search operation or a payment operation. Before the transaction processing result is displayed, the target object is avoided from performing multiple redundant triggering operations, thereby improving the efficiency of transaction processing.

[0135] As described above, the virtual object's execution of transaction processing according to the transaction intent actually includes the generation and verification of multiple layers of verification credentials. The detailed method for executing transaction processing according to the transaction intent is described below: In an exemplary embodiment, such as... Figure 22 As shown, the transaction processing is carried out according to the transaction intent, specifically including:

[0136] Step 2202: Generate intent verification credentials according to the transaction intent content, and determine the target transaction object that matches the transaction intent content based on the intent verification credentials.

[0137] Specifically, the virtual object generates an intent verification credential based on the transaction intent content, and determines the target transaction object that matches the transaction intent content based on the intent verification credential. As described in the foregoing embodiments, the virtual object responds to the target object inputting transaction intent content in the dialog interface and sends an understanding request for the transaction intent content to the large language model. The large language model responds to the understanding request for the transaction intent content by performing semantic analysis on the transaction intent content, identifying multiple intent entities in the transaction intent content, as well as the entity parameters matching each intent entity, and returning the entity parameters matching each intent entity to the virtual object. At this time, the virtual object displays the entity parameters matching each intent entity in the login terminal. Structured parameters can be constructed through the entity parameters matching each intent entity, and intent verification credential can be generated according to the structured parameters. Based on this, an object search is then performed on the transaction intent content matched by the intent verification credential to obtain the target transaction object that matches the transaction intent content.

[0138] Furthermore, based on the virtual object's understanding of the transaction intent content, including entity parameters matching the intent entity, it is necessary to generate intent verification credentials according to the structured parameters constructed based on the entity parameters matching each intent entity. The method for generating intent verification credentials is described below: In an exemplary optional embodiment, the virtual object's understanding of the transaction intent content includes entity parameters matching the intent entity. Based on this, the transaction processing method further includes: creating an intent authorization data structure according to the entity parameters matching each intent entity.

[0139] Specifically, the virtual object requests the verifiable digital credential generator to generate an intent verification credential, so that the verifiable digital credential generator can create an intent authorization data structure according to the entity parameters matching each intent entity. As can be seen from the foregoing embodiments, the large language model feeds back structured parameters including the entity parameters matching each intent entity to the virtual object. The virtual object requests the verifiable digital credential generator to generate an intent verification credential based on the received structured parameters, and the request carries the structured parameters. At this time, the verifiable digital credential generator specifically creates an intent authorization data structure according to the structured parameters (i.e., including the entity parameters matching each intent entity) and sets the authorization range to obtain a draft intent verification credential, thereby returning the draft intent verification credential to the virtual object. For ease of understanding, the structured parameters {category:"dress", season:"summer", style:"fresh", price_range:[200, 400]} obtained above are used as an example for further explanation. The authorization range obtained here is used to indicate that the maximum amount of the selected transaction object is 400, and the automatic transaction threshold is 300.

[0140] Based on this, an intent verification credential is generated according to the transaction intent content. Specifically, this includes: obtaining the operation information of the confirmation operation for the transaction authorization information, and embedding the operation information into the intent authorization data structure to obtain the intent verification credential.

[0141] The operation information is used only to describe the context of the complete record confirmation operation. This context information includes, but is not limited to, confirmation time, device information, network information, and session information, forming an immutable operation log. The confirmation time can be accurate to milliseconds (ms) according to actual application requirements. Device information includes, but is not limited to, terminal identifier, terminal model, and terminal operating system. Network information includes, but is not limited to, terminal IP and terminal geographical location. Session information may include, but is not limited to, the contextual dialogue information with the target object and virtual object in the dialogue interface and the number of dialogue interactions.

[0142] Specifically, as can be seen from the foregoing embodiments, after identifying multiple intent entities in the transaction intent content and the entity parameters matched by each intent entity, the entity parameters matched by each intent entity (belonging to the intent understanding result) will be displayed on the login terminal. Then, when the target object confirms the intent understanding result and triggers the confirmation operation for the transaction authorization information, the virtual object can obtain the operation information of the confirmation operation for the transaction authorization information, that is, record the confirmation time of triggering the confirmation operation for the transaction authorization information, the device information of the target object's login terminal, the network information of the target object's login terminal, the contextual dialogue information between the target object and the virtual object in the dialogue interface, and the number of dialogue interactions, etc.

[0143] Based on this, the virtual object can obtain the intent verification credential by embedding the operation information into the obtained intent authorization data structure. Since the verifiable digital credential generator specifically creates the intent authorization data structure according to the structured parameters and sets the authorization scope to obtain a draft intent verification credential, and then returns the draft intent verification credential to the virtual object, meaning the virtual object can essentially obtain the draft intent verification credential of the intent authorization data structure, after the virtual object obtains the operation information for the confirmation operation of the transaction authorization information, it constructs a matching operation confirmation record (ConfirmationRecord) according to the operation information, and then feeds back both the operation confirmation record and the draft intent verification credential to the verifiable digital credential generator. This allows the verifiable digital credential generator to embed the operation confirmation record into the intent authorization data structure in the draft intent verification credential, thereby obtaining the required intent verification credential. In an exemplary optional embodiment, the transaction processing method further includes: after generating the intent verification credential, determining the first hash value of the intent verification credential. Specifically, after generating the intent verification credential, the operation confirmation record can also perform a hash calculation based on the intent verification credential to obtain a SHA-256 hash value H1, and determine the SHA-256 hash value H1 as the first hash value of the intent verification credential. Then, the verifiable digital credential generator stores the obtained intent verification credential and the first hash value of the intent verification credential into the credential storage system.

[0144] To facilitate understanding of the aforementioned process, based on Figure 11 The example shown, which displays the intent understanding result on the login terminal and the transaction authorization information based on the intent understanding result, will be used as a basis for further introduction, such as... Figure 23As shown, after the login terminal displays the transaction authorization information based on the intent understanding result, if the target object triggers a confirmation operation on the transaction authorization information on the login terminal, the virtual object can obtain the operation information of the confirmation operation on the transaction authorization information, construct an operation confirmation record based on the obtained operation information, and then send the operation confirmation record and the intent verification certificate draft back to the verifiable digital certificate generator. This allows the verifiable digital certificate generator to embed the operation confirmation record into the intent verification certificate draft to obtain the intent verification certificate, calculate the first hash value based on the intent verification certificate, and store the intent verification certificate and the first hash value in the certificate storage system. After the certificate storage system completes the storage of the intent verification certificate and the first hash value, it sends a storage success notification back to the verifiable digital certificate generator, so that the verifiable digital certificate generator can then send a notification to the virtual object that the intent verification certificate generation is complete. Since the completion of the intent verification certificate generation reflects that the target object's intent has been authorized, the intent confirmation result for the transaction intent content can also be displayed as described in the previous embodiment. An example of the displayed intent confirmation result text could be: "Intent confirmed, searching for products..." and triggering the object search stage.

[0145] As described above, after generating the intent verification credential, the object search phase is triggered. At this point, the target transaction object that matches the transaction intent content can be determined. The following is a detailed description of this: In an exemplary specific embodiment, determining the target transaction object that matches the transaction intent content based on the intent verification credential specifically includes: obtaining the transaction intent content that matches the intent verification credential; and performing an object search according to multiple entity parameters in the transaction intent content to obtain the target transaction object that matches the transaction intent content.

[0146] Specifically, as described above, since the intent verification credential essentially embeds the operation confirmation record matched by the operation information, as well as the entity parameters matched by each intent entity, and since the entity parameters matched by each intent entity match the transaction intent content, an object search can be performed according to the multiple entity parameters in the transaction intent content to obtain the target transaction object that matches the transaction intent content. Therefore, the virtual object reads the stored intent verification credential and the first hash value from the credential storage system, and then obtains the fully authorized transaction intent content from the intent verification credential. The virtual object initiates an object query to the object search system based on the structured parameters of the transaction intent content (i.e., including multiple entity parameters), so that the object search system returns transaction objects that match the transaction intent content. Considering that there may be multiple transaction objects that match the transaction intent content, it is necessary to filter the multiple transaction objects that match the transaction intent content before determining the target transaction object. This will be described in detail below:

[0147] In one exemplary embodiment, object search is performed according to multiple entity parameters in the transaction intent content to obtain target transaction objects that conform to the transaction intent content. Specifically, this includes: performing object search according to multiple entity parameters in the transaction intent content to obtain multiple candidate transaction objects; for each candidate transaction object, object analysis is performed through multiple transaction dimensions to obtain a comprehensive score; and the candidate transaction object with the highest comprehensive score is selected as the target transaction object that conforms to the transaction intent content.

[0148] The transaction dimensions include, but are not limited to, price-performance ratio, seller reviews, merchant reputation, style matching, and return / exchange policies. Different transaction dimensions can be matched with different transaction weights. Specifically, the virtual object initiates an object query to the object search system based on the structured parameters of the transaction intent content (i.e., including multiple entity parameters). The object search system then searches for objects according to the multiple entity parameters in the transaction intent content, obtaining multiple candidate transaction objects, and then returns these candidate transaction objects to the virtual object. Based on this, the virtual object performs object analysis on each candidate transaction object through multiple transaction dimensions to obtain a comprehensive score. The comprehensive score can be obtained by performing object analysis on each transaction dimension to obtain dimension scores, and then averaging the dimension scores of each transaction dimension to obtain the comprehensive score; or, it can be obtained by performing object analysis on each transaction dimension to obtain dimension scores, and then weighting and summing the dimension scores of each transaction dimension with the dimension weights to obtain the comprehensive score. The calculation method of the comprehensive score is not limited here.

[0149] Based on this, the virtual object further sorts each candidate transaction object according to its comprehensive score from highest to lowest. The sorting result yields the candidate transaction object with the highest comprehensive score, which is then selected as the target transaction object that matches the transaction intent. For example, if the object search system provides the virtual object with candidate transaction objects A1, A2, A3, A4, and A5, and if the object search system analyzes candidate transaction objects A1 to A5 through multiple transaction dimensions, obtaining a comprehensive score of 90 for A1, 96 for A2, 85 for A3, 88 for A4, and 92 for A5, then the candidate with the highest comprehensive score of 96 is selected as the target transaction object that matches the transaction intent.

[0150] Furthermore, as described in the foregoing embodiments, after identifying the target transaction object, the target transaction object and its order information can be displayed on the target object's login terminal. In this case, candidate transaction object A2 and its order information can be displayed on the target object's login terminal. In practical applications, reasons for selecting the target transaction object (i.e., candidate transaction object A2) can also be displayed, such as the target transaction object's overall rating of 96, and the rating criteria being based on multiple transaction dimensions such as price-performance ratio, seller reviews, merchant reputation, style matching, and return / exchange policy. The specific content displayed is not limited here. To facilitate understanding of the actual interaction method of the aforementioned process, such as... Figure 24 As shown, after the object search system returns candidate transaction objects, the virtual object performs object analysis on each candidate transaction object through multiple transaction dimensions to obtain a comprehensive score, and selects the candidate transaction object with the highest comprehensive score as the target transaction object that meets the transaction intent content, and triggers the verification of the target transaction object.

[0151] Step 2204: Verify the target transaction object, and if the verification result indicates that the verification is successful, generate a transaction verification certificate based on the intent verification certificate.

[0152] Specifically, after identifying the target transaction object, a consistency verification is required to determine whether the target transaction object conforms to the intent verification credential. If the consistency verification fails, the verification result indicates that the verification has failed, and the virtual object stops processing the transaction intent content of the target object, and the transaction processing result of the virtual object is determined to be a transaction failure. Conversely, if the consistency verification passes, i.e., the verification result indicates that the verification has passed, a transaction verification credential is generated based on the intent verification credential. The following describes how to perform consistency verification and how to generate a transaction verification credential based on the intent verification credential:

[0153] In an exemplary optional embodiment, the target transaction object is verified, and if the verification result indicates that the verification is successful, a transaction verification credential is generated based on the intent verification credential. Specifically, this includes: performing a consistency match between the target transaction object and the intent verification credential; if the consistency match result indicates that the consistency match is successful, requesting a transaction signature from the merchant to which the target transaction object belongs; and if the transaction signature is received from the merchant to which the target transaction object belongs, obtaining the first hash value of the intent verification credential, and generating a transaction verification credential based on the first hash value.

[0154] Specifically, a consistency match is performed between the target transaction object and the intent verification credential. This means the virtual object requests verification of the consistency between the target transaction object and the intent verification credential from the verifiable digital credential generator. The verifiable digital credential generator then performs a consistency match between the target transaction object and the intent verification credential, obtaining a consistency score. If the consistency score is greater than or equal to a consistency score threshold, the consistency match is considered successful. Conversely, if the consistency score is less than the consistency score threshold, the consistency match is considered unsuccessful. The aforementioned consistency score threshold can be 60%, 70%, or a threshold set according to actual needs.

[0155] Taking the aforementioned embodiment as an example: a summer floral print dress with a target transaction object of 280, and a transaction object category of "dress", season of "summer", style of "fresh", and price range of [200, 400]. In this case, it is necessary to match whether 280 is within the price range [200, 400], whether the transaction object category matched with the summer floral print dress is "dress", whether the season matched with the summer floral print dress is "summer", and whether the style matched with the summer floral print dress is "fresh". If the consistency score threshold is 70% at this time, and the consistency score between the aforementioned target transaction object and the intent verification credential is 95%, then the consistency matching result indicates that the consistency matching has passed.

[0156] Furthermore, if the consistency matching result indicates that the consistency matching is successful, it means that the target transaction object matches the target transaction's intent. At this point, an order needs to be created to ensure that the purchase can be made to the target transaction object. Considering that the merchant to which the target transaction object belongs may be unable to provide transaction services, a transaction signature needs to be requested from the merchant. Upon receiving the transaction signature from the merchant, the first hash value of the intent verification credential is obtained, and a transaction verification credential is generated based on the first hash value, ensuring that the transaction verification credential includes complete intent verification credential information. Considering that the transaction verification credential needs to include the corresponding records of the transaction process, the transaction verification credential is generated specifically according to the first hash value, the target transaction object, the decision record, and the transaction signature from the merchant. A first hash chain connection is created, and then the second hash value of the transaction verification credential is calculated. The transaction verification credential and the second hash value are then associated with the intent verification credential and the first hash value according to the first hash chain connection. Since the merchant to which the target transaction object belongs is now confirmed to be able to provide transaction services, payment needs to be made to the target transaction object, thus automatically initiating the payment process for the target transaction object.

[0157] To facilitate understanding of the aforementioned process, based on, as follows Figure 24 The timing flowchart shown will be further explained, such as... Figure 25 As shown, the virtual object requests verification of the consistency between the target transaction object and the intended verification credential from the verifiable digital credential generator. This allows the verifiable digital credential generator to perform a consistency match between the target transaction object and the intended verification credential, obtaining a consistency score. The verifiable digital credential generator then returns the consistency score to the virtual object. If the consistency score is greater than or equal to a consistency score threshold, the virtual object determines that the consistency match has passed. Based on this, the virtual object then requests a transaction signature from the merchant system of the merchant to which the target transaction object belongs. The merchant system needs to verify the inventory and price of the target transaction object. After determining that the order can be fulfilled, it returns a transaction signature to the virtual object. Upon receiving the transaction signature from the merchant to which the target transaction object belongs, the generation of the transaction verification credential can begin.

[0158] In other words, the virtual object requests a verifiable digital certificate generator to generate a transaction verification certificate. The verifiable digital certificate generator generates a transaction verification certificate based on a first hash value, the target transaction object, the decision record, and the transaction signature provided by the merchant to which the target transaction object belongs. It also calculates a second hash value for the transaction verification certificate. The transaction verification certificate and the second hash value are then stored in the certificate storage system. Furthermore, the transaction verification certificate and the second hash value can be linked together with the intent verification certificate and the first hash value and stored in the certificate storage system according to a first hash chain, ensuring that multi-level verification certificates can be stacked for verification. After the certificate storage system completes the aforementioned storage, it sends a successful storage notification to the verifiable digital certificate generator, which then sends a notification to the virtual object that the transaction verification certificate generation is complete, triggering the virtual object to enter the payment stage.

[0159] Step 2206: Select the target payment method that matches the target object, generate the target payment token that matches the target payment method, and generate the payment verification credential based on the transaction verification credential.

[0160] Specifically, the payment authorization and execution phase is the final stage of interactive processing. During this phase, it's crucial to ensure secure payment execution and transmit AI scenario signals to the payment network, enabling the network to confirm that the payment request originated from a virtual object. Based on this, the virtual object sends its generated transaction verification credential to the payment system, requesting execution of the payment process. The payment system then obtains the transaction verification credential and extracts its second hash value. According to the information carried in the transaction verification credential, the payment system selects a target payment method matching the target object. The system first determines the candidate payment methods supported by the target object, then selects the target payment method from these candidates based on the information in the transaction verification credential. The selected target payment method can pay the price corresponding to the target transaction object. The method for determining the target payment method can be to evaluate the candidate payment methods, obtaining a payment score for each, and then selecting the candidate payment method with the highest score as the target payment method.

[0161] To facilitate understanding, let's take a summer floral dress with a target transaction value of 280 as an example. The payment system first determines the balance payment method and institutional payment method supported by the target item, then determines the target item's account status, and evaluates the balance payment method and institutional payment method. If the balance payment method has a payment score of 90 and the institutional payment method has a payment score of 70, then the balance payment method is selected as the target payment method, and the target item's account balance should be greater than the transaction amount of 280.

[0162] Furthermore, based on selecting a target payment method that matches the target object, a target payment token matching the target payment method is generated. This target payment token has a valid payment period, for example, 10 minutes. The target payment token is valid for 10 minutes; it can be verified within that period, but will fail verification after that period. Then, a payment verification certificate is generated based on the transaction verification certificate to ensure that the information in the payment verification certificate includes the information in the transaction verification certificate. It is understandable that, when generating the target payment token, a target risk signal for the target payment method can also be extracted, and a risk score for the target payment method can be calculated.

[0163] As can be seen from the foregoing embodiments, after generating the transaction verification credential, the second hash value of the transaction verification credential can be calculated. Therefore, the second hash value should also be considered when generating the payment verification credential. This will be described below: In an exemplary optional embodiment, the transaction processing method further includes: after generating the transaction verification credential, determining the second hash value of the transaction verification credential.

[0164] Specifically, the verifiable digital certificate generator generates a transaction verification certificate based on the first hash value, the target transaction object, the decision record, and the transaction signature fed back by the merchant to which the target transaction object belongs. It also calculates the second hash value of the transaction verification certificate and stores the transaction verification certificate and the second hash value in the certificate storage system. Furthermore, it can also store the transaction verification certificate and the second hash value, as well as the intent verification certificate and the first hash value, in the certificate storage system according to the first hash chain, to ensure that multi-level verification certificates can be verified in combination.

[0165] Based on this, a payment verification credential is generated based on the transaction verification credential, specifically including: obtaining the second hash value of the transaction verification credential, and generating a payment verification credential based on the second hash value.

[0166] Specifically, a second hash value of the transaction verification credential is obtained, and a payment verification credential is generated based on the second hash value, so that the payment verification credential can include the complete credential information of the transaction verification credential. Furthermore, considering the superposition of multiple layers of verification credentials, an intent verification credential can also be considered when generating the payment verification credential. That is, based on the aforementioned embodiments, a first hash value of the intent verification credential can also be obtained, and the payment verification credential is generated based on the first hash value and the second hash value.

[0167] Furthermore, considering that payment verification credentials need to include relevant records of the payment process, the payment verification credentials are generated specifically based on the first hash value, the second hash value, the AI ​​scenario signal, and the risk signal. The payment system then signs the payment verification credentials to ensure their authenticity. At this point, a second hash chain connection can also be created, and the payment verification credentials, the first hash value, the transaction verification credentials, the second hash value, and the intent verification credentials, and the first hash value can be associated according to the second hash chain connection.

[0168] To facilitate understanding of the aforementioned process, such as Figure 26 As shown, the virtual object sends a transaction verification credential to the payment system, enabling the payment system to extract the second hash value of the transaction verification credential, determine the target payment method, and generate a target payment token. Then, the payment system requests a verifiable digital credential generator to create a payment verification credential, so that the verifiable digital credential generator generates the payment verification credential and returns the obtained payment verification credential to the payment system. The payment system then signs the payment verification credential to ensure its authenticity.

[0169] Step 2208: Authorize and verify the target payment token and payment verification certificate, and determine the transaction processing result of the virtual object based on the obtained authorization and verification result.

[0170] Specifically, authorization verification is performed on the target payment token and payment verification credential. Based on the obtained authorization verification result, the transaction processing result of the virtual object is determined. Specifically, the payment system submits a transaction authorization request, including the payment verification credential and the target payment token, to the payment network. Since the payment verification credential includes AI scene signals, the payment network, in response to the transaction authorization request, can identify the AI ​​scene signals in the payment verification credential and trigger a specific authorization verification strategy for AI scenes. This authorization verification strategy is specifically used for risk detection of the payment environment. Based on this, after the payment network triggers the specific authorization verification strategy for AI scenes, it forwards the transaction authorization request, including the payment verification credential and the target payment token, to the institution for authorization verification. That is, the institution conducts risk control checks and authorization decisions on the payment verification credential and the target payment token. The institution performs comprehensive, multi-dimensional risk control checks on the payment verification credential and the target payment token to obtain the authorization verification result, and determines the transaction processing result of the virtual object based on the authorization verification result. Furthermore, the authorization verification result can indicate whether the authorization verification passed or failed.

[0171] The aforementioned multi-dimensional risk control checks include, but are not limited to: the consistency score between the transaction intent content and the target transaction object, the validity of the object's authorization, the rationality of the decision, and the trustworthiness of the device. To further illustrate with the previous example, a consistency score of 95% between the transaction intent content and the target transaction object indicates strong consistency. Assessing the validity of the object's authorization requires verifying the validity of the intent verification credential included in the payment verification credential, which matches the first hash value. If valid, it indicates the validity of the target object's confirmation operation regarding the transaction authorization information, and no tampering has occurred. The rationality of the decision is used to assess the queryability of the decision; if it can be queried, the decision is considered highly reasonable. A login device that is a frequently used device of the target object indicates high device trustworthiness; otherwise, it indicates low device trustworthiness. Based on the aforementioned multi-dimensional risk control checks, a comprehensive verification score can be obtained. If the comprehensive verification score is higher than the scoring threshold, it indicates low payment risk; in this case, the authorization verification result indicates successful authorization verification, and the transaction processing for virtual object transactions can be executed. If the comprehensive verification score is lower than the scoring threshold, it indicates high payment risk; in this case, the authorization verification result indicates failed authorization verification, and the transaction processing for virtual object transactions will not be executed.

[0172] To facilitate understanding of the aforementioned process, based on Figure 26 The process shown will be further explained, such as... Figure 27As shown, after the payment system obtains and signs the payment verification credential, it submits a transaction authorization request, including the payment verification credential and the target payment token, to the payment network. The payment network, responding to the authorization request, can identify the AI ​​scene signal in the payment verification credential, thereby recognizing the virtual object transaction. The transaction authorization request, including the payment verification credential and the target payment token, is then forwarded to the institution for authorization verification. The institution then reports the authorization verification result to the payment network, which in turn forwards it to the payment system. The payment system can then determine whether to continue transaction processing based on the authorization verification result and reports the transaction processing result back to the virtual object.

[0173] Since the authorization verification result can indicate whether the authorization verification is successful or unsuccessful, the two cases are described below: In an exemplary specific embodiment, determining the transaction processing result of the virtual object based on the obtained authorization verification result includes: if the obtained authorization verification result indicates that the authorization verification is unsuccessful, terminating the transaction processing of the virtual object and determining the transaction processing result of the virtual object as a transaction failure; if the obtained authorization verification result indicates that the authorization verification is successful, paying for the object resources matched with the target transaction object according to the target payment method and determining the transaction processing result of the virtual object as a transaction success.

[0174] Specifically, if the authorization verification result indicates that the authorization verification failed, it means that the institution discovered an anomaly during the authorization verification process, such as exceeding the limit, device malfunction, or verification credential tampering. In this case, the institution can refuse to provide the authorization verification result indicating that the authorization verification failed. The payment network forwards the authorization verification result to the payment system and terminates the transaction processing for the virtual object, determining the transaction processing result as a transaction failure and providing feedback to the virtual object. If the virtual object determines that the transaction processing result is a transaction failure, it can also display the transaction failure result and solution suggestions on the target object's login terminal. That is, it displays the solution information matching the reason for the authorization verification failure. For example, if the anomaly is exceeding the limit, the solution suggestion is to check the transaction amount of the target object. If the anomaly is device malfunction, the solution suggestion is to check if the device malfunction is a commonly used terminal device. If the anomaly is verification credential tampering, the solution suggestion is to check for abnormal account login and abnormal software intrusion.

[0175] Conversely, if the authorization verification result indicates that the authorization verification has passed, it means that the institution has not found any abnormalities during the authorization verification process. In this case, the institution can approve the transaction and send the authorization verification result indicating that the authorization verification has passed back to the payment network. The payment network will then forward the authorization verification result to the payment system so that the payment system can pay the target transaction object resource (i.e., the transaction amount) according to the target payment method and determine that the transaction processing result of the virtual object is a successful transaction, thereby notifying the target object that the purchase has been completed.

[0176] To facilitate understanding of the aforementioned process, based on Figure 27 The process shown will be further explained, such as... Figure 28 As shown, after the institution determines the authorization verification result, for authorization verification results indicating successful authorization, the institution can approve the transaction. The payment network confirms the institution's approval and forwards the transaction to the payment system, enabling the payment system to pay for the object resources matched to the target transaction object according to the target payment method. Upon successful payment, the virtual object notifies the target object that the purchase has been completed. Conversely, for authorization verification results indicating failed authorization, the institution does not approve the transaction. The payment network confirms the institution's failure and forwards the transaction to the payment system. The payment system terminates the transaction processing for the virtual object and, upon termination, notifies the target object of the transaction failure and provides suggested solutions.

[0177] It is understood that the foregoing examples are for the purpose of understanding this solution and should not be construed as specific limitations on this solution.

[0178] In this embodiment, by sequentially generating intent verification credentials, transaction verification credentials, and payment verification credentials, three layers of verifiable digital credentials provide verifiable authorization evidence for the target object during the intent determination, transaction, and payment processes. This ensures that the target object's confirmation operation authorizes the intent and transaction, forming a queryable authorization certificate, and also guarantees that the obtained transaction processing result conforms to the target object's transaction intent. Furthermore, since verifiable credentials are generated sequentially at all authorization stages, and each verifiable credential is interconnected, verification problems caused by credential tampering are avoided, further improving the reliability and security of transaction processing.

[0179] As described in the foregoing embodiments, the target object's confirmation operation can authorize the intent and transaction. That is, the entire transaction processing flow is based on the user confirmation record mechanism provided in this embodiment. The authorization operation of the target object is recorded only at the intent verification credential stage; the target object does not need to participate in the entire transaction processing flow. Specifically, as follows... Figure 29The flowchart of the secure signature mechanism shown first executes step 2901, whereby the target object triggers authorization. This step involves the target object confirming the intent understanding result and triggering a confirmation operation for the transaction authorization information to obtain the operation information for the confirmation operation. It can be understood that authorization is only required when generating the intent verification credential; the transaction verification credential and payment verification credential are automatically generated by the virtual object.

[0180] Based on this, step 2902, which involves collecting context information, requires determining the multi-dimensional context information to be collected, such as confirmation time, device information, network information, and session information. In step 2903, the operation confirmation record is constructed according to the operation information. Then, in step 2904, the operation confirmation record can be embedded into the intent authorization data structure within the intent verification credential draft, thereby obtaining the required intent verification credential. This ensures that the operation confirmation record becomes an inseparable part of the intent verification credential, and any modification to the intent verification credential will affect its hash value.

[0181] Furthermore, in step 2905 regarding the hash value of the intent verification credential, the information containing the operation confirmation record is serialized into a JSON structure, and then a SHA-256 hash value is calculated on the JSON structure information. The resulting SHA-256 hash value is the first hash value of the intent verification credential. Therefore, any modification to any credential field in the intent verification credential will change the first hash value, allowing detection of any credential field tampering based on the first hash value. In step 2906 regarding secure storage and backup, the intent verification credential and the first hash value are stored on the login device and also encrypted and stored on the server side. Therefore, in cases requiring dispute resolution or security auditing, the following multi-dimensional verifications are performed in step 2907 regarding verification and detection: integrity verification, timing verification, device verification, interaction behavior verification, and geolocation verification.

[0182] The verification process includes several key components: Integrity Verification, Transaction Verification, and Payment Verification, each with its own recalculated hash value, which is then compared to the stored hash values. Timing Verification checks the correctness of the timestamps between the credentials; the timestamps for the creation of the Intent Verification, Transaction Verification, and Payment Verification should be from earliest to latest. If the timestamps are not in the correct order, time sequence tampering has occurred. Device Verification verifies whether the login device initiating the transaction is a frequently used device of the target object. Interaction Behavior Verification checks whether the interaction mode is abnormal. Geographic Location Verification verifies whether the location of the login device initiating the transaction is a frequently used geographic location of the target object.

[0183] Therefore, dispute resolution information can include verification results obtained through multi-dimensional verification, such as integrity verification results, timing verification results, device verification results, interaction behavior verification results, and geolocation verification results.

[0184] Based on the detailed description of the foregoing embodiments, the complete flow of the transaction processing method in the embodiments of this application will be described below. In an exemplary embodiment, such as... Figure 30 As shown, a transaction processing method is provided, which is applied to... Figure 1 Taking terminal 102 as an example, it can be understood that this method can also be applied to a system including terminal 102 and server 104, and implemented through the interaction between terminal 102 and server 104. In this embodiment, the method includes steps 3002 to 3015. Wherein:

[0185] Step 3001: On the login terminal of the target object, display the dialog interface with the virtual object.

[0186] Specifically, when the target object requires automated transaction processing, a dialog interface with the virtual object can be displayed on the target object's login terminal. This dialog interface can display an input area for the target object to input content. It can also display multiple functional controls for payment processing. In practical applications, considering that the virtual object can provide automated payment process operations, the dialog interface can also display interactive information from the virtual object. This interactive information can be text messages instructing the target object to input transaction intent.

[0187] Step 3002: In response to the target object inputting transaction intent content in the dialog interface, perform semantic analysis on the transaction intent content, identify multiple intent entities in the transaction intent content, and the entity parameters matched by each intent entity; display the entity parameters matched by each intent entity.

[0188] Specifically, based on the dialog interface displayed with the virtual object, the target object can input the content of the transaction intention based on the real transaction intention. As can be seen from the above introduction, since the displayed dialog interface can display an information input area for the target object to input content, after the target object inputs the content of the transaction intention in the information input area, the content of the transaction intention entered by the target object in the dialog interface can be displayed.

[0189] Furthermore, the virtual object responds to the target object's input of transaction intent content in the dialogue interface and sends an understanding request for the transaction intent content to the large language model. The large language model, in response to this request, performs semantic analysis on the transaction intent content to identify multiple intent entities. Then, it generates structured parameters from the transaction intent content according to the intent entities to obtain the entity parameters matching each intent entity. After the large language model performs semantic analysis on the transaction intent content, identifies multiple intent entities and their matching entity parameters, it can feed back these entities and their matching entity parameters to the virtual object. This allows the virtual object to then send the matching entity parameters to the target object's login terminal, where they are displayed.

[0190] Step 3003: Create an intent authorization data structure according to the entity parameters matched for each intent entity.

[0191] Specifically, semantic analysis of transaction intent content is not performed through virtual objects. Instead, the virtual object sends an understanding request for the transaction intent content to the large language model. Therefore, the large language model feeds back structured parameters to the virtual object, including entity parameters matching each intent entity. Based on the received structured parameters, the virtual object requests the generation of an intent verification credential from the verifiable digital credential generator, carrying structured parameters including entity parameters matching each intent entity. Based on this, the verifiable digital credential generator creates an intent authorization data structure according to the entity parameters matching each intent entity and returns a draft of the intent verification credential to the virtual object. At this point, the virtual object feeds back the intent understanding result and the transaction authorization information based on the intent understanding result to the target object's login terminal, so that the login terminal displays the intent understanding result and the transaction authorization information based on the intent understanding result.

[0192] Step 3004: Obtain the operation information for the confirmation operation of the transaction authorization information, and embed the operation information into the intent authorization data structure to obtain the intent verification credential.

[0193] Specifically, since the login terminal can display the intent understanding result and the transaction authorization information based on that result, when the target object confirms the intent understanding result and triggers a confirmation operation for the transaction authorization information, the virtual object can obtain the operation information for the confirmation operation, which includes recording the confirmation time of the confirmation operation, the target object's login terminal device information, the target object's login terminal network information, the contextual dialogue information between the target object and the virtual object in the dialogue interface, and the number of dialogue interactions.

[0194] Based on this, the virtual object can obtain the intent verification credential by embedding the operation information into the obtained intent authorization data structure. Since the verifiable digital credential generator specifically creates the intent authorization data structure according to the structured parameters and sets the authorization scope to obtain a draft intent verification credential, and then returns the draft intent verification credential to the virtual object, meaning the virtual object can actually obtain the draft intent verification credential from the intent authorization data structure, after the virtual object obtains the operation information for the confirmation operation of the transaction authorization information, it constructs a matching operation confirmation record according to the operation information, and then feeds back both the operation confirmation record and the draft intent verification credential to the verifiable digital credential generator. This allows the verifiable digital credential generator to embed the operation confirmation record into the intent authorization data structure in the draft intent verification credential, thereby obtaining the required intent verification credential.

[0195] Step 3005: After generating the intent verification credential, display the intent confirmation result for the transaction intent content and the search progress for the transaction intent content on the target object's login terminal.

[0196] Specifically, in the process of generating intent verification credentials, it is necessary to obtain the operation information of the confirmation operation for the transaction authorization information. This operation information is then embedded into the obtained intent authorization data structure to obtain the intent verification credentials. After generating the intent verification credentials, to ensure that the target object can more directly confirm the transaction processing progress, the intent confirmation result for the transaction intent content can be displayed on the target object's login terminal; that is, the intent confirmation result is now "intent confirmation complete." Furthermore, during the execution of transaction processing, after generating the intent verification credentials, it is also necessary to determine the target transaction object that matches the transaction intent content based on the intent verification credentials. In other words, during the process of determining the target transaction object that matches the transaction intent content, to ensure that the target object can more directly confirm the transaction processing progress, the search progress for the transaction intent content can also be displayed on the target object's login terminal.

[0197] Step 3006: Determine the target transaction object that matches the transaction intent content based on the intent verification credentials.

[0198] Specifically, since the intent verification credential essentially embeds the operation confirmation record matched by the operation information, as well as the entity parameters matched by each intent entity, and since the entity parameters matched by each intent entity match the transaction intent content, an object search can be performed according to the multiple entity parameters in the transaction intent content to obtain the target transaction object that matches the transaction intent content. Therefore, the virtual object reads the stored intent verification credential and the first hash value from the credential storage system, and then obtains the fully authorized transaction intent content from the intent verification credential. The virtual object initiates an object query to the object search system based on the structured parameters of the transaction intent content (i.e., including multiple entity parameters), so that the object search system returns transaction objects that match the transaction intent content. Considering that there may be multiple transaction objects that match the transaction intent content, it is necessary to filter these multiple transaction objects before determining the target transaction object. In this case, an object search is performed according to the multiple entity parameters in the transaction intent content to obtain multiple candidate transaction objects. Then, for each candidate transaction object, object analysis is performed through multiple transaction dimensions to obtain a comprehensive score. Finally, the candidate transaction object with the highest comprehensive score is selected as the target transaction object that matches the transaction intent content.

[0199] Step 3007: After identifying the target transaction object, display the target transaction object and the order information for the target transaction object on the target object's login terminal.

[0200] Specifically, after identifying the target trading partner, the target trading partner and their order information can be displayed on their login terminal. In practical applications, the reasons for selecting the target trading partner can also be displayed, such as the target trading partner's overall rating of 96, and the rating criteria being based on multiple trading dimensions such as price-performance ratio, seller reviews, merchant reputation, style matching, and return / exchange policies. The specific content displayed is not limited here.

[0201] Step 3008: Verify the target transaction object, and if the verification result indicates that the verification is successful, generate a transaction verification certificate based on the intent verification certificate.

[0202] Specifically, a consistency match is performed between the target transaction object and the intent verification credential. This means the virtual object requests verification of the consistency between the target transaction object and the intent verification credential from the verifiable digital credential generator. The verifiable digital credential generator then performs a consistency match between the target transaction object and the intent verification credential, obtaining a consistency score. If the consistency score is greater than or equal to a consistency score threshold, the consistency match is considered successful. Conversely, if the consistency score is less than the consistency score threshold, the consistency match is considered unsuccessful.

[0203] Furthermore, if the obtained consistency matching result indicates that the consistency matching is successful, it means that the target transaction object matches the transaction intent content of the target object. At this time, it is necessary to create an order to ensure that the target transaction object can be purchased. Considering that the merchant to which the target transaction object belongs may be unable to provide transaction services, it is also necessary to request a transaction signature from the merchant to which the target transaction object belongs. After receiving the transaction signature from the merchant to which the target transaction object belongs, the first hash value of the intent verification credential is obtained, and a transaction verification credential is generated based on the first hash value.

[0204] This allows the transaction verification credential to include complete intent verification credential information. Furthermore, considering that the transaction verification credential needs to include corresponding records of the transaction process, the transaction verification credential is generated specifically based on the first hash value, the target transaction object, the decision record, and the transaction signature provided by the merchant to which the target transaction object belongs. A first hash chain connection is then created, followed by the calculation of the second hash value of the transaction verification credential. The transaction verification credential, the second hash value, and the intent verification credential and the first hash value are then associated according to the first hash chain connection. Since the merchant to which the target transaction object belongs has now been confirmed to be able to provide transaction services, payment needs to be made to the target transaction object, thus automatically initiating the payment process for the target transaction object.

[0205] Step 3009: During the verification process for the target transaction object, the verification progress is displayed on the target object's login terminal.

[0206] Specifically, during the verification process for the target transaction object, the verification progress can also be displayed on the target object's login terminal. It is understood that other information that can be displayed on the login terminal may also exist during the verification process, and the specific information displayed can be based on the verification process; this is not limited here.

[0207] Step 3010: Select the target payment method that matches the target object, generate the target payment token that matches the target payment method, and generate the payment verification credential based on the transaction verification credential.

[0208] Specifically, the payment authorization and execution phase is the final stage of interactive processing. During this phase, it's crucial to ensure secure payment execution and transmit AI scenario signals to the payment network, enabling the network to confirm that the payment request originated from a virtual object. Based on this, the virtual object sends its generated transaction verification credential to the payment system, requesting execution of the payment process. The payment system then obtains the transaction verification credential and extracts its second hash value. According to the information carried in the transaction verification credential, the payment system selects a target payment method matching the target object. The system first determines the candidate payment methods supported by the target object, then selects the target payment method from these candidates based on the information in the transaction verification credential. The selected target payment method can pay the price corresponding to the target transaction object. The method for determining the target payment method can be to evaluate the candidate payment methods, obtaining a payment score for each, and then selecting the candidate payment method with the highest score as the target payment method.

[0209] Furthermore, based on selecting a target payment method that matches the target object, a target payment token matching the target payment method is generated. This target payment token has a valid payment period; tokens valid within this period can be verified, while those exceeding the valid period cannot. Then, a payment verification credential is generated based on the transaction verification credential to ensure that the information in the payment verification credential includes the information in the transaction verification credential.

[0210] Step 3011: Authorize and verify the target payment token and payment verification certificate. If the authorization verification result indicates that the authorization verification is successful, pay the object resources matched with the target transaction object according to the target payment method, and determine the transaction processing result of the virtual object as a successful transaction.

[0211] Specifically, authorization verification is performed on the target payment token and payment verification credential. Based on the obtained authorization verification result, the transaction processing result of the virtual object is determined. Specifically, the payment system submits a transaction authorization request, including the payment verification credential and the target payment token, to the payment network. Since the payment verification credential includes AI scene signals, the payment network, in response to the transaction authorization request, can identify the AI ​​scene signals in the payment verification credential and trigger a specific authorization verification strategy for AI scenes. This authorization verification strategy is specifically used for risk detection of the payment environment. Based on this, after the payment network triggers the specific authorization verification strategy for AI scenes, it forwards the transaction authorization request, including the payment verification credential and the target payment token, to the institution for authorization verification. That is, the institution conducts risk control checks and authorization decisions on the payment verification credential and the target payment token. The institution performs comprehensive, multi-dimensional risk control checks on the payment verification credential and the target payment token to obtain the authorization verification result, and determines the transaction processing result of the virtual object based on the authorization verification result. Furthermore, the authorization verification result can indicate whether the authorization verification passed or failed.

[0212] Furthermore, if the authorization verification result indicates that the authorization verification has passed, it means that the institution has not found any abnormalities during the authorization verification process. At this time, the institution can approve the transaction and send the authorization verification result indicating that the authorization verification has passed back to the payment network. The payment network will then forward the authorization verification result to the payment system so that the payment system can pay the target transaction object resource (i.e., the transaction amount) according to the target payment method and determine that the transaction processing result of the virtual object is a successful transaction, thereby notifying the target object that the purchase has been completed.

[0213] Step 3012: Display the payment progress for the target transaction on the target's login terminal.

[0214] Specifically, after the target transaction object is verified, payment will be processed for the target transaction object. At this time, the payment progress for the target transaction object can also be displayed on the target transaction object's login terminal. It is understood that after the target transaction object is verified, there may be other information that can be displayed on the login terminal. The specific information displayed can be based on the verification result and is not limited here.

[0215] Step 3013: If the virtual object exits the dialog interface while performing transaction processing according to the transaction intent, a transaction processing notification is displayed on the login terminal; in response to the interactive operation triggered by the transaction processing notification, the transaction processing result of the virtual object is displayed.

[0216] Specifically, during the process of the virtual object executing the transaction according to the transaction intent, if the target object exits the dialog interface by triggering an exit operation, and if the virtual object receives the transaction processing result, a transaction processing notification will be pushed to the target object's login terminal so that the notification is displayed on the login terminal. Only after the target object confirms the completion of the transaction via the notification can it trigger the corresponding interactive operation, at which point the virtual object's transaction processing result will be displayed.

[0217] Step 3014: In response to the operation of viewing details of the transaction processing result, display the transaction processing details of the transaction processing result.

[0218] Specifically, after displaying the transaction processing result of the virtual object, a details viewing operation can be triggered on the transaction processing result, allowing the logged-in terminal to display the transaction processing details for that result. The target object can also view the complete content of the authorization certificate for the virtual object's transaction processing result. Each layer of authorization certificate clearly indicates the generation method and generation time. The transaction processing details may also include a details storage control and an appeal control. The target object can store the displayed transaction processing details by triggering the details storage control. If the target object has questions about the transaction processing result, it can trigger the appeal control to initiate a dispute appeal against the transaction order matching the generated transaction processing result. Since the transaction processing details include an authorization certificate chain, the authorization certificate chain can be used to determine whether there are verification errors that caused the problem with the result.

[0219] Step 3015: Authorize and verify the target payment token and payment verification certificate. If the authorization verification result indicates that the authorization verification has failed, terminate the transaction processing of the virtual object and determine that the transaction processing result of the virtual object is a transaction failure.

[0220] Specifically, the system authorizes and verifies the target payment token and payment verification credential. Based on the authorization verification result, it determines the transaction processing result for the virtual object. If the authorization verification result indicates that the authorization verification failed, it means that the institution discovered an anomaly during the authorization verification process, such as exceeding the limit, device malfunction, or verification credential tampering. In this case, the institution can refuse to provide feedback indicating that the authorization verification failed. The payment network forwards the authorization verification failure result to the payment system and terminates the transaction processing for the virtual object, determining the transaction processing result as a transaction failure and providing feedback to the virtual object. If the virtual object determines that the transaction processing result is a transaction failure, it can also display the transaction failure result and solution suggestions on the target object's login terminal. That is, it displays the solution information matching the reason for the authorization verification failure. For example, if the anomaly is exceeding the limit, the solution suggestion is to check the transaction amount of the target object. If the anomaly is device malfunction, the solution suggestion is to check whether the device malfunction is a commonly used terminal device. If the issue is related to verification credential tampering, the recommended solutions are to check for abnormal account logins and to investigate any suspicious software intrusions.

[0221] It should be understood that the specific implementation methods of steps 3001 to 3015 are similar to those of the aforementioned embodiments, and will not be repeated here.

[0222] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0223] Based on the same inventive concept, this application also provides a transaction processing apparatus for implementing the transaction processing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more transaction processing apparatus embodiments provided below can be found in the limitations of the transaction processing method described above, and will not be repeated here.

[0224] In one exemplary embodiment, such as Figure 31As shown, a transaction processing apparatus is provided, including: a dialog interface display module 3102, an information display module 3104, a transaction processing module 3106, and a transaction processing result display module 3108, wherein:

[0225] The dialog interface display module 3102 is used to display the dialog interface with the virtual object on the login terminal of the target object;

[0226] The information display module 3104 is used to respond to the target object's input of transaction intent content in the dialog interface, display the virtual object's understanding of the transaction intent content, and display the transaction authorization information for the transaction intent content;

[0227] Transaction processing module 3106 is used to have the virtual object perform transaction processing according to the transaction intent content when the target object confirms the result of understanding the intent and triggers a confirmation operation for the transaction authorization information;

[0228] The transaction processing result display module 3108 is used to display the transaction processing result of the virtual object.

[0229] In an exemplary embodiment, the information display module is further configured to display, after generating the intent verification credential, the intent confirmation result for the transaction intent content and the search progress for the transaction intent content on the login terminal of the target object.

[0230] In an exemplary embodiment, the information display module is further configured to display the target transaction object and the order information for the target transaction object on the login terminal of the target object after the target transaction object is determined.

[0231] In an exemplary embodiment, the information display module is further configured to display the verification progress and the payment progress of the target transaction object on the target object's login terminal during the verification process.

[0232] In an exemplary embodiment, the transaction processing module is specifically configured to display a transaction processing notification on the login terminal when the virtual object exits the dialog interface during the transaction processing process according to the transaction intent content; and to display the transaction processing result of the virtual object in response to the interactive operation triggered by the transaction processing notification.

[0233] In one exemplary embodiment, the information display module is further configured to display transaction processing details for the transaction processing result in response to a details viewing operation for the transaction processing result.

[0234] In an exemplary embodiment, the transaction processing module is specifically configured to generate an intent verification credential according to the transaction intent content, and determine a target transaction object that conforms to the transaction intent content based on the intent verification credential; verify the target transaction object, and generate a transaction verification credential based on the intent verification credential if the obtained verification result indicates that the verification is successful; select a target payment method that matches the target object, and generate a target payment token that matches the target payment method, and generate a payment verification credential based on the transaction verification credential; perform authorization verification on the target payment token and the payment verification credential, and determine the transaction processing result of the virtual object based on the obtained authorization verification result.

[0235] In an exemplary embodiment, the transaction processing module is specifically configured to terminate the transaction processing of the virtual object and determine the transaction processing result of the virtual object as a transaction failure if the obtained authorization verification result indicates that the authorization verification has passed; and to make payment for the object resources matched with the target transaction object according to the target payment method if the obtained authorization verification result indicates that the authorization verification has passed, and determine the transaction processing result of the virtual object as a transaction success.

[0236] In one exemplary embodiment, the virtual object's intent understanding result of the transaction intent content includes entity parameters matching the intent entity;

[0237] The transaction processing module is also used to create intent authorization data structures according to the entity parameters matched for each intent entity;

[0238] The transaction processing module is specifically used to obtain the operation information for the confirmation operation of the transaction authorization information, and embed the operation information into the intent authorization data structure to obtain the intent verification credential.

[0239] In an exemplary embodiment, the information display module is specifically configured to, in response to the target object inputting transaction intent content in the dialog interface, perform semantic analysis on the transaction intent content, identify multiple intent entities in the transaction intent content, and entity parameters matching each intent entity; and display the entity parameters matching each intent entity.

[0240] In an exemplary embodiment, the transaction processing module is specifically used to obtain transaction intent content that matches the intent verification credential; and to perform object search according to multiple entity parameters in the transaction intent content to obtain a target transaction object that matches the transaction intent content.

[0241] In an exemplary embodiment, the transaction processing module is specifically used to perform object search according to multiple entity parameters in the transaction intent content to obtain multiple candidate transaction objects; for each candidate transaction object, object analysis is performed through multiple transaction dimensions to obtain a comprehensive score; and the candidate transaction object with the highest comprehensive score is selected as the target transaction object that conforms to the transaction intent content.

[0242] In one exemplary embodiment, the transaction processing module is further configured to determine a first hash value of the intent verification credential after generating the intent verification credential.

[0243] The transaction processing module is specifically used to perform consistency matching between the target transaction object and the intent verification credential. If the consistency matching result indicates that the consistency matching is successful, it requests a transaction signature from the merchant to which the target transaction object belongs. If the transaction signature is received from the merchant to which the target transaction object belongs, it obtains the first hash value of the intent verification credential and generates a transaction verification credential based on the first hash value.

[0244] In one exemplary embodiment, the transaction processing module is further configured to determine a second hash value of the transaction verification credential after generating the transaction verification credential;

[0245] The transaction processing module is specifically used to obtain the second hash value of the transaction verification credential and generate a payment verification credential based on the second hash value.

[0246] In one embodiment, a computer device is provided, which can be a server or a terminal. This embodiment uses a computer device as a terminal as an example, and its internal structure diagram is as follows. Figure 32As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a transaction processing method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0247] Those skilled in the art will understand that Figure 32 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0248] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0249] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0250] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0251] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0252] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, etc., and are not limited to these.

[0253] The technical features in the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0254] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for transaction processing, characterized in that, The method includes: On the target object's login terminal, a dialog interface for interacting with the virtual object is displayed; In response to the target object inputting transaction intent content in the dialog interface, the virtual object's understanding result of the transaction intent content is displayed, and transaction authorization information for the transaction intent content is displayed; If the target object confirms the intent understanding result and triggers a confirmation operation for the transaction authorization information, the virtual object executes the transaction processing according to the transaction intent content; Displays the transaction processing results of the virtual object.

2. The method according to claim 1, characterized in that, The method further includes: After generating the intent verification credentials, the login terminal of the target object displays the intent confirmation result for the transaction intent content and the search progress for the transaction intent content.

3. The method according to claim 1, characterized in that, The method further includes: After identifying the target transaction object, the target transaction object and the order information for the target transaction object are displayed on the login terminal of the target object.

4. The method according to claim 1, characterized in that, The method further includes: During the verification process for the target transaction object, the verification progress is displayed on the login terminal of the target object; If the target transaction object is verified, the payment progress for the target transaction object will be displayed on the target object's login terminal.

5. The method according to claim 1, characterized in that, The display of the transaction processing result of the virtual object includes: If the virtual object exits the dialog interface while performing transaction processing according to the transaction intent, a transaction processing notification is displayed on the login terminal. In response to an interactive action triggered by the transaction processing notification, the transaction processing result of the virtual object is displayed.

6. The method according to claim 1, characterized in that, The method further includes: In response to a request to view details of the transaction processing result, the transaction processing details for the transaction processing result are displayed.

7. The method according to claim 1, characterized in that, The step of executing transaction processing according to the stated transaction intent includes: Generate an intent verification credential according to the transaction intent content, and determine the target transaction object that conforms to the transaction intent content based on the intent verification credential; The target transaction object is verified, and if the verification result indicates that the verification is successful, a transaction verification certificate is generated based on the intent verification certificate. Select a target payment method that matches the target object, generate a target payment token that matches the target payment method, and generate a payment verification credential based on the transaction verification credential. The target payment token and the payment verification credential are authorized and verified, and the transaction processing result of the virtual object is determined based on the obtained authorization and verification result.

8. The method according to claim 7, characterized in that, Determining the transaction processing result of the virtual object based on the obtained authorization verification result includes: If the authorization verification result indicates that the authorization verification has failed, the transaction processing of the virtual object is terminated, and the transaction processing result of the virtual object is determined to be a transaction failure. If the authorization verification result indicates that the authorization verification is successful, the payment is made to the object resources matched with the target transaction object according to the target payment method, and the transaction processing result of the virtual object is determined to be a successful transaction.

9. The method according to claim 7, characterized in that, The virtual object's understanding of the transaction intent content includes entity parameters matching the intent entity; The method further includes: Create an intent authorization data structure based on the entity parameters matched for each intent entity; The step of generating intent verification credentials according to the transaction intent content includes: Obtain operation information for the confirmation operation of the transaction authorization information, and embed the operation information into the intent authorization data structure to obtain the intent verification credential.

10. The method according to claim 9, characterized in that, The response to the target object inputting transaction intent content in the dialog interface, displaying the virtual object's understanding result of the transaction intent content, includes: In response to the target object inputting transaction intent content in the dialog interface, semantic analysis is performed on the transaction intent content to identify multiple intent entities in the transaction intent content, as well as the entity parameters matched by each intent entity; Displays the entity parameters that match each stated intent entity.

11. The method according to claim 7, characterized in that, The step of determining the target transaction object that matches the transaction intent based on the intent verification certificate includes: Obtain the transaction intent content that matches the intent verification credential; The target transaction object that matches the transaction intent content is obtained by performing an object search based on multiple entity parameters in the transaction intent content.

12. The method according to claim 11, characterized in that, An object search is performed based on multiple entity parameters in the transaction intent content to obtain target transaction objects that match the transaction intent content, including: A search is performed based on multiple entity parameters in the transaction intent content to obtain multiple candidate transaction objects; For each candidate transaction object, a comprehensive score is obtained through object analysis across multiple transaction dimensions. The candidate transaction object with the highest comprehensive score is selected as the target transaction object that matches the stated transaction intent.

13. The method according to claim 7, characterized in that, The method further includes: After generating the intent verification credential, determine the first hash value of the intent verification credential; The step of verifying the target transaction object and generating a transaction verification certificate based on the intent verification certificate when the verification result indicates that the verification is successful includes: The target transaction object and the intent verification credential are matched for consistency. If the consistency matching result indicates that the consistency matching is successful, a transaction signature is requested from the merchant to which the target transaction object belongs. Upon receiving the transaction signature from the merchant to which the target transaction object belongs, the first hash value of the intent verification credential is obtained, and a transaction verification credential is generated based on the first hash value.

14. The method according to claim 7, characterized in that, The method further includes: After generating the transaction verification credential, determine the second hash value of the transaction verification credential; The step of generating a payment verification certificate based on the transaction verification certificate includes: Obtain the second hash value of the transaction verification credential, and generate a payment verification credential based on the second hash value.

15. A transaction processing apparatus, characterized in that, The device includes: The dialog interface display module is used to display the dialog interface with the virtual object on the login terminal of the target object; The information display module is used to respond to the target object inputting transaction intent content in the dialog interface, display the virtual object's understanding result of the transaction intent content, and display transaction authorization information for the transaction intent content; The transaction processing module is used to have the virtual object perform transaction processing according to the transaction intent content when the target object confirms the intent understanding result and triggers a confirmation operation for the transaction authorization information; The transaction processing result display module is used to display the transaction processing result of the virtual object.

16. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 14.

17. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 14.

18. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method described in any one of claims 1 to 14.

Images