Payment method, device, equipment and system compatible with multiple payment modes, and medium
By using the acceptance terminal to apply for payment code from the payment platform in the payment system, the problem of complex architecture when the existing payment system is compatible with multiple payment methods is solved, and unified acceptance and system simplification of payment card payment and NFC payment is realized.
Patent Information
- Application Number
- CN202411132143.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-11-26
AI Technical Summary
The architecture of the existing payment system is too complex when compatible with multiple payment methods. It is necessary to set up multiple acceptance equipment at the merchant and introduce payment systems corresponding to each payment method, resulting in the complexity of the system.
The merchant information management system that allows payment card payment and NFC payment to be reused by payment codes, and simplifies the payment system architecture that is compatible with multiple payment methods.
It realizes unified acceptance of payment card payment and NFC payment, simplifies the payment system architecture, and does not require the introduction of other payment methods payment systems, reduces access difficulty and ensures user experience.
Smart Images

Figure CN119027113A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of payment technology, and in particular, relates to a payment method, device, equipment, system and medium that are compatible with multiple payment methods. Background Art
[0002] With the continuous development of payment technology, there are more and more payment methods. Users can pay based on payment cards, payment codes, or near field communication (NFC) technology. However, the payment systems of various payment methods are different. For example, payment based on payment cards requires the interaction between point-of-sale devices, i.e., POS machines, acquiring institutions, payment platforms, etc. Payment based on payment codes requires the interaction between cashier-specific acceptance devices, such as devices including barcode scanners, merchant management information systems (MIS), payment platforms, etc. Payment based on NFC technology requires the interaction between acceptance devices with NFC functions, acquiring institutions, payment platforms, etc. If you want to be compatible with the above payment methods, you need to set up a variety of acceptance devices at the merchant, and you also need to introduce the payment systems corresponding to each payment method, which makes the payment system architecture too complicated. Summary of the invention
[0003] The embodiments of the present application provide a payment method, device, equipment, system and medium that are compatible with multiple payment methods, which can simplify the architecture of a payment system that is compatible with multiple payment methods.
[0004] In the first aspect, an embodiment of the present application provides a payment method that is compatible with multiple payment methods, which is applied to an acceptance terminal. The method includes: when initiating payment, receiving a payment code acquisition request sent by a merchant information management system; interacting with a payment object, the payment object includes a payment card or a user terminal, and the user terminal has a near-field communication function; sending a payment code application request to a payment platform, or triggering the user terminal to send a payment code application request to the payment platform; receiving a target payment code fed back by the payment platform in response to the payment code application request, and sending the target payment code to the merchant information management system, so that the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0005] On the second aspect, an embodiment of the present application provides a payment method compatible with multiple payment methods, which is applied to a payment platform. The method includes: when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by a merchant information management system, receiving a payment code application request, the payment object includes a payment card or a user terminal, the user terminal has a near-field communication function, and the payment code application request is sent by the acceptance terminal or triggered by the user terminal to be sent by the acceptance terminal; in response to the payment code application request, feeding back a target payment code to the acceptance terminal so that the acceptance terminal sends the target payment code to the merchant information management system; interacting with the merchant information management system based on the target payment code to complete the payment.
[0006] On the third aspect, an embodiment of the present application provides a payment method compatible with multiple payment methods, which is applied to a user terminal, and the user terminal has a near-field communication function. The method includes: when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system, the accepted terminal triggers to send a payment code application request to the payment platform, so that the payment platform responds to the payment code application request and feeds back a target payment code to the acceptance terminal. The target payment code is used by the accepted terminal to send to the merchant information management system, and the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0007] In a fourth aspect, an embodiment of the present application provides an acceptance terminal, comprising: a receiving module, used to receive a payment code acquisition request sent by a merchant information management system when initiating a payment; a data transmission module, used to interact with a payment object, the payment object includes a payment card or a user terminal, and the user terminal has a near-field communication function; a sending module, used to send a payment code application request to a payment platform, or trigger the user terminal to send a payment code application request to the payment platform; the receiving module is also used to receive a target payment code fed back by the payment platform in response to the payment code application request, and send the target payment code to the merchant information management system, so that the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0008] In the fifth aspect, an embodiment of the present application provides a payment device compatible with multiple payment methods, which is applied to a payment platform. The device includes: a receiving module, which is used to receive a payment code application request when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system. The payment object includes a payment card or a user terminal. The user terminal has a near-field communication function. The payment code application request is sent by the acceptance terminal or triggered by the user terminal to be sent by the acceptance terminal; a sending module, which is used to respond to the payment code application request and feedback the target payment code to the acceptance terminal, so that the acceptance terminal sends the target payment code to the merchant information management system; the receiving module and the sending module are also used to interact with the merchant information management system based on the target payment code to complete the payment.
[0009] In a sixth aspect, an embodiment of the present application provides a user terminal having a near-field communication function, and the user terminal includes: a data trigger module, which is triggered by the acceptance terminal when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system; a sending module, which is used to send a payment code application request to the payment platform, so that the payment platform responds to the payment code application request and feeds back a target payment code to the acceptance terminal, and the target payment code is used to be sent by the acceptance terminal to the merchant information management system, and the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0010] In the seventh aspect, an embodiment of the present application provides an acceptance terminal, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the payment method of the first aspect that is compatible with multiple payment methods is implemented.
[0011] In an eighth aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the payment method of the second aspect that is compatible with multiple payment methods is implemented.
[0012] In the ninth aspect, an embodiment of the present application provides a user terminal, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the payment method of the third aspect that is compatible with multiple payment methods is implemented.
[0013] In a tenth aspect, an embodiment of the present application provides a payment system compatible with multiple payment methods, including:
[0014] An acceptance terminal, used to execute the payment method of the first aspect that is compatible with multiple payment methods;
[0015] A payment platform for executing the payment method of the second aspect that is compatible with multiple payment methods;
[0016] The user terminal is used to execute the payment method of the third aspect that is compatible with multiple payment methods.
[0017] In the eleventh aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the payment method compatible with multiple payment methods of the first aspect, the payment method compatible with multiple payment methods of the second aspect, or the payment method compatible with multiple payment methods of the third aspect is implemented.
[0018] In the twelfth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the payment method compatible with multiple payment methods of the first aspect, the payment method compatible with multiple payment methods of the second aspect, or the payment method compatible with multiple payment methods of the third aspect.
[0019] The embodiments of the present application provide a payment method, device, equipment, system and medium compatible with multiple payment methods. When initiating a payment, the merchant information management system can send a payment code acquisition request to the acceptance terminal, and the acceptance terminal interacts with the payment object, thereby sending a payment code application request to the payment platform, or triggering the user terminal to send a payment code application request to the payment platform, so that the payment platform allocates a target payment code for this payment and feeds back the target payment code to the acceptance terminal. The acceptance terminal sends the target payment code to the merchant information management system, so that payment card payment and NFC payment can reuse the merchant information management system originally used for payment code payment. The merchant information management system interacts with the payment platform according to the payment code payment process to complete the payment, and payment card payment and NFC payment can be realized. In addition to the payment system of payment code payment, there is no need to introduce payment systems of other payment methods to realize the unified acceptance of multiple payment methods such as payment code payment, payment card payment, NFC payment, etc., which simplifies the architecture of the payment system compatible with multiple payment methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] 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.
[0021] Figure 1 A schematic diagram of an example of an application architecture of a payment method compatible with multiple payment methods provided in an embodiment of the present application;
[0022] Figure 2 A schematic diagram of a framework of an example of an acceptance terminal provided in an embodiment of the present application;
[0023] Figure 3 A flowchart of a payment method compatible with multiple payment methods provided in an embodiment of the first aspect of the present application;
[0024] Figure 4 A flowchart of a payment method compatible with multiple payment methods provided in an embodiment of the second aspect of the present application;
[0025] Figure 5 A flowchart of a payment method compatible with multiple payment methods provided in an embodiment of the third aspect of the present application;
[0026] Figure 6 A schematic diagram of an example of a payment process for multiple payment methods provided in an embodiment of the present application;
[0027] Figure 7 A schematic diagram of the structure of an acceptance terminal provided for an embodiment of the fourth aspect of the present application;
[0028] Figure 8 A schematic diagram of the structure of a payment device compatible with multiple payment methods provided in an embodiment of the fifth aspect of the present application;
[0029] Fig. 9 A schematic diagram of the structure of a user terminal provided in an embodiment of the sixth aspect of the present application;
[0030] Fig.10 A schematic diagram of the structure of an acceptance terminal provided for an embodiment of the seventh aspect of the present application. DETAILED DESCRIPTION
[0031] 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.
[0032] With the continuous development of payment technology, there are more and more payment methods. Users can pay based on payment cards, payment codes, or NFC technology. However, the payment systems of various payment methods are different. For example, payment based on payment cards requires interaction between point-of-sale devices, i.e., POS machines, acquiring institutions, and payment platforms. Payment based on payment codes requires interaction between cashier-specific acceptance devices, such as devices including barcode scanners, merchant information management systems, i.e., merchant MIS, and payment platforms. Payment based on NFC technology requires interaction between acceptance devices with NFC functions, acquiring institutions, and payment platforms. If you want to be compatible with the above payment methods, you need to set up multiple acceptance devices at the merchant, and you also need to introduce payment systems corresponding to each payment method, which makes the payment system architecture too complicated.
[0033] The present application provides a payment method, device, equipment, system, medium and program product compatible with multiple payment methods. In the scenario of using payment cards for payment and using NFC payment, the payment code can be directly applied to the payment platform through the acceptance terminal or the user terminal that triggers NFC payment through the acceptance terminal can apply to the payment platform for the payment code, so that the payment acceptance terminal can obtain the payment code from the payment platform and provide the payment code to the merchant information management system, so that payment card payment and NFC payment can reuse the merchant information management system originally used for payment code payment, reuse the existing payment code payment business logic and interface, and do not modify the merchant information management system. It only needs to introduce a payment system for payment code payment to be compatible with multiple payment methods, which simplifies the architecture of the payment system compatible with multiple payment methods.
[0034] For ease of understanding, the following is a brief introduction to the application architecture of the payment method provided by this application that is compatible with multiple payment methods. Figure 1 A schematic diagram of an example of an application architecture of a payment method compatible with multiple payment methods provided in an embodiment of the present application, such as Figure 1 As shown, the payment method compatible with multiple payment methods involves an acceptance terminal 11 , a merchant information management system 12 , a user terminal 13 and a payment platform 14 .
[0035] The acceptance terminal 11 can be set at the merchant side and can accept payment code payment, payment card payment and NFC payment. In order to meet the needs of the above payment methods, the acceptance terminal 11 can be set with various structures, for example, Figure 2 The framework diagram of an example of an acceptance terminal provided in an embodiment of the present application, the acceptance terminal 11 may include a payment card acceptance module 111, an NFC module 112, a code scanning module 113 and other structures. The payment card acceptance module 111 can read the information of the payment card to realize the card swiping function. The NFC module 112 can perform NFC interaction with other devices with NFC function to transmit information. In some examples, the NFC module 112 may include but is not limited to structures such as NFC tags. The code scanning module 113 can shoot payment codes, product barcodes, etc., so as to obtain the information contained in the payment codes and product barcodes. In some examples, the code scanning module 113 may include but is not limited to structures such as cameras. The acceptance terminal 11 may also include a remote communication module 114, which can communicate and interact with the payment platform 14 through the remote communication module. The acceptance terminal 11 may also include but is not limited to structures such as a display screen 115 and a positioning module 116. The remote communication module 114 and the positioning module 116 may also cooperate to realize the management and upgrade of the acceptance terminal 11, and the upgrade may adopt but is not limited to Over-the-Air Technology (OTA).
[0036] The merchant information management system 12 can interact with the acceptance terminal 11 to obtain the payment code, thereby interacting with the payment platform 14 to realize the payment of the payment code. The merchant information management system 12 can be set on the merchant side and used as the merchant's cash register system. In the embodiment of the present application, there is no need to modify the merchant information management system, and the original functions of the merchant information management system can be used.
[0037] The user terminal 13 is a terminal device on the user side, which may include but is not limited to mobile phones, tablet computers, smart watches, smart bracelets and other devices. In the embodiment of the present application, the user terminal 13 has an NFC function and can communicate with the acceptance terminal 11 through NFC. The user terminal 13 may have an NFC payment function or a QR code payment function. The user terminal 13 may communicate and interact with the payment platform 14.
[0038] The payment platform 14 is used to execute payment tasks, and can communicate and interact with the acceptance terminal 11, the merchant information management system 12, and the user terminal 13. The number and type of devices in the payment platform 14 are not limited here.
[0039] The following describes the payment method, device, equipment, system, medium and program product provided by this application that are compatible with multiple payment methods.
[0040] A first aspect of the present application provides a payment method that is compatible with multiple payment methods, which can be applied to an acceptance terminal, that is, the payment method that is compatible with multiple payment methods can be executed by an acceptance terminal. Figure 3 A flowchart of a payment method compatible with multiple payment methods provided in the first aspect of the present application, such as Figure 3 As shown, the payment method compatible with multiple payment methods may include steps S201 to S204.
[0041] In step S201, when initiating payment, a payment code acquisition request is sent by a merchant information management system.
[0042] After the merchant information management system scans the product code, confirms and generates the order, payment can be initiated. The merchant information management system can send a payment code acquisition request to the acceptance terminal to request the payment code. In this process, the operation of the merchant cashier using the merchant information management system is consistent with the existing cashier process, and the operation process of the merchant information management system has not been modified.
[0043] In step S202, interact with the payment object.
[0044] The payment object may include a payment card or a user terminal, and the user terminal has an NFC function. In the case where the payment object includes a payment card, this payment is a payment card payment, and the acceptance terminal interacts with the payment card, and the acceptance terminal can obtain the card information of the payment card from the payment card. The card information may include but is not limited to the card identifier and the information required for authenticity verification of the payment card. The card identifier is used to identify the payment card. For example, the card identifier may include but is not limited to the payment card number. The information required for authenticity verification of the payment card may include but is not limited to the digital static signature and digital dynamic signature of the payment card. In the case where the payment object includes a user terminal with an NFC function, this payment is an NFC payment, and the acceptance terminal interacts with the user terminal through NFC. The user terminal can obtain the information required for implementing NFC payment and the acceptance terminal information from the acceptance terminal. The information required for implementing NFC payment may include information that assists in automatically calling up the payment application in the user terminal. The acceptance terminal information may identify the acceptance terminal. For example, the acceptance terminal information may include but is not limited to the acceptance terminal number, the merchant to which the acceptance terminal belongs, etc.
[0045] In step S203, a payment code application request is sent to the payment platform, or the user terminal is triggered to send a payment code application request to the payment platform.
[0046] Based on the interaction result between the acceptance terminal and the payment object, the acceptance terminal sends a payment code application request to the payment platform. The interaction result may include information obtained by the acceptance terminal from the payment object or information transmitted by the acceptance terminal to the payment object. If the payment object includes a payment card, that is, a payment card payment is made, the acceptance terminal sends a payment code application request to the payment platform. If the payment object includes a user terminal with NFC function, that is, an NFC payment is made, the acceptance terminal triggers the user terminal to send a payment code application request to the payment platform. The payment code application request is used to request the payment platform to provide a payment code. In the case of payment card payment and NFC payment, the payment platform can provide payment codes for these two non-payment code payment methods.
[0047] In some examples, before step S203, it may be determined whether the payment object has payment authority. If the payment object has payment authority, a payment code application request is sent to the payment platform, or the user terminal is triggered to send a payment code application request to the payment platform. In the case where the payment object includes a payment card, the authenticity of the payment card can be verified according to the card information. If the payment card passes the authenticity verification, it is considered that the payment card has payment authority. For example, in the payment card payment scenario, the authenticity of the payment card can be verified by static data authentication (SDA), dynamic data authentication (DDA), combined data authentication (CDA), extended data authentication (XDA), etc. In the case where the payment object includes a payment card, the acceptance terminal may also receive the payment password entered by the user, and may also verify the authenticity of the payment card according to the payment password. If the payment password is correct, it is considered that the payment card has payment authority. In the case where the payment object includes a user terminal with NFC function, it may be determined that the user terminal has payment authority according to the user's authorization input to the user terminal.
[0048] In step S204, the target payment code fed back by the payment platform in response to the payment code application request is received, and the target payment code is sent to the merchant information management system, so that the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0049] Regardless of whether the payment object includes a payment card or a user terminal with NFC function, the payment platform will feedback the target payment code to the acceptance terminal. In the scenario where the payment object includes a payment card, i.e., payment card payment, the payment code application request is sent by the acceptance terminal to the payment platform, and the payment platform can directly feedback the target payment code to the acceptance terminal. In the scenario where the payment object includes a user terminal with NFC function, i.e., NFC payment, the payment code application request is sent by the user terminal to the payment platform, and the payment platform can determine the acceptance terminal of this payment based on the information carried in the payment code application request, and thus feedback the target payment code to the acceptance terminal.
[0050] After the acceptance terminal obtains the target payment code, it sends the target payment code to the merchant information management system in response to the payment code acquisition request sent by the merchant information management system in step S201. After receiving the target payment code, the merchant information management system can interact with the payment platform according to the payment code payment process to enable the payment platform to complete this payment.
[0051] In an embodiment of the present application, when initiating payment, the merchant information management system may send a payment code acquisition request to the acceptance terminal, and the acceptance terminal interacts with the payment object, thereby sending a payment code application request to the payment platform, or triggering the user terminal to send a payment code application request to the payment platform, so that the payment platform can allocate a target payment code for this payment, and feed back the target payment code to the acceptance terminal. The acceptance terminal sends the target payment code to the merchant information management system, so that payment card payment and NFC payment can reuse the merchant information management system originally used for payment code payment. The merchant information management system interacts with the payment platform according to the payment code payment process to complete the payment, and payment card payment and NFC payment can be realized. In addition to the payment system of payment code payment, there is no need to introduce a payment system of other payment methods to realize the unified acceptance of multiple payment methods such as payment code payment, payment card payment, NFC payment, etc., which simplifies the architecture of the payment system compatible with multiple payment methods. Moreover, the above process does not require the modification of the merchant information management system, and the existing merchant information management system can be reused. The operation on the merchant side does not change, and no additional manpower and material resources are required for training; the operation on the user side does not change, and the user does not need to change his or her operating habits, which can ensure user experience. The solution of the embodiment of the present application can also reduce the difficulty of other payment methods to access the merchant information management system, and can further expand the payment methods of payment services.
[0052] In some embodiments, the payment object includes a payment card, and correspondingly, the payment code application request is sent by the acceptance terminal. The above step S202 can be specifically refined as follows: reading the card information in the payment card. The card information includes a card identifier. The card information is used to verify the authenticity of the payment card. The specific content of the authenticity verification can refer to the relevant description in the above embodiment, which will not be repeated here. The payment code application request may include a card identifier, acceptance terminal information, and an order identifier. The specific content of the card identifier and the acceptance terminal information can refer to the relevant description in the above embodiment, which will not be repeated here. The order identifier can be used to identify the order, and can also be used to identify this payment. The order identifier is unique.
[0053] In other embodiments, the payment object includes a user terminal with an NFC function, and correspondingly, the payment code application request is sent by the user terminal. The above step S202 can be specifically refined as follows: when the user terminal is sensed, the payment auxiliary information is transmitted to the user terminal through the near field communication function. Both the acceptance terminal and the user terminal have NFC functions, and the two can sense each other through the NFC function. For example, the acceptance terminal is provided with an NFC tag, and the user can bring the user terminal close to the NFC tag of the acceptance terminal, and the acceptance terminal can sense the user terminal. When the user terminal is in a locked state, the user can first unlock the user terminal, and then bring the user terminal close to the NFC tag of the acceptance terminal. When the acceptance terminal senses the user terminal, the user terminal can read the payment auxiliary information provided by the acceptance terminal through the NFC function. The payment auxiliary information includes application call-up information and acceptance terminal information, so that the user terminal can call up the corresponding payment application based on the application call-up information. The acceptance terminal information can refer to the relevant description in the above embodiments, which will not be repeated here. The application call-up information can be used by the user terminal to call up the payment application.
[0054] In some examples, the application call-up information may include a Uniform Resource Locator (URL) address and / or application information. The URL address may be used to indicate the address of an application in the user terminal that assists in calling up the payment application. The application information may be used to indicate the payment application that needs to be called up, and the application information may include but is not limited to the payment application name, the payment application package name, the payment application number, etc. The user terminal obtains the application call-up information, and may automatically call up the corresponding payment application according to the application call-up information, and send a payment code application request to the payment platform through the payment application. The payment code application request may include but is not limited to the acceptance terminal information and the order identifier. The specific content of the acceptance terminal information and the order identifier can be found in the relevant description in the above embodiments, and will not be repeated here.
[0055] For example, the application calling information includes a URL address, and the user terminal can automatically pull up the application indicated by the URL address first. The application can be a light application that comes with the operating system of the user terminal. Light applications are relative to traditional applications. Light applications do not need to be downloaded and installed. The light application can be used by opening the link through a browser. During use, the light application does not need to install a certificate, does not occupy the storage space of the user terminal, and has a fast startup speed, which does not affect the user experience. The corresponding payment application can be called up through the light application, and a payment code application request is sent to the payment platform through the payment application. For example, after the user terminal automatically pulls up the light application indicated by the URL address, the light application can have an "open" button. The user clicks the "open" button to jump to the payment application. Further, it can jump to the NFC payment function of the payment application, thereby sending a payment code application request to the payment platform. If the light application has established a relationship with the payment application in advance, the payment application can be directly pulled up with the user's authorization. Alternatively, the application calling information also includes application information. With the user's authorization, the light application can pull up the payment application according to the application information. This method can be applied to user terminals installed with iOS operating systems.
[0056] For another example, the application invocation information includes application information, and the user terminal can directly and automatically pull up the payment application indicated by the application information to send a payment code application request to the payment platform through the payment application. Furthermore, the user terminal directly and automatically pulls up the payment application indicated by the application information, and automatically jumps to the NFC payment function of the payment application. In the case where the user terminal automatically pulls up the payment application, the user terminal can directly send a payment code application request to the payment platform, or after receiving the user's authorization input, send a payment code application request to the payment platform. This method can be applied to user terminals installed with Android operating systems.
[0057] A second aspect of the present application provides a payment method that is compatible with multiple payment methods and can be applied to a payment platform, that is, the payment method that is compatible with multiple payment methods can be executed by the payment platform. Figure 4 A flowchart of a payment method compatible with multiple payment methods provided in an embodiment of the second aspect of the present application, such as Figure 4 As shown, the payment method compatible with multiple payment methods may include steps S301 to S303.
[0058] In step S301, when payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system, a payment code application request is received.
[0059] The payment object includes a payment card or a user terminal. The user terminal has a near field communication function. The payment code application request is sent by the acceptance terminal or triggered by the user terminal to be sent by the acceptance terminal.
[0060] In step S302, in response to the payment code application request, the target payment code is fed back to the acceptance terminal, so that the acceptance terminal sends the target payment code to the merchant information management system.
[0061] In step S303, the payment is completed by interacting with the merchant information management system based on the target payment code.
[0062] In some embodiments, the payment object includes a payment card. The card information in the payment card is read by the acceptance terminal for authenticity verification of the payment card, and the card information includes a card identifier. The payment code application request is sent by the acceptance terminal.
[0063] In some examples, the payment code application request includes a card identifier, acceptance terminal information, and an order identifier.
[0064] In some embodiments, the payment object includes a user terminal. When the acceptance terminal senses the user terminal, the user terminal reads payment auxiliary information from the acceptance terminal through a near field communication function, and the payment auxiliary information includes application call-up information and acceptance terminal information, so that the user terminal calls up a corresponding payment application based on the application call-up information. The payment code application request is sent by the user terminal.
[0065] In some examples, the application invocation information includes a uniform resource locator address and / or application information. The payment code application request includes acceptance terminal information and an order identifier.
[0066] It should be noted that the payment method compatible with multiple payment methods in the second aspect embodiment is a payment method on the payment platform side corresponding to the payment method compatible with multiple payment methods in the above-mentioned first aspect embodiment. All implementation methods in the above-mentioned first aspect embodiment are applicable to the second aspect embodiment and can achieve the same technical effects, which will not be repeated here.
[0067] A third aspect of the present application provides a payment method that is compatible with multiple payment methods, which can be applied to a user terminal, that is, the payment method that is compatible with multiple payment methods can be executed by a user terminal. Figure 5 A flowchart of a payment method compatible with multiple payment methods provided in an embodiment of the third aspect of the present application, such as Figure 5 As shown, the payment method compatible with multiple payment methods may include step S401.
[0068] In step S401, when payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system, the acceptance terminal triggers to send a payment code application request to the payment platform, so that the payment platform responds to the payment code application request and feeds back the target payment code to the acceptance terminal.
[0069] The target payment code is used to be sent by the acceptance terminal to the merchant information management system, and the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0070] In some embodiments, the above step S401 can be specifically refined as follows: when the acceptance terminal is sensed, payment auxiliary information is read from the acceptance terminal through the near field communication function, the payment auxiliary information includes application call-up information and acceptance terminal information; based on the application call-up information, the corresponding payment application is called up, and a payment code application request is sent to the payment platform.
[0071] In some examples, the steps of calling up the corresponding payment application based on the application calling information and sending a payment code application request to the payment platform can be specifically broken down into: when the application calling information includes a uniform resource locator address, calling up the lightweight application that comes with the operating system of the user terminal according to the uniform resource locator address; in response to the user's authorization input, jumping to the payment application and sending a payment code application request to the payment platform.
[0072] In some examples, the steps of calling up the corresponding payment application based on the application calling information and sending a payment code application request to the payment platform can be specifically broken down into: when the application calling information includes application information, calling up the payment application indicated by the application information, and sending a payment code application request to the payment platform.
[0073] In some examples, the payment code application request includes acceptance terminal information and an order identifier.
[0074] It should be noted that the payment method compatible with multiple payment methods in the third aspect embodiment is a payment method on the user terminal side corresponding to the payment method compatible with multiple payment methods in the above-mentioned first aspect embodiment. All implementation methods in the above-mentioned first aspect embodiment are applicable to the third aspect embodiment and can achieve the same technical effect, which will not be repeated here.
[0075] For ease of understanding, the payment process of each payment method in the embodiments of the present application is further explained here. Figure 6 A schematic diagram of an example of a payment process for multiple payment methods provided in an embodiment of the present application, such as Figure 6As shown, the payment code payment process in which the acceptance terminal scans the user's payment code may include steps a1 to a7 in sequence; the payment card payment process in which the acceptance terminal swipes the card may include steps a1, a2, b1, b2, and a5 to a7 in sequence; the NFC payment process of the user terminal may include steps a1, a2, c1 to c4, a5 to a7, and c5 in sequence.
[0076] In step a1, the merchant information management system interacts with the payment backend to obtain the payment order identifier.
[0077] In step a2, the merchant information management system initiates payment to the acceptance terminal. The merchant uses the merchant information management system to scan the goods, confirms the order in the merchant information management system and chooses to receive payment, thereby sending a payment code acquisition request to the acceptance terminal to initiate payment, and the merchant information management system waits for the acceptance terminal to feedback the payment code.
[0078] In step a3, the user terminal applies for a payment code from the payment platform, and the payment platform feeds back the payment code to the user terminal.
[0079] In step a4, the user terminal displays the payment code and the acceptance terminal scans the payment code.
[0080] In step a5, the acceptance terminal feeds back the payment code to the merchant information management system.
[0081] In step a6, the merchant information management system sends a payment transaction message to the payment platform so that the payment platform executes the payment.
[0082] In step a7, the payment platform feeds back the payment result to the merchant information management system.
[0083] In step b1, the acceptance terminal swipes the payment card to obtain card information from the payment card. The acceptance terminal can verify the authenticity of the payment card.
[0084] In step b2, the acceptance terminal sends a payment code application request to the payment platform, and the payment platform feeds back the payment code to the acceptance terminal.
[0085] In step c1, the user terminal interacts with the acceptance terminal and obtains payment auxiliary information from the acceptance terminal.
[0086] In step c2, the user terminal automatically calls up the payment application according to the application calling information in the payment auxiliary information.
[0087] In step c3, the user terminal sends a payment code application request to the payment platform.
[0088] In step c4, the payment platform feeds back the payment code to the acceptance terminal.
[0089] In step c5, the payment platform feeds back the payment result to the user terminal.
[0090] Figure 6 For the specific contents of the steps shown, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.
[0091] A fourth aspect of the present application provides an acceptance terminal. Figure 7 A schematic diagram of the structure of an acceptance terminal provided in an embodiment of the fourth aspect of the present application, such as Figure 7 As shown, the acceptance terminal 500 may include a receiving module 501 , a data reading module 502 and a sending module 503 .
[0092] The receiving module 501 may be used to receive a payment code acquisition request sent by a merchant information management system when a payment is initiated.
[0093] The data transmission module 502 may be used to interact with a payment object, which may include a payment card or a user terminal having a near field communication function.
[0094] The sending module 503 may be used to send a payment code application request to the payment platform, or trigger the user terminal to send a payment code application request to the payment platform.
[0095] The receiving module 501 can also be used to receive the target payment code fed back by the payment platform in response to the payment code application request, and send the target payment code to the merchant information management system so that the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0096] In some embodiments, the payment object includes a payment card. The data transmission module 502 can be specifically used to: read the card information in the payment card. The card information includes a card identifier, and the card information is used to verify the authenticity of the payment card. The payment code application request is sent by the acceptance terminal.
[0097] In some examples, the payment code application request includes a card identifier, acceptance terminal information, and an order identifier.
[0098] In some embodiments, the payment object includes a user terminal. The data transmission module 502 can be specifically used to: when the user terminal is sensed, transmit payment auxiliary information to the user terminal through the near field communication function. The payment auxiliary information includes application call-up information and acceptance terminal information, so that the user terminal calls up the corresponding payment application based on the application call-up information. Among them, the payment code application request is sent by the user terminal.
[0099] In some examples, the application invocation information includes a uniform resource locator address and / or application information. The payment code application request includes acceptance terminal information and an order identifier.
[0100] It should be noted that the acceptance terminal 500 is a device corresponding to the above-mentioned payment method that is compatible with multiple payment methods. All implementation methods in the above-mentioned method embodiments are applicable to the embodiments of the device and can achieve the same technical effects.
[0101] A fifth aspect of the present application provides a payment device that is compatible with multiple payment methods and can be applied to a payment platform. Figure 8 A schematic diagram of a payment device compatible with multiple payment methods provided in an embodiment of the fifth aspect of the present application, such as Figure 8 As shown, the payment device 600 compatible with multiple payment methods may include a receiving module 601 and a receiving module 602 .
[0102] The receiving module 601 can be used to receive a payment code application request when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system. The payment object includes a payment card or a user terminal. The user terminal has a near-field communication function. The payment code application request is sent by the acceptance terminal or is triggered to be sent by the user terminal by the acceptance terminal.
[0103] The sending module 602 may be used to respond to the payment code application request and feed back the target payment code to the acceptance terminal, so that the acceptance terminal sends the target payment code to the merchant information management system;
[0104] The receiving module 601 and the sending module 602 can also be used to interact with the merchant information management system based on the target payment code to complete the payment.
[0105] In some embodiments, the payment object includes a payment card. The card information in the payment card is read by the acceptance terminal for authenticity verification of the payment card, and the card information includes a card identifier. The payment code application request is sent by the acceptance terminal.
[0106] In some examples, the payment code application request includes a card identifier, acceptance terminal information, and an order identifier.
[0107] In some embodiments, the payment object includes a user terminal. When the acceptance terminal senses the user terminal, the user terminal reads payment auxiliary information from the acceptance terminal through a near field communication function, and the payment auxiliary information includes application call-up information and acceptance terminal information, so that the user terminal calls up a corresponding payment application based on the application call-up information. The payment code application request is sent by the user terminal.
[0108] In some examples, the application invocation information includes a uniform resource locator address and / or application information. The payment code application request includes acceptance terminal information and an order identifier.
[0109] It should be noted that the payment device 600 compatible with multiple payment methods is a device corresponding to the above-mentioned payment method compatible with multiple payment methods. All implementation methods in the above-mentioned method embodiment are applicable to the embodiment of the device and can achieve the same technical effect.
[0110] A sixth aspect of the present application provides a user terminal. Fig. 9 A schematic diagram of the structure of a user terminal provided in an embodiment of the sixth aspect of the present application, such as Fig. 9 As shown, the user terminal 700 may include a data triggering module 701 and a sending module 702 .
[0111] The data trigger module 701 may be configured to be triggered by the acceptance terminal when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system.
[0112] The sending module 702 may be used to send a payment code application request to the payment platform, so that the payment platform feeds back a target payment code to the acceptance terminal in response to the payment code application request.
[0113] The target payment code is used to be sent by the acceptance terminal to the merchant information management system, and the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
[0114] In some embodiments, the data trigger module 701 can be specifically used for: when sensing an acceptance terminal, reading payment auxiliary information from the acceptance terminal through the near field communication function, the payment auxiliary information including application call-up information and acceptance terminal information; and calling up the corresponding payment application based on the application call-up information.
[0115] In some embodiments, the data trigger module 701 can be specifically used to: when the application call-up information includes a uniform resource locator address, call up the lightweight application that comes with the operating system of the user terminal according to the uniform resource locator address; and jump to the payment application in response to the user's authorization input.
[0116] In some embodiments, the data trigger module 701 may be specifically configured to: when the application invoking information includes application information, invoking the payment application indicated by the application information.
[0117] In some examples, the payment code application request includes acceptance terminal information and an order identifier.
[0118] It should be noted that the user terminal 700 is a device corresponding to the above-mentioned payment method compatible with multiple payment methods. All implementation methods in the above-mentioned method embodiment are applicable to the embodiment of the device and can achieve the same technical effect.
[0119] The seventh aspect of the present application also provides an acceptance terminal. Fig.10 A schematic diagram of the structure of an acceptance terminal provided in an embodiment of the seventh aspect of the present application, such as Fig.10 As shown, the acceptance terminal 800 includes a memory 801 , a processor 802 , and a computer program stored in the memory 801 and executable on the processor 802 .
[0120] In some examples, the processor 802 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.
[0121] The memory 801 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 payment method compatible with multiple payment methods in the embodiment of the first aspect of the present application.
[0122] The processor 802 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 801, so as to implement the payment method compatible with multiple payment methods in the above-mentioned first aspect embodiment.
[0123] In some examples, the acceptance terminal 800 may also include a communication interface 803 and a bus 804. Fig.10 As shown, the memory 801, the processor 802, and the communication interface 803 are connected via a bus 804 and communicate with each other.
[0124] The communication interface 803 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiment of the present application. The communication interface 803 can also be used to access input devices and / or output devices.
[0125] The bus 804 includes hardware, software or both, coupling the components of the acceptance terminal 800 to each other. For example, but not limitation, the bus 804 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) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, 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 804 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.
[0126] An eighth aspect of the present application provides an electronic device applied to a payment platform, which may include a memory, a processor, and a computer program stored in the memory and executable on the processor.
[0127] The memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) 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 payment method compatible with multiple payment methods in the embodiment of the second aspect of the present application.
[0128] The processor runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the payment method compatible with multiple payment methods in the above-mentioned second aspect embodiment.
[0129] In some examples, the electronic device may also include a communication interface and a bus, and the memory, processor, and communication interface are connected through the bus to communicate with each other.
[0130] The connection between the memory, processor, communication interface, and bus in the electronic device and the specific implementation method can be found in the relevant description in the embodiment of the acceptance terminal in the seventh aspect above, and will not be repeated here.
[0131] A ninth aspect of the present application provides a user terminal applied to a payment platform, and the user terminal may include a memory, a processor, and a computer program stored in the memory and executable on the processor.
[0132] The memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) 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 payment method compatible with multiple payment methods in the embodiment of the third aspect of the present application.
[0133] The processor runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the payment method compatible with multiple payment methods in the above-mentioned third aspect embodiment.
[0134] In some examples, the user terminal may also include a communication interface and a bus, and the memory, processor, and communication interface are connected through the bus to communicate with each other.
[0135] The connection between the memory, processor, communication interface, and bus in the user terminal and the specific implementation method can be found in the relevant description of the embodiment of the acceptance terminal in the seventh aspect above, and will not be repeated here.
[0136] The tenth aspect of the present application provides a payment system compatible with multiple payment methods, which may include an acceptance terminal, a payment platform, and a user terminal. The acceptance terminal is used to execute the payment method compatible with multiple payment methods in the above-mentioned first aspect embodiment; the payment platform is used to execute the payment method compatible with multiple payment methods in the above-mentioned second aspect embodiment; the user terminal is used to execute the payment method compatible with multiple payment methods in the above-mentioned third aspect embodiment. The specific contents of the acceptance terminal, payment platform, user terminal, and payment method compatible with multiple payment methods can be found in the relevant descriptions in the above-mentioned embodiments, which will not be repeated here.
[0137] In the eleventh aspect of the present application, a computer-readable storage medium is provided, on which a computer program instruction is stored, and when the computer program instruction is executed by a processor, the payment method compatible with multiple payment methods in the first aspect embodiment, the payment method compatible with multiple payment methods in the second aspect embodiment, or the payment method compatible with multiple payment methods in the third aspect embodiment can be implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here. Among them, the above-mentioned computer-readable storage medium may include a non-transitory 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.
[0138] The twelfth aspect of the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the payment method compatible with multiple payment methods in the above-mentioned first aspect embodiment, the payment method compatible with multiple payment methods in the second aspect embodiment, or the payment method compatible with multiple payment methods in the third aspect embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0139] It should be clear that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. For device embodiments, acceptance terminal embodiments, user terminal embodiments, equipment embodiments, system 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.
[0140] 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.
[0141] 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 payment method that is compatible with multiple payment methods, It is characterized in that Applied to an acceptance terminal, the method includes: When initiating payment, receiving a payment code acquisition request sent by the merchant information management system; Interacting with a payment object, the payment object including a payment card or a user terminal, the user terminal having a near field communication function; Sending a payment code application request to a payment platform, or triggering the user terminal to send a payment code application request to the payment platform; Receive the target payment code fed back by the payment platform in response to the payment code application request, and send the target payment code to the merchant information management system, so that the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
2. The method according to claim 1, It is characterized in that The payment object includes a payment card; The interaction with the payment object includes: Read the card information in the payment card, including the card ID, which is used to verify the authenticity of the payment card. The payment code application request is sent by the acceptance terminal.
3. The method according to claim 2, It is characterized in that The payment code application request includes the card identification, acceptance terminal information and order identification.
4. The method according to claim 1, It is characterized in that The payment object includes the user terminal; The interaction with the payment object includes: When the user terminal is sensed, payment auxiliary information is transmitted to the user terminal through a near field communication function, wherein the payment auxiliary information includes application program invocation information and acceptance terminal information, so that the user terminal invokes a corresponding payment application program based on the application program invocation information. The payment code application request is sent by the user terminal.
5. The method according to claim 4, It is characterized in that The application calling information includes a uniform resource locator address and / or application information; The payment code application request includes the acceptance terminal information and the order identifier.
6. A payment method that is compatible with multiple payment methods, It is characterized in that Applied to a payment platform, the method comprises: When a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system, a payment code application request is received, the payment object includes a payment card or a user terminal, the user terminal has a near field communication function, and the payment code application request is sent by the acceptance terminal or is triggered by the acceptance terminal to be sent by the user terminal; In response to the payment code application request, feeding back a target payment code to the acceptance terminal, so that the acceptance terminal sends the target payment code to the merchant information management system; The payment is completed by interacting with the merchant information management system based on the target payment code.
7. The method according to claim 6, It is characterized in that The payment object includes a payment card; The card information in the payment card is read by the acceptance terminal to verify the authenticity of the payment card. The card information includes the card identification. The payment code application request is sent by the acceptance terminal.
8. The method according to claim 7, It is characterized in that The payment code application request includes the card identification, acceptance terminal information and order identification.
9. The method according to claim 6, It is characterized in that The payment object includes the user terminal; When the acceptance terminal senses the user terminal, the user terminal reads payment auxiliary information from the acceptance terminal through a near field communication function, the payment auxiliary information including application invocation information and acceptance terminal information, so that the user terminal invokes a corresponding payment application based on the application invocation information. The payment code application request is sent by the user terminal.
10. The method according to claim 9, It is characterized in that The application calling information includes a uniform resource locator address and / or application information; The payment code application request includes the acceptance terminal information and the order identifier.
11. A payment method that is compatible with multiple payment methods, It is characterized in that Applied to a user terminal, the user terminal having a near field communication function, the method comprising: When a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system, the acceptance terminal is triggered to send a payment code application request to the payment platform, so that the payment platform responds to the payment code application request and feeds back the target payment code to the acceptance terminal. The target payment code is used to be sent by the acceptance terminal to the merchant information management system, and the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
12. The method according to claim 11, It is characterized in that The sending of a payment code application request to the payment platform by the acceptance terminal includes: When the acceptance terminal is sensed, the payment auxiliary information is read from the acceptance terminal through the near field communication function, wherein the payment auxiliary information includes application calling information and acceptance terminal information; The corresponding payment application is called based on the application calling information, and a payment code application request is sent to the payment platform.
13. The method according to claim 12, It is characterized in that The calling up a corresponding payment application based on the application calling information and sending a payment code application request to the payment platform includes: In the case where the application calling information includes a uniform resource locator address, calling a light application that comes with the operating system of the user terminal according to the uniform resource locator address; In response to the user's authorization input, jump to the payment application and send a payment code application request to the payment platform.
14. The method according to claim 12, It is characterized in that The calling up a corresponding payment application based on the application calling information and sending a payment code application request to the payment platform includes: In the case that the application calling information includes application information, the payment application indicated by the application information is called up, and a payment code application request is sent to the payment platform.
15. The method according to any one of claims 12 to 14, It is characterized in that The payment code application request includes the acceptance terminal information and the order identifier.
16. A receiving terminal, It is characterized in that include: A receiving module, used to receive a payment code acquisition request sent by the merchant information management system when initiating payment; A data transmission module, used to interact with a payment object, wherein the payment object includes a payment card or a user terminal, and the user terminal has a near field communication function; A sending module, used to send a payment code application request to the payment platform, or trigger the user terminal to send a payment code application request to the payment platform; The receiving module is also used to receive the target payment code fed back by the payment platform in response to the payment code application request, and send the target payment code to the merchant information management system, so that the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
17. A payment device compatible with multiple payment methods, It is characterized in that Applied to a payment platform, the device comprises: A receiving module, configured to receive a payment code application request when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system, wherein the payment object includes a payment card or a user terminal, wherein the user terminal has a near field communication function, and the payment code application request is sent by the acceptance terminal or is triggered to be sent by the user terminal by the acceptance terminal; a sending module, configured to feed back a target payment code to the acceptance terminal in response to the payment code application request, so that the acceptance terminal sends the target payment code to the merchant information management system; The receiving module and the sending module are also used to interact with the merchant information management system based on the target payment code to complete the payment.
18. A user terminal, It is characterized in that The user terminal has a near field communication function, and the user terminal includes: A data trigger module, configured to be triggered by the acceptance terminal when a payment is initiated and the acceptance terminal receives a payment code acquisition request sent by the merchant information management system; a sending module, configured to send a payment code application request to the payment platform, so that the payment platform responds to the payment code application request and feeds back a target payment code to the acceptance terminal; The target payment code is used to be sent by the acceptance terminal to the merchant information management system, and the merchant information management system uses the target payment code to interact with the payment platform and complete the payment.
19. A receiving terminal, It is characterized in that include: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the payment method compatible with multiple payment methods as described in any one of claims 1 to 5 is implemented.
20. An electronic device, It is characterized in that include: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the payment method compatible with multiple payment methods as described in any one of claims 6 to 10 is implemented.
21. A user terminal, It is characterized in that include: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the payment method compatible with multiple payment methods as described in any one of claims 11 to 15 is implemented.
22. A payment system that is compatible with multiple payment methods. It is characterized in that include: An acceptance terminal, used for executing the payment method compatible with multiple payment methods as claimed in any one of claims 1 to 5; A payment platform for executing a payment method compatible with multiple payment methods as claimed in any one of claims 6 to 10; A user terminal, used to execute the payment method compatible with multiple payment methods as described in any one of claims 11 to 15.
23. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the payment method compatible with multiple payment methods as described in any one of claims 1 to 15.
24. A computer program product, It is characterized in that It comprises a computer program, which, when executed by a processor, implements the payment method compatible with multiple payment methods as described in any one of claims 1 to 15.
Citation Information
Cited By
Payment method and device, equipment and storage medium
CN119722057A
