Payment system, method, device, storage medium and electronic device

Abstract

This specification discloses a payment system in which a contactless payment device is deployed in a taxi. The taxi meter sends the fare amount to the taxi management system. The taxi management system creates an order based on the fare amount and sends an order identifier to the settlement system. The settlement system then sends the order identifier to the contactless payment device. In response to contactless communication with the user terminal, the contactless payment device obtains the payment identifier of the paying user and sends both the payment identifier and the order identifier to the settlement system. The settlement system then processes the payment for the order corresponding to the order identifier based on the payment identifier. Through this payment system, the paying user only needs to use their user terminal to communicate contactlessly with the contactless payment device deployed in the taxi to complete the payment for traditional taxi services, effectively improving payment efficiency and greatly enhancing the convenience of using traditional taxi services.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a payment system, method, apparatus, storage medium and electronic device. Background Technology

[0002] Currently, in the travel business scenario, although people are becoming more and more accustomed to ride-hailing services, traditional taxi services still occupy a certain proportion of the market, especially in environments such as airports and train stations.

[0003] When using ride-hailing services, passengers can pay directly online, but the payment process for traditional taxi services remains relatively cumbersome.

[0004] Therefore, improving the payment efficiency of traditional taxi services to enhance user convenience is an urgent problem to be solved. Summary of the Invention

[0005] This specification provides a payment system, method, apparatus, storage medium, and electronic device to partially address the problems existing in the prior art.

[0006] The embodiments in this specification adopt the following technical solutions:

[0007] This specification provides a payment system comprising: a user terminal, a non-acceptance device, a taxi fare meter, a taxi management system, and a settlement system; wherein the non-acceptance device and the taxi fare meter are both deployed in taxis; wherein:

[0008] The taxi metering device is used to send the amount received to the taxi management system;

[0009] The taxi management system is used to receive the amount of payment sent by the taxi metering device, create an order based on the amount of payment, and send the order identifier of the order to the settlement system;

[0010] The settlement system is used to send the order identifier to the non-accepting processing device;

[0011] The user terminal is used for contactless communication with the non-receiving device;

[0012] The non-receiving device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user and sends the payment identifier and the order identifier to the settlement system;

[0013] The settlement system is used to process payment settlements for the orders corresponding to the order identifiers based on the received payment identifiers.

[0014] This specification provides a payment method applied to a non-acceptance device deployed in a taxi; the method includes:

[0015] The system receives an order identifier sent by the settlement system; wherein the order identifier is the order identifier of the order created by the taxi management system based on the amount of payment received from the taxi metering device deployed on the taxi, and the order identifier sent by the settlement system is sent by the taxi management system to the settlement system.

[0016] To conduct contactless communication with user terminals;

[0017] In response to the contactless communication, the payment identifier of the paying user is obtained;

[0018] The payment identifier and the order identifier are sent to the settlement system, so that the settlement system can process payment settlement for the order corresponding to the order identifier based on the received payment identifier.

[0019] This specification provides a payment method applied to a taxi management platform, the method comprising:

[0020] The system receives a first order identifier from an external business order sent by a taxi SaaS platform; wherein the external business order is created by the taxi SaaS platform based on the amount of payment received from the taxi fare metering device deployed on the taxi.

[0021] Based on the received external business order corresponding to the first order identifier, create an internal business order associated with the external business order;

[0022] The second order identifier of the internal business order is sent to the settlement system, which then sends the second order identifier to a non-acceptance device deployed on the taxi. The non-acceptance device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user and sends the payment identifier and the second order identifier to the settlement system, which then performs payment settlement based on the payment identifier and the second order identifier.

[0023] This specification provides a payment method applied to a taxi SaaS platform, the method comprising:

[0024] Receive payment amounts sent by taxi metering devices deployed on taxis;

[0025] Create an external business order based on the stated amount received;

[0026] The first order identifier of the external business order is sent to the taxi management platform, which then creates an internal business order associated with the external business order based on the first order identifier. The second order identifier of the internal business order is then sent to the settlement system, which in turn sends the second order identifier to a non-accepting device deployed on the taxi. This non-accepting device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user and sends both the payment identifier and the second order identifier to the settlement system. The settlement system then performs payment settlement based on the payment identifier and the second order identifier.

[0027] This specification provides a payment method, which is applied to a settlement system, and the method includes:

[0028] The system receives an order identifier sent by the taxi management system. The order identifier is an order identifier created by the taxi management system based on the amount of payment received after the taxi metering device deployed on the taxi sends the amount of payment to the taxi management system.

[0029] The order identifier is sent to the non-acceptance device deployed on the taxi;

[0030] The system receives a payment identifier and an order identifier sent by the non-accepting device; wherein the payment identifier is a payment identifier of the paying user obtained by the non-accepting device in response to contactless communication with the user terminal.

[0031] Based on the received payment identifier, payment settlement is performed on the order corresponding to the order identifier.

[0032] This specification provides a payment device for use with a non-acceptance device deployed in a taxi; the device includes:

[0033] The receiving module is used to receive an order identifier sent by the settlement system; wherein, the order identifier is the order identifier of the order created by the taxi management system based on the amount of payment received from the taxi metering device deployed on the taxi after receiving the amount of payment, and the order identifier sent by the settlement system is sent by the taxi management system to the settlement system;

[0034] The communication module is used for contactless communication with the user terminal;

[0035] The acquisition module is used to acquire the payment identifier of the paying user in response to the contactless communication;

[0036] The sending module is used to send the payment identifier and the order identifier to the settlement system, so that the settlement system can perform payment settlement on the order corresponding to the order identifier based on the received payment identifier.

[0037] This specification provides a payment device, which is applied to a taxi management platform, and the device includes:

[0038] The receiving module is used to receive the first order identifier of an external business order sent by the taxi SaaS platform; wherein, the external business order is created by the taxi SaaS platform based on the amount of payment received from the taxi fare metering device deployed on the taxi;

[0039] A creation module is used to create an internal business order associated with the external business order based on the received first order identifier corresponding to the external business order;

[0040] The sending module is used to send the second order identifier of the internal business order to the settlement system, so that the settlement system sends the second order identifier to the non-acceptance device deployed on the taxi, so that the non-acceptance device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user, and sends the payment identifier and the second order identifier to the settlement system, so that the settlement system performs payment settlement based on the payment identifier and the second order identifier.

[0041] This specification provides a payment device applied to a taxi SaaS platform, the device comprising:

[0042] The receiving module is used to receive the payment amount sent by the taxi fare meter deployed on the taxi;

[0043] A module is created to generate external business orders based on the amount received.

[0044] The sending module is used to send the first order identifier of the external business order to the taxi management platform, so that the taxi management platform can create an internal business order associated with the external business order based on the external business order corresponding to the first order identifier, and send the second order identifier of the internal business order to the settlement system, so that the settlement system can send the second order identifier to the non-acceptance device deployed on the taxi, so that the non-acceptance device can obtain the payment identifier of the paying user in response to contactless communication with the user terminal, and send the payment identifier and the second order identifier to the settlement system, so that the settlement system can perform payment settlement based on the payment identifier and the second order identifier.

[0045] This specification provides a payment device, which is applied to a settlement system, and the device includes:

[0046] The first receiving module is used to receive an order identifier sent by the taxi management system. The order identifier is the order identifier of an order created by the taxi management system based on the amount of payment received after the taxi metering device deployed on the taxi sends the amount of payment received to the taxi management system.

[0047] A sending module is used to send the order identifier to a non-receiving device deployed on the taxi;

[0048] The second receiving module is used to receive the payment identifier and the order identifier sent by the non-receiving device; wherein, the payment identifier is the payment identifier of the paying user obtained by the non-receiving device in response to contactless communication with the user terminal;

[0049] The settlement module is used to perform payment settlement for the order corresponding to the order identifier based on the received payment identifier.

[0050] This specification provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the payment method described above.

[0051] This specification provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the aforementioned payment method.

[0052] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:

[0053] This specification discloses a payment system in which a contactless payment device is deployed in a taxi. The taxi meter sends the fare amount to the taxi management system. The taxi management system creates an order based on the fare amount and sends an order identifier to the settlement system. The settlement system then sends the order identifier to the contactless payment device. In response to contactless communication with the user terminal, the contactless payment device obtains the payment identifier of the paying user and sends both the payment identifier and the order identifier to the settlement system. The settlement system then processes the payment for the order corresponding to the order identifier based on the payment identifier. Through this payment system, the paying user only needs to use their user terminal to communicate contactlessly with the contactless payment device deployed in the taxi to complete the payment for traditional taxi services, effectively improving payment efficiency and greatly enhancing the convenience of using traditional taxi services. Attached Figure Description

[0054] The accompanying drawings, which are included to provide a further understanding of this specification and form part of this specification, illustrate exemplary embodiments and are used to explain this specification, but do not constitute an undue limitation thereof. In the drawings:

[0055] Figure 1 This specification provides a schematic diagram of a payment system structure as an embodiment.

[0056] Figure 2 A flowchart of a payment method provided in the embodiments of this specification;

[0057] Figure 3 This is a schematic diagram illustrating the process of a non-accepting device obtaining a payment identifier, provided in an embodiment of this specification.

[0058] Figure 4 A detailed flowchart of the payment method provided in the embodiments of this specification;

[0059] Figure 5 This is a schematic diagram of a first type of payment device provided in the embodiments of this specification;

[0060] Figure 6 This is a schematic diagram of a second payment device provided in the embodiments of this specification;

[0061] Figure 7 A schematic diagram of a third payment device provided in the embodiments of this specification;

[0062] Figure 8 A schematic diagram of the fourth payment device provided in the embodiments of this specification;

[0063] Figure 9 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this specification. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.

[0065] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0066] Figure 1 This specification provides a schematic diagram of a payment system structure, including: a user terminal, a non-acceptance device, a taxi fare metering device, a taxi management system, and a settlement system.

[0067] Among them, user terminals include the terminals used by payment users, especially mobile terminals such as mobile phones and smartwatches.

[0068] A non-contact payment device is a device used to provide various electronic payment methods to paying users, including offline electronic payment methods such as QR code scanning, facial recognition, and contactless communication-based electronic payments. This manual only uses the example of a non-contact payment device providing contactless communication-based electronic payments. This non-contact payment device is deployed in taxis and can communicate with various network-side devices, including the settlement system, via mobile networks (such as 4G and 5G).

[0069] Taxi fare calculation devices are also deployed in taxis and are the traditional fare calculation tools for taxis. They can record trip data locally and calculate fares locally based on the recorded trip data. These taxi fare calculation devices include, but are not limited to, fare meters. It should be noted that the taxis described in the embodiments of this specification refer to traditional taxis that use taxi fare calculation devices deployed in taxis, and not ride-hailing vehicles that record trip data through driver terminals or other positioning devices and upload the trip data to network-side devices via mobile networks or dedicated taxi networks for fare calculation.

[0070] The taxi management system is a network-side system used to manage traditional taxis. It can be used to record the correspondence between taxi metering devices, taxi vehicle identification (such as license plates), and driver information, and can also be used to supervise and manage each taxi.

[0071] The settlement system is also a network-side system used to settle payments for payers based on their payment identifiers and the amount received.

[0072] based on Figure 1 The payment system shown in this specification provides, as illustrated in the embodiments, the payment system provided in this specification. Figure 2 The payment methods shown.

[0073] Figure 2 A flowchart of a payment method provided for embodiments of this specification includes the following steps:

[0074] S200: The taxi metering device sends the amount received to the taxi management system.

[0075] In the embodiments described in this specification, the taxi fare meter can record the taxi's trip data in real time while the driver is providing services to passengers, and determine the fare amount based on the recorded trip data after the trip ends, and then send the fare amount to the taxi management system. Alternatively, the taxi fare meter can directly send the recorded trip data to the taxi management system after the trip ends, and the taxi management system can then determine the corresponding fare amount based on this trip data. The key is that the taxi management system can determine the fare amount.

[0076] Specifically, when the taxi meter is a meter, after the passenger gets in the car, the driver can press the meter down to start recording the trip data. When the passenger arrives at the destination, the driver can lift the meter up. The meter responds to this lifting operation, determines the amount to be charged based on the recorded trip data, and sends the amount to be charged and / or the recorded trip data to the taxi management system.

[0077] In addition, the taxi metering device can also send at least one of the following to the taxi management system: the identifier of the taxi metering device and the vehicle identifier of the taxi pre-written into the taxi metering device.

[0078] S202: The taxi management system receives the amount of payment sent by the taxi metering device, creates an order based on the amount of payment, and sends the order identifier of the order to the settlement system.

[0079] Specifically, after receiving the payment amount from the taxi meter, the taxi management system can first determine the taxi driver's payment account based on at least one of the meter's identifier and the taxi's vehicle identifier. Then, it creates an order based on the payment amount and the payment account, which includes both the payment amount and the payment account, and sends the order identifier to the settlement system.

[0080] At this point, the three elements used for payment in the order—payment account, amount received, and receiving account—already have the amount received and the receiving account; only the payment account is missing.

[0081] S204: The settlement system sends the order identifier to the non-accepting processing device.

[0082] After receiving the order identifier from the taxi management system, the settlement system can send the order identifier to the non-accepting device, so that the non-accepting device knows that the order has been created and can interact with the user terminal of the paying user to complete the payment for the order.

[0083] Accordingly, upon receiving the order identifier, the non-accepting device can display a preset prompt message in response to the order identifier. This prompt message is used to remind the paying user to use their own user terminal to conduct contactless communication with the non-accepting device. Specifically, this prompt message can be a voice prompt; that is, after receiving the order identifier, the non-accepting device can play a preset voice prompt message to remind the paying user (i.e., the passenger) to use their own user terminal to conduct contactless communication with the non-accepting device.

[0084] Of course, if the non-accepting device includes a display screen, the above-mentioned prompt information can also be text-based. In this case, after receiving the order identifier, the non-accepting device can display a preset text prompt information. This specification does not limit the specific form of the above-mentioned prompt information in the embodiments.

[0085] S206: The user terminal communicates with the non-receiving device without contact.

[0086] After receiving a prompt message displayed by the non-receiving device, the paying user can use their own user terminal to conduct contactless communication with the non-receiving device based on the prompt message.

[0087] S208: In response to contactless communication with the user terminal, the non-receiving device obtains the payment identifier of the paying user and sends the payment identifier and the order identifier to the settlement system.

[0088] In response to the establishment of this contactless communication, the non-receiving device can obtain the payment identifier of the paying user.

[0089] Specifically, the payment identifier can exist in the user terminal, allowing the non-accepting device to obtain the payment identifier from the user terminal based on the contactless communication. Alternatively, the payment identifier can be dynamically generated by the settlement system, allowing the non-accepting device to obtain the payment identifier from the settlement system in response to the contactless communication. Regardless of the method, the key is that the non-accepting device can obtain the payment identifier of the paying user. The specific process of the non-accepting device obtaining the payment identifier will not be described in detail here, but will be described in detail later.

[0090] The payment identifier contains the user identifier of the paying user.

[0091] After obtaining the payment identifier, the non-accepting device can return the payment identifier and the order identifier sent to the non-accepting device by the settlement system in step S204 to the settlement system.

[0092] S210: The settlement system performs payment settlement for the order corresponding to the order identifier based on the received payment identifier.

[0093] For the order created by the taxi management system in step S202, the settlement system has already obtained the receiving account and amount for the order in step S202. In step S210, after receiving the payment identifier from the paying user, the settlement system can query the paying user's payment account based on the user's identifier, since the payment identifier carries the user's identifier. Once the payment account is found, the three essential elements of the order are complete, and therefore, the settlement system can process the payment settlement for the order corresponding to the received order identifier. That is, the amount corresponding to the receiving amount in the payment account is transferred to the receiving account.

[0094] Using the above method, passengers (i.e., paying users) can complete the payment for the taxi service simply by establishing contactless communication with the non-receiving device on the taxi using their own user terminal. This effectively improves the payment efficiency of traditional taxi services and greatly enhances the convenience and experience for users of traditional taxi services.

[0095] In the embodiments described in this specification, such as Figure 1 The payment system shown may also include a non-acceptance service ( Figure 1 (Not shown in the image). The non-receiving server is also a network-side device. Then in... Figure 2 In step S202 shown, the taxi management system can send the order identifier of the created order to the settlement system through the non-accepting server.

[0096] Specifically, Figure 2 The detailed process of steps S202~S208, where the non-accepting device obtains the payment identifier of the paying user, is as follows: Figure 3 As shown. Figure 3 This is a schematic diagram illustrating the process of a non-accepting device obtaining a payment identifier, provided in an embodiment of this specification. The process specifically includes the following steps:

[0097] S2020: The taxi management system sends the order identifier of the created order to the non-accepting server.

[0098] S2022: The non-accepting server will send the received order identifier to the settlement system.

[0099] S2040: In response to the received order identifier, the settlement system returns the access address used to access the settlement system to the non-accepting server.

[0100] In step S2022, after receiving the order identifier, the settlement system knows that the order has been created. Next, it needs to enable the non-accepting device to obtain the payment identifier of the paying user. Since the payment identifier is generated by the settlement system and requires user authorization to be generated and allowed to be obtained by the non-accepting device, the settlement system can generate an access address for accessing the settlement system. This access address can specifically be a Uniform Resource Locator (URL), and the page pointed to by this access address can specifically be the payment page of the order corresponding to the order identifier, which may contain the amount received.

[0101] After the settlement system generates the above access address, it can return the access address to the non-accepting server.

[0102] S2042: The non-receiving server sends the access address and the order identifier to the non-receiving device.

[0103] Once the non-accepting server receives the access address, it can send the access address and the order identifier received in step S2020 to the non-accepting device.

[0104] Non-receiving devices can display preset prompts to encourage payment users to use their own user terminals to communicate with non-receiving devices without contact.

[0105] S206: The user terminal communicates with the non-receiving device without contact.

[0106] S2080: The non-receiving device sends the access address to the user terminal based on contactless communication with the user terminal.

[0107] Since the non-receiving device has established contactless communication with the user terminal at this time, the non-receiving device can use this contactless communication to send the access address generated by the settlement system in step S2040 to the user terminal.

[0108] S2082: The user terminal displays a payment page based on the access address, and in response to the payment user's operation on the payment page, authorizes the non-accepting device to obtain the payment identifier of the payment user.

[0109] After receiving the access address, the user terminal can access the settlement system and display the payment page corresponding to the order generated by the settlement system. In addition to the amount received, the payment page may also include an authorization button.

[0110] When a paying user clicks the authorization button, they authorize the non-accepting device to obtain their payment identifier. Specifically, when the paying user clicks the authorization button, the user terminal can send an authorization message to the settlement system. The settlement system can then generate the paying user's payment identifier and send it to the non-accepting device through the non-accepting server. Alternatively, when the paying user clicks the authorization button, the user terminal can send an authorization message to the settlement system. The settlement system can also forward this authorization message to the non-accepting server, which will then provide the paying user's payment identifier to the non-accepting device.

[0111] After the non-accepting device obtains the payment identifier of the paying user, it can send the payment identifier and the order identifier to the settlement system, so that the settlement system can continue to execute step S210 to process the payment settlement for the order.

[0112] In the embodiments described in this specification, since the non-acceptance processing device is deployed in the taxi, and the taxi management system, settlement system, and the aforementioned non-acceptance processing server are all located on the network side, in order to enable the network-side devices and systems to accurately address the non-acceptance processing device deployed in the taxi, the taxi management system can pre-store the binding relationship between the taxi's vehicle identifier and the device identifier of the non-acceptance processing device deployed in that taxi for each taxi. The vehicle identifier in this specification includes, but is not limited to, the taxi's license plate number.

[0113] In step S200, after the driver raises the meter, the taxi metering device sends the fare amount and the taxi's vehicle identification number to the taxi management system. In step S2020, the taxi management system creates an order based on the fare amount and, based on the received vehicle identification number, determines the pre-saved device identification number of the non-accepting device bound to that vehicle identification number. It then sends the order identification number and the device identification number to the non-accepting server. Therefore, after receiving the access address sent by the settlement system in step S2040, the non-accepting server, in step S2042, can send the access address and the order identification number to the non-accepting device corresponding to that device identification number, accurately locating the non-accepting device on the taxi corresponding to the order created by the taxi management system.

[0114] In the embodiments of this specification, the aforementioned settlement system, non-acceptance equipment, and non-acceptance server are generally implemented by institutions that can provide payment services. However, since the taxi management system not only needs to manage each taxi (such as supervising whether taxi operations are compliant), but also needs to create orders for payment, for the aforementioned institutions that can provide payment services, the taxi management system must provide both external taxi management functions and internal payment functions. While this is theoretically feasible, it is impractical in real-world applications. Therefore, the taxi management system described in the embodiments of this specification includes a taxi Software as a Service (SaaS) platform and a taxi management platform. The taxi SaaS platform is used to provide external taxi management functions, and the orders it creates are external business orders, while the taxi management platform is implemented by the aforementioned institutions that provide payment functions and is used to provide internal payment functions. Thus, the detailed payment process provided in the embodiments of this specification can be as follows: Figure 4 As shown.

[0115] Figure 4 A detailed flowchart of the payment method provided in the embodiments of this specification includes the following steps:

[0116] S2000: Taxi metering equipment sends the amount received to the taxi SaaS platform.

[0117] In the embodiments described in this specification, each taxi can be managed by a taxi SaaS platform. Therefore, the taxi SaaS platform can record in advance the binding relationship between information such as the taxi vehicle identification, taxi metering device, device identification of non-acceptance devices deployed on the taxi, driver's payment account, and driver terminal.

[0118] After the taxi meter determines the amount to be collected in response to the driver's action of raising the meter, it can send the amount collected, the trip data recorded this time, and the vehicle identification number of the taxi to the taxi SaaS platform.

[0119] S20200: The taxi SaaS platform creates an external business order based on the amount received and sends the first order identifier of the external business order to the taxi management platform.

[0120] The taxi SaaS platform can first perform simple verification on the received payment amount, the trip data recorded this time, and the vehicle identification of the taxi. For example, it can determine the payment amount based on the received trip data and compare it with the received payment amount. If they match, the verification passes; otherwise, the verification fails. Alternatively, it can determine the vehicle identification of the taxi bound to the taxi metering device based on the taxi metering device that sent this information, and compare it with the received vehicle identification. If they match, the verification passes; otherwise, the verification fails.

[0121] The taxi SaaS platform can also determine the driver's payment account associated with the received taxi vehicle identification and the device identification of non-accepting devices based on the received taxi vehicle identification.

[0122] After verification, an external business order can be created based on the amount received. In addition to the amount received, the external business order may also include the driver's payment account, as well as one or more of the aforementioned trip data and taxi vehicle identification.

[0123] It should be noted that, relative to the institution providing the payment service, the order created by the taxi SaaS platform at this time does not enter any of the institution's devices. Therefore, this order is an external order to the institution. Moreover, this order does not actually have the function of enabling the settlement system to process payment; it is only used to record which taxi provided how much payment and how many trips were covered, and what the driver's and passenger's payment and receipt accounts are. Therefore, essentially, this order is just a business order, not a payment order, and thus it is referred to as an external business order in this embodiment of the specification.

[0124] After creating the external business order, the taxi SaaS platform can send the order identifier, i.e., the first order identifier, of the external business order to the taxi management platform. It can also send the device identifier of the non-accepting device bound to the vehicle identifier to the taxi management platform.

[0125] S20202: The taxi management platform creates an internal business order associated with the external business order based on the received first order identifier, and sends the second order identifier of the internal business order to the non-receiving server.

[0126] The taxi management platform is implemented by the aforementioned payment service provider and is located within that provider.

[0127] After receiving the first order identifier, the taxi management platform, since the first order identifier has already entered the organization's internal system, can create an internal business order based on the external business order corresponding to the first order identifier. The function of this internal business order is similar to that of the external business order; it simply records the current trip and does not enable the settlement system to process payment; it is not a payment order.

[0128] However, although the internal business order at this stage is not a payment order, it still needs to provide data support for the subsequent payment process. Therefore, the taxi management platform needs to perform a relatively detailed verification of the external business order corresponding to the first order identifier received to determine whether the payment is legal if it is based on the data in the external business order. Only after successful verification is the internal business order created.

[0129] Internal business orders also include the amount received, and may also include the driver's payment account, as well as one or more of the following: trip data and taxi vehicle identification.

[0130] It should be noted that internal business orders also have a unique order identifier, namely the second order identifier. Since the second order identifier is used to uniquely identify the internal business order within the aforementioned organization, while the first order identifier is used to uniquely identify the external business order within the taxi SaaS platform outside the organization, this specification does not restrict whether the first order identifier and the second order identifier are the same, as long as the two order identifiers can uniquely identify the external business order and the internal business order within their respective required scopes.

[0131] After creating an internal business order, the taxi management platform can send the second order identifier of the internal business order and the device identifier of the non-accepting device received from the taxi SaaS platform to the non-accepting server, so that the non-accepting server can send the aforementioned second order identifier to the settlement system.

[0132] S2022: The non-accepting server sends the received second order identifier to the settlement system.

[0133] S2040: In response to the received second order identifier, the settlement system returns the access address used to access the settlement system to the non-accepting server.

[0134] S2042: The non-receiving server sends the access address and the second order identifier to the non-receiving device.

[0135] After receiving the access address, the non-accepting server can send the access address and the second order identifier received in step S20202 to the non-accepting device according to the device identifier of the non-accepting device.

[0136] Non-receiving devices can display preset prompts to encourage payment users to use their own user terminals to communicate with non-receiving devices without contact.

[0137] S206: The user terminal communicates with the non-receiving device without contact.

[0138] S2080: The non-receiving device sends the access address to the user terminal based on contactless communication with the user terminal.

[0139] S2082: The user terminal displays a payment page based on the access address, and in response to the payment user's operation on the payment page, authorizes the non-accepting device to obtain the payment identifier of the payment user.

[0140] Figure 4 The steps S2022~S2082 shown are... Figure 2 The steps S2022 to S2082 shown are basically the same, and will not be repeated here.

[0141] S2100: The non-accepting device sends the payment identifier and the second order identifier to the settlement system.

[0142] S2102: The settlement system sends the payment identifier and the second order identifier to the taxi management platform.

[0143] S2104: The taxi management platform writes the payment identifier into the internal business order and determines the first order identifier of the external business order associated with the internal business order corresponding to the received second order identifier, and sends the payment identifier and the first order identifier to the taxi SAAS platform.

[0144] The internal business order is created by the taxi management platform in step S20202. The information consistently missing from this internal business order is the user identifier of the paying user. In step S2102, the taxi management platform, based on the received second order identifier, determines that the user identifier carried in the received payment identifier is the user identifier consistently missing from the internal business order corresponding to the second order identifier. Therefore, in step S2104, the taxi management platform can, on the one hand, write the payment identifier into the internal business order to complete it. The completed internal business order now fully records all the information for the taxi's current trip. On the other hand, it also needs to determine the first order identifier of the external business order associated with the internal business order corresponding to the received second order identifier—that is, the first order identifier of the external business order created by the taxi SaaS platform in step S20200—and send the payment identifier and the first order identifier to the taxi SaaS platform.

[0145] S2106: The taxi SaaS platform writes the received payment identifier into the external business order corresponding to the first order identifier, creates a payment order based on the external business order after writing the payment identifier, and sends the payment order to the settlement system.

[0146] Similarly, the information that has always been missing from the external business order since it was created by the taxi SAAS platform in step S20200 is the user identifier of the paying user. In step S2106, after the taxi SAAS platform receives the first order identifier, it can determine that the user identifier carried in the received payment identifier is the user identifier that has always been missing in the external business order corresponding to the first order identifier.

[0147] Therefore, in step S2104, the taxi SAAS platform can write the payment identifier into the external business order to complete the external business order. The completed external business order has completely recorded all the information of the taxi's current travel service. At this time, both the internal business order and the external business order have been completed, indicating that both the internal and external institutions providing payment services have accurately recorded the complete business record of the taxi's current travel service.

[0148] Now that the business records for this trip have been accurately recorded both internally and externally, the taxi SaaS platform can formally initiate payment for this trip to the organization. Therefore, the taxi SaaS platform also needs to create a payment order based on the external business order with the payment identifier written in it. The payment order may only include the payment identifier of the paying user, the amount received, and the driver's receiving account, and then send the payment order to the settlement system.

[0149] S2108: The settlement system processes payments based on payment orders.

[0150] The settlement system can then determine the payment account of the paying user based on the payment identifier in the payment order, and transfer the amount corresponding to the payment amount in the payment account to the driver's receiving account.

[0151] Of course, the above is only an example of direct connection between the taxi SaaS system and the settlement system. If the taxi SaaS system and the settlement system are connected through a third-party institution, then in step S2106, the taxi SaaS platform needs to send the payment order to the settlement system through the third-party institution for payment settlement after creating the payment order.

[0152] As can be seen from the above methods, completing the payment process requires the paying user to establish contactless communication with the non-accepting device using their user terminal and authorize the non-accepting device to obtain the paying user's payment identifier on the payment page. If the paying user does not authorize the non-accepting device to obtain the payment identifier within a specified time after the payment page is displayed on the user terminal, the non-accepting device can issue a prompt to switch payment methods, reminding the paying user to switch payment methods. The paying user can then display a payment code on their user terminal. This payment code may include a barcode, QR code, or other graphic code carrying the paying user's identifier. The non-accepting device scans the payment code, obtains the user identifier carried in the payment code, and then sends the user identifier to the settlement system for payment settlement using the above methods. If the payment code is not the user's payment code from the aforementioned payment service provider, but rather from another institution that provides payment services, the settlement system can create a payment order for that other institution based on the payment code and send the payment order to that other institution, allowing the other institution's settlement system to process the payment settlement based on the payment order.

[0153] In addition, Figure 4 As shown in the process, after the settlement system completes the payment, it can also return the payment result to the taxi SaaS platform, informing the platform that the external business order it created has been paid for. The payment result can also be displayed on the payer's user terminal, allowing the payer to view the payment result on their device.

[0154] To further enrich the diversity of travel services provided by traditional taxis to users, in the embodiments of this specification, the taxi management system can also send a mini-program service address to a non-accepting device. The non-accepting device can then send the mini-program service address to the user terminal based on contactless communication with the user terminal. The user terminal can run the corresponding mini-program according to the mini-program service address and provide services to paying users through the mini-program.

[0155] Specifically, the taxi SaaS platform can send the mini-program service address to the taxi management platform. After receiving the mini-program service address, the taxi management platform will send the mini-program service address to the non-receiving server, which will then send the mini-program service address to the non-receiving device.

[0156] After receiving the mini-program service address, the non-receiving device can send a service prompt message to instruct the user (this user can include the paying user or other users in the taxi) to establish contactless communication with the non-receiving device using their own user terminal. It should be noted that this contactless communication may not be the same as the contactless communication established during the payment process. The user can then use their own user terminal to establish contactless communication with the non-receiving device based on the service prompt message, obtain the mini-program service address based on this communication, and then run the corresponding mini-program to obtain the service.

[0157] The following examples illustrate three services provided through mini-programs.

[0158] The first method involves the user terminal receiving advertisements and promotional information pushed by the taxi SaaS platform through a running mini-program, which is then displayed to the user, who can browse or purchase as needed.

[0159] The second type differs from ride-hailing services. Traditional taxis typically require passengers to verbally inform the driver of their desired destination upon boarding. However, the driver may not know the detailed address of this destination. Therefore, in this embodiment, the user terminal can receive the destination address information input by the user through a running mini-program and upload it to the taxi management system, specifically a taxi SaaS platform. The taxi management system can then identify the driver terminal bound to the non-receiving device that sent the aforementioned mini-program service address to the user terminal, and send the received destination address information to the driver terminal. The driver terminal can then use an electronic map to query the destination address information, display the corresponding destination, and generate a navigation route from the current location to the destination, thus facilitating convenient sharing of the destination from passenger to driver.

[0160] Thirdly, in certain application scenarios, passengers may need to obtain an electronic receipt for their ride after using traditional taxi services. To address this need, the user terminal can establish contactless communication with the non-receiving device after paying for the corresponding order using the methods described above, to run a mini-program. The mini-program will then display the receipt application page for the order and respond to the receipt application request entered by the user on the receipt application page, issuing the receipt corresponding to the order to the user.

[0161] The above three services are merely illustrative examples. Based on the mini-program service address sent by the taxi management system, the user terminal launches and runs the mini-program. Through this mini-program, the taxi management system can provide any service to the user during the passenger's ride in a traditional taxi or after payment. This specification does not limit the scope of these services.

[0162] The above is a payment method provided by the embodiments of this specification. Based on the same idea, this specification also provides corresponding devices, storage media and electronic devices.

[0163] Figure 5 This is a schematic diagram of a first payment device provided in an embodiment of this specification. The device is applied to a non-acceptance device deployed in a taxi; the device includes:

[0164] The receiving module 501 is used to receive an order identifier sent by the settlement system; wherein, the order identifier is the order identifier of the order created by the taxi management system based on the amount of payment received from the taxi metering device deployed on the taxi after receiving the amount of payment, and the order identifier sent by the settlement system is sent by the taxi management system to the settlement system;

[0165] Communication module 502 is used for contactless communication with user terminals;

[0166] The acquisition module 503 is used to acquire the payment identifier of the paying user in response to the contactless communication;

[0167] The sending module 504 is used to send the payment identifier and the order identifier to the settlement system, so that the settlement system can perform payment settlement on the order corresponding to the order identifier according to the received payment identifier.

[0168] Optionally, the acquisition module 503 is specifically configured to: receive the access address and the order identifier sent by the non-accepting agent server; the access address is used to access the settlement system; the order identifier is sent by the taxi management system to the settlement system through the non-accepting agent server; the access address and the order identifier sent by the non-accepting agent server are returned by the settlement system to the non-accepting agent server after receiving the order identifier sent by the non-accepting agent server; based on contactless communication with the user terminal, send the access address to the user terminal, so that the user terminal displays a payment page according to the access address, and in response to the payment user's operation on the payment page, authorize the device to obtain the payment identifier of the payment user.

[0169] Optionally, the communication module 502 is further configured to, after receiving the order identifier sent by the settlement system and before engaging in contactless communication with the user terminal, display a preset prompt message in response to the received order identifier, the prompt message being used to prompt the paying user to use the user terminal to engage in contactless communication with the non-receiving device.

[0170] Optionally, the receiving module 501 is further configured to receive the mini-program service address sent by the taxi management system;

[0171] The sending module 504 is further configured to send the mini-program service address to the user terminal based on contactless communication with the user terminal, so that the user terminal runs the mini-program according to the mini-program service address and provides services to paying users through the running mini-program.

[0172] Figure 6 This is a schematic diagram of a second payment device provided in an embodiment of this specification. The device is applied to a taxi management platform and includes:

[0173] The receiving module 601 is used to receive the first order identifier of an external business order sent by the taxi SaaS platform; wherein, the external business order is created by the taxi SaaS platform after receiving the payment amount sent by the taxi billing device deployed on the taxi;

[0174] The creation module 602 is used to create an internal business order associated with the external business order based on the received external business order corresponding to the first order identifier;

[0175] The sending module 603 is used to send the second order identifier of the internal business order to the settlement system, so that the settlement system sends the second order identifier to the non-acceptance device deployed on the taxi, so that the non-acceptance device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user, and sends the payment identifier and the second order identifier to the settlement system, so that the settlement system performs payment settlement based on the payment identifier and the second order identifier.

[0176] Optionally, the receiving module 601 is further configured to receive the payment identifier and the second order identifier sent by the settlement system; write the payment identifier into the internal business order corresponding to the second order identifier; and determine the first order identifier of the external business order associated with the internal business order.

[0177] The sending module 603 is further configured to send the payment identifier and the first order identifier to the taxi SAAS platform, so that the taxi SAAS platform writes the received payment identifier into the external business order corresponding to the first order identifier, creates a payment order based on the external business order after writing the payment identifier, and sends the payment order to the settlement system so that the settlement system can perform payment settlement based on the payment order.

[0178] Figure 7 This is a schematic diagram of a third payment device provided in the embodiments of this specification. The device is applied to a taxi SaaS platform and includes:

[0179] The receiving module 701 is used to receive the amount of payment sent by the taxi fare meter deployed on the taxi;

[0180] Module 702 is used to create external business orders based on the amount received.

[0181] The sending module 703 is used to send the first order identifier of the external business order to the taxi management platform, so that the taxi management platform can create an internal business order associated with the external business order based on the external business order corresponding to the first order identifier, and send the second order identifier of the internal business order to the settlement system, so that the settlement system can send the second order identifier to the non-acceptance device deployed on the taxi, so that the non-acceptance device can obtain the payment identifier of the paying user in response to contactless communication with the user terminal, and send the payment identifier and the second order identifier to the settlement system, so that the settlement system can perform payment settlement based on the payment identifier and the second order identifier.

[0182] Optionally, the receiving module 701 is further configured to receive a payment identifier and a first order identifier sent by the taxi management platform; wherein, the first order identifier is a first order identifier of an external business order associated with the internal business order determined by the taxi management platform based on the second order identifier after the settlement system sends the payment identifier and the second order identifier to the taxi management platform; and to write the received payment identifier into the external business order corresponding to the first order identifier;

[0183] The creation module 702 is also used to create a payment order based on the external business order written with the payment identifier;

[0184] The sending module 703 is specifically used to send the payment order to the settlement system, so that the settlement system can perform payment settlement according to the payment order.

[0185] Optionally, the receiving module 701 is specifically used to receive the vehicle identifier of the taxi sent by the taxi metering device deployed on the taxi;

[0186] The sending module 703 is specifically used to: determine, based on the received vehicle identifier, a pre-saved device identifier of a non-accepting device bound to the vehicle identifier; send the first order identifier of the external business order and the device identifier to the taxi management platform, so that the taxi management platform creates an internal business order associated with the external business order based on the external business order corresponding to the first order identifier; and send the device identifier and the second order identifier of the internal business order to the settlement system, so that the settlement system sends the second order identifier to the non-accepting device deployed on the taxi based on the device identifier.

[0187] Optionally, the sending module 703 is further configured to send the mini-program service address to the non-receiving device, so that the non-receiving device sends the mini-program service address to the user terminal based on contactless communication with the user terminal, so that the user terminal runs the mini-program according to the mini-program service address and provides services to the paying user through the running mini-program.

[0188] Optionally, the receiving module 701 is further configured to receive destination address information uploaded by the user terminal through the mini-program, wherein the destination address information is the destination address information input by the paying user received by the user terminal through the running mini-program;

[0189] The sending module 703 is further configured to determine, based on the device identifier of the non-receiving device, a driver terminal pre-bound to the device identifier; and send the received destination address information to the driver terminal.

[0190] Figure 8 This is a schematic diagram of a fourth payment device provided in the embodiments of this specification. The device is applied to a settlement system and includes:

[0191] The first receiving module 801 is used to receive an order identifier sent by the taxi management system. The order identifier is the order identifier of an order created by the taxi management system based on the amount of payment received after the taxi metering device deployed on the taxi sends the amount of payment received to the taxi management system.

[0192] Sending module 802 is used to send the order identifier to a non-acceptance device deployed on the taxi;

[0193] The second receiving module 803 is used to receive the payment identifier and the order identifier sent by the non-receiving device; wherein, the payment identifier is the payment identifier of the paying user obtained by the non-receiving device in response to contactless communication with the user terminal;

[0194] The settlement module 804 is used to perform payment settlement for the order corresponding to the order identifier based on the received payment identifier.

[0195] Optionally, the first receiving module 801 is specifically used to receive the order identifier sent by the taxi management system through a non-receiving server.

[0196] The sending module 802 is specifically used to, in response to the received order identifier, return the access address of the user accessing the settlement system to the non-accepting agent server, and send the access address and the order identifier to the non-accepting agent device through the non-accepting agent server.

[0197] Optionally, the taxi management system includes a taxi SaaS platform and a taxi management platform;

[0198] The order identifier received by the device is the second order identifier of the internal business order; the internal business order is an internal business order created by the taxi management platform based on the external business order corresponding to the first order identifier sent by the taxi SAAS platform and associated with the external business order; the external business order is created by the taxi SAAS platform based on the amount of payment sent by the taxi billing device;

[0199] The second receiving module 803 is specifically used to receive the payment identifier and the second order identifier sent by the non-accepting device;

[0200] The settlement module 804 is specifically used to: send the payment identifier and the second order identifier to the taxi management platform, causing the taxi management platform to write the payment identifier into the internal business order, and determine the first order identifier of the external business order associated with the internal business order corresponding to the received second order identifier; send the payment identifier and the first order identifier to the taxi SaaS platform; receive a payment order sent by the taxi SaaS platform, wherein the payment order is created by the taxi SaaS platform by writing the received payment identifier into the external business order corresponding to the first order identifier, and based on the external business order after writing the payment identifier; and perform payment settlement according to the payment order.

[0201] This specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can be used to perform the payment method provided above.

[0202] based on Figures 2-4 The payment method shown in this specification is further provided in the embodiments. Figure 9 The diagram shows the structure of the electronic device. Figure 9 At the hardware level, the electronic device includes a processor, internal bus, network interface, memory, and non-volatile storage, and may also include other hardware required for the business operations. The processor reads the corresponding computer program from the non-volatile storage into memory and then runs it to implement the aforementioned payment method.

[0203] The above description is merely an embodiment of this specification and is not intended to limit this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification.

Claims

1. A payment system, the payment system comprising: User terminal, non-receiving device, taxi fare metering device, taxi management system, settlement system; the non-receiving device and the taxi fare metering device are both deployed on taxis; wherein: The taxi metering device is used to send the amount received to the taxi management system; The taxi management system is used to receive the amount of payment sent by the taxi metering device, create an order based on the amount of payment, and send the order identifier of the order to the settlement system; The settlement system is used to send the order identifier to the non-accepting processing device; The user terminal is used for contactless communication with the non-receiving device; The non-receiving device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user dynamically generated by the settlement system from the settlement system, and sends the payment identifier and the order identifier to the settlement system; The settlement system is used to process payment settlements for the orders corresponding to the order identifiers based on the received payment identifiers.

2. The payment system as described in claim 1, further comprising: Non-receiving server; The taxi management system is specifically used to send the order identifier of the order to the non-accepting server. The non-accepting server is used to send the received order identifier to the settlement system; The settlement system is also used to, in response to the received order identifier, return the access address used to access the settlement system to the non-accepting server; The non-acceptance server is also used to send the access address and the order identifier to the non-acceptance device; The non-receiving device is specifically used to send the access address to the user terminal based on non-contact communication with the user terminal; The user terminal is specifically used to display a payment page based on the access address, and in response to the payment user's operation on the payment page, authorize the non-accepting device to obtain the payment identifier of the payment user.

3. The payment system as described in claim 1, wherein the non-accepting device is further configured to, in response to the received order identifier, display a preset prompt message, the prompt message being used to prompt the paying user to use the user terminal to conduct contactless communication with the non-accepting device.

4. The payment system as described in claim 2, wherein the taxi metering device is specifically used to send the amount received and the vehicle identification number of the taxi to the taxi management system; The taxi management system is specifically used to determine, based on the received vehicle identifier, a pre-saved device identifier of a non-accepting device bound to the vehicle identifier, and send the order identifier and the device identifier to the non-accepting server; Specifically, the non-accepting agent server is used to send the access address and the order identifier to the non-accepting agent device corresponding to the device identifier after receiving the access address returned by the settlement system.

5. The payment system as described in claim 1, wherein the taxi management system comprises a taxi SaaS platform and a taxi management platform; The taxi fare meter is specifically used to send the amount received to the taxi SaaS platform. The taxi SaaS platform is used to create external business orders based on the amount received, and send the first order identifier of the external business order to the taxi management platform. The taxi management platform is used to create an internal business order associated with the external business order based on the received first order identifier, and send the second order identifier of the internal business order to the settlement system.

6. The payment system as described in claim 5, wherein the settlement system is specifically configured to send the payment identifier and the second order identifier to the taxi management platform; The taxi management platform is also used to write the payment identifier into the internal business order, determine the first order identifier of the external business order associated with the internal business order corresponding to the received second order identifier, and send the payment identifier and the first order identifier to the taxi SAAS platform; The taxi SaaS platform is also used to write the received payment identifier into the external business order corresponding to the first order identifier, create a payment order based on the external business order after writing the payment identifier, and send the payment order to the settlement system; The settlement system is specifically used to process payment settlements based on the payment orders.

7. The payment system as described in claim 1, wherein the taxi management system is further configured to send a mini-program service address to the non-accepting device; The non-receiving device is also used to send the mini-program service address to the user terminal based on contactless communication with the user terminal; The user terminal is also used to run the mini-program according to the mini-program service address, and to provide services to paying users through the running mini-program.

8. The payment system of claim 7, further comprising: Driver terminal; The user terminal is specifically used to receive the destination address information input by the paying user through the running mini-program, and upload the destination address information to the taxi management system; The taxi management system is also used to determine the driver terminal pre-bound to the device identifier based on the device identifier of the non-accepting device, and send the received destination address information to the driver terminal.

9. The payment system as described in claim 7, wherein the user terminal is specifically configured to display the invoice application page for the order corresponding to the order identifier through the running mini-program, and in response to the invoice application request entered by the paying user on the invoice application page, issue an invoice corresponding to the order to the paying user.

10. A payment method applied to a non-acceptance device deployed in a taxi; the method comprising: The system receives an order identifier sent by the settlement system; wherein the order identifier is the order identifier of the order created by the taxi management system based on the amount of payment received from the taxi metering device deployed on the taxi, and the order identifier sent by the settlement system is sent by the taxi management system to the settlement system. To conduct contactless communication with user terminals; In response to the contactless communication, the payment identifier of the paying user dynamically generated by the settlement system is obtained from the settlement system; The payment identifier and the order identifier are sent to the settlement system, so that the settlement system can process payment settlement for the order corresponding to the order identifier based on the received payment identifier.

11. The method as described in claim 10, wherein obtaining the payment identifier of the paying user specifically includes: Receive the access address and the order identifier sent by the non-receiving server; The access address is used to access the settlement system; The order identifier is sent by the taxi management system to the settlement system through the non-accepting agent server; the access address and the order identifier sent by the non-accepting agent server are returned by the settlement system to the non-accepting agent server after receiving the order identifier sent by the non-accepting agent server. Based on contactless communication with the user terminal, the access address is sent to the user terminal, enabling the user terminal to display a payment page according to the access address, and in response to the payment user's operation on the payment page, authorizing the non-receiving device to obtain the payment identifier of the payment user.

12. The method of claim 10, wherein after receiving the order identifier sent by the settlement system and before engaging in contactless communication with the user terminal, the method further comprises: In response to the received order identifier, a preset prompt message is displayed, which prompts the paying user to use the user terminal to conduct contactless communication with the non-receiving device.

13. The method of claim 10, further comprising: Receive the mini-program service address sent by the taxi management system; Based on contactless communication with the user terminal, the mini-program service address is sent to the user terminal, enabling the user terminal to run the mini-program according to the mini-program service address and provide services to paying users through the running mini-program.

14. A payment method applied to a taxi management platform, the method comprising: The system receives a first order identifier from an external business order sent by a taxi SaaS platform; wherein the external business order is created by the taxi SaaS platform based on the amount of payment received from the taxi fare metering device deployed on the taxi. Based on the received external business order corresponding to the first order identifier, create an internal business order associated with the external business order; The second order identifier of the internal business order is sent to the settlement system, which then sends the second order identifier to the non-acceptance device deployed on the taxi. In response to contactless communication with the user terminal, the non-acceptance device obtains the payment identifier of the paying user dynamically generated by the settlement system and sends the payment identifier and the second order identifier to the settlement system, so that the settlement system performs payment settlement based on the payment identifier and the second order identifier.

15. The method of claim 14, further comprising: Receive the payment identifier and the second order identifier sent by the settlement system; Write the payment identifier into the internal business order corresponding to the second order identifier, and determine the first order identifier of the external business order associated with the internal business order; The payment identifier and the first order identifier are sent to the taxi SaaS platform, which then writes the received payment identifier into the external business order corresponding to the first order identifier, creates a payment order based on the external business order after the payment identifier is written, and sends the payment order to the settlement system so that the settlement system can perform payment settlement based on the payment order.

16. A payment method applied to a taxi SaaS platform, the method comprising: Receive payment amounts sent by taxi metering devices deployed on taxis; Create an external business order based on the stated amount received; The first order identifier of the external business order is sent to the taxi management platform, which then creates an internal business order associated with the external business order based on the first order identifier. The second order identifier of the internal business order is then sent to the settlement system, which in turn sends the second order identifier to a non-accepting device deployed on the taxi. This non-accepting device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user dynamically generated by the settlement system and sends both the payment identifier and the second order identifier to the settlement system. The settlement system then performs payment settlement based on the payment identifier and the second order identifier.

17. The method of claim 16, further comprising: The system receives a payment identifier and a first order identifier sent by the taxi management platform; wherein, the first order identifier is the first order identifier of the external business order associated with the internal business order, determined by the taxi management platform based on the second order identifier after the settlement system sends the payment identifier and the second order identifier to the taxi management platform; Write the received payment identifier into the external business order corresponding to the first order identifier; A payment order is created based on the external business order containing the payment identifier; The payment order is sent to the settlement system, so that the settlement system can process the payment settlement based on the payment order.

18. The method of claim 16, wherein receiving the payment amount sent by a taxi fare meter deployed on a taxi, specifically includes: Receive the vehicle identifier of the taxi sent by the taxi metering device deployed on the taxi; Sending the first order identifier of the external business order to the taxi management platform specifically includes: Based on the received vehicle identifier, determine the device identifier of the non-receiving device that is pre-saved and bound to the vehicle identifier; The first order identifier of the external business order and the device identifier are sent to the taxi management platform, so that the taxi management platform can create an internal business order associated with the external business order based on the external business order corresponding to the first order identifier, and send the device identifier and the second order identifier of the internal business order to the settlement system, so that the settlement system can send the second order identifier to the non-accepting device deployed on the taxi based on the device identifier.

19. The method of claim 16, further comprising: The non-accepting device sends the mini-program service address to the user terminal, enabling the non-accepting device to send the mini-program service address to the user terminal based on contactless communication with the user terminal. This allows the user terminal to run the mini-program according to the mini-program service address and provide services to the paying user through the running mini-program.

20. The method of claim 19, further comprising: The system receives destination address information uploaded by the user terminal through the mini-program, wherein the destination address information is the destination address information input by the paying user received by the user terminal through the running mini-program; Based on the device identifier of the non-accepting device, determine the driver terminal that is pre-bound to the device identifier; The received destination address information is sent to the driver's terminal.

21. A payment method, the method being applied to a settlement system, the method comprising: The system receives an order identifier sent by the taxi management system. The order identifier is an order identifier created by the taxi management system based on the amount of payment received after the taxi metering device deployed on the taxi sends the amount of payment to the taxi management system. The order identifier is sent to the non-acceptance device deployed on the taxi; The non-accepting device receives a payment identifier and an order identifier; wherein the payment identifier is a payment identifier of the paying user dynamically generated by the settlement system and obtained by the non-accepting device from the settlement system in response to contactless communication with the user terminal. Based on the received payment identifier, payment settlement is performed on the order corresponding to the order identifier.

22. The method of claim 21, wherein receiving an order identifier sent by the taxi management system specifically includes: Receive the order identifier sent by the taxi management system through a non-receiving server; Sending the order identifier to the non-acceptance device deployed on the taxi specifically includes: In response to the received order identifier, the access address of the user accessing the settlement system is returned to the non-accepting agent server, and the access address and the order identifier are sent to the non-accepting agent device through the non-accepting agent server.

23. The method of claim 21, wherein the taxi management system comprises a taxi SaaS platform and a taxi management platform; The order identifier received by the settlement system is the second order identifier of the internal business order; The internal business order is an internal business order created by the taxi management platform based on the external business order corresponding to the first order identifier sent by the taxi SaaS platform, and associated with the external business order; the external business order is created by the taxi SaaS platform based on the amount received sent by the taxi billing device; Receiving the payment identifier and the order identifier sent by the non-accepting device specifically includes: Receive the payment identifier and the second order identifier sent by the non-accepting device; Based on the received payment identifier, payment settlement is performed on the order corresponding to the order identifier, specifically including: The payment identifier and the second order identifier are sent to the taxi management platform, which then writes the payment identifier into the internal business order and determines the first order identifier of the external business order associated with the internal business order corresponding to the received second order identifier. The payment identifier and the first order identifier are then sent to the taxi SaaS platform. The system receives a payment order sent by the taxi SaaS platform. The payment order is created by the taxi SaaS platform by writing the received payment identifier into the external business order corresponding to the first order identifier, and by writing the payment identifier into the external business order. Payment settlement is performed according to the payment order.

24. A payment device applied to a non-acceptance device deployed in a taxi; the device comprising: The receiving module is used to receive an order identifier sent by the settlement system; wherein, the order identifier is the order identifier of the order created by the taxi management system based on the amount of payment received from the taxi metering device deployed on the taxi after receiving the amount of payment, and the order identifier sent by the settlement system is sent by the taxi management system to the settlement system; The communication module is used for contactless communication with the user terminal; The acquisition module is used to acquire, in response to the contactless communication, the payment identifier of the payment user dynamically generated by the settlement system from the settlement system; The sending module is used to send the payment identifier and the order identifier to the settlement system, so that the settlement system can perform payment settlement on the order corresponding to the order identifier based on the received payment identifier.

25. A payment device applied to a taxi management platform, the device comprising: The receiving module is used to receive the first order identifier of an external business order sent by the taxi SaaS platform; wherein, the external business order is created by the taxi SaaS platform based on the amount of payment received from the taxi fare metering device deployed on the taxi; A creation module is used to create an internal business order associated with the external business order based on the received first order identifier corresponding to the external business order; The sending module is used to send the second order identifier of the internal business order to the settlement system, so that the settlement system sends the second order identifier to the non-acceptance device deployed on the taxi, so that the non-acceptance device, in response to contactless communication with the user terminal, obtains the payment identifier of the paying user dynamically generated by the settlement system, and sends the payment identifier and the second order identifier to the settlement system, so that the settlement system performs payment settlement based on the payment identifier and the second order identifier.

26. A payment device applied to a taxi SaaS platform, the device comprising: The receiving module is used to receive the payment amount sent by the taxi fare meter deployed on the taxi; A module is created to generate external business orders based on the amount received. The sending module is used to send the first order identifier of the external business order to the taxi management platform, so that the taxi management platform can create an internal business order associated with the external business order based on the external business order corresponding to the first order identifier, and send the second order identifier of the internal business order to the settlement system, so that the settlement system can send the second order identifier to the non-accepting device deployed on the taxi, so that the non-accepting device can obtain the payment identifier of the paying user dynamically generated by the settlement system in response to contactless communication with the user terminal, and send the payment identifier and the second order identifier to the settlement system, so that the settlement system can perform payment settlement based on the payment identifier and the second order identifier.

27. A payment device, the device being used in a settlement system, the device comprising: The first receiving module is used to receive an order identifier sent by the taxi management system. The order identifier is the order identifier of an order created by the taxi management system based on the amount of payment received after the taxi metering device deployed on the taxi sends the amount of payment received to the taxi management system. A sending module is used to send the order identifier to a non-receiving device deployed on the taxi; The second receiving module is used to receive the payment identifier and the order identifier sent by the non-accepting device; wherein, the payment identifier is the payment identifier of the payment user dynamically generated by the settlement system and obtained by the non-accepting device from the settlement system in response to contactless communication with the user terminal; The settlement module is used to perform payment settlement for the order corresponding to the order identifier based on the received payment identifier.

28. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any one of claims 10-23.

29. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method described in any one of claims 10-23.

Images