Cross-border collection method, device, medium and program product

Abstract

The purpose of the present application is to provide a cross-border collection method, device, medium and program product. The present application associates the entry information and the contract order information in response to the association request initiated by the merchant for the entry information about the contract order information between the merchant and the overseas buyer through the cross-border system, obtains the first audit result information corresponding to the entry information, and sends the first audit result information to the channel system. Through the cross-border system, the second audit result information corresponding to the entry information provided by the channel system is obtained. If the second audit result information indicates that the entry information is passed, a corresponding settlement payment order is generated, and the digital currency corresponding to the entry amount information is transferred from the merchant's to-be-credited account to the merchant's available balance account based on the settlement payment order through the account system. It can be convenient for the merchant to quickly receive cross-border funds, reduce the cross-border fund transmission link, and reduce the cost of funds.

Description

[0001] This application claims priority to an earlier application (application number: CN202510077469.3, title: Cross-border payment methods, equipment, media and programs based on digital RMB, application date: 2025-01-17), the entire contents of which are incorporated herein by reference.

[0002] This application is a divisional application of "Cross-border payment methods, equipment, media and procedures based on digital RMB" (application number: 202610049791.X, application date: 2026-01-14). Technical Field

[0003] This application relates to the field of data processing, and more particularly to a technology for cross-border payment collection. Background Technology

[0004] In existing technologies, if an overseas payer makes a direct payment to a domestic bank, the payee information can only include the platform name and the platform's bank account number. This makes it impossible to identify which merchant the overseas payer is actually paying to. If manual identification is used, it is very inefficient, prone to errors, and lacks transparency, making it difficult to regulate. Summary of the Invention

[0005] One object of this application is to provide a method, device, medium, and program product for cross-border payment collection based on digital currency.

[0006] According to one aspect of this application, a method for cross-border payment collection based on digital currency is provided, applied to a payment platform, said payment platform including a cross-border system, a channel system, and an account system, the method comprising:

[0007] In response to a merchant's request to associate payment information with contract and order information between the merchant and an overseas buyer, the cross-border system associates the payment information with the contract and order information, obtains the first audit result information corresponding to the payment information, and sends the first audit result information to the channel system.

[0008] The cross-border system obtains the second audit result information corresponding to the billing information provided by the channel system.

[0009] If the second review result indicates that the payment information has been approved, a corresponding settlement payment order is generated, and the digital currency corresponding to the payment amount is transferred from the merchant's pending payment account to the merchant's available balance account through the account system based on the settlement payment order.

[0010] According to one aspect of this application, a computing device for cross-border payments based on digital currency is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to perform any of the methods described above.

[0011] According to one aspect of this application, a computer-readable storage medium is provided having a computer program stored thereon, characterized in that the computer program, when executed by a processor, implements the operation of any of the methods described above.

[0012] According to one aspect of this application, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the steps of any of the methods described above.

[0013] According to one aspect of this application, a computing device for cross-border payment collection based on digital currency is provided, the device comprising:

[0014] The module is used to respond to a merchant's request to associate the payment information with the contract order information between the merchant and the overseas buyer through the cross-border system, associate the payment information with the contract order information, obtain the first review result information corresponding to the payment information, and send the first review result information to the channel system.

[0015] The first and second modules are used to obtain the second audit result information corresponding to the accounting information provided by the channel system through the cross-border system;

[0016] The first and third modules are used to generate a corresponding settlement and payment order if the second review result information indicates that the payment information has been approved, and to transfer the digital currency corresponding to the payment amount information from the merchant's pending payment account to the merchant's available balance account through the account system based on the settlement and payment order.

[0017] Compared with existing technologies, this application, through the cross-border system, responds to a merchant's request to associate contract and order information between the merchant and the overseas buyer regarding the incoming payment information. It associates the incoming payment information with the contract and order information to obtain a first review result for the incoming payment information and sends this first review result to the channel system. The cross-border system then obtains a second review result for the incoming payment information provided by the channel system. If the second review result indicates that the incoming payment information has been approved, a corresponding settlement and payment order is generated. Based on this settlement and payment order, the account system transfers the digital currency corresponding to the incoming payment amount from the merchant's pending payment account to the merchant's available balance account. This facilitates faster receipt of cross-border funds for merchants, reduces cross-border fund transfer links, and lowers funding costs. Furthermore, by opening an umbrella wallet for each merchant, the information of payers and payees in cross-border scenarios is accurately reflected, which is more conducive to fund supervision and makes the fund flow transparent. Since a cross-border umbrella wallet is opened for each domestic merchant, when overseas payers make remittances, they can directly fill in the name of the domestic merchant as the payee and the account number as the cross-border umbrella wallet corresponding to the domestic merchant as the payee. From an information perspective, it is possible to directly identify which specific merchant the remittance is to. In addition, since the remittance information is filled in as a domestic merchant, the payee's name, payee's account number, and other information can be directly obtained in the incoming payment notification. The information is more transparent and more conducive to supervision. Moreover, by reducing the steps of transferring funds from overseas to domestic banks, the fund flow is shorter, which allows merchants to receive overseas payment notifications faster and reduces the transfer costs. In addition, funds are safer when they are directly in domestic banks, and the handling fees for transferring funds from overseas to domestic banks can be reduced, thus reducing costs and significantly improving the user experience when receiving cross-border payments. Attached Figure Description

[0018] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0019] Figure 1 This illustration shows a flowchart of a method for cross-border payment collection according to an embodiment of the present application;

[0020] Figure 2 This diagram illustrates a flowchart of an example cross-border payment collection method according to an embodiment of this application.

[0021] Figure 3 This diagram illustrates a method for opening a cross-border umbrella wallet, as provided in an embodiment of this application.

[0022] Figure 4 This diagram illustrates a computing device structure for cross-border payment collection according to one embodiment of the present application.

[0023] Figure 5 Exemplary systems that can be used to implement the various embodiments described in this application are shown;

[0024] Figure 6 A flowchart illustrating a method for cross-border payment collection according to an embodiment of this application is shown.

[0025] The same or similar reference numerals in the accompanying drawings represent the same or similar parts. Detailed Implementation

[0026] The present application will now be described in further detail with reference to the accompanying drawings.

[0027] In a typical configuration of this application, the terminal, the device of the service network, and the trusted party all include one or more processors (e.g., a central processing unit (CPU)), input / output interfaces, network interfaces, and memory.

[0028] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory. Memory is an example of computer-readable media.

[0029] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PCM), programmable random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0030] The devices referred to in this application include, but are not limited to, user equipment, network equipment, or devices composed of user equipment and network equipment integrated through a network. The user equipment includes, but is not limited to, any mobile electronic product capable of human-computer interaction (e.g., via a touchpad), such as smartphones and tablets. These mobile electronic products can use any operating system, such as Android or iOS. The network equipment includes an electronic device capable of automatically performing numerical calculations and information processing according to pre-set or stored instructions. Its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and embedded devices. The network equipment includes, but is not limited to, computers, network hosts, single network servers, multiple network server sets, or clouds composed of multiple servers. Here, a cloud consists of a large number of computers or network servers based on cloud computing, where cloud computing is a type of distributed computing, consisting of a virtual supercomputer composed of a group of loosely coupled computer sets. The network includes, but is not limited to, the Internet, wide area network, metropolitan area network, local area network, VPN network, wireless ad hoc network, etc. Preferably, the device can also be a program running on the user equipment, network device, or a device formed by integrating user equipment and network device, network device, touch terminal, or network device and touch terminal through a network.

[0031] Of course, those skilled in the art should understand that the above-described devices are merely examples, and other existing or future devices that are applicable to this application should also be included within the scope of protection of this application, and are hereby incorporated by reference.

[0032] In the description of this application, "multiple" means two or more, unless otherwise expressly and specifically defined.

[0033] Figure 1This document illustrates a flowchart of a method for cross-border payment collection according to an embodiment of this application. The method is used in a payment platform, which includes a cross-border system, a channel system, and an account system. The method includes steps S11, S12, and S13. In step S11, the cross-border system responds to a merchant's request to associate contract order information between the merchant and the overseas buyer regarding the incoming payment information. The system associates the incoming payment information with the contract order information to obtain a first review result information corresponding to the incoming payment information, and sends the first review result information to the channel system. In step S12, the cross-border system obtains a second review result information corresponding to the incoming payment information provided by the channel system. In step S13, if the second review result information indicates that the incoming payment information has been approved, a corresponding settlement payment order is generated. The account system then transfers the digital currency corresponding to the incoming payment amount from the merchant's pending payment account to the merchant's available balance account based on the settlement payment order.

[0034] In some embodiments, the cross-border payment collection targets cross-border B2B (business-to-business) trade scenarios, where cross-border transactions between domestic merchants and overseas buyer companies are based on long-term, continuous cooperation on orders, with overseas buyers making payments to merchants in installments (e.g., delayed or advanced by a certain period). This is not targeted at cross-border B2C (business-to-consumer) trade scenarios, where cross-border transactions between domestic merchants and overseas buyer individuals are single transactions, with overseas buyers making real-time payments to domestic merchants in equal amounts. In some embodiments, the payment platform includes a cross-border system, a channel system, and an account system. The cross-border system handles transactions related to cross-border transfers, the account system handles transactions related to merchant accounts, and the channel system handles transactions related to interactions between the payment platform and external institutions (e.g., banking institutions). The channel system acts as a hub for interaction between the payment platform and external institutions, internally receiving business requests from internal business systems and externally calling upon the systems of external institutions. In some embodiments, the cross-border system, channel system, and account system may reside on the same server, or they may reside on different servers. In some embodiments, the banking institutions in this application do not need to support the VA account system (i.e., Virtual Account, which is a form of account generated by a bank or payment institution for a customer, mainly used for cross-border payments and fund management).

[0035] In step S11, in response to the merchant's request to associate the payment information with the contract order information between the merchant and the overseas buyer, the cross-border system associates the payment information with the contract order information, obtains the first audit result information corresponding to the payment information, and sends the first audit result information to the channel system.

[0036] In some embodiments, the incoming payment information is generated by the payment platform based on receipt notification information from external institutions (e.g., banking institutions). This incoming payment information is used to record cross-border remittances from overseas buyers. The incoming payment information includes, but is not limited to, payer information (including but not limited to any information related to the payer), payee information (including but not limited to any information related to the payee), incoming payment amount information (including but not limited to any information related to the incoming payment amount), and incoming payment number information. Payer information includes, but is not limited to, payer account information, payer name information, payer address information, payer country information, and payer bank information. Payee information includes, but is not limited to, payee account information, payee name information, and payee address information. The incoming payment amount is the remittance amount for cross-border remittances by overseas buyers.

[0037] In some embodiments, reference Figure 6 The flowchart illustrates that merchants can initiate association requests for contract order information between themselves and overseas buyers on client-side platforms (including but not limited to web pages, applications, and mini-programs) to link the incoming payment information with the contract order information. The contract order information includes contract number information corresponding to one or more contract orders. In some embodiments, merchants can select one or more existing contract orders, or they can create one or more new contract orders and initiate association requests for the contract order information corresponding to these orders. In some embodiments, the incoming payment information can be associated with only one contract order, or it can be associated with multiple contract orders simultaneously. In some embodiments, the payment platform can allocate corresponding payment amount information to contract orders based on preset allocation rules (e.g., according to the order of order creation time or according to the size of the contract payment amount). In some embodiments, the contract order information also includes payment amount information corresponding to each contract order or corresponding allocation rules. For example, when a merchant selects the incoming payment information on the client-side and selects the contract orders to be associated, they can fill in the payment amount information corresponding to each contract order they expect to associate. The sum of the payment amounts corresponding to all contract orders associated with the incoming payment information must be less than or equal to the incoming payment amount corresponding to the incoming payment information. Alternatively, merchants can choose to omit the payment amount information and instead select the appropriate allocation rules.

[0038] In some embodiments, after associating the incoming payment information with the contract / order information, an audit can be performed based on the incoming payment information and the contract / order information to obtain the first audit result information corresponding to the incoming payment information. The cross-border system will use RPC (Remote Procedure Call) to call the channel system and send the first audit result information to the channel system. In some embodiments, this audit can be performed manually, and the corresponding first audit result information (i.e., the audit result information on the payment platform side corresponding to the incoming payment information) can be filled in. Alternatively, the payment platform (e.g., the cross-border system) can perform the audit and generate the corresponding first audit result information (i.e., the audit result information on the payment platform side corresponding to the incoming payment information).

[0039] In step S12, the second audit result information corresponding to the accounting information provided by the channel system is obtained through the cross-border system.

[0040] In some embodiments, the channel system provides the first review result information to the corresponding banking institution, for example, by calling an interface provided by the banking institution to send the first review result information to the banking institution. This application does not limit the specific method by which the channel system provides the first review result information to the banking institution. In some embodiments, refer to... Figure 6 As shown in the flowchart, the channel system also submits a fund disbursement application.

[0041] In some embodiments, the banking institution reviews the incoming payment information based on the first review result information. The banking institution can choose to refund to overseas or approve the payment, generating corresponding second review result information (i.e., the bank's review result information corresponding to the incoming payment information). This application does not limit the content of the second review result. Specifically, if the first review result information indicates that the incoming payment information is not approved by the payment platform, the banking institution does not need to review the incoming payment information and directly refunds the corresponding amount to overseas. If the first review result information indicates that the incoming payment information is approved by the payment platform, the banking institution needs to review the incoming payment information. If the review fails, the corresponding amount is refunded to overseas. In some embodiments, refer to... Figure 6 As shown in the flowchart, if the second review result includes approval, the banking institution can release the funds based on the payment platform's fund release application. After successful release, the credited amount will be deposited into the corresponding account on the payment platform.

[0042] In some embodiments, the channel system obtains the second review result information from the banking institution. For example, the banking institution calls an interface provided by the channel system to send the second review result information to the channel system. This application does not limit the specific method by which the channel system obtains the second review result information from the banking institution. In some embodiments, the channel system sends the second review result information to the cross-border system through a message middleware, for example, the message middleware could be RocketMQ, and this application does not limit the type of message middleware.

[0043] In step S13, if the second audit result information indicates that the payment information has been approved, a corresponding settlement payment order is generated, and the digital currency corresponding to the payment amount information is transferred from the merchant's pending payment account to the merchant's available balance account through the account system based on the settlement payment order.

[0044] In some embodiments, if the second review result indicates that the payment information has been approved by the bank, the cross-border system will continue to process the payment transaction. Under this payment transaction, a payment order of type "settlement" will be generated, namely a settlement payment order. Among the participants in the settlement payment order, the payer is the merchant's pending payment account, and the payee is the merchant's available balance account. In some embodiments, the cross-border system drives the account system through the clearing system. The account system uses double-entry bookkeeping for accounting. The merchant's pending payment account in the payment platform transfers the payment amount (i.e., the amount of digital currency deposited, i.e., the amount of digital currency credited to the merchant's pending payment account) to the merchant's available balance account in the payment platform. The amount transferred to the available balance account is a representation of the digital currency amount, and the actual digital currency remitted by the cross-border buyer remains with the corresponding bank. In some embodiments, the cross-border system will provide the corresponding payment review result to the merchant, for example, by calling the SMS system to notify the merchant of the corresponding payment review result via SMS. In some embodiments, merchants can withdraw funds from incoming amounts in their available balance account, while funds in the pending account cannot be withdrawn. For example, see reference... Figure 6 As shown in the flowchart, merchants can choose to link a bank account for the withdrawal process. The incoming amount is withdrawn from the available balance account to the bank account linked to the merchant through the payment platform.

[0045] refer to Figure 6The flowchart shown illustrates that this application obtains a payment notification from a bank corresponding to a merchant's digital currency-supporting umbrella wallet through the channel system. This payment notification is then provided to the cross-border system. The payment notification is generated by the bank based on overseas remittance information from an overseas buyer regarding digital currency to the umbrella wallet. The cross-border system obtains the corresponding payment information based on the payment notification, and the account system credits the corresponding amount to the merchant's pending payment account based on this payment information. The payment information includes payer information, payee information, and the amount to be credited for digital currency. Information; In response to a merchant's request to associate contract order information between the merchant and the overseas buyer regarding the incoming payment information, the cross-border system associates the incoming payment information with the contract order information, obtains the first review result information corresponding to the incoming payment information, and sends the first review result information to the channel system, wherein the first review result information is generated by the payment platform; The cross-border system obtains the second review result information corresponding to the incoming payment information provided by the channel system; if the second review result information indicates that the incoming payment information has been approved, a corresponding settlement payment order is generated, and... The account system transfers the digital currency corresponding to the incoming amount from the merchant's pending account to the merchant's available balance account based on the settlement payment order. The second audit result information is generated by the banking institution based on the first audit result information after auditing the incoming information. This facilitates merchants receiving cross-border funds quickly, reduces cross-border fund transfer links, and lowers funding costs. By opening an umbrella wallet for each merchant, the system accurately reflects the payee and payee information in cross-border scenarios, improving fund supervision and ensuring transparency in the fund flow. Because a cross-border umbrella wallet is opened for each domestic merchant, overseas payers can directly fill in the payee's name when remitting funds. This cross-border umbrella wallet uses the domestic merchant's name and payee account as its corresponding information. From an information perspective, it can directly identify which merchant the remittance is sent to. Furthermore, since the remittance information is filled in with the domestic merchant's name, the recipient's name and account number are directly provided in the incoming payment notification, making the information more transparent and easier to supervise. By reducing the steps of transferring funds from overseas to domestic banks, the fund flow is shorter, allowing merchants to receive overseas payment notifications faster and reducing transfer costs. In addition, funds held directly in domestic banks are safer and can reduce transaction fees for transferring funds back from overseas, lowering costs and significantly improving the user experience when receiving cross-border payments.

[0046] In some embodiments, the association request includes the invoice information and the contract order information; associating the invoice information and the contract order information to obtain the first audit result information corresponding to the invoice information includes: determining one or more contract orders from the order database of the payment platform based on the contract order information; associating at least one first contract order among the one or more contract orders with the invoice information; and auditing the invoice information and the first contract order associated therewith to obtain the first audit result information corresponding to the invoice information.

[0047] In some embodiments, the cross-border system can query one or more corresponding contract orders from the order database based on the contract number information in the contract order information. The contract order is generated based on one or more contracts between the merchant and the overseas buyer. The contract order includes, but is not limited to, contract number information, buyer and seller information, trading country / region, total order amount, currency, payment method, contract materials, contract product information (English name of product, Chinese name of product, quantity of product, unit price of product, unit of product), logistics information (logistics company name, shipping mode, freight forwarder name, actual shipping date, logistics method), creation time, and contract payment amount information, etc., which are not limited in this application. The contract payment amount information can be calculated based on the total order amount and the payment amount information already associated with the contract order. The cross-border system can associate all queried contract orders with the payment information, or select at least one first contract order from the queried contract orders that meets the requirements (e.g., the contract order matches the payment information) and associate it with the payment information. After associating the payment information with the contract orders, all associated first contract orders can be reviewed to obtain the first review result information corresponding to the payment information.

[0048] In some embodiments, associating at least one first contract order among the one or more contract orders with the billing information includes: filtering at least one first contract order from the one or more contract orders according to the billing information; for each first contract order among the at least one first contract order, associating the first contract order with the billing information by adding first association record information to the data record corresponding to the first contract order, wherein the first association record information includes the amount information in the billing information used to pay for the first contract order.

[0049] In some embodiments, the cross-border system can filter at least one matching first contract order from the one or more contract orders based on payer information, payee information, etc., in the invoice information, to avoid merchants selecting the wrong contract order and associating it with the wrong contract order. In some embodiments, after determining the first contract order that needs to be associated, the cross-border system can generate corresponding first association record information to complete the association between the first contract order and the invoice information. The first association record information includes, but is not limited to, invoice number information, contract number information, and payment amount information corresponding to each first contract order. The payment amount information corresponding to each first contract order can be determined based on the payment amount information or allocation rules selected by the merchant when initiating the association request, or it can be determined based on the allocation rules preset by the payment platform. In some embodiments, the payment amount information is usually less than or equal to the contract payment amount information, and the total amount of the payment amount information corresponding to each first contract order is less than or equal to the invoice amount information.

[0050] In some embodiments, for each of the at least one first contract orders, associating the first contract order with the payment information by adding first association record information to the data record corresponding to the first contract order, wherein the first association record information includes the amount information in the payment information used to pay the first contract order, includes: determining the payment amount information corresponding to each of the at least one first contract orders based on the payment information; adding first association record information to the data record corresponding to the first contract order based on the payment amount information corresponding to each of the at least one first contract orders, to associate the first contract order with the payment information, wherein the first association record information includes the amount information in the payment information used to pay the first contract order.

[0051] In some embodiments, if the contract order information includes payment amount information corresponding to each contract order, then the payment amount information corresponding to each first contract order is determined based on the contract order information. In some embodiments, if the contract order information includes corresponding allocation rules (e.g., the payment amount allocation ratio of each contract order, or the allocation order (e.g., sorted according to the order of order creation time or according to the size of the contract payment amount information), then the payment amount can be allocated based on the deposited amount in combination with the allocation rules, thereby determining the payment amount information corresponding to each first contract order. In some embodiments, if the merchant does not choose how to allocate, the payment platform can allocate the payment amount based on its preset allocation rules (e.g., equal distribution, or allocation according to the allocation order to determine the corresponding allocation ratio, etc.), thereby determining the payment amount information corresponding to each first contract order. After determining the payment amount information, corresponding first association record information can be added to associate the deposited information and the amount information in the deposited information used to pay for the first contract order with the first contract order. In some embodiments, the first associated record information may further include the review status of the incoming payment information (e.g., approved, unapproved, or pending review), so that the payment platform can determine whether the first associated record information is valid, as well as the contract amount to be paid corresponding to the first contract order.

[0052] In some embodiments, the step of reviewing the invoicing information and the associated first contract order to obtain the first review result information corresponding to the invoicing information includes: for each of the at least one first contract order, performing verification processing on the first contract order according to the first associated record information; if each of the at least one first contract order passes the verification, then the first review result information corresponding to the invoicing information is passed, otherwise the first review result information corresponding to the invoicing information is not passed.

[0053] In some embodiments, the first contract order includes contract payment amount information, which can be calculated based on the total order amount and valid (e.g., approved or pending) association record information corresponding to the first contract order before this association. If the payment amount information corresponding to the first association record information is less than or equal to the contract payment amount information, the first contract order passes the verification; otherwise, the first contract order fails the verification.

[0054] In some embodiments, the verification process for the first contract order based on the first associated record information includes: querying the historical associated record information of the first contract order from the order database; if the first contract order has at least one historical associated record information, then the sum of the payment amount information in the first associated record information and the payment amount information in each historical associated record information is taken as the total payment amount information of the first contract order; otherwise, the amount information in the first associated record information is taken as the total payment amount information of the first contract order; if the total payment amount information is less than or equal to the total order amount information of the first contract order, then the first contract order passes the verification; otherwise, the first contract order fails the verification. In some embodiments, the historical associated record information can be queried based on the contract number information of the first contract order, wherein the review status corresponding to the historical associated record information is "approved" or "under review". If there are historical associated record information with the review status condition, the total payment amount information of the first contract order is calculated by summing these historical associated record information with the payment amount information in the first associated record information. If not, the payment amount information in the first associated record information is taken as the total payment amount information of the first contract order. Then, it is determined whether the total payment amount is less than or equal to the total order amount of the first contract order. If so, the first contract order passes the verification; otherwise, the first contract order fails the verification.

[0055] In some embodiments, if all first contract orders corresponding to the incoming payment information pass verification, the first audit result information corresponding to the incoming payment information is considered passed; otherwise, the first audit result information corresponding to the incoming payment information is considered failed. In some embodiments, if the first audit result information is failed, the audit status of the first associated record information corresponding to each first contract order is changed from "under audit" to "failed audit." If the first audit result information is passed, the audit status of the first associated record information corresponding to each first contract order remains "under audit," and it needs to wait for the second audit result information generated by the banking institution. If the second audit result information indicates that the incoming payment information has been approved, the audit status of the first associated record information corresponding to each first contract order can be changed from "under audit" to "approved audit"; otherwise, the audit status of the first associated record information corresponding to each first contract order can be changed from "under audit" to "failed audit." In some embodiments, the banking institution can compare or conduct risk screening on the incoming payment information and the information in each first contract order to determine the corresponding second audit result information. For example, determining whether the payer and the contract buyer are the same, whether the trading country / region and the payment country / region are the same, whether the logistics information of the contract is authentic, and whether the total amount of payment information corresponding to each first contract order is less than or equal to the incoming payment amount information, etc.

[0056] In some embodiments, the method further includes: obtaining, through the channel system, a payment notification information provided by a banking institution corresponding to a digital currency-supporting umbrella wallet opened by the merchant; providing the payment notification information to the cross-border system, wherein the payment notification information is generated by the banking institution based on overseas remittance information regarding digital currency from an overseas buyer for the umbrella wallet; obtaining corresponding inflow information through the cross-border system based on the payment notification information; and crediting the corresponding inflow amount to the merchant's pending inflow account through the account system based on the inflow information, wherein the inflow information includes payer information, payee information, and inflow amount information regarding digital currency.

[0057] In some embodiments, the umbrella wallet opened by the merchant on the payment platform is a cross-border umbrella wallet that supports digital currencies (i.e., an umbrella wallet that supports cross-border transfers of digital currencies, and can receive digital currencies remitted from overseas). In some embodiments, the umbrella wallet is part of an umbrella wallet model, which together with the umbrella top wallet constitutes a digital currency settlement tool. The umbrella wallet model consists of an umbrella top wallet and an umbrella bottom wallet, where the umbrella top wallet is a physical wallet, and the umbrella bottom wallet is a wallet opened in the name of the umbrella top wallet. In the umbrella wallet model, banking institutions open corporate wallet sub-wallets for platform enterprises (e.g., payment platforms) and associate them with platform merchants one by one. When a merchant receives payment, the funds are automatically collected into the umbrella bottom wallet to complete the clearing and settlement. This model effectively lowers the threshold for merchants to enable digital currency payments, especially in cross-border payment scenarios, where a dedicated cross-border payment wallet is opened for each merchant as an umbrella bottom wallet. After the user remits funds, the funds are collected into the umbrella bottom wallet for clearing. In some embodiments, the cross-border umbrella wallet only allows digital currency payments, meaning that only cross-border buyers can use digital currency to remit funds from overseas to the merchant's umbrella wallet. In some embodiments, the cross-border umbrella wallet opened by the merchant on the payment platform needs to correspond to a banking institution. The payment platform can select one from among its partner banks when the merchant opens the umbrella wallet, or the merchant can select one from among its partner banks. In some embodiments, the umbrella wallet is not publicly accessible; the merchant can only view its identification information (e.g., wallet number) through the payment platform. Funds can only become available balances for the merchant after verification and release by the bank corresponding to the umbrella wallet.

[0058] In some embodiments, after a merchant provides the payee information of its cross-border umbrella wallet opened on a payment platform to an overseas buyer, the overseas buyer can use the payee information to make cross-border remittances to the umbrella wallet through channels such as CIPS (Cross-border Interbank Payment System) or SWIFT (Society for Worldwide Interbank Financial Telecommunications). That is, the overseas buyer transfers a certain amount of digital currency into the umbrella wallet from overseas. This application does not restrict the cross-border remittance channels.

[0059] In some embodiments, after an overseas buyer makes a cross-border remittance to a merchant's cross-border umbrella wallet, the corresponding remittance amount (i.e., the amount of digital currency remitted) will first be credited to the umbrella wallet. Subsequently, the payment platform and the bank institution corresponding to the umbrella wallet will review the incoming funds one after the other. After both have approved the review, the remittance amount will be transferred to the merchant's domestic bank account, enabling the merchant to complete the cross-border receipt of funds from the overseas buyer.

[0060] In some embodiments, the channel system obtains payment notification information from the bank corresponding to the merchant's umbrella wallet. Specifically, the bank can directly send payment notification information generated based on the overseas buyer's remittance information for the umbrella wallet to the channel system via an interface provided by the channel system. Alternatively, the bank can provide an interface to query payment notification information within a certain time period, allowing the channel system to retrieve all payment notification information within that time period by calling this interface at predetermined intervals (e.g., every predetermined time interval). Alternatively, the bank can write multiple overseas remittance information, including the overseas buyer's remittance information for the umbrella wallet, into a payment notification file at predetermined intervals (e.g., every predetermined time interval), and then the channel system retrieves the payment notification file from the bank at these predetermined time intervals. For example, the bank can upload the payment notification file to a file server (e.g., an SFTP server; SFTP (SSH File Transfer Protocol) is a secure file transfer protocol based on SSH). Shell (a secure file transfer protocol for secure remote login and file transfer) is used. This application does not limit the type of file server. The channel system then obtains the payment notification file from the file server. This application does not limit the specific method by which the channel system obtains the payment notification information from the banking institution. In some embodiments, after obtaining the payment notification file, the channel system parses the payment notification file to obtain the payment notification information. For example, the payment notification file may be of file type txt, with file encoding GB18030 and field separator "|". Each line in the payment notification file represents one payment notification message. This application does not limit the type of payment notification file.

[0061] In some embodiments, the fields in the payment notification information include message identifier, initiating direct participant bank, message time, message type, currency symbol, amount, cost bearer, direct participant bank number, indirect participant bank number, payer (bank) account number, payer (bank) name, payer (bank) opening bank number, payer's opening bank / non-bank payment institution name, receiving direct participant bank number, receiving person (bank) account number, receiving person (bank) name, receiving person (bank) opening bank number, remarks, etc. This application does not limit the field content of the payment notification information.

[0062] In some embodiments, the channel system sends the payment notification information to the cross-border system through a message middleware. For example, the message middleware can be RocketMQ (Rocket Message Queue), a distributed message middleware open-sourced by Alibaba and donated to Apache. It has advantages such as high performance, high reliability, high real-time performance, low latency, and massive message backlog. This application does not limit the type of message middleware.

[0063] In some embodiments, after receiving the payment notification information from the channel system, the cross-border system processes the notification information to obtain the corresponding payment information. Before processing the notification information, the cross-border system adds a distributed lock (e.g., a Redis (RemoteDictionary Server) distributed lock) to lock the notification for a preset duration (e.g., 3 minutes) to prevent data corruption caused by multiple machines executing the transaction. In some embodiments, the system also checks whether the transaction number corresponding to the payment notification is duplicated based on the transaction number between the payment platform and the bank. Only if it is determined that the transaction is not duplicated will subsequent operations continue. In some embodiments, the system uses SQL (Structured Query Language) to query the established mapping table using the bank's institution code and the payee's account information to obtain the merchant's identification information (e.g., merchant ID). In some embodiments, the channel system generates the corresponding payment transaction, and based on the payment information, generates corresponding transaction order information, payment order information, participant information, payment method information, etc., and saves them to the database. In some embodiments, the channel system sends the corresponding inflow request to the account system, which, according to payment clearing rules, uses double-entry bookkeeping to transfer the corresponding inflow amount (the inflow of digital currency, i.e., the amount credited to the merchant's cross-border umbrella wallet after the overseas buyer makes a cross-border remittance) from the umbrella wallet to the merchant's pending inflow account on the payment platform. The pending inflow account represents the digital currency amount; the actual digital currency remitted by the cross-border buyer remains with the corresponding bank. In some embodiments, after the inflow is completed, the cross-border system notifies the merchant of an incoming payment notification, for example, by calling the SMS system to notify the merchant of an incoming payment notification via SMS. The corresponding request parameters include, but are not limited to, the SMS template, mobile phone number, and parameters that need to be replaced in the SMS.

[0064] In some embodiments, obtaining the second audit result information from the bank side corresponding to the inflow information provided by the channel system through the cross-border system includes: generating a corresponding first audit result file based on the first audit result information through the channel system and providing it to the banking institution; enabling the banking institution to audit the inflow information based on the first audit result file and generate a corresponding second audit result file; obtaining the second audit result file from the banking institution through the channel system; obtaining the second audit result information from the bank side corresponding to the inflow information based on the second audit result file; and obtaining the second audit result information provided by the channel system through the cross-border system. In some embodiments, the channel system generates a corresponding first audit result file by tagging the received first audit result information with the current batch number (e.g., obtaining the maximum batch number of the day, and adding 1 to the batch number to get the current batch number). This first audit result file is generated based on all audit result information, including the first audit result information, within the current batch number. For example, the first audit result file is a txt file, with fields separated by "|". Each line in the file represents a single first audit result. The fields in the first audit result include, but are not limited to, the transaction number, audit result, payee name, organization code, and final clearing account. This application does not limit the type or content of the first audit result file. In some embodiments, the channel system provides the first audit result file to the banking institution. This can be done by calling an interface provided by the banking institution to send the first audit result file to the banking institution, or by placing the first audit result file in a designated directory on a file server, from which the banking institution obtains the first audit result file. This application does not limit the specific method by which the channel system provides the first audit result file to the banking institution. In some embodiments, the banking institution reviews the transaction information based on the first audit result file. The banking institution can choose to refund overseas or approve the transaction, generating a corresponding second audit result file. In some embodiments, the channel system obtains the second audit result file from the banking institution. For example, the banking institution sends the second audit result file to the channel system via an interface provided by the channel system, or the banking institution places the second audit result file in a designated directory on a file server, and the channel system obtains the second audit result file from the file server. This application does not limit the specific method by which the channel system obtains the second audit result file from the banking institution. In some embodiments, the channel system parses the second audit result file to obtain the second audit result information on the bank side corresponding to the accounting information, and sends the second audit result information to the cross-border system through a message middleware.For example, the file type of the second audit result file is txt, the field separator is "|", each line in the file content represents each second audit result, and the field content of the second audit result includes, but is not limited to, the entry serial number, audit result, etc. This application does not restrict the type and content of the second audit result file.

[0065] In some embodiments, the payer information includes payer name information and payer address information, and the payee information includes payee name information and payee address information; wherein, obtaining the corresponding payment information through the cross-border system based on the payment notification information includes: parsing the payment notification information through the cross-border system to obtain the corresponding payer field and payee field; and splitting the payer field and the payee field respectively to obtain payer name information, payer address information, payee name information, and payee address information. In some embodiments, because the payer's name and address information in the bank's payment notification are often in the same field without being split, and similarly, the payee's name and address information are also often in the same field without being split, the cross-border system can only obtain the corresponding payer and payee fields after parsing the payment notification. Therefore, it needs to use a method based on preset keywords or regular expressions to split the payer and payee fields separately to obtain the payer's name, payer's address, payee's name, and payee's address information. In some embodiments, the payer's name and payee's name information also need to be formatted separately to obtain formatted payer's name and payee's name information.

[0066] In some embodiments, the payer information further includes payer country information; wherein, obtaining the corresponding inflow information through the cross-border system based on the inflow notification information further includes any one of the following: parsing the inflow notification information through the cross-border system to obtain a bank international code field; splitting the character information of a preset number of digits in the bank international code field to obtain payer country information; and obtaining payer country information that matches the replaced payer address information after special character replacement through the cross-border system. In some embodiments, if the inflow notification information provided by the banking institution does not contain payer country information, the inflow notification information can be parsed first to obtain a bank international code field, and then the character information of a preset number of digits (e.g., the 5th and 6th digits) in the bank international code field can be split to obtain a two-digit country / region code, which can be used as the payer country information; or, after special character replacement of the payer address information obtained from the inflow notification information, the replaced payer address information can be matched with keywords in the "keyword and country / region mapping table". If a match is found, the two-digit code of the matching country / region information can be used as the payer country information.

[0067] In some embodiments, the payer information further includes payer bank information; wherein, obtaining the corresponding inflow information through the cross-border system based on the inflow notification information further includes any one of the following: parsing the inflow notification information through the cross-border system to obtain a bank international code field; querying to obtain the payer bank information corresponding to the bank international code field; parsing the inflow notification information through the cross-border system to obtain payer account information; and obtaining the payer bank information from the historical inflow notification information corresponding to the overseas seller based on the payer account information. In some embodiments, if the inflow notification information provided by the banking institution does not contain payer bank information, the inflow notification information can be parsed first to obtain the bank international code field, and then the payer bank information corresponding to the bank international code field can be obtained by querying the local basic data table, and used as the payer bank information corresponding to the inflow information; alternatively, the inflow notification information can be parsed first to obtain the payer account information, and then the payer bank information from the corresponding overseas seller's historical inflow notification information can be obtained based on the payer account information, and used as the payer bank information corresponding to the inflow information.

[0068] In some embodiments, the payment platform further includes a risk control system; wherein, the step of crediting the corresponding crediting amount to the merchant's pending crediting account through the account system based on the crediting information includes: performing risk screening on the payee information through the risk control system; if the risk screening is passed, crediting the corresponding crediting amount to the merchant's pending crediting account through the account system based on the crediting information. In some embodiments, the risk control system is used to handle business related to merchant risk and to control merchant risk. In some embodiments, the risk control system performs risk screening on at least one of the payee name, payee identification number, payment method code name, and payment method code identification number in the payee information in a designated list database; only if the risk screening is passed will the crediting amount corresponding to the crediting information be credited to the merchant's pending crediting account through the account system.

[0069] In some embodiments, obtaining the first audit result information corresponding to the receipt information further includes: performing transaction verification on the receipt information and parameter verification on the contract order information; if the receipt information passes the transaction verification and the contract order information passes the parameter verification, the first audit result information corresponding to the receipt information is obtained. In some embodiments, after associating the contract order information with the receipt information, it is necessary to first verify the transaction corresponding to the receipt information and verify the parameters corresponding to the contract order information. Only if both the transaction verification and parameter verification pass will the first audit result information on the payment platform side corresponding to the receipt information be obtained. Otherwise, the payment platform side does not need to audit the receipt information again and can directly determine that the receipt information has failed the audit on the payment platform side. In some embodiments, the transaction verification performed on the receipt information includes, but is not limited to, verifying whether the corresponding transaction of the receipt information is in the "contract to be associated" state. This example embodiment does not impose any special limitations on this. In some embodiments, parameter validation of contract order information includes, but is not limited to, validating whether the number of contracts corresponding to the billing information is less than or equal to a preset threshold for the number of associated contracts (e.g., 10 contracts) and validating whether the contracts corresponding to the billing information are in a "rejected" state. This example embodiment does not impose any special limitations on these aspects.

[0070] In some embodiments, the method further includes: performing a consistency check on the matching between the incoming payment information and the contract order information; wherein, obtaining the first audit result information corresponding to the incoming payment information if the incoming payment information passes the transaction verification and the contract order information passes the parameter verification includes: obtaining the first audit result information corresponding to the incoming payment information if the incoming payment information passes the transaction verification, the contract order information passes the parameter verification, and the matching between the incoming payment information and the contract order information passes the consistency check. In some embodiments, in addition to performing transaction verification on the incoming payment information and parameter verification on the contract order information, it is also necessary to perform a consistency check on the matching between the incoming payment information and the contract order information. Only if all three checks—transaction verification, parameter verification, and consistency check—pass will the first audit result information on the payment platform side corresponding to the incoming payment information be obtained. Otherwise, the payment platform side does not need to audit the incoming payment information again and can directly determine that the incoming payment information has failed the audit on the payment platform side. In some embodiments, the consistency verification of the matching between the receipt information and the contract order information includes, but is not limited to, verifying whether the currency of the transaction corresponding to the receipt information is consistent with the currency of the contract corresponding to the contract order information, verifying whether the amount of the transaction corresponding to the receipt information is consistent with the total amount of the contract corresponding to the contract order information, and verifying whether the institution of the transaction corresponding to the receipt information is consistent with the institution to which the contract corresponding to the contract order information belongs. This example embodiment does not impose any special limitations on this.

[0071] In some embodiments, obtaining the first audit result information corresponding to the payment information if the payment information passes the transaction verification, the contract order information passes the parameter verification, and the matching between the payment information and the contract order information passes the consistency verification includes: if the payment information passes the transaction verification, the contract order information passes the parameter verification, and the matching between the payment information and the contract order information passes the consistency verification, the risk control system performs risk screening on the payee information again; if the risk screening passes, the first audit result information corresponding to the payment information is obtained. In some embodiments, if all transaction verification, parameter verification, and consistency verification are passed, the risk control system will again conduct risk screening on at least one of the following in the payee information: payee name, payee ID number, payment method code name, and payment method code ID number, in a designated list database. Only if the risk screening is passed will the first review result information from the payment platform corresponding to the incoming payment information be obtained. If the business verification is not passed, no further review is required, and it can be directly determined that the incoming payment information has failed the review on the payment platform side. The purpose of conducting risk screening on the payee information again is to avoid the situation where the time of receiving the payment notification information and the time of associating the incoming payment information with the contract order information are not the same day. The list database may be updated, so another risk screening is required.

[0072] In some embodiments, obtaining the first audit result information corresponding to the payment information includes: automatically auditing the payment information based on the merchant information, payment information, and contract / order information provided by the channel system through the risk control system, and obtaining the first audit result information corresponding to the payment information. In some embodiments, the risk control system will automatically audit the payment information based on the merchant information, payment information, and contract / order information provided by the channel system, according to its own historical data statistics (e.g., the number of successful audits in the merchant's history) plus a preset list or preset rules, and obtain the first audit result information on the payment platform side corresponding to the payment information.

[0073] In some embodiments, the method further includes: if the second review result information indicates that the payment information is subject to a refund, freezing the payment amount in the merchant's pending payment account through the account system. In some embodiments, if the second review result information indicates that the payment information is subject to a refund initiated by the bank, the account system will use double-entry bookkeeping to record the transaction and first freeze the payment amount in the merchant's pending payment account.

[0074] In some embodiments, the method further includes: obtaining the refund status corresponding to the incoming amount from the channel system through the account system; if the refund status indicates a successful refund, deducting the incoming amount from the merchant's pending payment account; if the refund status indicates a failed refund, unfreezing the incoming amount in the merchant's pending payment account. In some embodiments, the banking institution provides the refund status corresponding to the incoming amount to the channel system, enabling the account system to obtain the refund status from the channel system. If the refund status indicates a successful refund, the account system will use double-entry bookkeeping to record the transaction and deduct the incoming amount from the merchant's pending payment account; if the refund status indicates a failed refund, the account system will use double-entry bookkeeping to record the transaction and unfreeze the incoming amount in the merchant's pending payment account.

[0075] In some embodiments, the payment platform further includes a merchant system; wherein the method further includes: responding to a merchant's request to open an umbrella wallet, generating corresponding wallet opening details through the merchant system, and sending the wallet opening details to the channel system; providing the wallet opening application document corresponding to the wallet opening details to the banking institution through the channel system, so that the banking institution generates a corresponding return file based on the wallet opening application document, obtaining the return file from the banking institution through the channel system, parsing the return file to obtain corresponding wallet opening result information, and providing the wallet opening result information to the merchant system; if the wallet opening result information indicates successful opening, binding the umbrella wallet's identifier information in the wallet opening result information with the merchant's identifier information through the merchant system, providing the merchant with the umbrella wallet's receiving account information, so that the overseas buyer can make overseas remittances based on the receiving account information. In some embodiments, the merchant system is used to process business related to merchant account opening. In response to a merchant initiating a request to open an umbrella wallet on the application page of the client (including but not limited to applications, web pages, mini programs, etc.), the client will send the request to the merchant system. After receiving the request, the merchant system generates a record with a status of pending reporting. The corresponding fields include but are not limited to merchant ID, merchant name, institution merchant number, institution account name, institution, reporting status, business type, creation time, modification time, etc. This application does not impose any restrictions on this. In some embodiments, after the reporting status is changed to "Pending Reporting," a scheduled task processes the records to be reported, generates corresponding wallet opening details, and sends these details to the channel system. During task processing, each record to be reported is processed individually, aggregating the merchant's information to generate the corresponding wallet opening details. This merchant information includes, but is not limited to, merchant ID, Chinese name, English name, function type, merchant type, MCC (Merchant Category Code), business license number, province code, city code, business address, merchant responsible person, merchant account opening contact person's name, merchant account opening contact person's email address, merchant account opening contact person's phone number, legal representative's name, and document type. This application does not impose any limitations on this. In some embodiments, after data processing is complete, the generated wallet opening details are sent to the channel system via an RPC call. After a successful call, the reporting status is changed to "Reporting in Progress."In some embodiments, the channel system writes multiple wallet opening details, including the wallet opening details, into the wallet opening application file and uploads the wallet opening application file to a designated directory on the file server. Each wallet opening details includes, but is not limited to, the merchant ID, merchant abbreviation, merchant full name, parent wallet (i.e., umbrella wallet) number, sub-wallet name, sub-wallet function type, merchant type, MCC code, business license number, province code, city code, business address, merchant responsible person, merchant account opening contact person's name, merchant account opening contact person's email, merchant account opening contact person's phone number, and signatory, etc., which are not limited in this application. In some embodiments, the channel system provides the wallet opening application file to a banking institution. For example, the channel system can send the wallet opening application file to the banking institution by calling the interface provided by the banking institution, or the channel system can upload the wallet opening application file to a designated directory on the file server, and then the banking institution can retrieve the wallet opening application file from the file server.

[0076] In some embodiments, the banking institution generates a corresponding response file (i.e., a wallet opening result file) based on the wallet opening application file obtained from the file server, and then uploads the response file to a designated directory on the file server. This response file includes, but is not limited to, the transaction number, the wallet number at the bottom of the transaction, the status, the result code, and the result description; this application does not impose any limitations on this. In some embodiments, the banking institution provides the response file to the channel system. For example, the banking institution sends the response file to the channel system by calling an interface provided by the channel system, or the banking institution uploads the response file to a designated directory on the file server, and then the channel system retrieves the response file from the file server. This application does not impose any limitations on the specific method by which the banking institution provides the response file to the channel system. In some embodiments, the channel system obtains the corresponding wallet opening result information by parsing the response file, and sends the wallet opening result information to the merchant system via asynchronous notification through a message middleware, such as RocketMQ. In some embodiments, the merchant system can also proactively query the channel system for the corresponding wallet opening result information. Proactive query and asynchronous notification form a combined approach to ensure information completeness. If the asynchronous notification is not sent to the merchant system due to an abnormal situation, the query function can still retrieve the wallet opening result.

[0077] In some embodiments, after obtaining the wallet opening result information, if the wallet opening result information indicates successful opening, the merchant system binds the umbrella wallet's identification information (e.g., umbrella wallet number) in the wallet opening result information with the merchant's identification information (e.g., merchant ID), and provides the merchant with the payment receiving account information of the umbrella wallet. This allows the merchant to view the payment receiving account information on the front-end page, enabling the merchant to send the payment receiving account information to overseas buyers, allowing overseas buyers to make cross-border remittances based on the payment receiving account information. The payment receiving account information includes, but is not limited to, the payment receiving account number (wallet number), recipient name, currency, bank name, account opening region, account opening address, bank international code, bank interbank code, etc., and this application does not impose any limitations on this.

[0078] In some embodiments, the method further includes: determining the bank institution corresponding to the umbrella wallet from among multiple banking institutions cooperating with the payment platform through the merchant system. In some embodiments, when a merchant initiates an umbrella wallet opening request, the merchant needs to select a bank institution from among multiple banking institutions cooperating with the payment platform displayed on the client (application, webpage, mini-program, etc.). Then, the client sends the identification information of the bank institution selected by the user to the merchant system, and the merchant system will use that bank institution as the bank institution corresponding to the merchant's currently opened overseas umbrella wallet. In some embodiments, when a merchant initiates an umbrella wallet opening request, the merchant system will automatically select a bank institution from among multiple banking institutions cooperating with the payment platform as the bank institution corresponding to the merchant's currently opened overseas umbrella wallet. For example, the merchant system determines a bank institution that matches the merchant's historical transaction profile information from among multiple banking institutions as the bank institution corresponding to the overseas umbrella wallet. Another example is that the merchant system selects a bank institution from among multiple banking institutions that the merchant has already linked a corresponding bank card to the payment platform as the bank institution corresponding to the overseas umbrella wallet.

[0079] In some embodiments, sending the wallet opening details information to the channel system includes: mapping the wallet opening details information to fields based on preset field rules of the bank institution corresponding to the umbrella wallet, and sending the mapped wallet opening details information to the channel system. In some embodiments, when the merchant system processes the data of the records to be reported to generate the corresponding wallet opening details information, it will map the field names and / or field values ​​of preset fields in the wallet opening details information according to the preset field mapping rules of the bank institution corresponding to the cross-border umbrella wallet, and then send the mapped wallet opening details information to the channel system. The preset fields include, but are not limited to, document type, merchant type, etc., and this application does not limit them.

[0080] In some embodiments, uploading the wallet opening application file corresponding to the wallet opening details information to the file server through the channel system includes: adding the current batch number to the wallet opening details information through the channel system, writing multiple wallet opening details information corresponding to the current batch number into the wallet opening application file, and uploading the wallet opening application file to the file server. In some embodiments, the channel system will batch package the wallet opening details information. Before batch packaging the wallet opening details information, a distributed lock (e.g., a Redis distributed lock) will be added to lock the wallet opening details information for a preset duration (e.g., 3 minutes). Then, the current maximum batch number will be obtained, the maximum batch number will be incremented by 1 to obtain the current batch number, and the wallet opening details information will be added with the current batch number. The number of details corresponding to each batch number has an upper limit, and the corresponding upper limit value can be preset. In some embodiments, the channel system processes the wallet opening details information of batches, processing each batch individually. Before processing, a distributed lock is added to lock the batch for a preset time. Then, all wallet opening details within the batch are retrieved and written into the wallet opening application file, updating the batch status to "sending". In some embodiments, the first line of the wallet opening application file records the file header content, including record identifier, sequence number, source file name, total number of details, batch / online identifier, data batch number, file processing type, and remarks. This application does not impose any limitations on this. Each line of data starting from the second line in the wallet opening application file represents one wallet opening detail. In some embodiments, the channel system uploads the wallet opening application file to a designated directory on the file server. If the transmission is normal, the batch status is updated to "sent". If the transmission is abnormal, the batch status is updated to "sent abnormal", and the reason for the abnormality is recorded. The abnormal batch will be regenerated and uploaded in the next task. In some embodiments, the channel system retrieves the return file at preset time intervals. For a batch currently being processed, the system assembles the file name of the return file corresponding to the batch based on the file name of the wallet opening application file corresponding to the batch. The system then retrieves the return file from a specified directory on the file server and parses the return file to obtain the wallet opening result information corresponding to one or more wallet opening details for the batch.

[0081] In some embodiments, providing the wallet opening result information to the merchant system includes: encrypting the identification information of the umbrella wallet in the wallet opening result information, and providing the encrypted wallet opening result information to the merchant system; wherein, binding the identification information of the umbrella wallet in the wallet opening result information with the merchant's identification information through the merchant system includes: obtaining the identification information of the umbrella wallet from the wallet opening result information through decryption processing by the merchant system; and binding the identification information of the umbrella wallet with the merchant's identification information. In some embodiments, after the channel system parses the return file to obtain the corresponding wallet opening result information, it will encrypt the identification information (umbrella wallet number) of the umbrella wallet in the wallet opening result information (for example, SM (Elliptic Curve Public Key Cryptography Algorithm) 4 symmetric encryption, where the SM4 key is encrypted and stored by SM2; this application does not limit the encryption method), and then provide the encrypted wallet opening result information to the merchant system. In some embodiments, after obtaining the wallet opening result information provided by the channel system, the merchant system needs to decrypt the wallet opening result information to obtain the umbrella wallet's identification information, and then bind the umbrella wallet's identification information with the merchant's identification information.

[0082] Figure 2 A flowchart illustrating an example of a cross-border payment collection method according to an embodiment of this application is shown.

[0083] like Figure 2As shown, the payment platform includes a cross-border system, a clearing system, an account system, and a channel system. Overseas buyers conduct TT (Telegraphic Transfer) transactions overseas based on the payee information of the cross-border umbrella wallet opened by the merchant. For electronic remittances, the bank corresponding to the cross-border umbrella wallet obtains the incoming payment notification file for the overseas remittance information and provides it to the channel system. The channel system parses the incoming payment notification file to obtain the corresponding incoming payment notification and pushes it to the cross-border system. The cross-border system generates a corresponding transaction record based on the incoming payment notification. Then, the risk control system conducts a risk screening of the payee. If the risk screening is passed, the account system will conduct account settlement based on the clearing system, and the corresponding incoming amount will be credited to the merchant's pending payment account. The cross-border system will then notify the merchant of an incoming payment notification. The merchant creates contract order information on the client and submits a request to the cross-border system to associate the contract order information with the incoming payment transaction. The cross-border system will conduct corresponding business verification based on the association request. After the business verification is passed, the payee will undergo another risk screening. If the risk screening is passed, a pre-approval will be conducted, and... The corresponding review results are notified to the channel system on a case-by-case basis. The channel system will then compile the order data in batches and provide it to the banking institution for review. The channel system will then obtain the bank's processing result file and notify the cross-border system of the corresponding bank's review result. If the bank's review is approved, the cross-border system will continue to process the incoming transaction. The account system will then clear the transaction based on the clearing system, transferring the corresponding incoming amount from the merchant's pending incoming account to the merchant's available balance account. If the bank chooses to refund directly overseas, the cross-border system will generate another incoming refund transaction under this incoming transaction, freezing the merchant's pending incoming account balance. The channel system will then provide the cross-border system with the corresponding bank's notification (refund successful or failed). The cross-border system will parse the bank's notification, and the account system will clear the transaction based on the clearing system. If the refund is successful, the merchant's pending incoming account balance will be deducted; if the refund fails, the merchant's pending incoming account balance will be unfrozen.

[0084] Figure 3 A flowchart illustrating an example of a method for opening a cross-border umbrella wallet according to an embodiment of this application is shown.

[0085] like Figure 3As shown, in response to a domestic merchant's application for opening a cross-border umbrella wallet, the merchant system sends the application to the channel system. The channel system then batch-packages the received application requests to generate corresponding application documents and sends them to the banking institution. The channel system polls the corresponding response file for the application document, parses the response file to obtain the corresponding account opening result, and notifies the merchant system of the result. The merchant system can also proactively query the account opening status and respond to the domestic merchant's request to view the account opening result. The cross-border system will then return the corresponding account opening result to the domestic merchant.

[0086] Figure 4 This diagram illustrates a computing device structure for cross-border payment collection according to an embodiment of this application. The payment platform includes a cross-border system, a channel system, and an account system. The computing device includes module 11, module 12, and module 13. Module 11, in response to a merchant's request to associate payment information with contract order information between the merchant and an overseas buyer, associates the payment information with the contract order information through the cross-border system, obtains a first review result information corresponding to the payment information, and sends the first review result information to the channel system. Module 12, through the cross-border system, obtains a second review result information corresponding to the payment information provided by the channel system. Module 13, if the second review result information indicates that the payment information has been approved, generates a corresponding settlement payment order and, through the account system, transfers the digital currency corresponding to the payment amount from the merchant's pending payment account to the merchant's available balance account based on the settlement payment order. Here, the... Figure 4 The specific implementation methods corresponding to the first module 11, the second module 12 and the third module 13 shown are the same as or similar to the specific embodiments of the aforementioned steps S11, S12 and S13, and therefore will not be repeated here. They are included here by reference.

[0087] In addition to the methods and devices described in the above embodiments, this application also provides a computer-readable storage medium storing computer code that, when executed, performs the method described in any of the preceding embodiments.

[0088] This application also provides a computer program product that, when executed by a computing device, performs the method described in any of the preceding claims.

[0089] This application also provides a computing device, the computing device comprising:

[0090] One or more processors;

[0091] Memory, used to store one or more computer programs;

[0092] When the one or more computer programs are executed by the one or more processors, the one or more processors cause the one or more processors to perform the method as described in any of the preceding methods.

[0093] Figure 5 Exemplary systems that can be used to implement the various embodiments described in this application are shown;

[0094] like Figure 5 As shown in some embodiments, system 300 can function as any of the devices described in each of the embodiments. In some embodiments, system 300 may include one or more computer-readable media having instructions (e.g., system memory or NVM / storage device 320) and one or more processors (e.g., one or more processors 305) coupled to the one or more computer-readable media and configured to execute the instructions to implement the module and thus perform the actions described in this application.

[0095] In one embodiment, the system control module 310 may include any suitable interface controller to provide any suitable interface to at least one of the processors 305 and / or any suitable device or component communicating with the system control module 310.

[0096] The system control module 310 may include a memory controller module 330 to provide an interface to the system memory 315. The memory controller module 330 may be a hardware module, a software module, and / or a firmware module.

[0097] System memory 315 can be used, for example, to load and store data and / or instructions for system 300. In one embodiment, system memory 315 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, system memory 315 may include double data rate type quad synchronous dynamic random access memory (DDR4 SDRAM).

[0098] In one embodiment, the system control module 310 may include one or more input / output (I / O) controllers to provide interfaces to the NVM / storage device 320 and (one or more) communication interfaces 325.

[0099] For example, NVM / storage device 320 may be used to store data and / or instructions. NVM / storage device 320 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable (one or more) non-volatile storage devices (e.g., one or more hard disk drives (HDDs), one or more optical disc drives (CDs), and / or one or more digital universal optical disc (DVD) drives).

[0100] NVM / storage device 320 may include storage resources that are physically part of a device on which system 300 is mounted, or that can be accessed by the device without necessarily being part of it. For example, NVM / storage device 320 may be accessed via a network through one or more communication interfaces 325.

[0101] One or more communication interfaces 325 may provide the system 300 with an interface to communicate over one or more networks and / or with any other suitable device. The system 300 may wirelessly communicate with one or more components of a wireless network in accordance with any of one or more wireless network standards and / or protocols.

[0102] In one embodiment, at least one of the processors 305 may be logically packaged with one or more controllers of the system control module 310 (e.g., memory controller module 330). In one embodiment, at least one of the processors 305 may be logically packaged with one or more controllers of the system control module 310 to form a system-in-package (SiP). In one embodiment, at least one of the processors 305 may be integrated with the logic of one or more controllers of the system control module 310 on the same die. In one embodiment, at least one of the processors 305 may be integrated with the logic of one or more controllers of the system control module 310 on the same die to form a system-on-a-chip (SoC).

[0103] In various embodiments, system 300 may be, but is not limited to, a server, workstation, desktop computing device, or mobile computing device (e.g., laptop computing device, handheld computing device, tablet computer, netbook, etc.). In various embodiments, system 300 may have more or fewer components and / or different architectures. For example, in some embodiments, system 300 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0104] In addition to the methods and devices described in the above embodiments, this application also provides a computer-readable storage medium storing computer code that, when executed, performs the method described in any of the preceding embodiments.

[0105] This application also provides a computer program product that, when executed by a computing device, performs the method described in any of the preceding claims.

[0106] This application also provides a computing device, the computing device comprising:

[0107] One or more processors;

[0108] Memory, used to store one or more computer programs;

[0109] When the one or more computer programs are executed by the one or more processors, the one or more processors cause the one or more processors to perform the method as described in any of the preceding methods.

[0110] It should be noted that this application can be implemented in software and / or a combination of software and hardware, for example, using an application-specific integrated circuit (ASIC), a general-purpose computer, or any other similar hardware device. In one embodiment, the software program of this application can be executed by a processor to implement the steps or functions described above. Similarly, the software program of this application (including related data structures) can be stored in a computer-readable recording medium, such as RAM memory, a magnetic or optical drive, a floppy disk, or similar devices. Furthermore, some steps or functions of this application can be implemented in hardware, for example, as circuitry that cooperates with a processor to perform the various steps or functions.

[0111] Furthermore, a portion of this application can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to this application through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0112] Communication media include media through which communication signals containing, for example, computer-readable instructions, data structures, program modules, or other data are transmitted from one system to another. Communication media can include guided transmission media (such as cables and wires (e.g., optical fibers, coaxial cables, etc.)) and wireless (unguided transmission) media capable of propagating energy waves, such as sound, electromagnetic, RF, microwave, and infrared. Computer-readable instructions, data structures, program modules, or other data can be embodied as modulated data signals in, for example, wireless media (such as carrier waves or similar mechanisms embodied as part of spread spectrum technology). The term "modulated data signal" refers to a signal whose one or more characteristics are altered or set in a manner that encodes information in the signal. Modulation can be analog, digital, or a hybrid modulation technique.

[0113] By way of example and not limitation, computer-readable storage media may include volatile and non-volatile, removable and non-removable media implemented by any method or technique for storing information such as computer-readable instructions, data structures, program modules or other data. For example, computer-readable storage media include, but are not limited to, volatile memories such as random access memory (RAM, DRAM, SRAM); and non-volatile memories such as flash memory, various read-only memories (ROM, PROM, EPROM, EEPROM), magnetic and ferromagnetic / ferroelectric memories (MRAM, FeRAM); and magnetic and optical storage devices (hard disks, magnetic tapes, CDs, DVDs); or other media now known or hereafter developed capable of storing computer-readable information / data for use by a computer system.

[0114] Herein, one embodiment of this application includes an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the apparatus is triggered to run a method and / or technical solution based on the foregoing embodiments of this application.

[0115] It will be apparent to those skilled in the art that this application is not limited to the details of the exemplary embodiments described above, and that this application can be implemented in other specific forms without departing from the spirit or essential characteristics of this application. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of this application is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within this application. No reference numerals in the claims should be construed as limiting the scope of the claims. Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in the apparatus claims may also be implemented by a single unit or device in software or hardware. The terms "first," "second," etc., are used to indicate names and do not indicate any particular order.

Claims

1. A method for cross-border payment collection, applied to a payment platform, said payment platform comprising a cross-border system, a channel system, and an account system, wherein, The method includes: In response to a merchant's request to associate payment information with contract and order information between the merchant and an overseas buyer, the cross-border system associates the payment information with the contract and order information, obtains the first audit result information corresponding to the payment information, and sends the first audit result information to the channel system. The cross-border system obtains the second audit result information corresponding to the billing information provided by the channel system. If the second review result indicates that the payment information has been approved, a corresponding settlement payment order is generated, and the digital currency corresponding to the payment amount is transferred from the merchant's pending payment account to the merchant's available balance account through the account system based on the settlement payment order.

2. The method according to claim 1, wherein, The association request includes the billing information and the contract / order information; The step of associating the payment information with the contract order information to obtain the first audit result information corresponding to the payment information includes: One or more contract orders are determined from the order database of the payment platform based on the contract order information; Associate at least one first contract order among the one or more contract orders with the accounting information; The invoice information and its associated first contract order are reviewed to obtain the first review result information corresponding to the invoice information.

3. The method according to claim 2, wherein, The step of associating at least one first contract order from the one or more contract orders with the accounting information includes: Based on the accounting information, at least one first contract order is selected from the one or more contract orders; For each of the at least one first contract order, a first association record is added to the data record corresponding to the first contract order to associate the first contract order with the billing information, wherein the first association record includes the amount information in the billing information used to pay for the first contract order.

4. The method according to claim 3, wherein, For each of the at least one first contract order, by adding first association record information to the data record corresponding to the first contract order, the first contract order is associated with the payment information. The first association record information includes the amount information in the payment information used to pay for the first contract order, including: Based on the invoicing information, determine the payment amount information corresponding to each of the at least one first contract orders; Based on the payment amount information corresponding to each of the at least one first contract orders, a first association record is added to the data record corresponding to the first contract order to associate the first contract order with the billing information. The first association record includes the amount information in the billing information used to pay for the first contract order.

5. The method according to claim 3 or 4, wherein, The step of reviewing the receipt information and its associated first contract order to obtain the first review result information corresponding to the receipt information includes: For each of the at least one first contract order, the first contract order is verified based on the first associated record information; If all first contract orders in at least one first contract order pass the verification, then the first audit result information corresponding to the accounting information is passed; otherwise, the first audit result information corresponding to the accounting information is not passed.

6. The method according to claim 5, wherein, The step of verifying the first contract order based on the first associated record information includes: The system queries the historical associated records of the first contract order from the order database. If the first contract order has at least one historical associated record, the total payment amount of the first associated record is the sum of the payment amount information in the first associated record and the payment amount information in each historical associated record. Otherwise, the amount information in the first associated record is used as the total payment amount of the first contract order. If the total payment amount is less than or equal to the total order amount of the first contract order, then the first contract order passes the verification; otherwise, the first contract order fails the verification.

7. The method according to any one of claims 1 to 6, wherein, The method includes: The system obtains the settlement notification information provided by the banking institution corresponding to the umbrella wallet that supports digital currency opened by the merchant, and provides the settlement notification information to the cross-border system. The settlement notification information is generated by the banking institution based on the overseas remittance information of the overseas buyer regarding digital currency for the umbrella wallet. The cross-border system obtains the corresponding payment information based on the payment notification information, and the account system credits the corresponding payment amount to the merchant's pending payment account based on the payment information. The payment information includes payer information, payee information, and payment amount information related to digital currency.

8. The method according to claim 7, wherein, The step of obtaining the second audit result information corresponding to the payment information provided by the channel system through the cross-border system includes: The channel system generates a corresponding first audit result file based on the first audit result information and provides it to the banking institution, so that the banking institution audits the incoming payment information based on the first audit result file and generates a corresponding second audit result file. The channel system obtains the second audit result file from the banking institution, obtains the second audit result information corresponding to the incoming payment information based on the second audit result file, and obtains the second audit result information provided by the channel system through the cross-border system.

9. The method according to claim 7, wherein, The payer information includes the payer's name and address information, and the payee information includes the payee's name and address information; The step of obtaining the corresponding payment information through the cross-border system based on the payment notification information includes: The cross-border system parses the payment notification information to obtain the corresponding payer and payee fields; The payer field and the payee field are split into fields to obtain payer name information, payer address information, payee name information, and payee address information.

10. The method according to claim 7, wherein, The payer information also includes the payer's country information; The step of obtaining the corresponding payment information through the cross-border system based on the payment notification information also includes any one of the following: The cross-border system parses the payment notification information to obtain the bank's international code field; the system then splits the pre-defined number of characters in the bank's international code field to obtain the payer's country information. After the payer's address information is replaced with special characters by the cross-border system, the payer's country information that matches the replaced payer's address information is obtained.

11. The method according to claim 7, wherein, The payer information also includes the payer's bank information; The step of obtaining the corresponding payment information through the cross-border system based on the payment notification information also includes any one of the following: The cross-border system parses the payment notification information to obtain the bank's international code field; and queries to obtain the payer's bank information corresponding to the bank's international code field. The cross-border system parses the payment notification information to obtain the payer's account information; based on the payer's account information, the payer's bank information is obtained from the historical payment notification information corresponding to the overseas seller.

12. A computing device for cross-border payment collection, comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method as described in any one of claims 1 to 11.

13. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method as described in any one of claims 1 to 11.

14. 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 as described in any one of claims 1 to 11.

Images