Method, apparatus, device, storage medium and computer program product for resource transfer processing

Abstract

This application relates to a method, apparatus, device, storage medium, and computer program product for resource transfer processing. The method includes: in response to a first object scanning a second object's resource receiving code through a first resource platform, and upon identification of the resource receiving code as an aggregation code by a cross-resource management platform, displaying a resource transfer page provided by the cross-resource management platform on the application interface of the first resource platform; displaying the identification information of the second object and the amount of the target resource input by the first object on the resource transfer page; and in response to the first object's confirmation operation for the input target resource, displaying the resource transfer result of transferring the target resource to the aggregation management platform that provided the aggregation code through the cross-resource management platform. This method avoids the resource waste of platform modifications required for cross-resource type transfers and ensures the reliability of cross-resource type resource transfer processing.

Description

Technical Field

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

[0002] With the rapid development of cross-border tourism and trade, the demand for overseas users to make payments within China using overseas e-wallets is increasing. However, overseas e-wallets need to connect with domestic payment platforms to enable cross-border payment functionality. Currently, this typically involves payment integration via QR code aggregation. This means that after the overseas e-wallet user scans the QR code of a domestic merchant, for indirect payment platforms that have undergone adaptation, the indirect platform's electronic QR code can also be recognized. The overseas e-wallet application then displays the information on its payment page. After the overseas e-wallet user confirms the payment, the overseas e-wallet's backend server connects with the indirect platform via an Application Programming Interface (API) to complete the transaction.

[0003] However, for cross-border wallets to recognize and complete payments, the intermediary institution must adapt its API. In cross-border payment scenarios, adapting aggregated codes requires significant resources, while cross-border payments cannot be completed without API adaptation. Therefore, how to reduce resource waste and ensure payment reliability in cross-border payment scenarios is an urgent problem to be solved. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, equipment, storage medium, and computer program product for resource transfer processing that reduces resource waste and ensures payment reliability in cross-border payment scenarios, addressing the aforementioned technical problems.

[0005] Firstly, this application provides a method for resource transfer processing. The method includes:

[0006] In response to the first object scanning the resource receiving code of the second object through the first resource platform, if the resource receiving code is identified as an aggregation code through the cross-resource management platform, the resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform; the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform.

[0007] On the resource transfer page, the identification information of the second object and the amount of the target resource entered by the first object are displayed. The resource type of the target resource is the same as the resource type of the second resource platform.

[0008] In response to the first object's confirmation operation for the input target resource, the resource transfer result is displayed, showing the transfer of the target resource to the aggregation management platform that provides the aggregation code across resource management platforms.

[0009] Secondly, this application provides another method for resource transfer processing. The method includes:

[0010] Receive the identification request initiated by the first object through scanning the resource receiving code on the first resource platform, and identify the category to which the resource receiving code belongs;

[0011] When the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform can display the resource transfer page in the application interface; the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform.

[0012] Based on the resource transfer confirmation event initiated by the first object, the target resource is transferred from the first resource platform to the aggregation management platform that provides the aggregation code, according to the amount of target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0013] Thirdly, this application also provides a resource transfer processing apparatus. The apparatus includes:

[0014] The page display module is used to respond to the first object scanning the resource receiving code of the second object through the first resource platform. If the resource receiving code is identified as an aggregation code by the cross-resource management platform, the resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform. The resource type of the second resource platform to which the aggregation code is bound is different from that of the first resource platform.

[0015] The page display module is also used to display the identification information of the second object and the amount of the target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0016] The results display module is used to respond to the first object's transfer confirmation operation for the input target resource and display the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through cross-resource management platforms.

[0017] Fourthly, this application also provides another resource transfer processing apparatus. The apparatus includes:

[0018] The request processing module is used to receive the identification request initiated by the first object through scanning the resource receiving code on the first resource platform, and to identify the category to which the resource receiving code belongs;

[0019] The page rendering module is used to send the rendering parameters of the resource transfer page to the first resource platform when the resource receiving code belongs to the category of aggregation code, so that the first resource platform can display the resource transfer page in the application interface; the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform.

[0020] The resource transfer processing module is used to transfer the target resource from the first resource platform to the aggregation management platform that provides the aggregation code, based on the resource transfer confirmation event initiated by the first object and according to the amount of the target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0021] Fifthly, 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:

[0022] In response to the first object scanning the resource receiving code of the second object through the first resource platform, if the resource receiving code is identified as an aggregation code through the cross-resource management platform, the resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform; the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform.

[0023] On the resource transfer page, the identification information of the second object and the amount of the target resource entered by the first object are displayed. The resource type of the target resource is the same as the resource type of the second resource platform.

[0024] In response to the first object's confirmation operation for the input target resource, the resource transfer result is displayed, showing the transfer of the target resource to the aggregation management platform that provides the aggregation code across resource management platforms.

[0025] Sixthly, 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:

[0026] Receive the identification request initiated by the first object through scanning the resource receiving code on the first resource platform, and identify the category to which the resource receiving code belongs;

[0027] When the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform can display the resource transfer page in the application interface; the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform.

[0028] Based on the resource transfer confirmation event initiated by the first object, the target resource is transferred from the first resource platform to the aggregation management platform that provides the aggregation code, according to the amount of target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0029] Seventhly, 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:

[0030] In response to the first object scanning the resource receiving code of the second object through the first resource platform, if the resource receiving code is identified as an aggregation code through the cross-resource management platform, the resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform; the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform.

[0031] On the resource transfer page, the identification information of the second object and the amount of the target resource entered by the first object are displayed. The resource type of the target resource is the same as the resource type of the second resource platform.

[0032] In response to the first object's confirmation operation for the input target resource, the resource transfer result is displayed, showing the transfer of the target resource to the aggregation management platform that provides the aggregation code across resource management platforms.

[0033] Eighthly, 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:

[0034] Receive the identification request initiated by the first object through scanning the resource receiving code on the first resource platform, and identify the category to which the resource receiving code belongs;

[0035] When the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform can display the resource transfer page in the application interface; the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform.

[0036] Based on the resource transfer confirmation event initiated by the first object, the target resource is transferred from the first resource platform to the aggregation management platform that provides the aggregation code, according to the amount of target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0037] Ninthly, 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:

[0038] In response to the first object scanning the resource receiving code of the second object through the first resource platform, if the resource receiving code is identified as an aggregation code through the cross-resource management platform, the resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform; the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform.

[0039] On the resource transfer page, the identification information of the second object and the amount of the target resource entered by the first object are displayed. The resource type of the target resource is the same as the resource type of the second resource platform.

[0040] In response to the first object's confirmation operation for the input target resource, the resource transfer result is displayed, showing the transfer of the target resource to the aggregation management platform that provides the aggregation code across resource management platforms.

[0041] Tenthly, 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:

[0042] Receive the identification request initiated by the first object through scanning the resource receiving code on the first resource platform, and identify the category to which the resource receiving code belongs;

[0043] When the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform can display the resource transfer page in the application interface; the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform.

[0044] Based on the resource transfer confirmation event initiated by the first object, the target resource is transferred from the first resource platform to the aggregation management platform that provides the aggregation code, according to the amount of target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0045] The aforementioned resource transfer processing method, apparatus, computer equipment, storage medium, and computer program product, after the first object scans the resource receiving code of the second object through the first resource platform, performs type identification of the resource receiving code through a cross-resource management platform. If the resource receiving code is an aggregation code, a resource transfer page is loaded and displayed on the application interface of the first resource platform. At this time, the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform, meaning there is a cross-resource type resource transfer. The first object needs to perform a transfer confirmation operation. In this case, the cross-resource management platform can directly transfer the target resource to the aggregation management platform that provides the aggregation code, without requiring platform adaptation modifications to the aggregation management platform. Instead, it uses the aggregation payment capability of the aggregation code provided by the aggregation management platform to transfer the received target resource to the second object's resource account on the second resource platform, completing the cross-resource type resource transfer processing. Therefore, in scenarios involving cross-resource type resource transfers, the resource waste of platform modifications for cross-resource type transfers is avoided, and the reliability of cross-resource type resource transfer processing is guaranteed. Attached Figure Description

[0046] 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.

[0047] Figure 1 This is an application environment diagram of a resource transfer processing method in one embodiment;

[0048] Figure 2 This is a schematic diagram of the overall process of cross-resource transfer processing in one embodiment;

[0049] Figure 3 This is a flowchart illustrating a method for resource transfer processing in one embodiment;

[0050] Figure 4 This is a schematic diagram illustrating the scanning of the resource receiving code of a second object in one embodiment;

[0051] Figure 5 This is an interactive flowchart for identifying the category to which a resource receiving code belongs in one embodiment;

[0052] Figure 6 This is a schematic diagram of a resource transfer page in one embodiment;

[0053] Figure 7This is an example of an interactive flowchart showing the resource transfer page displayed on the application interface of the first resource platform.

[0054] Figure 8 This is a schematic diagram of a page displaying identification information and an amount input area on a resource transfer page, as shown in one embodiment.

[0055] Figure 9 This is a schematic diagram of a page displaying identification information and the target resource on a resource transfer page, as shown in one embodiment.

[0056] Figure 10 This is a schematic diagram of a page displaying the conversion amount on a resource transfer page in one embodiment;

[0057] Figure 11 This is a schematic diagram of a page showing the resource transfer result of the target resource in one embodiment;

[0058] Figure 12 This is a schematic diagram of the interactive process for displaying the resource transfer result of the target resource in one embodiment;

[0059] Figure 13 This is a schematic diagram of a page that displays the amount of the target resource and platform information on a resource confirmation page in one embodiment.

[0060] Figure 14 This is a schematic diagram of a page in one embodiment where a transfer confirmation operation is triggered on the resource confirmation page to display the resource transfer result of the target resource;

[0061] Figure 15 This is a schematic diagram of the interaction process for calling the resource management service of the first resource platform in one embodiment;

[0062] Figure 16 This is a schematic diagram of the interaction process of launching the resource management service after domain name verification in one embodiment;

[0063] Figure 17 This is a schematic diagram of a page displaying the amount of available resources and the amount of conversion on a transfer confirmation page, as shown in one embodiment.

[0064] Figure 18 This is a flowchart illustrating a resource transfer processing method in another embodiment;

[0065] Figure 19 This is a schematic diagram illustrating the division of platform information in one embodiment;

[0066] Figure 20 This is a schematic diagram illustrating information segmentation and matching in one embodiment;

[0067] Figure 21This is a schematic diagram illustrating the process of parsing information to complete page rendering in one embodiment;

[0068] Figure 22 This is a schematic diagram of the complete process of resource transfer in one embodiment;

[0069] Figure 23 This is a complete flowchart of a resource transfer processing method in one embodiment;

[0070] Figure 24 This is a structural block diagram of a resource transfer processing device in one embodiment;

[0071] Figure 25 This is a structural block diagram of the resource transfer processing apparatus in another embodiment;

[0072] Figure 26 This is an internal structural diagram of a computer device in one embodiment;

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

[0074] 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.

[0075] With the rapid development of cross-border tourism and trade, the demand for overseas users to make payments within China using overseas e-wallets is increasing. However, overseas e-wallets need to connect with domestic payment platforms to enable cross-border payment functionality. Currently, the connection between cross-border wallets and domestic payment platforms mainly adopts a server-side integration model. Because the payment methods supported by cross-border wallets differ from those in China, and because aggregated payment codes are unified collection codes provided by intermediary institutions and can support multiple payment methods simultaneously, payment integration typically requires using aggregated payment codes. This means that after the user of the overseas e-wallet scans the aggregated payment code of a domestic merchant, for intermediary institutions that have completed the adaptation, the intermediary institution's electronic QR code can also be recognized by the cross-border acquiring platform. At this point, the overseas e-wallet application will display the domestic merchant's information and amount input interface on the overseas e-wallet's payment page. After the user of the overseas e-wallet confirms the payment, the overseas e-wallet's backend server completes the transaction by connecting with the intermediary institution through an Application Programming Interface (API).

[0076] However, the backend model requires indirect payment institutions to undergo API-level adaptation to be recognized by cross-border wallets and complete payments. Furthermore, since these indirect institutions are independent third-party acquiring institutions, adaptation for them also requires development resources. Therefore, in cross-border payment scenarios, adapting aggregated codes consumes significant resources, and cross-border payments cannot be completed without adaptation. Moreover, because the aggregated codes of indirect institutions are already connected to the domestic payment platform's acceptance network, cross-border wallets that haven't undergone adaptation cannot recognize them, resulting in the underutilization of the existing acceptance network's payment capabilities and wasted resources. Therefore, how to reduce resource waste and ensure payment reliability in cross-border payment scenarios is an urgent problem to be solved.

[0077] This application provides a resource transfer method that avoids resource waste caused by platform modifications during cross-resource type transfers and ensures the reliability of cross-resource type resource transfer processing in such scenarios. The resource transfer 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.

[0078] Specifically, taking terminal 102 as an example, in response to the first object scanning the resource receiving code of the second object through the first resource platform, and upon recognizing the resource receiving code as an aggregation code through the cross-resource management platform, terminal 102 displays a resource transfer page provided by the cross-resource management platform on the application interface of the first resource platform. Then, on the resource transfer page, terminal 102 displays the identification information of the second object and the amount of the target resource entered by the first object. In response to the first object's confirmation operation for the input target resource, it displays the resource transfer result of transferring the target resource to the aggregation management platform that provided the aggregation code through the cross-resource management platform. At this time, the first object is unaware of the background processing flow of the cross-resource management platform, while the cross-resource management platform directly transfers the target resource to the aggregation management platform that provided the aggregation code. It directly uses the aggregation payment capability of the aggregation code provided by the aggregation management platform to transfer the received target resource to the second object's resource account on the second resource platform, completing the cross-resource type resource transfer process. This eliminates the need for platform adaptation and modification of the aggregation management platform, avoiding the waste of resources associated with platform modifications for cross-resource type transfers and ensuring the reliability of cross-resource type resource transfer processing.

[0079] Secondly, taking server 104 as an example, server 104 receives an identification request initiated by the first object through scanning the resource receiving code on the first resource platform, identifies the category to which the resource receiving code belongs, and if the category to which the resource receiving code belongs is an aggregation code, it feeds back the rendering parameters of the resource transfer page to the first resource platform so that the first resource platform displays the resource transfer page in the application interface. At this time, the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform, that is, it is a scenario of cross-resource type resource transfer processing. Then, based on the resource transfer confirmation event initiated by the first object, server 104 transfers the target resource from the first resource platform to the aggregation management platform that provides the aggregation code, according to the amount of target resource entered by the first object on the resource transfer page, so that the aggregation management platform transfers the target resource to the resource account of the second object to which the resource receiving code belongs on the second resource platform. Since cross-resource management platforms can directly transfer target resources to the aggregation management platform that provides aggregation codes, there is no need to adapt or modify the aggregation management platform. Instead, the target resources received are transferred to the resource account of the second object on the second resource platform through the aggregation payment capability of the aggregation code provided by the aggregation management platform, thus completing the cross-resource type resource transfer process. Therefore, in the scenario of cross-resource type resource transfer, the resource waste of platform modification for cross-resource type transfer is avoided, and the reliability of cross-resource type resource transfer processing is guaranteed.

[0080] 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. In this embodiment, the terminal 102 must support payment functionality, meaning it must be able to support both domestic and cross-border payment processing. 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 resource transfer processing method provided in this embodiment can be applied to various scenarios, including but not limited to offline merchant payment processing and online transaction payment processing, where cross-border payments are required.

[0081] The following will introduce the relevant technical concepts involved in the resource transfer processing method in the embodiments of this application:

[0082] Cross-border wallets: Cross-border wallets mainly refer to e-wallet applications (apps) used by overseas entities, such as ZaloPay and ShopeePay used by entities in Southeast Asia, and PayPal used by entities in Europe and America. Overseas entities can use cross-border wallets to make QR code payments at domestic merchants. In this application, when the currency used by the e-wallet application for payment differs from the currency supported by the merchant, the e-wallet application for payment is the cross-border wallet, and the merchant is the domestic merchant. Therefore, to ensure the reliability of data transmission and request response, the cross-border wallet needs to interact with a cross-border acquiring platform, which then connects to the domestic acquiring network to complete the communication connection and complete the cross-border payment transaction, i.e., complete the cross-resource type resource transfer processing required by this application. The cross-border acquiring platform in this application is a cross-resource management platform.

[0083] Indirect Connecting Institution: An indirect connecting institution refers to an acquiring institution that connects to a payment platform through an indirect connection, also known as an aggregated payment service provider. Therefore, in this application, the indirect connecting institution specifically refers to an aggregated management platform. Indirect connecting institutions must hold a payment business license or be registered as an acquiring outsourcing service provider. At this time, the indirect connecting institution provides a unified QR code that supports multiple payment methods simultaneously, and a service relationship exists between the indirect connecting institution and the payment platform. That is, the indirect connecting institution and the payment platform do not have a direct contractual relationship; the relationship between the indirect connecting institution and the payment platform is: Merchant ↔ Indirect Connecting Institution ↔ Payment Platform. In this application, considering the scenario of cross-border payments, the resource platform to which the payment recipient belongs and the resource platform to which the merchant belongs cannot communicate directly. Therefore, it is necessary to communicate through an indirect connecting institution with the resource platform to which the payment recipient belongs, that is, to communicate between the indirect connecting institution and the resource platform to which the merchant belongs, thereby completing the resource transfer processing across resource types.

[0084] Aggregated QR codes: Aggregated QR codes refer to unified payment codes provided by intermediary institutions, where a single code can support different payment methods simultaneously. These codes are often accompanied by independent payment H5 pages or payment mini-program pages, which display merchant information and provide the payment recipient with the function of entering the payment amount. In this application, different intermediary institutions provide different aggregated QR codes; that is, different aggregation management platforms provide different aggregated QR codes. For example, aggregation management platform A1 provides aggregated QR code B1, aggregation management platform A2 provides aggregated QR code B2, and aggregation management platform A3 provides aggregated QR code B3. If the payment recipient scans aggregated QR code B1, the page provided by aggregation management platform A1 will be displayed, and the amount paid by the payment recipient through an overseas wallet will be transferred through aggregation management platform A1 to the resource account under the merchant's payment platform.

[0085] Direct Connect Code: A direct connect code is a payment code generated after a merchant signs a contract directly with the payment platform. Therefore, the merchant can directly interact with the payment platform for fund and information flow without going through a third-party acquiring institution. In this case, the contractual relationship between the merchant and the payment platform is: Merchant ↔ Payment Platform.

[0086] Backend Mode (Server-Side Integration Mode): Backend mode is a payment interaction mode where the wallet app uses its own payment page as the user interface. After the user confirms the payment through the interface provided by the wallet app, the wallet app's backend server directly calls the acquiring institution's backend server via API to make the deduction request, without redirecting to an external webpage. In other words, in backend mode, the order is created by the wallet institution.

[0087] Foreground Mode (Page Redirect Mode): Foreground mode is another payment interaction mode. The wallet app does not provide a native payment page. The wallet app needs to access the page through a Uniform Resource Locator (URL) generated and provided by the acquiring institution and complete the payment interaction within the page. In foreground mode, the order is created by the acquiring institution, and the wallet institution passively responds to the deduction instruction. The resource transfer processing method provided in this application embodiment is specifically applied to the foreground mode, that is, the payment page displayed in the application interface of the wallet app, which is specifically provided by the cross-resource management platform.

[0088] JavaScript Bridge: A JavaScript Bridge is a communication mechanism between a web page and a native app. Through a JavaScript Bridge, an H5 page running in the embedded browser of a wallet app can call the wallet app's native capabilities, achieving cross-domain communication and capability invocation. Since the resource transfer processing method provided in this application is specifically applied to the foreground mode, and payment needs to be performed on a payment page not provided by the wallet app, a JavaScript Bridge is needed to call the wallet app's native capabilities to ensure that the payment object can complete the payment.

[0089] Unified Payment Page: The unified payment page is a standardized H5 payment page provided by the cross-resource management platform in this application. Specifically, the unified payment page runs within the embedded browser of the overseas wallet app. Therefore, the unified payment page is responsible for parsing merchant information of indirect institutions and displaying the payment interface based on the unified payment page. It receives user input amounts through the unified payment page and interacts with the wallet app via JS Bridge, thereby ensuring that the payment recipient can complete the payment. The unified payment page in this application is specifically a pre-defined page.

[0090] Prepayment Transaction Session Identifier (prepay_id): The prepay_id is a unique transaction identifier returned by the payment platform in this application after the merchant places an order. It is used to subsequently launch the cross-border wallet to complete the deduction. In front-end mode, the prepay_id is generated after the order is placed on the indirect institution's page and passed to the wallet APP for order association.

[0091] Transaction encapsulation: Transaction encapsulation is used to standardize cross-border transactions initiated by overseas wallets. This includes user identity mapping (such as generating an Openid), platform parameter completion, signature verification, and security checks. Transaction encapsulation enables cross-border transactions to conform to the standard transaction format of domestic payment platforms, allowing processing to be completed through existing acceptance networks that require no modification. In this application, user identity mapping is specifically used to generate an Openid (i.e., the target object identifier of the payment object), while platform parameter completion includes, but is not limited to, scenario parameter completion, transaction parameter completion, and order number completion.

[0092] Trusted Domain List: The trusted domain list is a whitelist of domains pre-configured and distributed to the wallet app on the cross-resource management platform in this application. The trusted domain list is specifically used for security verification. That is, when the wallet app loads a page or initiates a network request, it can perform domain verification based on the trusted domain list to ensure that only pages from domains on the trusted domain list are displayed, and only requests from domains on the trusted domain list are processed, thereby preventing malicious attacks.

[0093] As described above, this application's resource transfer processing is specifically applied in cross-resource transfer scenarios. This processing involves at least a cross-resource management platform, an aggregated management platform, an overseas wallet app, and a unified payment page working together to complete the cross-resource transfer. The overall methodology is as follows: Figure 2 As shown:

[0094] First, the platform pages and interface request rules of each aggregation management platform are extracted offline across resource management platforms. This involves parsing information from each aggregation management platform to obtain the platform pages and interface request rules. Then, the platform pages and interface request rules of each aggregation management platform are encapsulated to obtain platform rule scripts that match the aggregation management platform. For example, platform rule script 1 matches aggregation management platform 1, platform rule script 2 matches aggregation management platform 2, and platform rule script 3 matches aggregation management platform 3. Next, the code prefix information matching each aggregation management platform is determined, thereby establishing a mapping relationship between the code prefix information and the platform rule scripts, and this mapping relationship is stored. It is understood that in practical applications, artificial intelligence (AI) can also be used to automatically pre-parse the platform information of each aggregation management platform to obtain platform rule scripts that match the aggregation management platform; the method of obtaining the platform rule scripts is not limited here.

[0095] Therefore, when a payee scans a merchant's QR code through an overseas wallet app, it is necessary to obtain the code prefix information that matches each aggregation management platform, and perform information matching on the QR code to determine its category, i.e., distinguishing whether the QR code is a direct connection code or an aggregation code. If the QR code is a direct connection code, the payment page is displayed directly through the overseas wallet app, without needing the page display method provided in the resource transfer processing of this application. Conversely, if the QR code is an aggregation code, the resource transfer processing method provided in this application is further executed.

[0096] In other words, when the QR code is an aggregated code, the unified payment page is first loaded in the overseas wallet app. The overseas wallet app then requests platform rule scripts from the cross-resource management platform. The cross-resource management platform can determine the platform rule scripts that store the mapping relationship between the code prefix information matched with the QR code, based on the aforementioned stored mapping relationship. At this point, it is also necessary to obtain the payment object's identification information and the overseas wallet app's platform information. Then, a target object identifier (i.e., openid) is generated using the payment object's identification information and the overseas wallet app's platform information. Using the target object identifier, both the payment object and the domestic object can participate in the transaction payment process of the aggregated management platform.

[0097] Then, using the obtained platform rule script and target object identifier, the system retrieves merchant information from the aggregation management platform to obtain rendering parameters for the payment page. These parameters are then fed back to the overseas wallet app, enabling it to load and display the rendered payment page in the unified payment page. The payment recipient can enter the desired transaction amount on the payment page. After confirming the amount, the system interacts with the cross-resource management platform to initiate a pre-order request for the entered amount to the domestic acquiring network. At this point, the aggregation management platform obtains a pre-order transaction identifier (prepay_id) matching the pre-order request and associates it with order information. Therefore, the overseas wallet app then interacts with the cross-resource management platform to initiate an information request carrying the pre-order transaction identifier to obtain the pre-order order information from the domestic acquiring network. Once the overseas wallet app obtains the order information based on the pre-order transaction identifier, it can launch the native cashier of the overseas wallet app through JS Bridge. After the payee completes the payment of the amount in the order information, it interacts with the cross-resource management platform to notify the domestic acquiring network to complete the payment. At this time, the domestic acquiring network needs to notify the aggregation management platform that it has received the required transaction amount so that the aggregation management platform can transfer the paid amount to the merchant's transaction account, thereby completing the cross-border transaction supported in this application embodiment.

[0098] The following examples illustrate in detail how to perform resource transfer processing in cross-resource transfer scenarios: In one exemplary embodiment, as shown... Figure 3 As shown, a method for resource transfer processing 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 is implemented through the interaction between terminal 102 and server 104. In this application, terminal 102 specifically refers to the terminal used by the first object. In this embodiment, the method includes steps 302 to 306, wherein:

[0099] Step 302: In response to the first object scanning the resource receiving code of the second object through the first resource platform, if the resource receiving code is identified as an aggregation code through the cross-resource management platform, the resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform; the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform.

[0100] Here, the first object is the payment object using the first resource platform, and the first resource platform is the payment platform used by the first object. Taking the above introduction as an example, the first resource platform can be a cross-border wallet, in which case the first object is an overseas payment object, and the first resource platform is specifically the e-wallet APP used by the overseas payment object. For example, if the first object is a payment object belonging to region C1, the first resource platform can be the first resource platform D1, or if the first object is a payment object belonging to region C2, the first resource platform is D2.

[0101] Secondly, the second object is the merchant providing the service, and in this embodiment, the second object and the first object belong to different regions. That is, if the first object is an overseas payment object, the second object is a domestic merchant. Therefore, the first object can scan the QR code provided by the second object to make payment through the first resource platform. Furthermore, the services provided by the second object can be online or offline. Specifically, the second object can be an online merchant providing online services, such as online virtual services or online goods services based on online transactions. Alternatively, the second object can also be an online merchant providing offline services, such as offline physical services or offline goods services based on offline transactions. The resource receiving code of the second object is specifically its QR code, and this code cannot be directly generated by the second object; instead, it needs to be provided by the resource management platform based on the second object's application request. Specifically, if the resource receiving code is a direct connection code, it is provided by the direct connection management platform; if it is an aggregated code, it is provided by the aggregated management platform.

[0102] Based on this, when the resource receiving code is an aggregation code, the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform, taking into account the different currency types used in different regions. Therefore, the aggregation code in this application is a QR code provided by a domestic aggregation management platform. For example, if the first object is a payment object belonging to region C1, and the resource type used in region C1 is resource type E1, then the first resource platform D1 matches resource type E1. In this case, the aggregation management platform must not belong to region 1, and the resource type of the second resource platform bound to the aggregation code provided by the aggregation management platform is not resource type E1. That is, the resource type of the second platform can be resource type E2, resource type E3, or other types that are not resource type E1.

[0103] Specifically, when resource transfer is required between the first object and the second object, the resource receiving code of the second object is first determined. Then, the first object uses the first resource platform installed on its terminal to perform a scanning trigger operation. This involves scanning the resource receiving code of the second object through the scanning area displayed on the application interface of the first resource platform, so that the first object's terminal responds to the obtained resource receiving code. For ease of understanding, as follows... Figure 4 As shown, a scanning area 404 is displayed in the application interface 402 of the first resource platform. By scanning the resource receiving code 406 of the second object in the scanning area 404, the object terminal of the first object can respond to the resource receiving code obtained by scanning.

[0104] Based on this, after the first object's terminal receives the obtained resource receiving code through scanning, it can also generate an identification request based on the resource receiving code and send the identification request carrying the resource receiving code to the cross-resource management platform. This allows the cross-resource management platform to identify the resource receiving code in response to the identification request, determining its category. The category of the resource receiving code can be either an aggregation code or a direct connection code. After determining the category of the resource receiving code, the cross-resource management platform feeds back the category to the first object's terminal, at which point the first object's terminal obtains the category of the resource receiving code. For ease of understanding, as follows... Figure 5 As shown, the first object scans the resource receiving code of the second object through the first resource platform, enabling the first resource platform to send an identification request carrying the resource receiving code to the cross-resource management platform. The cross-resource management platform identifies the category to which the resource receiving code belongs and returns the category to the first resource platform. It is understandable that, in practical applications, the cross-resource management platform can also return the foreground mode and the page access address of the preset page to the first resource platform when the resource receiving code is an aggregate code.

[0105] Based on this, the target terminal of the first object determines whether the resource receiving code is an aggregated code or a direct connection code based on the category to which the resource receiving code belongs. If the category indicates that the resource receiving code is a direct connection code, a background mode is triggered. As described above, in background mode, the wallet app can use its own payment page as the interface for user interaction. Therefore, the application interface of the first resource platform displays the resource transfer page provided by the first resource platform. This means that processing is not required through the page display method provided in the resource transfer processing of this application, and the resource transfer process is controlled by the first resource platform. Conversely, if the category indicates that the resource receiving code is an aggregated code, a foreground mode is triggered. As described above, in foreground mode, the wallet app does not provide a native payment page but needs to provide a payment page through a cross-resource management platform for user interaction. Therefore, if the resource receiving code is an aggregated code, the application interface of the first resource platform will display the resource transfer page provided by the cross-resource management platform.

[0106] Therefore, it can be seen that the cross-resource management platform specifically searches for the page rule script that matches the resource receiving code according to its category, determines the rendering parameters of the resource transfer page based on the page rule script, and then feeds back the rendering parameters of the resource transfer page to the first resource platform. At this time, the first resource platform will display the resource transfer page obtained by rendering the preset page according to the rendering parameters in the application interface. Figure 6 The resource transfer page shown, when the resource receiving code is an aggregation code, displays the resource transfer page 604 provided by the first resource platform on the application interface 602 of the first resource platform.

[0107] In practical applications, displaying payment pages from other platforms on the application interface of the first resource platform requires a unified payment page. This unified payment page, specifically a preset page, runs within the embedded browser of the first resource platform. Therefore, when the resource receiving code is an aggregation code, the cross-resource management platform can also send back the foreground mode and the page access address of the preset page to the first resource platform. This allows the first resource platform to request the preset page according to the page access address, enabling the preset page to render the required resource transfer page using rendering parameters. For ease of understanding, based on... Figure 5 The interaction flowchart shown will be further explained, especially when the resource receiving code is an aggregate code, such as... Figure 7As shown, when the rendering parameters of the resource transfer page are fed back to the first resource platform through the cross-resource management platform, the page access address of the foreground mode and the preset page can also be fed back to the first resource platform. The first resource platform directly determines to trigger the foreground mode and loads the preset page according to the page access address. Thus, the resource transfer page is obtained by rendering the page on the preset page through the rendering parameters and displayed on the application interface of the first resource platform.

[0108] Understandably, the distinction between front-end and back-end modes can also be achieved through a transaction scenario recognition mechanism. This involves identifying the information format of the resource transfer information to determine whether the transfer is in front-end or back-end mode. Specifically, the first resource platform can receive the resource receiving code's category and the resource transfer information, identify the information format, and determine whether front-end or back-end mode is triggered. If the first resource platform triggers front-end mode, a preset page is loaded according to the page access address. Then, the resource transfer page is rendered on the preset page using rendering parameters and displayed on the first resource platform's application interface.

[0109] Step 304: On the resource transfer page, display the identification information of the second object and the amount of the target resource entered by the first object. The resource type of the target resource is the same as the resource type of the second resource platform.

[0110] The identification information of the second object includes at least its object name; that is, if the second object is a merchant, its object name is the merchant's name. In practical applications, the identification information of the second object may also include a unique object identifier, platform information of the second resource platform, and other information related to the second object; this is not limited here. The amount of the target resource entered by the first object is specifically obtained by the first object entering it in the amount input area displayed on the resource transfer page. Furthermore, if the resource type of the target resource entered by the first object is the same as the resource type of the second resource platform, then the resource type of the target resource entered by the first object is different from the resource type of the first resource platform. For example, if the first resource platform D1 matches resource type E1, and the second resource platform matches resource type E2, then the displayed resource type of the target resource entered by the first object is resource type E2.

[0111] Specifically, on the application interface of the first resource platform, in addition to displaying the resource transfer page provided by the cross-resource management platform, the interface also displays the identification information of the second object, as well as an input area for the amount of resources transferred for the second object. This input area can also display the resource type matching the second resource platform. For ease of understanding, as follows... Figure 8 As shown, the resource transfer page 802 displays the identification information 804 of the second object and the amount input area 806. At this time, the amount input area also displays the resource type 808 matching the second resource platform, and the amount input area 806 is used to provide the function of inputting the amount of the required transferred resource. Based on this, the first object needs to perform a resource transfer input operation in the amount input area displayed on the resource transfer page, so that the amount of the target resource input by the first object can be displayed on the resource transfer page. For ease of understanding, based on... Figure 8 The resource transfer page shown will be further described, such as... Figure 9 As shown, the resource transfer page 902 displays the identification information 904 of the second object and the amount input area 906. The first object enters the amount of the target resource to be transferred in the amount input area 906, so that the amount 908 of the target resource can also be displayed on the resource transfer page 902.

[0112] In an exemplary optional embodiment, the resource transfer processing method further includes: displaying the conversion amount corresponding to the target resource under the first resource platform on the resource transfer page. Specifically, since the resource type of the target resource is the same as the resource type of the second resource platform, and the first object uses the resource type of the first resource platform, in order to allow the first object to determine the amount of the target resource to be transferred, the conversion amount corresponding to the target resource under the first resource platform can also be displayed on the resource transfer page. The conversion amount is obtained based on the resource conversion ratio between the resource type of the first resource platform and the resource type of the second resource platform. For example, if the resource conversion ratio between the resource type of the first resource platform and the resource type of the second resource platform is 5:1, and the amount of the target resource is 100, then the conversion amount corresponding to the target resource under the first resource platform is 500. For ease of understanding, as follows... Figure 10 As shown, the amount of the target resource 1004 and the conversion amount 1006 corresponding to the target resource under the first resource platform are displayed on the resource transfer page 1002.

[0113] Step 306: In response to the first object's transfer confirmation operation for the input target resource, display the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through cross-resource management platforms.

[0114] The transfer confirmation operation signifies the completion of the confirmation of the amount of the target resource input by the first object, and the confirmation of transferring the amount of the target resource to the resource account of the second object. Cross-resource management platforms need to transfer the target resource to the aggregation management platform that provides the aggregation code, and the identification information of the second object receiving the target resource is carried during the transfer process. The resource transfer result is then indicated as either "target resource transfer successful" or "target resource transfer failed."

[0115] Therefore, the aggregation management platform can transfer the target resources to the resource account of the second object on the second resource platform based on the identification information of the second object. The aforementioned aggregation management platform is the indirect connection institution described in the preceding embodiments. Since an indirect connection institution refers to an acquiring institution that connects to the payment platform through an indirect connection, the target resources transferred by the first object in the first resource platform need to be transferred to the resource account of the second object on the second resource platform through the aggregation management platform. At this time, the relationship between the aggregation management platform, the first resource platform of the first object, and the second resource platform of the second object is specifically: the second resource platform of the second object ↔ the aggregation management platform ↔ the first resource platform of the first object.

[0116] Specifically, since the resource transfer page can display the identification information of the second object and the amount of the target resource entered by the first object, and the first object confirms that the object receiving the resource is correct based on the identification information of the second object, and the amount of the target resource is correct, a transfer confirmation operation can be triggered for the target resource. This allows the terminal to respond to the transfer confirmation operation triggered by the first object, thereby displaying the resource transfer result—the transfer of the target resource to the aggregation management platform that provides the aggregation code—on the application interface of the first resource platform. For ease of understanding, as follows... Figure 11 As shown, on the application interface 1102 of the first resource platform, the resource transfer result 1104 of the target resource is displayed. At this time, the resource transfer result 1104 indicates that the target resource has been successfully transferred, and the amount 1106 of the successfully transferred target resource can also be displayed in the resource transfer result 1104.

[0117] The result of transferring the target resource is the transfer of the target resource. This transfer requires a transfer confirmation operation and interaction between the first resource platform, the cross-resource management platform, and the aggregation management platform. Specifically, after the terminal responds to the transfer confirmation operation triggered by the first object, the first resource platform generates a resource transfer confirmation event initiated by the first object. The first resource platform then sends this confirmation event back to the cross-resource management platform. This confirmation event includes the identification information of the second object and the amount of the target resource input by the first object. Therefore, the cross-resource management platform, through the resource transfer confirmation event, first identifies the aggregation management platform providing the aggregation code using the identification information of the second object. Then, it initiates a resource transfer request to the aggregation management platform according to the amount of the target resource. The aggregation management platform can extract the identification information of the second object from the resource transfer request and also identify the first object and the first resource platform. In other words, the aggregation management platform needs to obtain the target resource to be transferred from the first resource platform. Finally, the aggregation management platform sends the resource transfer result back to the cross-resource management platform, which then sends the result back to the first resource platform. Therefore, the first resource platform can receive the resource transfer result of the target resource and display the resource transfer result of the target resource on the application interface of the first resource platform.

[0118] For ease of understanding, based on Figure 7 The interactive flowchart of the resource transfer page shown is further explained below, such as... Figure 12 As shown, the first object triggers a transfer confirmation operation on the first resource platform. The first resource platform sends a resource transfer confirmation event generated based on the transfer confirmation operation to the cross resource management platform. The cross resource management platform then initiates a resource transfer request for the target resource to the aggregation management platform, causing the aggregation management platform to request the target resource from the first resource platform. The first resource platform then transfers the resource to the aggregation management platform. Based on the result of the resource transfer processing performed by the first resource platform, the aggregation management platform determines the resource transfer result of the target resource. That is, if the aggregation management platform receives the target resource transferred by the first resource platform, it determines that the target resource transfer is successful. If the aggregation management platform does not receive the target resource transferred by the first resource platform, it determines that the target resource transfer is unsuccessful.

[0119] Based on this, the aggregation management platform feeds back the resource transfer results to the cross-resource management platform, which then feeds back the resource transfer results to the first resource platform. The resource transfer results are then displayed on the application interface of the first resource platform. Furthermore, as described in the foregoing embodiments, the unified payment page in this application is specifically a preset page, meaning the preset page runs within the embedded browser of the first resource platform. Therefore, the display of resource transfer results on the application interface of the first resource platform also needs to be done through the preset page. That is, after receiving the resource transfer results, the first resource platform needs to initiate a JS callback notification to the preset page, and at this time, it also needs to carry the feedback resource transfer results so that the preset page can be rendered using the resource transfer results, thereby obtaining the resource transfer result page for displaying the resource transfer results. This resource transfer result page is then displayed on the application interface of the first resource platform.

[0120] Since the transfer confirmation operation represents the completion of the confirmation of the amount of the target resource input by the first object, and confirms the transfer of the amount of the target resource to the resource account of the second object, the prerequisite for triggering the transfer confirmation operation is that the first object has already confirmed the amount of the target resource input. That is, before the transfer confirmation operation, it is necessary to confirm the amount of the target resource. This is described below: In an exemplary optional embodiment, the resource transfer processing method further includes: in response to the resource confirmation operation triggered by the first object for the target resource on the resource transfer page, displaying a resource confirmation page for the target resource; on the resource confirmation page, displaying the amount of the target resource and the platform information of the second resource platform.

[0121] The resource confirmation operation is used to confirm the amount of the target resource input by the first object. Specifically, as described above, since the identification information of the second object and the amount of the target resource input by the first object can be displayed on the resource transfer page, if the first object correctly determines the object to receive the resource based on the identification information of the second object and the amount of the target resource is correct, a resource confirmation operation is first triggered on the resource transfer page for the determined amount of the target resource. This causes the first resource platform to respond to the resource confirmation operation triggered for the amount of the target resource and display a resource confirmation page for the target resource. Since the resource confirmation operation is a confirmation operation triggered for the target resource, to ensure the accuracy of the determined amount of the target resource, the amount of the target resource can also be displayed on the resource confirmation page. Furthermore, since the specific requirement is to transfer resources to the second object, and the resource types of the resource platforms involved in the resource transfer are not consistent, the platform information of the second resource platform can also be displayed on the resource confirmation page. Because the resource confirmation page is used for displaying the resource amount and platform information, a transfer confirmation control can also be displayed to trigger the required transfer confirmation operation. For ease of understanding, as follows... Figure 13 As shown, on the resource confirmation page 1302, the amount of the target resource 1304 and the platform information of the second resource platform 1306 are displayed, and the transfer confirmation space 1308 is also displayed.

[0122] Based on this, in response to the first object's transfer confirmation operation for the input target resource, the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through cross-resource management platforms is displayed. Specifically, this includes: in response to the transfer confirmation operation triggered by the first object on the resource confirmation page, displaying the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through cross-resource management platforms.

[0123] Specifically, the first object will verify the accuracy of the displayed target resource amount on the resource confirmation page. Once verified, it will trigger a transfer confirmation operation. This will display the resource transfer result—transferring the target resource to the aggregation management platform providing the aggregation code—on the application interface of the first resource platform. As illustrated in the aforementioned embodiment, since the resource confirmation page displays resource amounts and platform information, a transfer confirmation control can also be displayed. This allows the required transfer confirmation operation to be triggered via the control; that is, the first object can trigger the transfer confirmation operation for the target resource by interacting with the transfer confirmation control. For ease of understanding, based on... Figure 11 and Figure 13 Examples are provided, such as Figure 14 As shown, the first object can trigger a transfer confirmation operation for the target resource by interacting with the transfer confirmation control 1404 on the resource confirmation page 1402, so that the resource transfer result 1408 of the target resource is displayed on the application interface 1406 of the first resource platform.

[0124] And after the first object triggers the resource confirmation operation, it is actually necessary for the first resource platform to transfer a determined amount of target resources to the aggregation management platform. The first resource platform specifically handles the resource transfer through the resource management service, which is described in detail below: In an exemplary specific embodiment, in response to the resource confirmation operation triggered by the first object for the input target resource on the resource transfer page, a transfer confirmation page for the target resource is displayed. Specifically, in response to the resource confirmation operation triggered by the first object for the input target resource on the resource transfer page, the resource management service matching the first resource platform is invoked, so that the resource management service responds to the transfer confirmation operation and transfers the target resource to the aggregation management platform.

[0125] The resource management service is used to transfer the target resource to the aggregation management platform in response to the transfer confirmation operation. In practical application, the resource management service is the native payment gateway of the first resource platform. Specifically, if the first object correctly identifies the recipient of the resource based on the second object's identification information, and the amount of the target resource is correct, a resource confirmation operation is triggered for the target resource. This causes the first resource platform to respond to the resource confirmation operation triggered for the target resource by calling the resource management service matched with the first resource platform. Since the page display in this application is all done through a preset page (i.e., the unified payment page), triggering the resource confirmation operation on the page requires communication and interaction with the first resource platform. JS Bridge is a communication mechanism between a web page and a native app. Therefore, in response to the resource confirmation operation triggered for the target resource on the preset page, the resource management service of the first resource platform needs to be called through JS Bridge so that the first resource platform can transfer the target resource to the aggregation management platform through the resource management service. For ease of understanding, as follows... Figure 15 As shown, the first object triggers a resource confirmation operation on the first resource platform. In fact, the resource confirmation operation is triggered on the resource transfer page provided by the preset page. At this time, the preset page needs to call the resource management service of the first resource platform through the JS Bridge so that the first resource platform can start the resource management service and complete the transfer of the target resource through the resource management service.

[0126] Considering the possibility of abnormal resource transfers, and to ensure the security of resource transfers by the first resource platform, domain name verification is required before the first resource platform launches its resource management service. This is to prevent abnormal domain name attacks from reducing the security of resource transfers. The following describes this process: In an exemplary embodiment, in response to a resource confirmation operation triggered by the first object on the resource transfer page for the input target resource, a resource management service matching the first resource platform is invoked. This includes: in response to the resource confirmation operation triggered by the first object on the resource transfer page for the target resource, obtaining the domain name information to be verified matching the resource confirmation operation; verifying the domain name information to be verified using preset accessible domain name information to obtain a domain name verification result; and informing the first resource platform if the domain name verification result indicates that the domain name verification is successful.

[0127] The preset accessible domain name information is the domain name information issued during the routing communication phase. The domain name verification result indicates whether the domain name verification passed or failed. Specifically, when the first object triggers a resource confirmation operation on the resource transfer page for the determined amount of target resources, the first resource platform can obtain the domain name information to be verified that matches the resource confirmation operation, and perform domain name verification on the domain name information to be verified to obtain the domain name verification result. That is, it determines whether the domain name information to be verified is in the preset accessible domain name information. If it is, the domain name verification result indicates that the domain name verification passed. Conversely, if the domain name information to be verified is not in the preset accessible domain name information, then the domain name information to be verified may be abnormal domain name information, and the domain name verification result indicates that the domain name verification failed.

[0128] Therefore, if the domain verification result indicates that the domain verification is successful, the resource management service matching the first resource platform will then be invoked. However, if the domain verification result indicates that the domain verification is unsuccessful, the request to invoke the resource management service will be rejected, thus suspending the transfer of the target resource. For ease of understanding, as follows... Figure 16 As shown, the first object triggers a resource confirmation operation on the resource transfer page of the first resource platform. In fact, the resource confirmation operation is triggered on the resource confirmation page provided by the preset page. At this time, the preset page needs to call the resource management service of the first resource platform through the JS Bridge. That is, the resource management service of the first resource platform is called through the JS Bridge according to the resource confirmation operation request. At this time, the first resource platform will obtain the domain name information to be verified that matches the resource confirmation operation, and perform domain name verification on the domain name information to be verified. If the domain name verification result indicates that the domain name verification is successful, the resource management service will be launched again, and the target resource transfer will be completed through the resource management service.

[0129] In an exemplary optional embodiment, the resource transfer processing method further includes: displaying on the transfer confirmation page the amount of available resources of the first object under the first resource platform, and the corresponding conversion amount of the target resource on the first resource platform. Specifically, since the resource type of the target resource is the same as the resource type of the second resource platform, and the first object uses the resource type of the first resource platform, in order to enable the first object to determine the amount of the target resource to be transferred, the transfer confirmation page can also display the corresponding conversion amount of the target resource on the first resource platform. Furthermore, to ensure that the first object has resources sufficient to pay for the target resource amount, the amount of available resources of the first object under the first resource platform can also be displayed, along with the resource account information of the first object under the first resource platform, so that the first object knows which resource account is used for the resource transfer. For ease of understanding, as... Figure 17As shown, the transfer confirmation page 1702 also displays the available resource amount 1704 of the first object under the first resource platform, the corresponding conversion amount 1706 of the target resource under the first resource platform, and the resource account information 1708 of the first object under the first resource platform.

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

[0131] In the above-described resource transfer processing method, after the first object scans the resource receiving code of the second object through the first resource platform, the resource receiving code is identified by the cross-resource management platform. If the resource receiving code is an aggregation code, the resource transfer page is loaded and displayed on the application interface of the first resource platform. At this time, the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform, which means there is a cross-resource type resource transfer. At this time, the first object needs to perform a transfer confirmation operation. The cross-resource management platform can directly transfer the target resource to the aggregation management platform that provides the aggregation code without the need for platform adaptation and modification of the aggregation management platform. Instead, the received target resource is transferred to the resource account of the second object on the second resource platform through the aggregation payment capability of the aggregation code provided by the aggregation management platform, thus completing the cross-resource type resource transfer processing. Therefore, in the scenario of cross-resource type resource transfer processing, the resource waste of platform modification for cross-resource type transfer is avoided, and the reliability of cross-resource type resource transfer processing is guaranteed.

[0132] The foregoing embodiments describe the page displayed on the terminal of the first object during resource transfer processing. However, resource transfer processing requires information processing and interaction between the terminal and the server to be completed. This will be described in detail below: In an exemplary embodiment, such as... Figure 18 As shown, a method for resource transfer processing is provided, which is applied to... Figure 1 Taking server 104 as an example for illustration, 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 application, server 104 is a cross-resource management platform. In this embodiment, the method includes steps 1802 to 1806, wherein:

[0133] Step 1802: Receive the identification request initiated by the first object through scanning the resource receiving code on the first resource platform, and identify the category to which the resource receiving code belongs.

[0134] In this context, the first object is the payment recipient using the first resource platform, which is the payment platform used by the first object. The resource receiving code is a QR code provided by the second object. The resource receiving code for the second object cannot be directly generated by the second object; instead, it needs to be provided by the resource management platform based on the second object's application request. The identification request is generated by the first object scanning the resource receiving code through the first resource platform. Therefore, the identification request carries the object information of the first object, as well as the resource receiving code obtained from the scan. The resource receiving code belongs to two categories: direct connection codes and aggregation codes. If the second object's resource receiving code is a direct connection code, it is specifically provided by the direct connection management platform; if the second object's resource receiving code is an aggregation code, it is specifically provided by the aggregation management platform.

[0135] Specifically, when resource transfer is required between the first object and the second object, the first object uses the first resource platform installed on its terminal to trigger a scanning operation. This involves scanning the resource receiving code of the second object through the scanning area displayed on the application interface of the first resource platform. The first object's terminal then responds to the obtained resource receiving code. After responding to the obtained resource receiving code, the first object's terminal generates an identification request containing the resource receiving code and sends this request to the cross-resource management platform. The cross-resource management platform receives the identification request, extracts the resource receiving code from it, and performs receiving code category identification to determine the category to which the resource receiving code belongs—that is, whether it is an aggregation code or a direct connection code.

[0136] The following details the specific methods for identifying whether a resource receiving code is an aggregation code or a direct connection code. In an exemplary embodiment, identifying the category to which the resource receiving code belongs includes: obtaining platform information that matches each management platform; matching the resource receiving code with the platform information that matches each management platform to obtain the matching result; and determining the category to which the resource receiving code belongs based on the matching result.

[0137] Each management platform is matched with different platform information. That is, different aggregation management platforms have different platform information, and since different aggregation management platforms provide different aggregation codes, and each aggregation code has code prefix information matching the aggregation management platform, the platform information of the aggregation management platform in this application specifically indicates the code prefix information of the aggregation management platform. For example, aggregation management platform A1 provides aggregation code B1, and aggregation management platform A1 matches code prefix information F1. Code prefix information F1 is the platform information G1 of aggregation management platform A1, and code prefix information F1 can be read by scanning aggregation code B1. Or, aggregation management platform A2 provides aggregation code B2, and aggregation management platform A2 matches code prefix information F2. Code prefix information F2 is the platform information G2 of aggregation management platform A2, and code prefix information F2 can be read by scanning aggregation code B2. It is understandable that in practical applications, due to the existence of aggregation codes and direct connection codes—that is, different direct connection management platforms have different platform information—and because different direct connection management platforms provide different direct connection codes, and each direct connection code has code prefix information matching the direct connection management platform, the platform information of the direct connection management platform in this application specifically indicates the code prefix information of the direct connection management platform. For example, the platform information is https: / / a.com / b / c / d, or the platform information is https: / / e.com / f / g / h / .

[0138] Specifically, the server obtains platform information matching each management platform, that is, the platform information matching each aggregation management platform and the platform information matching each direct-connect management platform. The platform information matching each management platform is pre-generated. Before the aggregation management platform signs a resource transfer agreement with the second object, the platform information matching the aggregation management platform already exists. Therefore, the aggregation code provided by the aggregation management platform to the second object carries the platform information. If the second object has already signed a resource transfer agreement with the direct-connect management platform to which the first object's first resource platform belongs, then the direct-connect code provided by the direct-connect management platform to the second object carries the platform information. Thus, the data storage system can store the platform information matching each aggregation management platform and the platform information matching each direct-connect management platform.

[0139] Based on this, when type identification of the resource receiving code is required, the server can retrieve the platform information matching each aggregation management platform and the platform information matching each direct-connect management platform from the data storage system. Then, the server performs information matching between the resource receiving code and the platform information matching each aggregation management platform and each direct-connect management platform, respectively, to obtain the information matching result. This means the information matching result can indicate that the resource receiving code matches the target platform information of the target aggregation management platform, or that the resource receiving code matches the target platform information of the target direct-connect management platform. Such an information matching result indicates that the code prefix information in the resource receiving code is consistent with the target code prefix information represented by the target platform information. Alternatively, the information matching result can also indicate that the resource receiving code cannot match any platform information, meaning that the code prefix information in the resource receiving code cannot be consistent with the code prefix information represented by any platform information.

[0140] Therefore, the category of the resource receiving code is determined by the information matching results. If the information matching results indicate that the resource receiving code cannot be matched with any platform information, the category of the resource receiving code is empty, meaning that the category of the resource receiving code required for the identification request cannot be fed back. However, if the information matching results indicate that the resource receiving code matches the target platform information, then the category of the resource receiving code can be determined by directly identifying whether the target platform information belongs to a direct connection management platform or an aggregation management platform. In other words, if the target platform information belongs to a direct connection management platform, the resource receiving code belongs to the direct connection code category; if the target platform information belongs to an aggregation management platform, the resource receiving code belongs to the aggregation code category.

[0141] Since the platform information of the management platform is specifically code prefix information, and the code prefix information usually carries multi-dimensional prefix information such as protocol information, domain name information, and at least one path information, the prefix information under the same dimension should be matched sequentially during the information matching process. This is described in detail below: In an exemplary embodiment, the platform information includes multiple platform splitting information. The aforementioned platform splitting information is multi-dimensional prefix information of protocol information, domain name information, and path information. Each platform splitting information is separated by a preset symbol. In this embodiment, the preset symbols " / " and " / " are used to split the platform splitting information. Therefore, information not separated by the preset symbols " / " and " / " is not platform splitting information. For example, if the platform information is https: / / a.com / b / c / d, then the multiple platform splitting information included in the platform information are: protocol information "https", domain name information "a.com", path information "b", and path information "c". That is, since "d" in " / d" is not separated by the preset symbols " / " and " / ", it is not defined as platform splitting information. Alternatively, if the platform information is https: / / e.com / f / g / h / , then the platform information includes multiple platform-specific details: protocol information "https", domain information "e.com", path information "f", path information "g", and path information "h". Compared to the previous example, since the "h" in " / h / " can be separated by the default symbol " / ", it can be defined as platform-specific details.

[0142] It is understandable that in practical applications, platform segmentation information can also include information length, that is, the number of characters included in the platform segmentation information can be described by the information length. Furthermore, the number of path information entries in this application is three; therefore, if the path information in the platform information has fewer than three entries, it will be set to an empty string. For ease of understanding of platform information and platform segmentation information, as follows... Figure 19 As shown, platform information 1901 is specifically https: / / a.12345.com / 00010000 / . At this time, it is separated by the preset symbol " / ". Protocol information 1902 is "https", domain information 1903 is "a.12345.com", and path information 1904 is "00010000". With the number of path information items being 3, path information 1905 and path information 1906 are set to empty strings, and the information length 1907 is 30.

[0143] Based on this, for the platform information matched with each management platform, information matching is performed with the resource receiving code to obtain information matching results. Specifically, this includes: splitting the code information matched with the resource receiving code according to the preset splitting rules to obtain multiple splitting information in sequence; for the multiple platform splitting information matched with the platform information matched with each management platform, information matching is performed on the multiple splitting information from back to front to obtain information matching results.

[0144] The code information matched by the resource receiving code is the code prefix information of the resource receiving code. The preset splitting rule is to split the code information matched by the resource receiving code sequentially according to the information order of protocol information, domain name information, and path information, based on the preset symbol " / ". Specifically, based on the platform information including multiple platform splitting information, the code information matched by the resource receiving code is split according to the preset splitting rule that matches the platform splitting information, resulting in multiple splitting information ordered from front to back. That is, the multiple splitting information ordered from front to back is specifically ordered according to the information order of protocol information, domain name information, and path information. For ease of understanding, let's take the resource receiving code matching the code information https: / / a.12345.com / 00010000 / 01316785607205401163117143534316 as an example. In this case, the split information can be extracted as: protocol information "https", domain information "a.12345.com", and path information "00010000".

[0145] Based on this, for the multiple platform segmentation information that matches the platform information of each management platform, the information matching of the multiple segmentation information is performed sequentially from back to front to obtain the information matching result. That is, the segmentation information is matched with the multiple platform segmentation information of each platform information sequentially from back to front, and the first successfully matched platform information is returned as the information matching result. That is, the first successfully matched platform information is the target platform information described above. If the matching of the segmentation information of the protocol information is not completed before the matching is completed, it means that the information matching result is that the matching cannot be completed. It is understood that in practical applications, there may be code information with only protocol information, or only code information with both protocol information and domain name information. Therefore, when the number of management platforms is large enough and the platform information matched by each management platform is large enough, by splitting the platform information, the number of matches can be reduced and accurate matching can be guaranteed through a more granular matching method. The specific implementation method of the above embodiment is described in detail below:

[0146] First, the code prefix information (i.e., platform information) of each management platform (including direct connection management platform and aggregation management platform) is split into multiple platform split information according to a preset splitting rule. That is, the code prefix information is decomposed into protocol information, domain name information, path information 1, path information 2, path information 3, and information length, which are stored in the database. Path information is specifically divided using preset symbols " / ". If the code prefix information contains fewer than 3 path information entries, the missing path information portion is set to an empty string. Based on this, the code information matched by the resource receiving code of the first object scan is also split into multiple split information according to the preset splitting rule, that is, split into protocol information, domain name information, and path information in sequential order. Considering that the code prefix only contains a portion of the path information split from the code information, matching needs to be performed from back to front. The matching method is described in detail below:

[0147] 1. The first round uses full-splitting matching, which means splitting the code information matched by the resource receiving code into protocol information, domain name information, and three path information (i.e., path information 1, path information 2, and path information 3). Then, according to the protocol information, domain name information, path information 1, path information 2, and path information 3, a full-field match is performed against the multiple platform split information stored in the database that match each management platform, sorted in reverse order starting from path information 3. If a match is successful, the successfully matched platform information is taken as the target platform information. Otherwise, if no match is found, the second round continues.

[0148] 2. The second round is initiated because path information 3 cannot be matched, meaning that path information 3 cannot be found. In the second round, path information 3 is fixed as an empty string, and matching begins from path information 2 (the information preceding path information 3). If a match is found, the successfully matched platform information is used as the target platform information. Otherwise, if no match is found, the third round continues.

[0149] 3. The third round is initiated because path information 2 cannot be matched, meaning that path information 2 cannot be found. In the third round, both path information 2 and path information 3 are fixed as empty strings, and matching begins from path information 1 (i.e., the information preceding path information 1). If a match is found, the successfully matched platform information is used as the target platform information. Otherwise, if no match is found, the fourth round continues.

[0150] 4. The fourth round is initiated because path information 1 cannot be matched, meaning that path information 1 cannot be found. In the fourth round, path information 1, path information 2, and path information 3 are all fixed as empty strings, and matching begins from the domain information (i.e., the information preceding path information 1). If a match is found, the successfully matched platform information is taken as the target platform information. Otherwise, if no match is found, the fifth and final round of matching continues.

[0151] 5. The fifth round is only conducted if no domain information can be matched, meaning no domain information can be found. In the fifth round, the domain information, path information 1, path information 2, and path information 3 are all set to empty strings, and the matching begins from the protocol information (i.e., the information preceding the domain information). If a match is found, the successfully matched platform information is used as the target platform information. Otherwise, if no match is found...

[0152] Therefore, since the fifth round is the final matching round, if a match is successful, the successfully matched platform information will be used as the target platform information and fed back. Conversely, if a match fails, it indicates that the code information matched by the resource receiving code is not supported, meaning the category to which the resource receiving code belongs cannot be identified, and a notification of type identification failure will be fed back. In this case, the relevant notification can be displayed on the terminal of the first target.

[0153] For ease of understanding, based on Figure 19 The platform information shown, and the code information matched by the resource receiving code, is https: / / a.12345.com / 00010000 / 01316785607205401163117143534316. This will be used as an example for further explanation. Figure 20 As shown, the code information 2001 matched by the resource receiving code is divided according to the preset symbols " / ". At this time, the protocol information 2002 is "https", the domain information 2003 is "a.12345.com", and the path information 2004 is "00010000". Further division is not possible. Therefore, the protocol information 2002 "https", the domain information 2003 "a.12345.com", and the path information "00010000" are matched with the platform information "https: / / a.12345.com / 00010000 / " from the end to the beginning. The path information "00010000" can directly match the path information "00010000" in the platform information without further matching. This means that the successfully matched platform information can be immediately reported as the target platform information for matching the resource receiving code. Therefore, this method reduces recognition efficiency when there are millions of platform information entries.

[0154] Therefore, when the resource receiving code's category indicates it is a direct connection code, a background mode is triggered. In background mode, the wallet app can use its own payment page as the user interface. Thus, the resource transfer page provided by the first resource platform is displayed on the application interface of the first resource platform. This means that processing via the page display method provided in the resource transfer processing of this application is unnecessary, and the resource transfer process is controlled by the first resource platform. When the resource receiving code's category indicates it is an aggregation code, a foreground mode is triggered, meaning step 1804 needs to be executed.

[0155] Step 1804: If the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform displays the resource transfer page in the application interface; the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform.

[0156] In the case of a resource receiving code that is an aggregation code, the resource type of the second resource platform bound to the aggregation code is different from that of the first resource platform, taking into account the different currency types used in different regions. Therefore, the aggregation code in this application is a QR code provided by a domestic aggregation management platform. For example, if the first object is a payment object belonging to region C1, and the resource type used in region C1 is resource type E1, then the first resource platform D1 matches resource type E1. In this case, the aggregation management platform must not belong to region 1, and the resource type of the second resource platform bound to the aggregation code provided by the aggregation management platform is not resource type E1. That is, the resource type of the second resource platform can be resource type E2, resource type E3, or other types that are not resource type E1. Secondly, the rendering parameters include, but are not limited to, the platform parameters of the aggregation management platform.

[0157] Specifically, when the resource receiving code belongs to the category of aggregate code, the first resource platform of the first object cannot directly transfer resources through the native page. In this case, the server needs to provide rendering parameters for the resource transfer page to enable the display of the page and resource transfer process in front-end mode. That is, the server first determines the page rule script matching the resource receiving code, determines the rendering parameters of the resource transfer page based on the page rule script, and then feeds back the rendering parameters of the resource transfer page to the first resource platform so that the first resource platform can display the resource transfer page rendered according to the preset page rendering parameters in the application interface. The following describes how to determine the rendering parameters through the page rule script:

[0158] In an exemplary embodiment, when the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform. Specifically, this includes: when the resource receiving code belongs to the category of aggregation code, searching for a page rule script that matches the resource receiving code according to the category of the resource receiving code; determining the rendering parameters of the resource transfer page based on the page rule script, and feeding back the rendering parameters of the resource transfer page to the first resource platform, so that the first resource platform displays the resource transfer page obtained by rendering the preset page according to the rendering parameters on the application interface.

[0159] Because different aggregation management platforms have inconsistent page display structures regarding platform information, supported languages, and component display information, and given that the resource receiving code belongs to the aggregation code category (meaning it is actually provided by the aggregation management platform), the specific resource receiving code is queried using corresponding page rule scripts, taking into account the page display structure matching the aggregation management platform. Therefore, the page rule scripts specifically include, but are not limited to, the aggregation management platform's platform page and interface request rules. These scripts are used to indicate the request information for initiating requests to the aggregation management platform and to invoke requests to the aggregation management platform.

[0160] Specifically, when the resource receive code belongs to the category of aggregate code, the target prefix information of the resource receive code is first determined based on its category. Then, the surface rule scripts that match the target prefix information are searched, and these surface rule scripts are identified as page rule scripts that match the resource receive code. The following details how to find page rule scripts that match the resource receive code:

[0161] In one exemplary embodiment, finding a page rule script that matches the resource receiving code according to its category includes: determining the target prefix information that matches the resource receiving code according to its category; finding the platform rule script that has a mapping relationship with the target prefix information based on the mapping relationship between the platform rule script and platform information of each aggregation management platform; and determining the platform rule script that has a mapping relationship with the target prefix information as the page rule script that matches the resource receiving code.

[0162] The mapping relationship between platform rule scripts and platform information for each aggregation management platform is generated in advance. Specifically, the mapping relationship between platform rule scripts and platform information for each aggregation management platform is first obtained. At this time, the server extracts the platform page and interface request rules of each aggregation management platform offline, encapsulates them into a platform rule script that matches the aggregation management platform, and then creates and stores the mapping relationship between the platform rule script that matches the aggregation management platform and the platform information that matches the aggregation management platform. The following describes how to create the mapping relationship between platform rule scripts and platform information for each aggregation management platform. In an exemplary optional embodiment, the creation method of the mapping relationship between platform rule scripts and platform information for each aggregation management platform includes: obtaining the platform page and interface request rules of each aggregation management platform, and the platform information that matches each aggregation management platform; for each aggregation management platform, encapsulating the platform page and interface request rules to obtain a platform rule script; and creating the mapping relationship between the platform rule script and the platform information.

[0163] Specifically, the server first extracts the platform page and interface request rules for each aggregation management platform offline. This means each aggregation management platform has its own platform page and interface request rules for initiating requests to it. Then, it also obtains the platform information matched by each aggregation management platform, specifically the code prefix information of the resource receiving code provided by that platform. For example, it can obtain platform information G1 for aggregation management platform A1, platform information G2 for aggregation management platform A2, and aggregate management platform A1 is matched with platform page H1 and interface request rule I1, while aggregation management platform A2 is matched with platform page H2 and interface request rule I2.

[0164] Based on this, for each aggregation management platform, the platform page and interface request rules of the aggregation management platform are encapsulated to obtain a platform rule script encapsulated with the platform page and interface request rules. This platform rule script is matched one-to-one with the aggregation management platform. Therefore, a mapping relationship can be created between the platform rule script matched by the aggregation management platform and the platform information matched by the aggregation management platform. For example, further illustrating the previous example, for aggregation management platform A1, encapsulating the matched platform page H1 and interface request rule I1 yields a platform rule script J1 encapsulated with platform page H1 and interface request rule I1. A mapping relationship is then created between platform rule script J1 and the platform information G1 of aggregation management platform A1. Similarly, for aggregation management platform A2, encapsulating the matched platform page H2 and interface request rule I2 yields a platform rule script J2 encapsulated with platform page H2 and interface request rule I2. A mapping relationship is then created between platform rule script J2 and the platform information G2 of aggregation management platform A2.

[0165] Based on this, before resource transfer, the server or a data storage system communicating with the server can store the mapping relationship between the platform rule scripts and platform information of each aggregation management platform. Then, after identifying the category of the resource receiving code through the previous embodiment, if the resource receiving code belongs to the aggregation code category, the target prefix information matching the resource receiving code can be obtained during the process of determining the resource receiving code category. As described above, the target prefix information is the code prefix information of the resource receiving code, and the code prefix information actually indicates the platform information (i.e., code prefix information) of the aggregation management platform that provides the aggregation code. That is, through the target prefix information matching the resource receiving code, the target platform information of the aggregation management platform can be confirmed. Then, through the mapping relationship between the platform rule scripts and platform information of each aggregation management platform, the platform rule script that has a mapping relationship with the target platform information can be queried, thereby determining the platform rule script that has a mapping relationship with the target platform information as the page rule script matching the resource receiving code.

[0166] For ease of understanding, based on the example given in the foregoing embodiments, where the code prefix information F1 of the aggregation management platform A1 is the platform information G1 of the aggregation management platform A1, and the code prefix information F2 of the aggregation management platform A2 is the platform information G2 of the aggregation management platform A2, this section introduces how to determine the page rule script. If the target prefix information that matches the resource receiving code is obtained as code prefix information F1, as shown in the foregoing example, code prefix information F1 is the platform information G1 of the aggregation management platform A1. There is a mapping relationship between platform information G1 and platform rule script J1, which means that at this time it can be determined that platform rule script J1 is the page rule script that matches the resource receiving code.

[0167] Furthermore, after the server determines the page rule script that matches the resource receiving code using the method described in the aforementioned embodiments, it also needs to determine the rendering parameters of the resource transfer page based on the page rule script. These rendering parameters need to take into account the platform parameters of the aggregation management platform; that is, in determining the rendering parameters of the resource transfer page, the platform page of the aggregation management platform needs to be parsed to obtain the platform parameters. Based on this, the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform can display the resource transfer page rendered according to the preset page in the application interface.

[0168] For ease of understanding, considering practical applications, different aggregation management platforms have different platform pages, and the display structures of commonly used language types and resource types included under each aggregation management platform are inconsistent. Furthermore, different aggregation management platforms may offer different page themes. Therefore, it is necessary to dynamically parse the page rule script matching the resource receiving code before rendering the page. In other words, the determination of rendering parameters needs to be based on the dynamic parsing of the page rule script. Specifically, the display of the resource transfer page on the first resource platform includes: determining the rendering parameters through the page rule script matching the resource receiving code; feeding back the rendering parameters of the resource transfer page to the first resource platform; enabling the preset page embedded in the first resource platform to parse the rendering parameters; loading the platform parameters from the aggregation management platform into the page content parsing; parsing to obtain the object information and interface call information of the second object; and the preset page also calling the JS Bridge to obtain the language preference of the first object. The preset page then integrates the object information of the second object, the language preference of the first object, the platform identifier of the first resource platform, and the interface call information to obtain structured data. Finally, the preset page renders the resource transfer page displayed on the first resource platform using this structured data, thus displaying the rendered resource transfer page on the first resource platform.

[0169] For ease of understanding, the specifics are as follows: Figure 21As shown, before loading the resource transfer page through the preset page rendering, the resource receiving code is first transmitted to the parsing service. The parsing service determines the target platform information to be matched based on the code information of the resource receiving code. Then, through the mapping relationship between the platform rule script of each aggregation management platform and the platform information, the platform rule script that has a mapping relationship with the target platform information is queried. Thus, the platform rule script that has a mapping relationship with the target platform information is determined as the page rule script that matches the resource receiving code. Based on this, the rendering parameters are determined by the page rule script matching the resource receiving code, and the rendering parameters of the resource transfer page are fed back to the first resource platform. At this time, the preset page embedded in the first resource platform parses the rendering parameters and loads the platform parameters of the aggregation management platform into the page content parsing. Then, the object information and interface call information of the second object are parsed. At this time, the language preference of the first object is obtained by calling the JS Bridge through the preset page. The parsing results are then combined with the platform identifier of the first resource platform to integrate and output structured data. The resource transfer page displayed on the first resource platform is rendered through the structured data. The rendering of the resource transfer page displayed on the first resource platform includes, but is not limited to: local language adaptation, platform theme adaptation, resource component initialization, etc., to ensure that the language of the resource transfer page is adapted to the language preference of the first object, and that the resource components are adapted to the page theme.

[0170] Step 1806: Based on the resource transfer confirmation event initiated by the first object, the target resource is transferred from the first resource platform to the aggregation management platform that provides the aggregation code, according to the amount of target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0171] The aggregation management platform is used to transfer target resources to the resource account of the second object belonging to the resource receiving code on the second resource platform. The resource transfer confirmation event is generated based on the transfer confirmation operation of the first object for the input target resource. Specifically, as described in the foregoing embodiments, the first resource platform displays a resource transfer page on the application interface, which also displays the identification information of the second object and the amount of the target resource input by the first object. If the first object correctly determines the object receiving the resource based on the identification information of the second object, and the amount of the target resource is correct, it can trigger a transfer confirmation operation for the target resource. This allows the terminal to respond to the transfer confirmation operation triggered by the first object, generating a resource transfer confirmation event initiated by the first object through the first resource platform. The first resource platform then feeds back the resource transfer confirmation event initiated by the first object to the cross-resource management platform. At this time, the resource transfer confirmation event includes the identification information of the second object and the amount of the target resource input by the first object.

[0172] Therefore, the cross-resource management platform can receive resource transfer confirmation events and determine the identification information of the second object and the amount of the target resource input by the first object through these events. The identification information of the second object can identify the aggregation management platform providing the aggregation code, while the amount of the target resource input by the first object can determine the specific amount of resources to be transferred. This allows the first resource platform to transfer the target resource to the aggregation management platform. In other words, transferring the target resource requires interaction between the first resource platform, the aggregation management platform, and the cross-resource management platform. This will be explained in detail below:

[0173] In one exemplary embodiment, based on a resource transfer confirmation event initiated by a first object, the first resource platform transfers the target resource to the aggregation management platform providing the aggregation code according to the amount of the target resource entered by the first object on the resource transfer page. This includes: determining the amount of the target resource entered by the first object on the resource transfer page based on the resource transfer confirmation event initiated by the first object; and transferring the target resource from the first resource platform to the aggregation management platform providing the aggregation code according to the amount of the target resource and the identification information of the second object, so that the aggregation management platform transfers the target resource to the resource account of the second object on the second resource platform according to the amount of the target resource based on the identification information of the second object.

[0174] Specifically, in response to the transfer confirmation operation triggered by the first object, the terminal generates a resource transfer confirmation event initiated by the first object through the first resource platform. The first resource platform then feeds back this event to the cross-resource management platform. The cross-resource management platform receives the resource transfer confirmation event and uses it to determine the identification information of the second object and the amount of the target resource input by the first object. Based on this, the cross-resource management platform first determines the aggregation management platform providing the aggregation code through the identification information of the second object, and then initiates a resource transfer request to the aggregation management platform according to the amount of the target resource. The aggregation management platform can extract the identification information of the second object from the resource transfer request, and also determine the first object and the first resource platform involved in the resource transfer. At this point, the aggregation management platform needs to obtain the target resource to be transferred from the first resource platform. Based on the amount of the target resource input by the first object, the aggregation management platform obtains the target resource to be transferred from the first resource platform, thus completing the resource transfer process from the first resource platform to the aggregation management platform providing the aggregation code. Based on this, the aggregation management platform feeds back the resource transfer result of the target resource to the cross-resource management platform, which in turn feeds back the resource transfer result of the target resource to the first resource platform. Therefore, the first resource platform can receive the resource transfer result of the target resource and display the resource transfer result of the target resource on the application interface of the first resource platform.

[0175] Considering that the resource transfer confirmation event is essentially generated by the transfer confirmation operation, in order to ensure the security of the resource transfer, a resource confirmation operation needs to be triggered for the target resource before the first object performs the transfer confirmation operation. This confirms that the specific amount of the transferred resource is the amount of the target resource, so that the amount of the target resource is the amount input and confirmed by the first object. This will be explained in detail below:

[0176] In an exemplary optional embodiment, the resource transfer processing method further includes: based on a resource amount confirmation event initiated by the first object on the resource transfer page, obtaining a resource transfer identifier matching the resource amount confirmation event, determining resource transfer information matching the resource amount confirmation event, and associating and storing the information association relationship between the resource transfer identifier and the resource transfer information; the resource transfer information includes at least the amount of the target resource; and sending confirmation information carrying the resource transfer identifier back to the first resource platform so that the first resource platform displays the resource confirmation page.

[0177] The resource amount confirmation event is generated by the resource confirmation operation triggered by the first object on the resource transfer page for the target resource. This resource confirmation operation is used to confirm the amount of the target resource entered by the first object. In this application, the aforementioned resource transfer identifier is specifically the prepayment transaction session identifier (prepay_id), which is a unique transaction identifier generated by the first resource platform after placing an order with the second object. This resource transfer identifier is used to call the resource management service matched with the first resource platform to complete the resource transfer. The resource transfer information in this application is specifically order information, which is obtained after generating an order through the resource confirmation operation via the aggregation management platform. Therefore, the resource transfer information includes at least the amount of the target resource, and may also include the second object's identifier information, order time, etc., which are not limited here.

[0178] Specifically, as described above, since the first resource platform can display the identification information of the second object and the amount of the target resource entered by the first object on the resource transfer page, if the first object correctly determines the object to receive the resource based on the identification information of the second object and the amount of the target resource is correct, it first triggers a resource confirmation operation on the resource transfer page for the determined amount of the target resource. The first resource platform responds to the resource confirmation operation and generates a resource amount confirmation event initiated by the first object on the resource transfer page. At this time, the first resource platform feeds back the resource amount confirmation event initiated by the first object to the preset page, so that the preset page can receive the resource amount confirmation event, obtain the resource transfer identifier matching the resource amount confirmation event, and determine the resource transfer information matching the resource amount confirmation event. Then, it associates and stores the information association relationship between the resource transfer identifier and the resource transfer information. Based on this, the preset page then feeds back the confirmation information carrying the resource transfer identifier to the first resource platform through the JS Bridge and calls the resource management service matching the first resource platform so that the first resource platform displays the resource confirmation page.

[0179] Based on this, based on the resource transfer confirmation event initiated by the first object, the amount of the target resource entered by the first object on the resource transfer page is determined, specifically including: based on the resource transfer confirmation event initiated by the first object, determining the resource transfer identifier to be identified that matches the resource transfer confirmation event; based on the information association relationship between the resource transfer identifier and the resource transfer information, querying the target resource transfer information associated with the resource transfer identifier to be identified, and determining the amount of the target resource based on the target resource transfer information.

[0180] Specifically, this application uses a resource transfer identifier as a preset page embedded in the first resource platform for page rendering and display, which communicates with the cross-resource management platform to resolve the association issue between the process of creating an order on the aggregation management platform and transferring resources through the resource management service matched by the first resource platform. Therefore, the first object triggers a resource confirmation operation on the resource transfer page to call the resource management service matched by the first resource platform. Since all page displays in this application are performed through the preset page, triggering the resource confirmation operation on the page requires communication and interaction with the first resource platform. JS Bridge is a communication mechanism between a web page and a native app. Therefore, the displayed page needs to respond to the resource confirmation operation triggered for the target resource, calling the resource management service of the first resource platform through JS Bridge, so that the first resource platform can transfer the target resource to the aggregation management platform through the resource management service. The question then arises: how can the aggregation management platform and the cross-resource management platform determine whether the required amount of the target resource matches and whether the transferred target resource has been received? At this point, the first resource platform needs to generate a resource transfer confirmation event in response to the transfer confirmation operation triggered for the target resource, and send the resource transfer confirmation event to the cross-resource management platform so that the cross-resource management platform can determine the resource transfer identifier to be identified that matches the resource transfer confirmation event. At this point, it is necessary to query the target resource transfer information associated with the resource transfer identifier to be identified based on the information association relationship between the resource transfer identifier and the resource transfer information stored in the aforementioned embodiment. Since the resource transfer information includes at least the amount of the target resource, the amount of the target resource can be determined based on the target resource transfer information.

[0181] Therefore, by generating a resource transfer identifier from resource transfer information and then transmitting this identifier to the first resource platform via JS Bridge, the first resource platform can carry the resource transfer identifier during resource transfers. Based on this identifier, the cross-resource management platform can then associate the resource transfer information, thereby identifying the target resource to be transferred and the identifier information of the second object receiving the target resource. At this point, the cross-resource management platform can transfer the target resource to the resource account of the second object on the second resource platform based on the identifier information. The following details how to obtain the resource transfer identifier:

[0182] In one exemplary embodiment, obtaining a resource transfer identifier matching the resource amount confirmation event initiated by the first object on the resource transfer page specifically includes: obtaining the identifier information of the first object and the platform information of the first resource platform based on the resource transfer confirmation event initiated by the first object; generating a target object identifier based on the identifier information of the first object and the platform information of the first resource platform; initiating an information generation request matching the resource transfer confirmation event to the aggregation management platform according to the target object identifier, so that the aggregation management platform responds to the information generation request and generates a resource transfer identifier matching the information generation request; receiving the resource transfer identifier generated by the aggregation management platform in response to the information generation request, and determining the resource transfer identifier as the resource transfer identifier matching the resource transfer confirmation event.

[0183] Specifically, the preset page embedded in the first resource platform, based on the resource transfer confirmation event initiated by the first object, obtains the identification information of the first object and the platform information of the first resource platform through the JS Bridge. Then, based on the identification information of the first object and the platform information of the first resource platform, it generates a target object identifier (Openid). The target object identifier enables the first object and the second object to participate in the transfer process of the aggregation management platform. Based on this, the preset page embedded in the first resource platform then sends an information generation request matching the resource transfer confirmation event to the aggregation management platform according to the target object identifier. The information generation request is the order request. At this time, the aggregation management platform responds to the information generation request and generates a resource transfer identifier matching the information generation request. Therefore, the preset page receives the resource transfer identifier, identifies the resource transfer identifier as the one matching the resource transfer confirmation event, and then associates and stores the resource transfer identifier with the resource transfer information to ensure the smooth progress of the subsequent resource transfer process.

[0184] For ease of understanding, such as Figure 22As shown, the first object triggers a resource confirmation operation on the first resource platform, which is actually triggered on the resource transfer page provided by the preset page. At this time, the preset page obtains the identification information of the first object and the platform information of the first resource platform through the JS Bridge, and generates a target object identifier through the aforementioned information. Then, according to the target object identifier, it sends an information generation request matching the resource transfer confirmation event to the aggregation management platform. The aggregation management platform responds to the information generation request, generates a resource transfer identifier, and feeds back the resource transfer identifier to the preset page. Therefore, the preset page can associate and store the resource transfer identifier and resource transfer information. At this time, the resource management service of the first resource platform is called through the JS Bridge. The first resource platform will obtain the domain name information to be verified that matches the resource confirmation operation, and perform domain name verification on the domain name information to be verified. If the domain name verification result indicates that the domain name verification is successful, the resource management service will be launched. Based on this, the first object triggers a transfer confirmation operation for the target resource. The first resource platform sends a resource transfer confirmation event generated based on the transfer confirmation operation to the cross-resource management platform. The cross-resource management platform then initiates a resource transfer request for the target resource to the aggregated management platform, causing the aggregated management platform to request the target resource from the first resource platform. The first resource platform then performs the resource transfer to the aggregated management platform through its initiated resource management service. Based on the result of the resource transfer processing performed by the first resource platform, the aggregated management platform determines the resource transfer result of the target resource, thereby completing the target resource transfer through the resource management service. After receiving the resource transfer result, the first resource platform needs to send a JS callback notification to the preset page, and at this time, it also needs to feed back the resource transfer result so that the preset page can render the page based on the resource transfer result to obtain a resource transfer result page for displaying the resource transfer result, and then display the resource transfer result page in the application interface of the first resource platform.

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

[0186] In the above-described resource transfer processing method, after receiving the identification request initiated by the first object through scanning the resource receiving code on the first resource platform, the resource receiving code is identified by type. If the resource receiving code is an aggregation code, the resource transfer page is loaded so that it is displayed on the application interface of the first resource platform. After the first object completes the transfer confirmation operation on the resource transfer page, a resource transfer confirmation event is triggered. At this time, the target resource is directly transferred to the aggregation management platform that provides the aggregation code. There is no need to adapt or modify the aggregation management platform. Instead, the target resource is transferred to the resource account of the second object on the second resource platform through the aggregation payment capability of the aggregation code provided by the aggregation management platform, thus completing the cross-resource type resource transfer processing. Therefore, in the scenario of cross-resource type resource transfer processing, the resource waste of platform modification for cross-resource type transfer is avoided, and the reliability of cross-resource type resource transfer processing is guaranteed.

[0187] Based on the detailed description of the foregoing embodiments, the complete flow of the resource transfer processing method in the embodiments of this application will be described below. In an exemplary embodiment, such as... Figure 23 As shown, a method for resource transfer processing is provided, applied to a system including a terminal 102 and a server 104. The method is illustrated through the interaction between the terminal 102 and the server 104. Specifically, the terminal 102 is a terminal equipped with the first resource platform used by the first object, and the server 104 is a cross-resource management platform. In this embodiment, the method includes the following steps:

[0188] Step 2301: The first resource platform responds to the first object scanning the resource receiving code of the second object through the first resource platform and sends an identification request to the cross-resource management platform for the resource receiving code.

[0189] Specifically, when resource transfer processing is required between the first object and the second object, the resource receiving code of the second object is first determined. Then, the first object uses the first resource platform installed on its terminal to trigger a scanning operation. This involves scanning the resource receiving code of the second object through the scanning area displayed on the application interface of the first resource platform. The first object's terminal then responds to the obtained resource receiving code. Based on this, after responding to the obtained resource receiving code, the first object's terminal can also generate an identification request based on the resource receiving code and send the identification request carrying the resource receiving code to the cross-resource management platform.

[0190] Step 2302: Receive the identification request initiated by the cross-resource management platform for the resource receiving code and identify the category to which the resource receiving code belongs.

[0191] Specifically, the cross-resource management platform receives identification requests for resource receiving codes and responds to these requests to obtain platform information that matches each management platform. Based on this, the cross-resource management platform performs information matching between the resource receiving code and the platform information that matches each aggregated management platform and each directly connected management platform, respectively. The information matching result indicates that the resource receiving code matches the target platform information of the target aggregated management platform, or matches the target platform information of the target directly connected management platform. Such a matching result indicates that the code prefix information in the resource receiving code is consistent with the target code prefix information represented by the target platform information. Alternatively, the information matching result may indicate that the resource receiving code cannot match any platform information, meaning that the code prefix information in the resource receiving code cannot match the code prefix information represented by any platform information.

[0192] Therefore, the category of the resource receiving code is determined by the information matching results. If the information matching results indicate that the resource receiving code cannot be matched with any platform information, the category of the resource receiving code is empty, meaning that the category of the resource receiving code required for the identification request cannot be fed back. However, if the information matching results indicate that the resource receiving code matches the target platform information, then the category of the resource receiving code can be determined by directly identifying whether the target platform information belongs to a direct connection management platform or an aggregation management platform. In other words, if the target platform information belongs to a direct connection management platform, the resource receiving code belongs to the direct connection code category; if the target platform information belongs to an aggregation management platform, the resource receiving code belongs to the aggregation code category.

[0193] Furthermore, it's necessary to consider that the platform information of the management platform is specifically code prefix information. This code prefix information typically carries multi-dimensional prefix information, including protocol information, domain name information, and at least one path information. Therefore, during the information matching process, prefix information under the same dimensions should be matched sequentially. In other words, platform information includes multiple platform breakdown information. For each management platform's platform breakdown information, which matches against its own platform breakdown information, the information matching is performed sequentially from the end to the beginning. This yields the matching result. Specifically, the breakdown information is matched sequentially with the multiple platform breakdown information of each platform, and the first successfully matched platform information is returned as the matching result. The first successfully matched platform information is the target platform information described above. If the matching is not completed before the protocol information breakdown information is reached, the matching result is considered unsuccessful. It's understandable that in practical applications, there may be code information containing only protocol information, or code information containing only protocol and domain name information.

[0194] If the resource receiving code's category indicates it is a direct connection code, a background mode is triggered. In background mode, the wallet app can use its own payment page as the user interface. Therefore, the resource transfer page provided by the first resource platform is displayed on the application interface of the first resource platform. This means that processing via the page display method provided in the resource transfer processing described in this application is unnecessary, and the resource transfer process is controlled by the first resource platform. If the resource receiving code's category indicates it is an aggregation code, a foreground mode is triggered, and step 2303 is executed.

[0195] Step 2303: If the resource receiving code belongs to the category of aggregation code, determine the page rule script that matches the resource receiving code across the resource management platform.

[0196] Specifically, when the resource receiving code belongs to the category of aggregation code, the first resource platform of the first object cannot directly transfer resources through the native page. Therefore, the cross-resource management platform needs to provide rendering parameters for the resource transfer page to enable the display of the page and resource transfer process through the front-end mode. The cross-resource management platform then obtains the target prefix information matching the resource receiving code. As mentioned above, the target prefix information is the code prefix information of the resource receiving code, and this code prefix information actually indicates the platform information (i.e., code prefix information) of the aggregation management platform that provides the aggregation code. In other words, by using the target prefix information matching the resource receiving code, the target platform information of the aggregation management platform can be identified. Then, through the mapping relationship between the platform rule scripts of each aggregation management platform and the platform information, the platform rule scripts that have a mapping relationship with the target platform information can be found, thus determining the platform rule scripts that have a mapping relationship with the target platform information as the page rule scripts that match the resource receiving code.

[0197] Step 2304: The cross-resource management platform determines the rendering parameters of the resource transfer page based on the page rule script, and sends the category of the resource receiving code and the rendering parameters back to the first resource platform.

[0198] Specifically, the rendering parameters of the resource transfer page are determined based on the page rule script. These rendering parameters need to take into account the platform parameters of the aggregation management platform; that is, in determining the rendering parameters of the resource transfer page, the platform page of the aggregation management platform needs to be parsed to obtain the platform parameters. Based on this, the rendering parameters of the resource transfer page are fed back to the first resource platform, so that the first resource platform can display the resource transfer page rendered according to the preset page in the application interface.

[0199] Step 2305: The first resource platform loads the preset page, so that the preset page is rendered on the preset page according to the rendering parameters to obtain the resource transfer page, and then the resource transfer page is fed back to the first resource platform; so that the resource transfer page is displayed in the application interface of the first resource platform.

[0200] Specifically, when the foreground mode is triggered on the first resource platform, the preset page is loaded according to the page access address, and the resource transfer page is obtained by rendering the preset page through rendering parameters, and then the resource transfer page is displayed on the application interface of the first resource platform.

[0201] Furthermore, considering that in practical applications, different aggregation management platforms have different platform pages, and the display structures of commonly used language types and resource types included in the aggregation management platform are inconsistent, and different aggregation management platforms may also provide different page themes. Therefore, it is necessary to dynamically parse the page rule script that matches the resource receiving code before rendering the page. In other words, the determination of rendering parameters needs to be based on the dynamic parsing of the page rule script. Specifically, the display of the resource transfer page on the first resource platform includes: determining the rendering parameters through the page rule script that matches the resource receiving code, feeding back the rendering parameters of the resource transfer page to the first resource platform, so that the preset page embedded in the first resource platform can parse the rendering parameters, load the platform parameters of the aggregation management platform into the page content parsing, parse to obtain the object information and interface call information of the second object, and the preset page also calls the JS Bridge to obtain the language preference of the first object. Then, the preset page integrates the object information of the second object, the language preference of the first object, the platform identifier of the first resource platform, and the interface call information to obtain structured data. Finally, the preset page renders the resource transfer page displayed on the first resource platform through the structured data, thus displaying the rendered resource transfer page on the first resource platform.

[0202] Step 2306: The first resource platform responds to the resource confirmation operation triggered by the first object on the resource transfer page for the target resource.

[0203] The resource confirmation operation is used to confirm the amount of the target resource input by the first object. Specifically, the first object triggers a resource confirmation operation on the resource transfer page for the determined amount of the target resource. This causes the first resource platform to respond to the resource confirmation operation triggered for the amount of the target resource and display a resource confirmation page for the target resource. Since the resource confirmation operation is triggered for the target resource, to ensure the accuracy of the determined amount of the target resource, the amount of the target resource can also be displayed on the resource confirmation page. Furthermore, if the specific requirement is to transfer resources to the second object, and the resource types of the resource transfer platforms are different, the platform information of the second resource platform can also be displayed on the resource confirmation page. Because the resource confirmation page is used for displaying the resource amount and platform information, a transfer confirmation control can also be displayed to trigger the required transfer confirmation operation.

[0204] Step 2307: The preset page obtains the identification information of the first object and the platform information of the first resource platform, and generates the target object identification through the identification information and platform information.

[0205] Specifically, the preset page built into the first resource platform obtains the identification information of the first object and the platform information of the first resource platform through the JS Bridge based on the resource transfer confirmation event initiated by the first object. Then, based on the identification information of the first object and the platform information of the first resource platform, a target object identifier (Openid) is generated. The target object identifier enables the first object and the second object to participate in the transfer process of the aggregation management platform.

[0206] Step 2308: The preset page initiates an information generation request to the aggregation management platform according to the target object identifier.

[0207] Specifically, the preset page built into the first resource platform then sends an information generation request to the aggregation management platform according to the target object identifier, which matches the resource transfer confirmation event. The information generation request is the order placement request.

[0208] Step 2309: The aggregation management platform responds to the information generation request by generating a resource transfer identifier and sends the resource transfer identifier back to the preset page.

[0209] Specifically, in response to an information generation request, the aggregation management platform generates a resource transfer identifier using resource transfer information, and then sends the resource transfer identifier that matches the information generation request back to the preset page.

[0210] Step 2310: Preset the page to associate storage resource transfer identifier and resource transfer information, and call the resource management service of the first resource platform.

[0211] Specifically, a preset page embedded in the first resource platform is used to associate and store resource transfer identifiers and resource transfer information, and then the resource management service of the first resource platform is called through the JS Bridge.

[0212] Step 2311: The first resource platform obtains the domain name information to be verified and performs domain name verification on the domain name information to be verified; if the domain name verification result indicates that the domain name verification is successful, the resource management service is launched.

[0213] Specifically, the first resource platform obtains the domain name information to be verified that matches the resource confirmation operation, and performs domain name verification on this information to obtain a verification result. This means determining whether the domain name information to be verified is among the preset accessible domain names. If so, the verification result indicates that the domain name verification passed. Conversely, if the domain name information is not among the preset accessible domain names, it may be an abnormal domain name, and the verification result indicates that the verification failed. Therefore, if the verification result indicates that the domain name verification passed, the resource management service matching the first resource platform is then invoked. If the verification result indicates that the domain name verification failed, the request to invoke the resource management service will be rejected, thus suspending the transfer of the target resource.

[0214] Step 2312: The first resource platform displays a resource confirmation page, which shows the amount of the target resource and the platform information of the second resource platform.

[0215] Specifically, the first resource platform displays a resource confirmation page for the target resource. Considering that the resource confirmation operation is triggered for the target resource, in order to ensure the accuracy of the determined amount of the target resource, the amount of the target resource can also be displayed on the resource confirmation page. In addition, the specific requirement is to transfer resources to the second object. Since the resource types of the resource transfer platforms are not the same, the platform information of the second resource platform can also be displayed on the resource confirmation page. Since the resource confirmation page is used to display the resource amount and platform information, a transfer confirmation control can also be displayed so that the required transfer confirmation operation can be triggered through the transfer confirmation control.

[0216] Step 2313: In response to the transfer confirmation operation triggered by the first object on the resource confirmation page, the first resource platform generates and sends a resource transfer confirmation event based on the transfer confirmation operation to the cross-resource management platform.

[0217] Specifically, the first object will check on the resource confirmation page whether the amount of the target resource displayed is correct. After confirming that it is correct, it will trigger a transfer confirmation operation. In response to the transfer confirmation operation triggered by the first object, the first resource platform will generate a resource transfer confirmation event initiated by the first object and send the resource transfer confirmation event initiated by the first object to the cross-resource management platform.

[0218] Step 2314: The cross-resource management platform identifies the resource transfer identifier to be identified that matches the resource transfer confirmation event; based on the information association between the resource transfer identifier and the resource transfer information, the target resource transfer information associated with the resource transfer identifier to be identified is queried, and the amount of the target resource is determined based on the target resource transfer information.

[0219] Specifically, the cross-resource management platform identifies the resource transfer identifier to be identified that matches the resource transfer confirmation event. Based on the information association between the stored resource transfer identifier and the resource transfer information, it queries the target resource transfer information associated with the resource transfer identifier to be identified. Since the resource transfer information includes at least the amount of the target resource, the amount of the target resource can be determined based on the target resource transfer information.

[0220] Step 2315: The cross-resource management platform initiates a resource transfer request for the target resource to the aggregation management platform, causing the aggregation management platform to request the target resource from the first resource platform.

[0221] Specifically, after determining the amount of the target resource, the cross-resource management platform first identifies the aggregation management platform that provides the aggregation code through the identification information of the second object, and then initiates a resource transfer request to the aggregation management platform according to the amount of the target resource, so that the aggregation management platform requests the target resource corresponding to the amount of the target resource from the first resource platform.

[0222] Step 2316: The first resource platform transfers the target resource to the aggregation management platform according to the amount of the target resource and the identification information of the second object.

[0223] Specifically, the first resource platform transfers resources to the aggregation management platform through the resource management service it initiates, based on the amount of the target resource and the identification information of the second object.

[0224] Step 2317: Based on the result of the resource transfer processing of the first resource platform, the aggregation management platform determines the resource transfer result of the target resource and feeds back the resource transfer result to the cross-resource management platform so that the cross-resource management platform can feed back the resource transfer result to the first resource platform.

[0225] Specifically, if the aggregation management platform receives the target resource transferred from the first resource platform, the resource transfer result is determined to be successful. Conversely, if the aggregation management platform does not receive the target resource transferred from the first resource platform, the resource transfer result is determined to be failed. Based on this, the aggregation management platform feeds back the resource transfer result to the cross-resource management platform, which then feeds back the resource transfer result to the first resource platform.

[0226] Step 2318: The first resource platform sends a callback notification to the preset page so that the preset page can render the page using the resource transfer results to obtain a resource transfer result page for displaying the resource transfer results, and then display the resource transfer result page in the application interface of the first resource platform.

[0227] Specifically, after receiving the resource transfer result, the first resource platform needs to send a JS callback notification to the preset page, and at this time, it also needs to carry the feedback resource transfer result so that the preset page can be rendered through the resource transfer result, thereby obtaining the resource transfer result page for displaying the resource transfer result, and then displaying the resource transfer result page for displaying the resource transfer result in the application interface of the first resource platform.

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

[0229] 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.

[0230] Based on the same inventive concept, this application also provides a resource transfer processing apparatus for implementing the resource transfer 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 resource transfer processing apparatus embodiments provided below can be found in the limitations of the resource transfer processing method described above, and will not be repeated here.

[0231] In one exemplary embodiment, such as Figure 24 As shown, a resource transfer processing device is provided, including: a page display module 2402 and a result display module 2404, wherein:

[0232] The page display module 2402 is used to respond to the first object scanning the resource receiving code of the second object through the first resource platform. If the resource receiving code is identified as an aggregation code by the cross-resource management platform, the resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform. The resource type of the second resource platform to which the aggregation code is bound is different from that of the first resource platform.

[0233] The page display module 2402 is also used to display the identification information of the second object and the amount of the target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0234] The result display module 2404 is used to display the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through cross-resource management platforms in response to the transfer confirmation operation of the first object for the input target resource.

[0235] In an exemplary embodiment, the page display module is further configured to, in response to a resource confirmation operation triggered by the first object on the resource transfer page for the target resource, display a resource confirmation page for the target resource; on the resource confirmation page, display the amount of the target resource and the platform information of the second resource platform;

[0236] The page display module is specifically used to respond to the transfer confirmation operation triggered by the first object on the resource confirmation page, and to display the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through cross-resource management platforms.

[0237] In one exemplary embodiment, the resource transfer processing apparatus further includes a service invocation module;

[0238] The service invocation module is used to respond to the resource confirmation operation triggered by the first object on the resource transfer page for the input target resource, and to invoke the resource management service that matches the first resource platform, so that the resource management service responds to the transfer confirmation operation and transfers the target resource to the aggregation management platform.

[0239] In an exemplary embodiment, the service invocation module is specifically used to respond to a resource confirmation operation triggered by the first object on the resource transfer page for the target resource, obtain the domain name information to be verified that matches the resource confirmation operation; verify the domain name information to be verified by using preset accessible domain name information, and obtain the domain name verification result; and, if the domain name verification result indicates that the domain name verification is successful, invoke the resource management service that matches the first resource platform.

[0240] In an exemplary embodiment, the page display module is further configured to display on the transfer confirmation page the amount of available resources for the first object under the first resource platform, and the corresponding conversion amount of the target resource on the first resource platform.

[0241] In another exemplary embodiment, such as Figure 25 As shown, another resource transfer processing device is provided, including: a request processing module 2502, a page rendering module 2504, and a resource transfer processing module 2506, wherein:

[0242] Request processing module 2502 is used to receive an identification request initiated by the first object through scanning the resource receiving code on the first resource platform, and to identify the category to which the resource receiving code belongs;

[0243] The page rendering module 2504 is used to feed back the rendering parameters of the resource transfer page to the first resource platform when the resource receiving code belongs to the category of aggregation code, so that the first resource platform can display the resource transfer page in the application interface; the resource type of the second resource platform bound to the aggregation code is different from the resource type of the first resource platform.

[0244] The resource transfer processing module 2506 is used to transfer the target resource from the first resource platform to the aggregation management platform that provides the aggregation code, based on the resource transfer confirmation event initiated by the first object and according to the amount of the target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

[0245] In an exemplary embodiment, the request processing module is specifically used to obtain platform information that matches each management platform; for the platform information that matches each management platform, it performs information matching with the resource receiving code to obtain information matching results; and determines the category to which the resource receiving code belongs based on the information matching results.

[0246] In one exemplary embodiment, the platform information includes multiple platform splitting information;

[0247] The request processing module is specifically used to split the code information matched by the resource receiving code according to the preset splitting rules, and obtain multiple splitting information in sequence; for the multiple platform splitting information that match the platform information of each management platform, the module performs information matching on the multiple splitting information from back to front, and obtains the information matching result.

[0248] In an exemplary embodiment, the page rendering module is specifically used to, when the category to which the resource receiving code belongs is an aggregation code, search for a page rule script that matches the resource receiving code according to the category to which the resource receiving code belongs; determine the rendering parameters of the resource transfer page based on the page rule script, and feed back the rendering parameters of the resource transfer page to the first resource platform, so that the first resource platform displays the resource transfer page obtained by rendering the preset page according to the rendering parameters on the application interface.

[0249] In an exemplary embodiment, the page rendering module is specifically configured to: determine the target prefix information matching the resource receiving code according to the category to which the resource receiving code belongs; search for the platform rule script that has a mapping relationship with the target prefix information based on the mapping relationship between the platform rule script and platform information of each aggregation management platform; and determine the platform rule script that has a mapping relationship with the target prefix information as the page rule script that matches the resource receiving code.

[0250] In one exemplary embodiment, the resource transfer processing apparatus further includes a mapping relationship creation module;

[0251] The mapping relationship creation module is used to obtain the platform page and interface request rules of each aggregation management platform, as well as the platform information that matches each aggregation management platform; for each aggregation management platform, it encapsulates the platform page and interface request rules to obtain the platform rule script; and creates the mapping relationship between the platform rule script and the platform information.

[0252] In an exemplary embodiment, the resource transfer processing module is specifically used to determine the amount of target resources entered by the first object on the resource transfer page based on the resource transfer confirmation event initiated by the first object; and to transfer the target resources from the first resource platform to the aggregation management platform that provides the aggregation code according to the amount of the target resources and the identification information of the second object, so that the aggregation management platform transfers the target resources to the resource account of the second object on the second resource platform according to the identification information of the second object and the amount of the target resources.

[0253] In an exemplary embodiment, the resource transfer processing module is further configured to: obtain a resource transfer identifier matching the resource amount confirmation event based on the resource amount confirmation event initiated by the first object on the resource transfer page; determine resource transfer information matching the resource amount confirmation event; and associate and store the information association relationship between the resource transfer identifier and the resource transfer information; the resource transfer information includes at least the amount of the target resource; and send confirmation information carrying the resource transfer identifier back to the first resource platform so that the first resource platform displays the resource confirmation page.

[0254] The resource transfer processing module is specifically used to determine the resource transfer identifier to be identified that matches the resource transfer confirmation event initiated by the first object; to query the target resource transfer information associated with the resource transfer identifier to be identified based on the information association relationship between the resource transfer identifier and the resource transfer information; and to determine the amount of the target resource based on the target resource transfer information.

[0255] In an exemplary embodiment, the resource transfer processing module is specifically configured to: obtain the identification information of the first object and the platform information of the first resource platform based on a resource transfer confirmation event initiated by the first object; generate a target object identifier based on the identification information of the first object and the platform information of the first resource platform; initiate an information generation request matching the resource transfer confirmation event to the aggregation management platform according to the target object identifier, so that the aggregation management platform responds to the information generation request and generates a resource transfer identifier matching the information generation request; receive the resource transfer identifier generated by the aggregation management platform in response to the information generation request, and determine the resource transfer identifier as the resource transfer identifier matching the resource transfer confirmation event.

[0256] In one exemplary embodiment, a computer device is provided. This computer device can be a server or a terminal. In this embodiment, the computer device is described as a terminal as an example. Its internal structure diagram can be as follows: Figure 26As shown, the computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface 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 interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium 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 medium. The input / output interface is 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, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a resource transfer processing method. The display unit of the computer device is used to form a visually visible image. It 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.

[0257] In another exemplary embodiment, a computer device is provided, which can be a server or a terminal. This embodiment uses a server as an example for description, and its internal structure diagram can be as follows: Figure 27 As shown, the computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The database stores platform information matching each resource platform, page rule scripts, and other data related to the embodiments of this application. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a resource transfer processing method.

[0258] Those skilled in the art will understand that Figure 26 as well as Figure 27The 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.

[0259] In one exemplary 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-described method embodiments.

[0260] In one exemplary 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-described method embodiments.

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

[0262] It should be noted that the object information (including but not limited to object device information, object 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 object or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0263] 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.

[0264] 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.

[0265] 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 resource transfer processing, characterized in that, The method includes: In response to the first object scanning the resource receiving code of the second object through the first resource platform, if the resource receiving code is identified as an aggregation code by the cross-resource management platform, a resource transfer page provided by the cross-resource management platform is displayed on the application interface of the first resource platform; the resource type of the second resource platform to which the aggregation code is bound is different from that of the first resource platform. On the resource transfer page, the identification information of the second object and the amount of the target resource entered by the first object are displayed. The resource type of the target resource is the same as the resource type of the second resource platform. In response to the first object's confirmation operation for the input target resource, the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through the cross-resource management platform is displayed.

2. The method according to claim 1, characterized in that, The method further includes: In response to the resource confirmation operation triggered by the first object on the resource transfer page for the target resource, a resource confirmation page for the target resource is displayed; The resource confirmation page displays the amount of the target resource and the platform information of the second resource platform; The response to the first object's transfer confirmation operation for the input target resource displays the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through the cross-resource management platform, including: In response to the transfer confirmation operation triggered by the first object on the resource confirmation page, the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through the cross-resource management platform is displayed.

3. The method according to claim 2, characterized in that, The step of displaying a transfer confirmation page for the target resource in response to a resource confirmation operation triggered by the first object on the resource transfer page for the input target resource includes: In response to the resource confirmation operation triggered by the first object on the resource transfer page for the input target resource, a resource management service matching the first resource platform is invoked, so that the resource management service, in response to the transfer confirmation operation, transfers the target resource to the aggregation management platform.

4. The method according to claim 3, characterized in that, The response to the resource confirmation operation triggered by the first object on the resource transfer page for the input target resource, invoking a resource management service matching the first resource platform, includes: In response to the resource confirmation operation triggered by the first object on the resource transfer page for the target resource, obtain the domain name information to be verified that matches the resource confirmation operation; The domain name information to be verified is verified by pre-defined accessible domain name information to obtain the domain name verification result; If the domain name verification result indicates that the domain name verification is successful, the resource management service matching the first resource platform is invoked.

5. The method according to claim 2, characterized in that, The method further includes: The transfer confirmation page displays the amount of available resources for the first object on the first resource platform, as well as the corresponding conversion amount of the target resource on the first resource platform.

6. A method for resource transfer processing, characterized in that, The method includes: Receive an identification request initiated by the first object through scanning a resource receiving code on the first resource platform, and identify the category to which the resource receiving code belongs; When the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform displays the resource transfer page in the application interface; the resource type of the second resource platform to which the aggregation code is bound is different from the resource type of the first resource platform. Based on the resource transfer confirmation event initiated by the first object, the target resource is transferred from the first resource platform to the aggregation management platform that provides the aggregation code, according to the amount of target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

7. The method according to claim 6, characterized in that, The identification of the category to which the resource receiving code belongs includes: Obtain platform information that matches each management platform; For each management platform's information, which is matched with its corresponding resource receiving code, information matching results are obtained. The category to which the resource receiving code belongs is determined by the information matching results.

8. The method according to claim 7, characterized in that, The platform information includes information on the breakdown of multiple platforms; For each platform information matched with its respective management platform, the information is matched with the resource receiving code to obtain the matching results, including: The code information matched by the resource receiving code is split according to the preset splitting rules to obtain multiple splitting information in sequence; For each management platform, multiple platform-specific information segments are matched sequentially from back to front to obtain matching results.

9. The method according to claim 6, characterized in that, When the resource receiving code belongs to the category of aggregation code, the rendering parameters of the resource transfer page are fed back to the first resource platform, including: If the resource receiving code belongs to the category of aggregation code, then search for the page rule script that matches the resource receiving code according to the category to which the resource receiving code belongs; The rendering parameters of the resource transfer page are determined based on the page rule script, and the rendering parameters of the resource transfer page are fed back to the first resource platform so that the first resource platform can display the resource transfer page obtained by rendering the preset page according to the rendering parameters in the application interface.

10. The method according to claim 9, characterized in that, The step of searching for page rule scripts that match the resource receiving code according to its category includes: According to the category to which the resource receiving code belongs, determine the target prefix information that matches the resource receiving code; Based on the mapping relationship between the platform rule scripts and platform information of each aggregation management platform, find the platform rule scripts that have a mapping relationship with the target prefix information; The platform rule scripts that have a mapping relationship with the target prefix information are identified as the page rule scripts that match the resource receiving code.

11. The method according to claim 10, characterized in that, The methods for creating the mapping relationship between platform rule scripts and platform information for each of the aforementioned aggregation management platforms include: Obtain the platform page and interface request rules of each of the aforementioned aggregation management platforms, as well as the platform information that matches each of the aforementioned aggregation management platforms; For each of the aforementioned aggregation management platforms, the platform page and the interface request rules are encapsulated to obtain a platform rule script; Create a mapping relationship between the platform rule script and the platform information.

12. The method according to claim 6, characterized in that, The resource transfer confirmation event initiated by the first object, based on the amount of target resources entered by the first object on the resource transfer page, involves the first resource platform transferring the target resources to the aggregation management platform that provides the aggregation code, including: Based on the resource transfer confirmation event initiated by the first object, determine the amount of the target resource entered by the first object on the resource transfer page; According to the amount of the target resource and the identification information of the second object, the target resource is transferred from the first resource platform to the aggregation management platform that provides the aggregation code, so that the aggregation management platform transfers the target resource to the resource account of the second object on the second resource platform based on the identification information of the second object and according to the amount of the target resource.

13. The method according to claim 12, characterized in that, The method further includes: Based on the resource amount confirmation event initiated by the first object on the resource transfer page, a resource transfer identifier matching the resource amount confirmation event is obtained, resource transfer information matching the resource amount confirmation event is determined, and the information association relationship between the resource transfer identifier and the resource transfer information is associated and stored; the resource transfer information includes at least the amount of the target resource; The system sends a confirmation message carrying the resource transfer identifier back to the first resource platform, so that the first resource platform displays a resource confirmation page. The determination of the amount of the target resource entered by the first object on the resource transfer page based on the resource transfer confirmation event initiated by the first object includes: Based on the resource transfer confirmation event initiated by the first object, determine the resource transfer identifier to be identified that matches the resource transfer confirmation event; Based on the information association between the resource transfer identifier and the resource transfer information, the target resource transfer information associated with the resource transfer identifier to be identified is queried, and the amount of the target resource is determined based on the target resource transfer information.

14. The method according to claim 13, characterized in that, The step of obtaining a resource transfer identifier matching the resource amount confirmation event initiated by the first object on the resource transfer page includes: Based on the resource transfer confirmation event initiated by the first object, obtain the identification information of the first object and the platform information of the first resource platform; Based on the identification information of the first object and the platform information of the first resource platform, a target object identifier is generated; According to the target object identifier, an information generation request matching the resource transfer confirmation event is initiated to the aggregation management platform, so that the aggregation management platform responds to the information generation request and generates a resource transfer identifier matching the information generation request; The system receives the resource transfer identifier generated by the aggregation management platform in response to the information generation request, and identifies the resource transfer identifier as the resource transfer identifier that matches the resource transfer confirmation event.

15. A resource transfer and processing device, characterized in that, The device includes: The page display module is used to respond to the first object scanning the resource receiving code of the second object through the first resource platform. If the resource receiving code is identified as an aggregation code by the cross-resource management platform, the module displays a resource transfer page provided by the cross-resource management platform on the application interface of the first resource platform. The resource type of the second resource platform to which the aggregation code is bound is different from that of the first resource platform. The page display module is also used to display the identification information of the second object and the amount of the target resource input by the first object on the resource transfer page, wherein the resource type of the target resource is the same as the resource type of the second resource platform; The result display module is used to respond to the first object's transfer confirmation operation for the input target resource and display the resource transfer result of transferring the target resource to the aggregation management platform that provides the aggregation code through the cross-resource management platform.

16. A resource transfer and processing device, characterized in that, The device includes: The request processing module is used to receive an identification request initiated by the first object through scanning a resource receiving code on the first resource platform, and to identify the category to which the resource receiving code belongs; The page rendering module is used to feed back the rendering parameters of the resource transfer page to the first resource platform when the category of the resource receiving code is an aggregation code, so that the first resource platform displays the resource transfer page in the application interface; the resource type of the second resource platform to which the aggregation code is bound is different from the resource type of the first resource platform. The resource transfer processing module is used to transfer the target resource from the first resource platform to the aggregation management platform that provides the aggregation code, based on the resource transfer confirmation event initiated by the first object and according to the amount of the target resource entered by the first object on the resource transfer page. The resource type of the target resource is the same as the resource type of the second resource platform.

17. 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.

18. 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.

19. 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