Transaction switching method and device based on multi-service system, equipment and medium
Through abstracting the core elements of trading business and building multi-business systems, the problems of poor universality and compatibility of existing trading transfer systems are solved, compatibility and resource interoperability of different types of trading services are achieved, and flexibility of trading transfer is improved. Sex and extensibility.
Patent Information
- Application Number
- CN202410947068.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-15
- Publication Date
- 2024-11-12
AI Technical Summary
Due to its strong specialization, the existing transaction transfer system cannot be compatible with different types of transaction services, resulting in poor universality and compatibility, making it difficult to achieve the integration of different types of transaction services.
By highly abstracting the core elements of multiple transaction services and building a multi-business system, it realizes the interconnection of different types of resources, supports the combined transaction of different types of accounts and resources, and performs permission management, and extracts the user's opening in the organization The basic concept model of the account to the merchant's payment of resources, realizing transactions between the transaction initiator and the acceptance party.
Improve the universality and compatibility of the transaction transfer system, so that the multi-service system can be compatible with multiple transaction services, realize the combined payment of heterogeneous resources, multi-order merged payment and Yigou resources, and improve the flexibility of system processing. Sex and extensibility.
Smart Images

Figure CN118941283A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of transaction payment, and in particular to a transaction transfer method, device, equipment and medium based on a multi-business system. Background Art
[0002] There are various businesses in the field of transaction business, such as card-based transaction business, cardless transaction business, barcode transaction business, ticket transaction business, points transaction business, etc. In all of the above businesses, a transfer system needs to be established to establish business transfers between some institutions and other institutions. Different businesses have different core exchange elements, which requires the establishment of different transfer systems for different businesses. For example, the core exchange element of the card-based transaction business is the bank card ID, and the core exchange element of the points transaction business is the points acceptor ID and user ID. The points transaction business cannot reuse the transfer system of the card-based transaction business. Similarly, the card-based transaction business cannot reuse the transfer system of the points transaction business. The special nature of the transfer system makes it incompatible with different types of transaction businesses, and it is even more difficult to realize the integration of different types of transaction businesses. The existing transaction transfer system has poor versatility and compatibility. Summary of the invention
[0003] The embodiments of the present application provide a transaction transfer method, device, equipment and medium based on a multi-business system, which can improve the versatility and compatibility of transaction transfer.
[0004] In a first aspect, an embodiment of the present application provides a transaction transfer method based on a multi-business system, which is applied to a multi-business system, the method comprising: receiving a transaction request, the transaction request comprising at least one transaction sub-request, each transaction sub-request comprising a payer element, a payee element, an account acceptor element, an account element and a transaction resource element, and at least one of the account acceptor element, the account element and the transaction resource element in different transaction sub-requests in the same transaction request is different; according to the transaction request, determining the amount of acceptance resources, generating an acceptance request, the acceptance request comprising the payer element, the payee element, the account element and the amount of acceptance resources; sending the acceptance request to the account acceptor indicated by the account acceptor element, so that the account acceptor completes the transaction according to the acceptance request.
[0005] In a second aspect, an embodiment of the present application provides a transaction switching device based on a multi-business system, which is applied to a multi-business system. The device includes: a receiving module, which is used to receive a transaction request, the transaction request includes at least one transaction sub-request, each transaction sub-request includes a payer element, a payee element, an account acceptor element, an account element and a transaction resource element, and at least one of the account acceptor element, the account element and the transaction resource element in different transaction sub-requests in the same transaction request is different; an information processing module, which is used to determine the acceptance resource amount and generate an acceptance request based on the transaction request, the acceptance request includes a payer element, a payee element, an account element and the acceptance resource amount; a sending module, which is used to send an acceptance request to the account acceptor indicated by the account acceptor element, so that the account acceptor completes the transaction according to the acceptance request.
[0006] In a third aspect, an embodiment of the present application provides a transaction transfer device based on a multi-business system, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the transaction transfer method based on a multi-business system of the first aspect is implemented.
[0007] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having computer program instructions stored thereon, and when the computer program instructions are executed by a processor, the transaction transfer method based on a multi-business system of the first aspect is implemented.
[0008] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the transaction transfer method based on a multi-business system of the first aspect.
[0009] The embodiment of the present application provides a transaction transfer method, device, equipment and medium based on a multi-business system. The multi-business system can receive a transaction request in a standard format. The transaction request may include at least one transaction sub-request. The format of the transaction sub-request is unified and standardized. The transaction sub-request may include a payee element, a payee element, an account acceptor element, an account element and a transaction resource element. The multi-business platform can determine the amount of resources that need to be accepted with the account acceptor for this transaction according to the transaction request, and generate an acceptance request including the payee element, the payee element, the account element and the acceptance resource amount and send it to the account acceptor so that the account acceptor completes the transaction. Through the payee element, the payee element, the account acceptor element, the account element and the transaction resource element, the core elements of various types of transaction services can be highly abstracted, and through the payee element, the payee element, the account element and the acceptance resource amount, the core elements that the account acceptor needs to know of various types of transaction services can be highly abstracted, so that the multi-business system and the transaction parties of various types of transaction services can interact through standard message requests, realize the business expression of various types of transaction services, and improve the versatility and compatibility of transaction transfer. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0011] Figure 1 A schematic diagram of an example of establishing different switching systems for different services in the related art;
[0012] Figure 2 A schematic diagram of an example of a multi-service system provided in an embodiment of the present application;
[0013] Figure 3 A flowchart of a transaction transfer method based on a multi-business system provided in one embodiment of the present application;
[0014] Figure 4 A schematic diagram of an example of a transaction process based on a multi-business system provided in an embodiment of the present application;
[0015] Figure 5 A schematic diagram of another example of a transaction process based on a multi-business system provided in an embodiment of the present application;
[0016] Figure 6 A flowchart of a transaction transfer method based on a multi-business system provided in another embodiment of the present application;
[0017] Figure 7A schematic diagram of an example of a verification process provided in an embodiment of the present application;
[0018] Figure 8 A schematic diagram of an example of a risk control verification calling verification plug-in provided in an embodiment of the present application;
[0019] Fig. 9 A schematic diagram of another example of a multi-service system provided in an embodiment of the present application;
[0020] Fig.10 A schematic diagram of the structure of a transaction switching device based on a multi-business system provided in one embodiment of the present application;
[0021] Fig.11 A schematic diagram of the structure of a transaction switching device based on a multi-business system provided in one embodiment of the present application. DETAILED DESCRIPTION
[0022] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended only to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application. It should be noted that the acquisition, storage, use, and processing of information and data in the embodiments of the present application are authorized by users or relevant agencies, in compliance with the relevant provisions of national laws and regulations.
[0023] There are various businesses in the transaction business field, such as card-present transaction business, cardless transaction business, barcode transaction business, ticket transaction business, points transaction business, etc. In all of the above businesses, a transfer system needs to be established to establish business transfers between some institutions and other institutions. Different businesses have different core exchange elements, which requires different transfer systems to be established for different businesses. For example, the core exchange element of the card-present transaction business is the bank card ID, and the core exchange element of the points transaction business is the points acceptor ID and user ID. The points transaction business cannot reuse the transfer system of the card-present transaction business. Similarly, the card-present transaction business cannot reuse the transfer system of the points transaction business. Figure 1 A schematic diagram of an example of establishing different switching systems for different services in the related art, such as Figure 1As shown, in the card-present transaction business scenario, the acquiring institution needs to interact with the card-present transaction transfer system through the card-present transaction transfer system; in one type of card-free transaction business scenario, the merchant or acquiring institution needs to access the card-present transaction transfer system through the card-present transaction transfer system A, and then interact with the card-present transaction transfer system through the card-present transaction transfer system; in another type of card-free transaction business scenario, the payment institution needs to interact with the card-present transaction transfer system B, and a network bridge structure can be established between the card-free transaction transfer system B and the card-present transaction transfer system; in the barcode transaction business scenario, the acquiring structure needs to interact with the barcode payment institution through the barcode transaction transfer system; in the points transaction business scenario, the channel party needs to interact with the issuer of the points through the points transaction transfer system; in the ticket transaction business scenario, the channel party needs to interact with the issuer of the ticket through the ticket transaction transfer system. It can be seen that the transfer systems of different transaction businesses are specialized, and the specialized nature of the transfer system makes it incompatible with different types of transaction businesses, and it is even more difficult to achieve integrated business with different types of transaction businesses. The existing transaction transfer system has poor versatility and compatibility.
[0024] The present application provides a transaction transfer method, device, equipment, system, storage medium and computer program product based on a multi-business system. By highly abstracting the core elements of various transaction businesses and adding type elements that can reflect different transaction businesses, a multi-business system that can be compatible with various transaction businesses is constructed. Any transaction business can be refined into a basic conceptual model of "a user purchases a certain commodity at a certain merchant, and pays a certain amount of a certain category of resources in a specific unit from the user's account opened in an institution to the merchant" to complete the transaction between the transaction initiator and the transaction acceptor. The multi-business system can realize the interconnection and interoperability of different types of resources, support combined transactions of different types of accounts and different types of resources, and realize the management, maintenance and use of permissions of different types of businesses. The multi-business system can be used as a transaction transfer system for any transaction business, improving the versatility and compatibility of the transaction transfer system.
[0025] To facilitate understanding, a brief description is first given of the multi-service system provided in the embodiment of the present application. Figure 2 A schematic diagram of an example of a multi-service system provided in an embodiment of the present application, such as Figure 2As shown, the merchant / acquirer 111, payment institution 112, barcode acquirer 113 and other acquirers 114 as transaction initiators can access the unified access terminal 12 through their respective normalized standard interfaces, and then access the multi-business system 13 through the unified access terminal 12. The user 115 as the transaction initiator can access the multi-business system 13 through the digital cashier platform 14, which can be a platform for e-commerce platforms to conduct payment transactions. The card issuer 151, payment institution 152, points issuer 153, ticket issuer 154 and other resource issuers 155 as account acceptors can access the unified access terminal 16 through their respective normalized standard interfaces, and then access the multi-business system 13 through the unified access terminal 16.
[0026] The transaction transfer method, device, equipment, storage medium and computer program product based on a multi-business system provided by the present application are described below respectively.
[0027] A first aspect of the present application provides a transaction transfer method based on a multi-business system. The transaction transfer method is applied to the multi-business system, that is, the transaction transfer method can be executed by the multi-business system. Figure 3 A flowchart of a transaction transfer method based on a multi-business system provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the transaction transfer method based on the multi-business system may include steps S201 to S203.
[0028] In step S201, a transaction request is received.
[0029] The transaction request may be initiated by a digital cash register platform, a merchant / acquirer, a payment institution, a barcode acquirer or other acquirer, which is not limited here. However, no matter which party initiates the transaction request, the message format of the transaction request received by the multi-business system is consistent. The transaction request is used to request a transaction service. The transaction request may correspond to a transaction, but this transaction may include one order or multiple orders, that is, the transaction request may correspond to one payment order or more than two payment orders, thereby realizing the combined payment of multiple orders. For a transaction, a user may use one type of account or a combination of multiple types of accounts. The transaction request may include at least one transaction sub-request. The transaction sub-request may be divided according to the different account types of the account in which the user conducts the transaction, or according to the different orders, which is not limited here.
[0030] Each transaction sub-request may include a payee element, a payee element, an account acceptor element, an account element, and a transaction resource element.
[0031] The payer element is used to characterize the relevant information of the payer. In some examples, the payer element may include, but is not limited to, the payer identification, the payer personal information, and the payer supplementary information. The payer identification is used to identify the payer, such as the payer identification may include the payer ID. The payer personal information is used to characterize the personal identity of the payer, such as the payer personal information may include the payer's name. The payer supplementary information may include other information of the payer that needs to be supplemented, which can be set according to specific scenarios, needs, etc. For example, the payer supplementary information may include the payer's location information, and the location information may be Global Positioning System (GPS) information, but is not limited to this.
[0032] The payee element is used to represent the relevant information of the payee. In the embodiment of the present application, the payee may include the merchant in the transaction, etc. In some examples, the payee element may include but is not limited to the payee identification, the payee order identification and the payee supplementary information. The payee identification is used to identify the payee, such as the payee identification may include the payee ID. The payee order identification includes the order identification associated with the payee in this transaction, and the payee order identification is unique. The payee supplementary information may include other information of the payee that needs to be supplemented, such as the payee supplementary information may include the location information of the payee, and the location information may be GPS information, but is not limited to this. In some examples, the transaction sub-request in the transaction request may include a group of payee elements or more than two groups of payee elements, a group of payee elements may represent a payee, and different groups of payee elements represent different payees, that is, a transaction may correspond to more than two payees, thereby realizing the collection of multiple payees in multi-order payment.
[0033] The account acceptor element is used to characterize the information of the acceptor of the transaction resource. In some examples, the account acceptor element may include but is not limited to the account acceptor type and the account acceptor identifier. The account acceptor type is used to characterize the type of the account acceptor. For example, the account acceptor type may include a card issuing bank, a payment institution, a points issuer, a ticket issuer, etc., which are not limited here. The account acceptor identifier is used to identify the account acceptor. For example, the account acceptor identifier may include the account acceptor ID. The account element may include but is not limited to the account type and the account identifier. The account type is used to characterize the type of the account. For example, the account type may include a card account, a barcode payment account, a points account, a ticket account, etc. The account identifier is used to identify the account. For example, the account identifier may include an account ID. The account ID corresponds to the account type. The account ID can be implemented as a card number, a barcode account ID, a points account ID, a ticket code, etc. The transaction resource element is used to characterize the transaction resource. For example, transaction resource elements may include but are not limited to transaction resource quantity, transaction resource unit, transaction resource type, transaction standard resource type and transaction standard resource conversion ratio. In some examples, transaction resource elements may also include the total transaction resource amount or the total transaction standard resource amount. The transaction resource quantity is the number of transaction resources of the transaction resource type corresponding to the transaction sub-request. The transaction resource unit also corresponds to the transaction resource type. For example, if the transaction resource type is RMB, the transaction resource unit is RMB. The transaction standard resource type represents the type of transaction resource as a standard. When the transaction is settled, the transaction resource of the transaction standard resource type is generally used for settlement. The transaction standard resource conversion ratio is the conversion ratio of the transaction resource of the transaction resource type to the transaction resource of the transaction standard resource type.
[0034] In some examples, the transaction sub-request may also include an acceptor element and / or an order element; the acceptor element is applied to transactions in a three-party architecture, which includes a payee, a payee and an acceptor, and the acceptor element is used to characterize the acceptor, which may be a third-party payment institution, etc., and is not limited here; for example, the acceptor element may include an acceptor identifier, the acceptor identifier may include an acceptor ID, and the acceptor element may also include an acceptor type; the order element may be used to characterize relevant information of an order, for example, the order element may include order content, etc.
[0035] At least one of the account acceptor element, account element, and transaction resource element in different transaction sub-requests in the same transaction request is different. In the case where the transaction request includes multiple transaction sub-requests, the transaction request may be a request for a combined transaction of multiple types of resources, that is, the multi-business system may support combined transactions through multiple types of resources such as payment cards, third-party payment accounts, points, tickets, etc. Correspondingly, the account acceptor element, account element, and transaction resource element in different transaction sub-requests in the transaction request may be different. For example, if a transaction request includes three transaction sub-requests, the first transaction sub-request is for payment using a payment card, the second transaction sub-request is for payment using a third-party payment account, and the third transaction sub-request is for payment using points, then the account acceptor indicated by the account acceptor element in the first transaction sub-request is the issuing bank of the payment card, the account indicated by the account element is the payment card, and the payment resource type indicated by the transaction resource element is the amount, the account acceptor indicated by the account acceptor element in the second transaction sub-request is the third-party payment institution, the account indicated by the account element is the third-party payment account, and the payment resource type indicated by the transaction resource element is the amount, and the account acceptor indicated by the account acceptor element in the third transaction sub-request is the points issuer, the account indicated by the account element is the points account, and the payment resource type indicated by the transaction resource element is points. The transaction resource type and transaction resource amount in the transaction resource element in the transaction sub-request can be determined according to the input of the user who triggers the transaction request, that is, the user can select the type and amount of resources used in the transaction.
[0036] By extracting payer elements, payee elements, account acceptor elements, account elements and transaction resource elements, transaction requests are standardized, so that in different business scenarios, multiple business systems can complete transaction transfers based on transaction requests in the same standard format.
[0037] In some examples, the transaction request may include a payment request and a return request. In the case where the transaction request is a payment request, the implemented transaction is a payment transaction. In the case where the transaction request is a return request, the implemented transaction is a return transaction. The transaction transfer method based on a multi-business system in the embodiment of the present application can support partial or full returns in a transaction.
[0038] In step S202, the acceptance resource amount is determined according to the transaction request, and an acceptance request is generated.
[0039] The acceptance resource quantity is the number of resources of the transaction resource type corresponding to the account acceptor element of this transaction. In the case where the transaction resource type in the transaction resource element of the transaction request corresponds to the account acceptor type in the account acceptor element, the transaction resource quantity in the transaction resource element of the transaction request can be determined as the acceptance resource quantity. In the case where the transaction resource type in the transaction resource element of the transaction request does not correspond to the account acceptor type in the account acceptor element, the transaction resource quantity in the transaction resource element of the transaction request can be converted to the quantity of transaction resources corresponding to the account acceptor type in the account acceptor element, and the converted quantity of transaction resources corresponding to the account acceptor type is determined as the acceptance resource quantity. The acceptance request may include the payee element, the payee element, the account element and the acceptance resource quantity. For specific content, please refer to the relevant description in the above embodiment, which will not be repeated here.
[0040] In step S203, an acceptance request is sent to the account acceptor indicated by the account acceptor element, so that the account acceptor completes the transaction according to the acceptance request.
[0041] After receiving the acceptance request, the account acceptor can determine the payer, the payee, the account involved in the transaction, and the amount of resources required for the transaction to be accepted, and then complete the acceptance based on the payer, the payee, the account involved in the transaction, and the amount of resources required for the transaction to be accepted. After completing the acceptance, the account acceptor can also send an acceptance response to the multi-business system, and the multi-business system can determine whether the acceptance is successful or failed based on the acceptance response, so as to facilitate subsequent settlement.
[0042] In some examples, a transaction subrequest has a subtransaction identifier and a transaction family identifier. The subtransaction identifiers of different transaction subrequests are different, and the transaction family identifiers of transaction subrequests belonging to the same transaction request are the same. The subtransaction identifier is used to identify the subtransaction indicated by the transaction subrequest, and the subtransaction identifier is unique to the transaction subrequest. The transaction family identifier is used to identify the transaction indicated by the transaction request to which the transaction subrequest belongs, and transaction subrequests with the same transaction family identifier belong to the same transaction. After receiving the acceptance response of the acceptance request corresponding to each transaction subrequest, the multi-business system can record the subtransaction identifier and transaction family identifier of the transaction subrequest to record this subtransaction.
[0043] By extracting the payer elements, payee elements, account elements and acceptance resource volume, the acceptance request is standardized, so that in different business scenarios, multiple business systems can complete transaction transfers based on the same standard format of acceptance requests. Standardized transaction requests and acceptance requests allow multiple business systems to access transaction parties involved in various types of transaction businesses and realize the transfer of various types of transaction businesses.
[0044] In an embodiment of the present application, a multi-business system can receive a transaction request in a standard format, and the transaction request may include at least one transaction sub-request. The format of the transaction sub-request is unified and standardized. The transaction sub-request may include a payee element, a payee element, an account acceptor element, an account element, and a transaction resource element. The multi-business platform can determine the amount of resources that need to be accepted with the account acceptor for this transaction based on the transaction request, and generate an acceptance request including the payee element, the payee element, the account element, and the acceptance resource amount and send it to the account acceptor so that the account acceptor completes the transaction. Through the payee element, the payee element, the account acceptor element, the account element, and the transaction resource element, the core elements of various types of transaction services can be highly abstracted, and through the payee element, the payee element, the account element, and the acceptance resource amount, the core elements that the account acceptor needs to know of various types of transaction services can be highly abstracted, so that the multi-business system and the transaction parties of various types of transaction services can interact through standard message requests, realize the business expression of various types of transaction services, and improve the versatility and compatibility of transaction transfer.
[0045] Moreover, by setting various elements in standardized transaction requests, the standardized circulation of non-monetary resources such as points and tickets can be realized. Non-monetary resources such as points and tickets can be converted into monetary resources for settlement based on transaction resource elements to ensure the payment and settlement of transactions. In addition to the conversion of non-monetary resources to monetary resources, the conversion of non-monetary resources to other non-monetary resources, as well as the conversion of monetary resources to other monetary resources can also be realized, realizing the network circulation of heterogeneous resources and the transaction circulation of resources of multiple standard resource types. In addition, the transaction transfer method based on a multi-business system in the embodiment of the present application can also realize the combined payment of heterogeneous resources, the combined payment of multiple orders, and the account separation and settlement of easy-to-buy resources, thereby improving the flexibility and scalability of the system processing of transaction services.
[0046] In some embodiments, a combined payment of heterogeneous resources is performed, and correspondingly, the transaction request includes multiple transaction sub-requests, each transaction sub-request corresponds to an account type, and an acceptance request corresponds to a transaction sub-request. The above step S202 can be specifically refined as follows: according to the first transaction sub-request, determine the acceptance resource amount of the first transaction sub-request, and generate the acceptance request corresponding to the first transaction sub-request; when the acceptance response corresponding to the first transaction sub-request is received and the transaction standard resource amount of the first transaction sub-request does not reach the total transaction standard resource amount indicated by the transaction request, determine the acceptance resource amount of the second transaction sub-request according to the second transaction sub-request, and generate the acceptance request corresponding to the second transaction sub-request, until the acceptance response corresponding to the Nth transaction sub-request is received and the sum of the transaction standard resource amounts of the first N transaction sub-requests reaches the total transaction standard resource amount indicated by the transaction request, N is a positive integer greater than or equal to 2.
[0047] In the case where a transaction request includes multiple transaction sub-requests, the multi-business system may receive the transaction sub-requests in sequence, and process the next transaction sub-request after processing one transaction sub-request. The multi-business system receives the first transaction sub-request, determines the acceptance resource amount of the first transaction sub-request based on the first transaction sub-request, generates the first acceptance request, and sends the acceptance request to the account acceptor indicated by the first transaction sub-request. The account acceptor indicated by the first transaction sub-request performs acceptance processing based on the acceptance request, and feeds back the first acceptance response to the multi-business system, which indicates that the acceptance is successful. The multi-business system determines whether the accepted transaction standard resource amount has reached the total transaction standard resource amount of this transaction. If not, the multi-business system receives the second transaction sub-request, determines the acceptance resource amount of the second transaction sub-request based on the second transaction sub-request, generates the second acceptance request, and sends the acceptance request to the account acceptor indicated by the second transaction sub-request. And so on, until the account acceptor indicated by the Nth transaction sub-request feeds back an acceptance response, and the amount of accepted transaction standard resources reaches the total amount of transaction standard resources for this transaction, then other transaction sub-requests in this transaction request will no longer be received.
[0048] In some examples, the transaction request is triggered by the transaction platform, and the transaction platform can be implemented as an e-commerce platform, which is not limited here. When the multi-business system receives the acceptance response corresponding to the Nth transaction sub-request and the sum of the transaction standard resource amounts of the first N transaction sub-requests reaches the total transaction standard resource amount indicated by the transaction request, the multi-business system sends a transaction notification to the transaction platform that triggered the transaction request, and the transaction notification is used to notify the transaction platform that the transaction has been successful. The transaction notification has a sub-transaction identifier and a transaction family identifier, and the transaction family identifier of the transaction notification is the same as the transaction family identifier of the transaction request. The transaction notification can be regarded as the N+1th sub-transaction in the transaction indicated by the transaction request, but the N+1th sub-transaction is mainly used to notify the transaction platform so that the transaction platform can align information with the multi-business platform, and no new resource deduction will be generated. The sub-transactions corresponding to the N sub-transaction requests and the N+1th sub-transaction corresponding to the transaction notification can be associated through the transaction family identifier, and the multi-business system will record the transaction family identifier and sub-transaction identifier of the N+1 sub-transaction to facilitate subsequent settlement through the transaction family identifier.
[0049] For ease of understanding, the transaction transfer method based on a multi-business system in an embodiment of the present application is explained here by taking the combined payment of heterogeneous resources as an example. Figure 4 A schematic diagram of an example of a transaction process based on a multi-business system provided in an embodiment of the present application. In this example, after a user places an order through a trading platform, he selects a payment card, a third-party payment account, and a communication points combination payment to complete a payment of 200 yuan. Figure 4 As shown, the transaction process may include steps a1 to a24.
[0050] In step a1, the user initiates a payment order to the trading platform. The total amount of the payment order is 200 yuan.
[0051] In step a2, the transaction platform calls up the digital cashier platform.
[0052] In step a3, the user enters the payment amount of the payment card into the digital cash register platform. The payment amount of the payment card is 50 yuan.
[0053] In step a4, the digital cash register platform sends the first transaction sub-request to the multi-business system. In the first transaction sub-request, the account acceptor indicated by the account acceptor element is the issuing bank of the payment card, the account indicated by the account element is the payment card, the total amount of transaction standard resources indicated by the transaction resource element, that is, the total amount is 200 yuan, the transaction resource amount of the sub-transaction indicated by the transaction resource element is 50 yuan, the transaction resource type and transaction standard resource type indicated by the transaction resource element are RMB, and the transaction standard resource conversion ratio indicated by the transaction resource element is 1:1.
[0054] In step a5, the multi-business system sends a first acceptance request to the issuing bank of the payment card according to the first transaction sub-request. The acceptance resource amount in the acceptance request is 50 yuan.
[0055] In step a6, the multi-service system receives an acceptance response sent by the issuing bank of the payment card. The acceptance response indicates that the acceptance is successful.
[0056] In step a7, the multi-business system records the sub-transaction identifier TransId1 and the transaction family identifier TransFamilyId of the first sub-transaction.
[0057] In step a8, the multi-service system sends a transaction response to the digital cash register platform, indicating that the amount to be paid for this transaction is RMB 150.
[0058] In step a9, the user enters the payment amount of the third-party payment account into the digital cash register platform. The payment amount of the third-party payment account is 90 yuan.
[0059] In step a10, the digital cash register platform sends a second transaction sub-request to the multi-business system. In the second transaction sub-request, the account acceptor indicated by the account acceptor element is a third-party payment institution, the account indicated by the account element is a third-party payment account, the total amount of transaction standard resources indicated by the transaction resource element, that is, the total amount is 200 yuan, the transaction resource amount of the sub-transaction indicated by the transaction resource element is 90 yuan, the transaction resource type and transaction standard resource type indicated by the transaction resource element are RMB, and the transaction standard resource conversion ratio indicated by the transaction resource element is 1:1.
[0060] In step a11, the multi-business system sends a second acceptance request to the issuing bank of the payment card according to the second transaction sub-request. The acceptance resource amount in the acceptance request is 90 yuan.
[0061] In step a12, the multi-service system receives an acceptance response sent by the issuing bank of the payment card. The acceptance response indicates that the acceptance is successful.
[0062] In step a13, the multi-business system records the sub-transaction identifier TransId2 and the transaction family identifier TransFamilyId of the second sub-transaction.
[0063] In step a14, the multi-business system sends a transaction response to the digital cash register platform, indicating that the amount to be paid for this transaction is 60 yuan.
[0064] In step a15, the user enters the payment amount of points into the digital cash register platform. The payment amount is 6000 points, the conversion ratio of points to money is 100:1, and the payment amount corresponding to 6000 points is 60 yuan.
[0065] In step a16, the digital cash register platform sends a third transaction sub-request to the multi-business system. In the third transaction sub-request, the account acceptor indicated by the account acceptor element is the communication points issuer, the account indicated by the account element is a points account, the total amount of transaction standard resources indicated by the transaction resource element, that is, the total amount is 200 yuan, the transaction resource amount of the sub-transaction indicated by the transaction resource element is 6000 points, the transaction resource type and transaction standard resource type indicated by the transaction resource element are RMB, and the transaction standard resource conversion ratio indicated by the transaction resource element is 100:1.
[0066] In step a17, the multi-business system sends a first acceptance request to the issuing bank of the payment card according to the third transaction sub-request. The acceptance resource amount in the acceptance request is 6000 points.
[0067] In step a18, the multi-service system receives the acceptance response sent by the communication credit issuer. The acceptance response indicates that the acceptance is successful.
[0068] In step a19, the multi-business system records the sub-transaction identifier TransId3 and the transaction family identifier TransFamilyId of the third sub-transaction.
[0069] In step a20, the multi-business system sends a transaction response to the digital cash register platform. The multi-business system converts the points into money according to the conversion ratio of points to money, and obtains that the payment amount of the third sub-transaction is 60 yuan. The amount to be paid for this transaction is calculated to be 0 yuan, and the transaction response indicates that the amount to be paid for this transaction is 0 yuan.
[0070] In step a21, the multi-business system sends a transaction notification to the transaction platform, which indicates that the amount to be paid for this transaction is 0 yuan, and 200 yuan has been paid.
[0071] In step a22, the multi-business system records the sub-transaction identifier TransId4 and the transaction family identifier TransFamilyId of the fourth sub-transaction. It should be noted that the notification to the trading platform is regarded as the fourth sub-transaction here, but the fourth sub-transaction is only a notification for the convenience of settlement of the trading platform, and no new payment amount is generated.
[0072] In step a23, the transaction platform feeds back a transaction notification response to the multi-business system.
[0073] In step a24, the multi-business system sends a transaction completion notification to the digital cash register platform. The transaction completion notification indicates that the transaction is completed.
[0074] For other specific contents of the above steps a1 to a24, reference may be made to the relevant descriptions in the above embodiments, which will not be repeated here.
[0075] In the case where the transaction resource type in the transaction sub-request is different from the transaction standard resource type, in order to facilitate settlement, the transaction resource amount corresponding to the transaction resource type needs to be converted into the transaction standard resource amount corresponding to the transaction standard resource type, especially for non-monetary resources such as points. The account acceptor of non-monetary resources such as points can open a standard resource account in advance to facilitate the transfer of the transaction standard resource amount in the standard resource account to the account of the payee. The transaction resource elements include transaction resource amount, transaction resource type, transaction standard resource type and transaction standard resource conversion ratio. In the case where the transaction resource type in the transaction sub-request is different from the transaction standard resource type, the multi-business system converts the transaction resource amount in the transaction sub-request into the transaction standard resource amount corresponding to the transaction standard resource type according to the transaction standard resource conversion ratio; the transaction is completed according to the converted transaction standard resource amount using the standard resource account pre-set by the account acceptor indicated by the account acceptor element in the transaction sub-request.
[0076] In some cross-border transaction scenarios, it is necessary to convert two transaction standard resources, one of which is a foreign transaction standard resource and the other is a domestic transaction standard resource. In the conversion of the two transaction standard resources, one transaction standard resource is used as an intermediate conversion transaction standard resource, and the other is used as a final conversion transaction standard resource. The account acceptor of the cross-border transaction can sign a pre-conversion contract with the multi-business system in advance, and the multi-business system pre-stores the pre-conversion contract. The pre-conversion contract may include the pre-transaction standard resource type and the pre-transaction standard resource conversion ratio. The pre-transaction standard resource type is the intermediate conversion transaction standard resource type, and the pre-transaction standard resource conversion ratio is the intermediate conversion transaction standard resource conversion ratio. The transaction resource elements in the transaction sub-request include the transaction resource quantity, transaction resource type, transaction standard resource type, and transaction standard resource conversion ratio. The above step S202 can be specifically refined as follows: when the transaction resource type in the transaction sub-request is different from the transaction standard resource type and the account acceptor indicated by the account acceptor element in the transaction sub-request has a pre-conversion contract, the multi-business system converts the transaction resource amount in the transaction request into the pre-transaction standard resource amount corresponding to the pre-transaction standard resource type according to the pre-transaction standard resource conversion ratio; converts the pre-transaction standard resource amount into the transaction standard resource amount corresponding to the transaction standard resource type in the transaction sub-request, and determines the converted transaction standard resource amount as the acceptance resource amount.
[0077] For example, if a user wishes to use the bank points of country A1 to complete payment on the e-commerce platform of country A2, the bank of country A1 may sign a pre-conversion contract with the multi-business platform in advance, and the pre-transaction standard resource type in the pre-conversion contract is the transaction standard resource type of country A1, and the pre-transaction standard resource conversion ratio in the pre-conversion contract is the conversion ratio of the bank points of country A1 to the transaction resources of the transaction standard resource type in country A1. The multi-business system may convert the bank points of country A1 into the transaction standard resource amount of the transaction standard resource type of country A1 according to the pre-transaction standard resources, and then convert the transaction standard resource amount of the transaction standard resource type of country A1 into the transaction standard resource amount of the transaction standard resource type of country A2, and determine the transaction standard resource amount of the transaction standard resource type of country A2 as the acceptance resource amount to generate an acceptance request.
[0078] In some embodiments, the multi-business system can also realize the conversion of transaction resources of two transaction resource types through transaction resources of another transaction resource type. The transaction resource elements may include a first transaction standard resource type, a first transaction standard resource conversion ratio, a second transaction standard resource type, and a second transaction standard resource conversion ratio. The first transaction standard resource type corresponds to the first transaction standard resource conversion ratio, and the second transaction standard resource type corresponds to the second transaction standard resource conversion ratio. The above step S202 can be specifically refined as follows: according to the first transaction standard resource conversion ratio, the transaction resource amount in the transaction sub-request is converted into the first transaction standard resource amount corresponding to the first transaction standard resource type; according to the second transaction standard resource conversion ratio, the first transaction standard resource amount is converted into the second transaction standard resource amount corresponding to the second transaction standard resource type, and the second transaction standard resource amount is determined as the acceptance resource amount to generate an acceptance request.
[0079] For ease of understanding, the transaction transfer method based on a multi-business system in an embodiment of the present application is explained below using the conversion of points and airline miles through RMB amounts as an example. Figure 5 A schematic diagram of another example of a transaction process based on a multi-business system provided in an embodiment of the present application. In this example, a user requests a third-party payment institution to convert bank points into airline miles, such as Figure 5 As shown, the transaction process may include steps b1 to b9.
[0080] In step b1, the user initiates an exchange to a third-party payment institution, which is the acceptor in this example.
[0081] In step b2, the third-party payment institution sends a transaction request to the multi-business system, which is used to request to exchange 100 bank points for airline miles.
[0082] In step b3, the multi-business system sends a transfer acceptance request to the points issuing bank. The transfer acceptance request is used to request to transfer 100 bank points out of the user's bank points account. The bank is the payer in this example.
[0083] In step b4, the points issuing bank feeds back a transfer acceptance response to the multi-business system. The transfer acceptance response indicates that the bank points transfer is successful.
[0084] In step b5, the multi-business system converts the transaction resources. Specifically, the first transaction standard resource type is RMB, and the first transaction standard resource conversion ratio is 100:1, that is, 100 bank points can be converted into 1 RMB, and the second transaction standard resource type is mileage, and the second transaction standard resource conversion ratio is 1:500, that is, 1 RMB can be converted into 500 miles.
[0085] In step b6, the multi-service system sends a transfer-in acceptance request to the airline. The transfer-in acceptance response is used to request that the converted 500 miles be transferred to the user's account at the airline. The airline is the payee in this example.
[0086] In step b7, the airline company feeds back a transfer-in acceptance response to the multi-service system. The transfer-in acceptance response indicates that the mileage transfer-in is successful.
[0087] In step b8, the multi-service system sends a transaction response to the third-party payment institution. The transaction response indicates that the transaction is successful.
[0088] In step b9, the third-party payment structure displays the transaction result of successful transaction to the user.
[0089] For other specific contents of the above steps b1 to b9, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.
[0090] In some embodiments, after receiving a transaction request, the transaction can be verified first, and after the verification is passed, the subsequent transaction process can be carried out. Various verification functions can be implemented through flexible verification plug-ins, and comprehensive management can be performed from multiple aspects such as the circulation capacity of resources, the circulation capacity of the account acceptor, the circulation capacity of the payer, and the circulation capacity of the payee to ensure transaction security. The verification plug-in adopts unified standard input parameters and output parameters, and the call of the verification plug-in is also standardized. In the case of functional updates in multiple business systems, the updated functions can be implemented by adding new plug-ins. The newly added plug-ins will not affect the original business function logic, and the flexible expansion of transaction business can be achieved by plugging and unplugging plug-ins.
[0091] Figure 6 This is a flowchart of a transaction transfer method based on a multi-business system provided in another embodiment of the present application. Figure 6 and Figure 3 The difference is that Figure 6 The transaction transfer method based on the multi-business system shown may also include step S204, Figure 3 Step S202 in the above example can be specifically broken down into Figure 6 Step S2021 shown.
[0092] In step S204, according to the transaction request, the verification plug-in corresponding to the account element is called to verify the transaction indicated by the transaction request.
[0093] Different account elements included in the transaction sub-request in the transaction request will call different verification plug-ins. The verification plug-in to be called can be determined based on the account elements included in the transaction sub-request in the transaction request, and the verification plug-in is called, and the verification plug-in performs verification of the transaction indicated by the transaction request.
[0094] In some examples, the verification plug-in can be used to verify one or more of the transaction resource elements, account acceptor elements, payer elements, and payee elements. The verification plug-in includes one or more of the authority verification plug-in, the credit verification plug-in, and the risk control verification plug-in. The authority verification plug-in may further include a transaction resource authority verification plug-in, an account acceptor authority verification plug-in, a payer authority verification plug-in, a payee authority verification plug-in, etc. The credit verification plug-in may further include a transaction resource credit verification plug-in, an account acceptor credit verification plug-in, a payer credit verification plug-in, a payee credit verification plug-in, etc. The risk control verification plug-in may further include a transaction resource risk control verification plug-in, an account acceptor risk control verification plug-in, a payer risk control verification plug-in, a payee risk control verification plug-in, etc.
[0095] For example, Figure 7 A schematic diagram of an example of a verification process provided in an embodiment of the present application, such as Figure 7As shown, the authority verification, quota verification and risk control verification can be carried out in sequence, and other verifications can also be carried out. The authority verification may include the authority verification of the circulation of transaction resources, the authority verification of the circulation of account acceptors, the authority verification of the circulation of payers and the authority verification of the circulation of payees. The authority verification of the circulation of transaction resources can be carried out according to the pre-set transaction resource switch, transaction resource whitelist, transaction resource blacklist, etc. to verify the access authority of the transaction resources, that is, to verify whether the transaction resources are allowed to circulate in the transaction business. The authority verification of the circulation of account acceptors can be carried out according to the pre-set classification rules to verify the authority of the account acceptors. The classification rules can be set according to the account acceptors, the acceptance quota of the account acceptors, the whitelist of the account acceptors, the whitelist of the transactions that the account acceptors can participate in, etc. The authority verification of the circulation of payers can be carried out according to the pre-set whitelist, yellow list, blacklist, etc. The authority verification of the circulation of payees can be carried out according to the pre-set whitelist, yellow list, blacklist, etc. Similarly, the limit verification may include the limit verification of the circulation of transaction resources, the limit verification of the circulation of account acceptors, the limit verification of the circulation of payers, and the limit verification of the circulation of payees. The limit verification is similar to the above-mentioned permission verification, except that the verification is based on the limit. The limit of transaction resources, account acceptors, payers, and payees can be verified according to the pre-set limit rules. The risk control verification may include the risk control verification of the circulation of transaction resources, the risk verification of the circulation of account acceptors, the risk verification of the circulation of payers, and the risk verification of the circulation of payees. The risk control verification is similar to the above-mentioned permission verification, except that the verification is based on risk control. The risk control verification of transaction resources, account acceptors, payers, and payees can be verified according to the pre-set risk rules, risk whitelists, risk yellowlists, risk blacklists, etc.
[0096] By verifying the transaction resources, account acceptor, payer, and payee, the transaction security is improved. The verification rules set in the verification plug-in can realize flexible configuration of verification and achieve efficient verification.
[0097] In the above embodiments, the input data and output data of the verification plug-in are uniformly standardized, and the verification plug-in can be processed according to the standardized input data to obtain the verification result. Specifically, the multi-business system can obtain the standard input data required by the verification plug-in from the transaction request; call the verification plug-in, input the standard input data into the verification plug-in, so that the verification plug-in outputs the verification result standard data based on the standard input data; obtain the verification result standard data from the verification plug-in. The standard input data may include the payer account identifier, transaction resource amount, transaction resource type, payee identifier and verification type. The verification type corresponds to the account type indicated by the account element. In some examples, the verification type can be directly assigned with the account type. The verification result standard data includes the verification result.
[0098] For example, Figure 8 A schematic diagram of an example of a risk control verification calling verification plug-in provided in an embodiment of the present application, such as Figure 8 As shown, the verification plug-ins that can be called for risk control verification may include payment card risk verification plug-ins, points risk verification plug-ins, and other verification plug-ins. Each verification plug-in can be pre-registered in the plug-in registration center, and the multi-business system can pre-subscribe to the verification plug-ins that need to be called from the plug-in registration center, and call the corresponding plug-in when it needs to be called. For example, if the account indicated by the account element is a payment card, the payment card risk verification plug-in is called; if the account indicated by the account element is a points account, the points risk verification plug-in is called. The standard input data of the verification plug-in may include the payer account identifier PayerAcctId, the transaction resource amount TrxTmt, the transaction resource type currency, the payee identifier merchantNO, and the verification type serviceGroup. The verification result standard data of the verification plug-in may include the risk score score.
[0099] In step S2021, when the verification is passed, the acceptance resource amount is determined according to the transaction request and an acceptance request is generated.
[0100] If the verification fails, the transaction will be aborted.
[0101] It should be noted that in the embodiments of the present application, functions other than verification in the multi-business system can also be implemented through plug-ins. For example, functions such as conversion and clearing of transaction resources can all be implemented as plug-ins. The embodiments of the present application can support plug-ins for each access party in terms of access, authority, quota, risk control, and operation management. Each plug-in can be dynamically loaded and unloaded. The newly added functional logic is implemented through plug-ins without affecting the original business functional logic, making the implementation of transaction services more flexible.
[0102] In some embodiments, it is necessary to allow time for the access party of the multi-business system to transform and access. When the access party of the multi-business system has not yet successfully transformed, a system transition phase can be set for the access party of the multi-business system, and a front-end compatible system and a rear-end compatible system can be configured for the multi-business system, and the message protocol, interface type, etc. of the original interface are compatible through the front-end compatible system and the rear-end compatible system. The front-end compatible system is used to convert the request sent by the original interface of the access party into a transaction request that meets the requirements of the multi-business system, and the rear-end compatible system can be used to convert the acceptance request output by the multi-business system into a request that meets the original interface of the access party. The access party may include the transaction initiator and the account acceptor, and the transaction initiator may include the user, the third-party payment institution, the transaction platform, the digital cash register platform, the acquiring institution, etc.
[0103] During the system transition phase, the request sent by the transaction initiator using the original interface is converted into a transaction request through the front-end compatible system; during the system transition phase, the acceptance request is converted into a request that meets the original interface requirements of the account acceptor through the back-end compatible system and sent to the account acceptor. For example, Fig. 9 A schematic diagram of another example of a multi-service system provided in an embodiment of the present application, Fig. 9 and Figure 2 The difference is that Fig. 9 The multi-business system 13 shown is also configured with a front-end compatible system 17 and a back-end compatible system 18. Merchants / acquirers 111, payment institutions 112, barcode acquirers 113 and other acquirers 114 can access the unified access terminal 12 through a normalized standard interface. Merchants / acquirers 111, payment institutions 112, barcode acquirers 113 and other acquirers 114 can also access the front-end compatible system 17 through an original interface. Card issuers 151, payment institutions 152, points issuers 153, ticket issuers 154 and other resource issuers 155 can access the unified access terminal 16 through a normalized standard interface. Card issuers 151, payment institutions 152, points issuers 153, ticket issuers 154 and other resource issuers 155 can access the back-end compatible system 18 through an original interface.
[0104] A second aspect of the present application provides a transaction switching device based on a multi-business system, which is applied to a multi-business system. Fig.10 A schematic diagram of the structure of a transaction switching device based on a multi-business system provided in an embodiment of the present application, such as Fig.10 As shown, the transaction switching device 300 based on the multi-business system may include a receiving module 301 , an information processing module 302 and a sending module 303 .
[0105] The receiving module 301 may be used to receive a transaction request.
[0106] The transaction request includes at least one transaction sub-request. Each transaction sub-request includes a payer element, a payee element, an account acceptor element, an account element, and a transaction resource element. At least one of the account acceptor element, the account element, and the transaction resource element in different transaction sub-requests in the same transaction request is different.
[0107] The information processing module 302 may be used to determine the amount of acceptance resources and generate an acceptance request according to the transaction request.
[0108] The acceptance request includes payee elements, payee elements, account elements and acceptance resource amount.
[0109] The sending module 303 may be used to send an acceptance request to the account acceptor indicated by the account acceptor element, so that the account acceptor completes the transaction according to the acceptance request.
[0110] In some embodiments, the transaction request includes multiple transaction sub-requests, each transaction sub-request corresponding to an account type. The information processing module 302 can be specifically used to: determine the acceptance resource amount of the first transaction sub-request according to the first transaction sub-request, and generate an acceptance request corresponding to the first transaction sub-request; when receiving the acceptance response corresponding to the first transaction sub-request and the transaction standard resource amount of the first transaction sub-request does not reach the total transaction standard resource amount indicated by the transaction request, determine the acceptance resource amount of the second transaction sub-request according to the second transaction sub-request, and generate an acceptance request corresponding to the second transaction sub-request, until the acceptance response corresponding to the Nth transaction sub-request is received and the sum of the transaction standard resource amounts of the first N transaction sub-requests reaches the total transaction standard resource amount indicated by the transaction request, where N is a positive integer greater than or equal to 2.
[0111] In some embodiments, the information processing module 302 can also be used to: send a transaction notification to the transaction platform that triggered the transaction request when an acceptance response corresponding to the Nth transaction sub-request is received and the sum of the transaction standard resource quantities of the first N transaction sub-requests reaches the total transaction standard resource quantity indicated by the transaction request.
[0112] The transaction notification has a sub-transaction identifier and a transaction family identifier, and the transaction family identifier of the transaction notification is the same as the transaction family identifier of the transaction request.
[0113] In some embodiments, the transaction resource elements include transaction resource quantity, transaction resource type, transaction standard resource type and transaction standard resource conversion ratio. The information processing module 302 may also be used to: when the transaction resource type in the transaction sub-request is different from the transaction standard resource type, convert the transaction resource quantity in the transaction sub-request into the transaction standard resource quantity corresponding to the transaction standard resource type according to the transaction standard resource conversion ratio; and complete the transaction according to the converted transaction standard resource quantity using the standard resource account pre-set by the account acceptor indicated by the account acceptor element in the transaction sub-request.
[0114] In some embodiments, the transaction sub-request has a sub-transaction identifier and a transaction family identifier. Different transaction sub-requests have different sub-transaction identifiers, and transaction sub-requests belonging to the same transaction request have the same transaction family identifier.
[0115] In some embodiments, transaction resource elements include transaction resource quantity, transaction resource type, transaction standard resource type and transaction standard resource conversion ratio. The multi-business system pre-stores a pre-conversion contract, which includes a pre-transaction standard resource type and a pre-transaction standard resource conversion ratio.
[0116] The information processing module 302 can be specifically used for: when the transaction resource type in the transaction sub-request is different from the transaction standard resource type and the account acceptor indicated by the account acceptor element in the transaction sub-request has a pre-conversion contract, according to the pre-transaction standard resource conversion ratio, converting the transaction resource amount in the transaction request into the pre-transaction standard resource amount corresponding to the pre-transaction standard resource type; converting the pre-transaction standard resource amount into the transaction standard resource amount corresponding to the transaction standard resource type in the transaction sub-request, and determining the converted transaction standard resource amount as the acceptance resource amount.
[0117] In some embodiments, the transaction resource element includes a first transaction standard resource type, a first transaction standard resource conversion ratio, a second transaction standard resource type, and a second transaction standard resource conversion ratio. The information processing module 302 can be specifically used to: convert the transaction resource amount in the transaction sub-request into the first transaction standard resource amount corresponding to the first transaction standard resource type according to the first transaction standard resource conversion ratio; convert the first transaction standard resource amount into the second transaction standard resource amount corresponding to the second transaction standard resource type according to the second transaction standard resource conversion ratio, and determine the second transaction standard resource amount as the acceptance resource amount.
[0118] In some embodiments, the transaction switching device 300 based on the multi-business system may further include a verification module. The verification module may be used to: call a verification plug-in corresponding to the account element according to the transaction request to verify the transaction indicated by the transaction request.
[0119] The information processing module 302 may be specifically used to: determine the amount of acceptance resources and generate an acceptance request according to the transaction request when the verification is passed.
[0120] In some examples, the verification plug-in is used to verify one or more of the transaction resource element, the account acceptor element, the payer element, and the payee element. The verification plug-in includes one or more of the authority verification plug-in, the quota verification plug-in, and the risk control verification plug-in.
[0121] In some examples, the verification module can be specifically used to: obtain standard input data required by the verification plug-in from the transaction request; call the verification plug-in, input the standard input data into the verification plug-in, so that the verification plug-in outputs verification result standard data based on the standard input data; obtain the verification result standard data from the verification plug-in.
[0122] In some examples, the transaction request includes a payment request and a return request.
[0123] In some embodiments, the multi-business system is configured with a front-end compatible system and a back-end compatible system. The transaction switching device 300 of the multi-business system also includes a conversion module, which can be used to: during the system transition phase, convert the request sent by the transaction initiator using the original interface into a transaction request through the front-end compatible system; during the system transition phase, convert the acceptance request into a request that meets the original interface requirements of the account acceptor through the back-end compatible system, and send it to the account acceptor.
[0124] In some examples, the transaction request corresponds to one payment order or more than two payment orders. The transaction sub-request in the transaction request includes one set of payee elements or more than two sets of payee elements.
[0125] In some examples, the payer elements include a payer identification, payer personal information, and payer supplemental information.
[0126] The payee elements include the payee ID, the payee order ID and the payee supplementary information.
[0127] Account elements include account type and account ID.
[0128] The account acceptor elements include the account acceptor type and the account acceptor identifier.
[0129] The elements of trading resources include trading resource volume, trading resource units, trading resource types, trading standard resource types and trading standard resource conversion ratio.
[0130] In some examples, the transaction sub-request also includes an acquirer element and / or an order element.
[0131] It should be noted that the transaction switching device 300 based on a multi-business system is a device corresponding to the above-mentioned transaction switching method based on a multi-business system. All implementation methods in the above-mentioned method embodiment are applicable to the embodiments of the device and can achieve the same technical effects.
[0132] The third aspect of the present application also provides a transaction switching device based on a multi-business system. Fig.11 This is a schematic diagram of the structure of a transaction switching device based on a multi-business system provided in an embodiment of the present application. Fig.11 As shown, the transaction switching device 400 based on the multi-business system includes a memory 401 , a processor 402 , and a computer program stored in the memory 401 and executable on the processor 402 .
[0133] In some examples, the processor 402 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0134] The memory 401 may include a read-only memory (ROM), a random access memory (RAM), a disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the transaction transfer method based on a multi-business system in an embodiment of the present application.
[0135] The processor 402 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 401, so as to implement the transaction transfer method based on the multi-business system in the above embodiment.
[0136] In some examples, the transaction switching device 400 based on the multi-business system may further include a communication interface 403 and a bus 404. Fig.11 As shown, the memory 401, the processor 402, and the communication interface 403 are connected via a bus 404 and communicate with each other.
[0137] The communication interface 403 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiment of the present application. The input device and / or output device can also be accessed through the communication interface 403.
[0138] The bus 404 includes hardware, software or both, and couples the components of the transaction switching device 400 based on the multi-business system to each other. For example, but not limitation, the bus 404 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnection, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnection, a Low Pin Count (LPC) bus, a Memory Bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, the bus 404 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.
[0139] In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program instruction is stored, and when the computer program instruction is executed by a processor, the transaction transfer method based on a multi-business system in the above-mentioned embodiment can be implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the above-mentioned computer-readable storage medium may include a non-transient computer-readable storage medium, such as a read-only memory (Read-Only Memory, referred to as ROM), a random access memory (Random Access Memory, referred to as RAM), a disk or an optical disk, etc., which is not limited here.
[0140] The fifth aspect of the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the transaction transfer method based on a multi-business system in the above-mentioned embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0141] It should be clear that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For device embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments, the relevant parts can refer to the description part of the method embodiment. The present application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application. In addition, for the sake of brevity, a detailed description of known method technologies is omitted here.
[0142] The above reference is according to the method of the embodiment of the present application, the flow chart of the device (system) and the computer program product and / or the block diagram described various aspects of the present application.It should be understood that each square box in the flow chart and / or the block diagram and the combination of each square box in the flow chart and / or the block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the realization of the function / action specified in one or more square boxes of the flow chart and / or the block diagram.Such a processor can be but is not limited to a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit.It can also be understood that each square box in the block diagram and / or the flow chart and the combination of the square boxes in the block diagram and / or the flow chart can also be realized by the dedicated hardware that performs the specified function or action, or can be realized by the combination of dedicated hardware and computer instructions.
[0143] Those skilled in the art should understand that the above embodiments are exemplary rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on the study of the drawings, the specification and the claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other devices or steps; the quantifier "one" does not exclude multiple; the terms "first" and "second" are used to indicate names rather than to indicate any specific order. Any figure marks in the claims should not be understood as limiting the scope of protection. The functions of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.
Claims
1. A transaction transfer method based on a multi-business system, It is characterized in that Applied to a multi-service system, the method comprises: receiving a transaction request, the transaction request comprising at least one transaction sub-request, each of the transaction sub-requests comprising a payer element, a payee element, an account acceptor element, an account element and a transaction resource element, and at least one of the account acceptor element, the account element and the transaction resource element in different transaction sub-requests in the same transaction request is different; Determine the acceptance resource amount according to the transaction request, and generate an acceptance request, wherein the acceptance request includes the payee element, the payee element, the account element and the acceptance resource amount; The acceptance request is sent to the account acceptor indicated by the account acceptor element, so that the account acceptor completes the transaction according to the acceptance request.
2. The method according to claim 1, It is characterized in that The transaction request includes a plurality of transaction sub-requests, each transaction sub-request corresponding to an account type; The step of determining the acceptance resource amount according to the transaction request and generating the acceptance request includes: Determine the acceptance resource amount of the first transaction sub-request according to the first transaction sub-request, and generate the acceptance request corresponding to the first transaction sub-request; When an acceptance response corresponding to the first transaction sub-request is received and the transaction standard resource amount of the first transaction sub-request does not reach the total transaction standard resource amount indicated by the transaction request, the acceptance resource amount of the second transaction sub-request is determined according to the second transaction sub-request, and the acceptance request corresponding to the second transaction sub-request is generated, until an acceptance response corresponding to the Nth transaction sub-request is received and the sum of the transaction standard resource amounts of the first N transaction sub-requests reaches the total transaction standard resource amount indicated by the transaction request, where N is a positive integer greater than or equal to 2.
3. The method according to claim 2, It is characterized in that Also includes: When receiving an acceptance response corresponding to the Nth transaction sub-request and the sum of the transaction standard resource amounts of the first N transaction sub-requests reaches the total transaction standard resource amount indicated by the transaction request, sending a transaction notification to the transaction platform that triggered the transaction request; The transaction notification has a sub-transaction identifier and a transaction family identifier, and the transaction family identifier of the transaction notification is the same as the transaction family identifier of the transaction request.
4. The method according to claim 1, It is characterized in that The transaction resource elements include transaction resource quantity, transaction resource type, transaction standard resource type and transaction standard resource conversion ratio; The method further comprises: In the case where the transaction resource type in the transaction sub-request is different from the transaction standard resource type, converting the transaction resource amount in the transaction sub-request into a transaction standard resource amount corresponding to the transaction standard resource type according to the transaction standard resource conversion ratio; The transaction is completed according to the transaction standard resource amount obtained by conversion by using the standard resource account pre-set by the account acceptor indicated by the account acceptor element in the transaction sub-request.
5. The method according to claim 1, It is characterized in that The transaction sub-request has a sub-transaction identifier and a transaction family identifier. Different transaction sub-requests have different sub-transaction identifiers, and the transaction sub-requests belonging to the same transaction request have the same transaction family identifier.
6. The method according to claim 1, It is characterized in that The transaction resource elements include transaction resource quantity, transaction resource type, transaction standard resource type and transaction standard resource conversion ratio. The multi-business system pre-stores a pre-conversion contract, and the pre-conversion contract includes a pre-transaction standard resource type and a pre-transaction standard resource conversion ratio. The step of determining the amount of accepted resources according to the transaction request includes: In the case where the transaction resource type in the transaction sub-request is different from the transaction standard resource type and the account acceptor indicated by the account acceptor element in the transaction sub-request has the pre-conversion contract, converting the transaction resource amount in the transaction request into the pre-transaction standard resource amount corresponding to the pre-transaction standard resource type according to the pre-transaction standard resource conversion ratio; The pre-transaction standard resource amount is converted into a transaction standard resource amount corresponding to the transaction standard resource type in the transaction sub-request, and the converted transaction standard resource amount is determined as the acceptance resource amount.
7. The method according to claim 1, It is characterized in that The transaction resource elements include a first transaction standard resource type, a first transaction standard resource conversion ratio, a second transaction standard resource type, and a second transaction standard resource conversion ratio; The step of determining the amount of accepted resources according to the transaction request includes: converting the transaction resource amount in the transaction sub-request into a first transaction standard resource amount corresponding to the first transaction standard resource type according to a first transaction standard resource conversion ratio; According to the second transaction standard resource conversion ratio, the first transaction standard resource amount is converted into a second transaction standard resource amount corresponding to the second transaction standard resource type, and the second transaction standard resource amount is determined as the acceptance resource amount.
8. The method according to claim 1, It is characterized in that Before determining the acceptance resource amount according to the transaction request and generating the acceptance request, the method further includes: According to the transaction request, calling the verification plug-in corresponding to the account element to verify the transaction indicated by the transaction request; The step of determining the acceptance resource amount according to the transaction request and generating the acceptance request includes: When the verification is passed, the acceptance resource amount is determined according to the transaction request, and the acceptance request is generated.
9. The method according to claim 8, It is characterized in that The verification plug-in is used to verify one or more of the transaction resource element, the account acceptor element, the payer element, and the payee element; The verification plug-in includes one or more of a permission verification plug-in, a limit verification plug-in, and a risk control verification plug-in.
10. The method according to claim 8, It is characterized in that The calling, according to the transaction request, a verification plug-in corresponding to the account element to verify the transaction indicated by the transaction request includes: Obtaining standard input data required by the verification plug-in from the transaction request; Calling the verification plug-in, inputting the standard input data into the verification plug-in, so that the verification plug-in outputs verification result standard data based on the standard input data; The verification result standard data is obtained from the verification plug-in.
11. The method according to claim 1, It is characterized in that The transaction request includes a payment request and a return request.
12. The method according to claim 1, It is characterized in that The multi-service system is configured with a front-end compatible system and a rear-end compatible system; The method further comprises: During the system transition phase, the request sent by the transaction initiator using the original interface is converted into the transaction request through the pre-compatible system; During the system transition phase, the acceptance request is converted into a request that meets the original interface requirements of the account acceptor through the post-compatible system and sent to the account acceptor.
13. The method according to claim 1, It is characterized in that The transaction request corresponds to one payment order or more than two payment orders; The transaction sub-request in the transaction request includes one group of the payee elements or more than two groups of the payee elements.
14. The method according to any one of claims 1 to 13, It is characterized in that The payer elements include payer identification, payer personal information and payer supplementary information; The payee elements include the payee ID, the payee order ID and the payee supplementary information; The account elements include account type and account identifier; The account acceptor element includes the account acceptor type and the account acceptor identifier; The transaction resource elements include transaction resource quantity, transaction resource unit, transaction resource type, transaction standard resource type and transaction standard resource conversion ratio.
15. The method according to any one of claims 1 to 13, It is characterized in that The transaction sub-request also includes an acquirer element and / or an order element.
16. A transaction switching device based on a multi-business system, It is characterized in that Applied to a multi-service system, the device comprises: a receiving module, configured to receive a transaction request, wherein the transaction request includes at least one transaction sub-request, each of the transaction sub-requests includes a payer element, a payee element, an account acceptor element, an account element, and a transaction resource element, and at least one of the account acceptor element, the account element, and the transaction resource element in different transaction sub-requests in the same transaction request is different; An information processing module, configured to determine the amount of acceptance resources according to the transaction request and generate an acceptance request, wherein the acceptance request includes the payee element, the payee element, the account element and the amount of acceptance resources; The sending module is used to send the acceptance request to the account acceptor indicated by the account acceptor element, so that the account acceptor completes the transaction according to the acceptance request.
17. A transaction switching device based on a multi-business system, It is characterized in that include: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the transaction transfer method based on the multi-business system as described in any one of claims 1 to 15 is implemented.
18. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by the processor, the transaction transfer method based on the multi-business system as described in any one of claims 1 to 15 is implemented.
19. A computer program product, It is characterized in that It includes a computer program, which, when executed by a processor, implements the transaction transfer method based on a multi-business system as described in any one of claims 1 to 15.
Citation Information
Cited By
Transaction switching method, apparatus and device based on multi-service system, and medium
WO2026016409A1
