Payment methods, systems, devices, platforms, media, and products

Abstract

This application discloses a payment method, system, device, platform, medium, and product, belonging to the field of data processing technology. The method includes: receiving a vehicle service bill sent by a payment device, the vehicle service bill including a bill type; acquiring vehicle monitoring data associated with the bill type of the vehicle service bill; generating payment voucher information when the vehicle service bill matches the vehicle monitoring data; and paying the corresponding amount of the vehicle service bill based on the payment voucher information. According to the embodiments of this application, payment efficiency can be improved and payment time shortened in vehicle service scenarios.

Description

Technical Field

[0001] This application belongs to the field of data processing, and in particular relates to a payment method, system, device, platform, medium and product. Background Technology

[0002] With continuous economic progress and development, automobiles have become an integral part of people's lives. At the same time, the vehicle services provided to car owners are becoming increasingly diversified, such as refueling, parking, and vehicle maintenance.

[0003] In practical applications, after providing vehicle services, users need to verify the service results before completing payment. For example, in a refueling scenario, users need to get out of the car to verify the amount of fuel and the amount to be paid, and then complete the payment through their user terminal. Thus, in vehicle service scenarios, users need to manually verify the service results during the payment process, which is time-consuming and inefficient. Summary of the Invention

[0004] This application provides a payment method, system, device, platform, medium, and product that can improve payment efficiency and shorten payment time in vehicle service scenarios.

[0005] In a first aspect, embodiments of this application provide a payment method applied to an in-vehicle payment system, the method comprising:

[0006] Receive vehicle service bills sent by the payment device, including the bill type;

[0007] Retrieve vehicle monitoring data associated with the billing type of the vehicle service bill;

[0008] When the vehicle service bill is matched with the vehicle monitoring data, payment voucher information is generated;

[0009] Based on the payment voucher information, pay the amount corresponding to the vehicle service bill.

[0010] Secondly, embodiments of this application provide a payment method applied to a payment receiving device, the method comprising:

[0011] Based on the obtained vehicle identification and payment amount, a vehicle service bill is generated;

[0012] Send a vehicle service bill to the vehicle corresponding to the vehicle identification number. The vehicle includes an in-vehicle payment system.

[0013] If the vehicle service bill is successfully verified by the in-vehicle payment system, the system will receive payment voucher information sent by the in-vehicle payment system. The payment voucher information is generated based on the vehicle service bill.

[0014] Send vehicle service bills and payment voucher information to the payment platform;

[0015] Once the payment platform successfully verifies the vehicle service bill and payment voucher information and successfully deducts the payment, the system receives the payment result sent by the payment platform. In this process, the payment platform deducts the amount corresponding to the vehicle service bill from the funds account associated with the in-vehicle payment system and transfers the amount to the funds account corresponding to the payment device.

[0016] Thirdly, embodiments of this application provide a payment method applied to a payment platform, the method comprising:

[0017] Receive vehicle service bill and payment voucher information sent by the payment device. The vehicle service bill is generated by the payment device based on the vehicle identifier and the payment amount. The payment voucher information is generated by the in-vehicle payment system in the vehicle corresponding to the vehicle identifier after the vehicle service bill is successfully verified.

[0018] Perform risk verification on vehicle service bills and payment voucher information;

[0019] If the verification is successful, the amount corresponding to the vehicle service bill will be deducted from the funds account associated with the vehicle payment system, and the amount will be transferred to the funds account corresponding to the payment device to generate a payment result.

[0020] Send payment results to payment devices and in-vehicle payment systems.

[0021] Fourthly, embodiments of this application provide an in-vehicle payment system, including:

[0022] The receiving module is used to receive vehicle service bills sent by the payment device. The vehicle service bill includes the bill type.

[0023] The acquisition module is used to acquire vehicle monitoring data associated with the bill type of the vehicle service bill;

[0024] The generation module is used to generate payment voucher information when the vehicle service bill is matched with the vehicle monitoring data;

[0025] The payment module is used to pay the amount corresponding to the vehicle service bill based on the payment voucher information.

[0026] Fifthly, embodiments of this application provide a payment collection device, including:

[0027] The generation module is used to generate a vehicle service bill based on the obtained vehicle identifier and payment amount;

[0028] The sending module is used to send vehicle service bills to the vehicle corresponding to the vehicle identifier, including the vehicle's in-vehicle payment system;

[0029] The receiving module is used to receive payment voucher information sent by the vehicle payment system when the vehicle service bill is successfully verified by the vehicle payment system. The payment voucher information is generated based on the vehicle service bill.

[0030] The sending module is used to send vehicle service bills and payment voucher information to the payment platform;

[0031] The receiving module is also used to receive the payment result sent by the payment platform when the payment platform successfully verifies the vehicle service bill and payment voucher information and successfully deducts the payment. In this process, the payment platform deducts the amount corresponding to the vehicle service bill from the fund account associated with the vehicle payment system and transfers the amount to the fund account corresponding to the payment device.

[0032] Sixthly, embodiments of this application provide a payment platform, including:

[0033] The receiving module is used to receive vehicle service bills and payment voucher information sent by the payment receiving device. The vehicle service bill is generated by the payment receiving device based on the vehicle identifier and the amount received, and the payment voucher information is generated by the in-vehicle payment system in the vehicle corresponding to the vehicle identifier after the vehicle service bill is successfully verified.

[0034] The risk verification module is used to perform risk verification on vehicle service bills and payment voucher information;

[0035] The payment processing module is used to deduct the amount corresponding to the vehicle service bill from the fund account associated with the vehicle payment system when the verification is successful, and transfer the amount to the fund account corresponding to the payment device to generate the payment result.

[0036] The sending module is used to send payment results to the payment receiving device and the vehicle payment system.

[0037] In a seventh aspect, embodiments of this application provide a payment device, including: a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the payment method of the first aspect, the second aspect, or the third aspect.

[0038] Eighthly, embodiments of this application provide a computer-readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the payment method as shown in the first, second, or third aspects.

[0039] Ninthly, embodiments of this application provide a computer program product stored in a non-volatile storage medium, which, when executed by at least one processor, implements the steps of the payment method as shown in the first, second, or third aspects.

[0040] This application provides a payment method, system, device, platform, medium, and product. An in-vehicle payment system installed in a vehicle can receive vehicle service bills and obtain vehicle monitoring data associated with the bill type of the service bill. Based on this, the in-vehicle payment system can automatically verify the vehicle service bill and vehicle monitoring data, confirming whether they match, eliminating the need for manual verification by the user and simplifying the payment process. Furthermore, if the vehicle service bill and vehicle monitoring data match, i.e., the verification is successful, the in-vehicle payment system can generate payment voucher information and pay the corresponding amount on the vehicle service bill based on this voucher information, completing the payment process. Thus, this application can intelligently verify vehicle service results in vehicle service scenarios, simplifying the user's payment process, effectively improving bill payment efficiency, and shortening payment time. Attached Figure Description

[0041] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 A schematic diagram illustrating an example application scenario of the payment method provided in this application embodiment;

[0043] Figure 2 A flowchart of an embodiment of the payment method provided in the first aspect of this application;

[0044] Figure 3 A flowchart of another embodiment of the payment method provided in the first aspect of this application;

[0045] Figure 4 A flowchart of yet another embodiment of the payment method provided in the first aspect of this application;

[0046] Figure 5 A flowchart illustrating yet another embodiment of the payment method provided in the first aspect of this application;

[0047] Figure 6 A flowchart illustrating yet another embodiment of the payment method provided in the first aspect of this application;

[0048] Figure 7 A flowchart of an embodiment of the payment method provided in the second aspect of this application;

[0049] Figure 8 A flowchart of an embodiment of the payment method provided in the third aspect of this application;

[0050] Figure 9 A flowchart illustrating an example of a payment process provided in an embodiment of this application;

[0051] Figure 10 A schematic diagram of the structure of an embodiment of the in-vehicle payment system provided in the fourth aspect of this application;

[0052] Figure 11 A schematic diagram of the structure of an embodiment of the payment collection device provided in the fifth aspect of this application;

[0053] Figure 12 A schematic diagram of the structure of an embodiment of the payment platform provided in the sixth aspect of this application;

[0054] Figure 13 A schematic diagram of the structure of an embodiment of the payment device provided in the seventh aspect of this application. Detailed Implementation

[0055] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0056] With continuous economic progress and development, automobiles have become an integral part of people's lives. Simultaneously, the vehicle services offered to car owners have become increasingly diversified, including refueling, parking, and vehicle maintenance. In practical applications, after a vehicle service is provided, users need to verify the service result before completing payment. For example, in the refueling scenario, users need to get out of their vehicles to verify the amount refueled and the amount to be paid, and then complete the payment through their user terminals. Thus, in vehicle service scenarios, users need to manually verify the service result during the payment process, resulting in longer payment times and lower efficiency.

[0057] In view of the above-mentioned problems, this application provides a payment method, system, device, platform, medium and product that can automatically verify the vehicle service bill and vehicle monitoring data through the vehicle-mounted payment system installed in the vehicle in the vehicle service scenario. That is, it can confirm whether the vehicle service bill and vehicle monitoring data match, and intelligently verify the vehicle service results without requiring the user to manually check and verify, simplifying the user's payment operation steps, effectively improving the payment efficiency of the bill and shortening the payment time.

[0058] The payment method in this application embodiment can be applied to vehicle service scenarios. This payment method may involve the payer's in-vehicle payment system, the payee's electronic device (hereinafter referred to as the payment device), and the payment platform. The following is in conjunction with... Figure 1 The payment architecture in the embodiments of this application will be described in detail.

[0059] Figure 1 This is a schematic diagram illustrating an example of the application scenario of the payment method provided in this application embodiment.

[0060] like Figure 1 As shown, the architecture of this payment method may include an in-vehicle payment system 11, a payment receiving device 12, and a payment platform 13.

[0061] The in-vehicle payment system 11 can be installed in a vehicle. The in-vehicle payment system 11 may include an in-vehicle application and a payment software development kit (SDK) integrated with the in-vehicle application. The payment SDK provides payment services. The in-vehicle payment system 11 is associated with at least one funds account of the payer to complete the payment through the funds account. The funds account in this embodiment includes, but is not limited to, at least one of the following: a bank account, a third-party payment account, and a mobile wallet account.

[0062] The payment receiving device 12 is a terminal device used by the payee to interact with the in-vehicle payment system 11 during the payment process. Specifically, it can be a mobile phone, tablet, smart wearable device, smart point-of-sale (POS) device, edge device, or cloud service device, etc., without limiting the specific type of payment receiving device 12. In a vehicle service scenario, the payment receiving device 12 can push a vehicle service bill to the in-vehicle payment system 11. This vehicle service bill may include the bill type and the amount received. The payment receiving device 12 may have a payment application installed. The payment application can be used for receiving payments and provides payment services. The payment service is authorized to be linked to at least one of the payee's funds accounts so that the amount received from the vehicle service bill can be added to the funds account.

[0063] The payment platform 13 can be used to communicate with the vehicle payment system 11 and the collection system 12 respectively, to provide the transmission of payment resources for payment services and collection services, thereby completing the deduction of payment accounts and the collection of payment accounts. It can also be used for payment risk verification, control, and settlement.

[0064] Based on the above appendix Figure 1 The payment architecture provided in the embodiments of this application is shown below, and the payment method provided in the embodiments of this application will be described in detail.

[0065] The first aspect of this application provides a payment method applicable to an in-vehicle payment system, meaning that the payment method can be executed by the in-vehicle payment system. For details regarding the in-vehicle payment system, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0066] Figure 2 A flowchart illustrating an embodiment of the payment method provided in the first aspect of this application. Figure 2 As shown, the payment method may include steps 210-240.

[0067] Step 210: Receive the vehicle service bill sent by the payment device.

[0068] The vehicle service bill may include the bill type.

[0069] Step 220: Obtain vehicle monitoring data associated with the billing type of the vehicle service bill.

[0070] Step 230: If the vehicle service bill matches the vehicle monitoring data, generate payment voucher information.

[0071] Step 240: Based on the payment voucher information, pay the amount corresponding to the vehicle service bill.

[0072] The payment method provided in this application embodiment allows the in-vehicle payment system installed in the vehicle to receive vehicle service bills and obtain vehicle monitoring data associated with the bill type of the service bill. Based on this, the in-vehicle payment system can automatically verify the vehicle service bill and vehicle monitoring data, confirming whether they match, eliminating the need for manual verification by the user and simplifying the payment process. Furthermore, if the vehicle service bill and vehicle monitoring data match, i.e., the verification passes, the in-vehicle payment system can generate payment voucher information and pay the corresponding amount on the vehicle service bill based on this voucher information, completing the payment process. Thus, this application enables intelligent verification of vehicle service results in vehicle service scenarios, simplifying the user's payment process, effectively improving bill payment efficiency, and shortening payment time.

[0073] The specific implementation of the above steps will be described in detail below with reference to the embodiments.

[0074] Step 210 involves receiving the vehicle service bill sent by the payment device.

[0075] In the context of vehicle services, the payee can provide vehicle services to the payer. After the service is completed, the payee can set the payment amount for the vehicle service in the payment device, so that the payment device can generate a vehicle service bill for the vehicle service and send the vehicle service bill to the payer's in-vehicle payment system.

[0076] In some embodiments of this application, the payment device may include a payment application for providing payment services. The payment application includes a payment interface, which may include a payment amount input box, in which a user can set the payment amount.

[0077] In some examples, in the context of refueling services, the payment device can be a gas station management device. After the refueling is completed, the refueling attendant needs to enter the payment amount on the payment interface of the gas station management device so that the gas station management device can generate and push the vehicle service bill to the vehicle's onboard payment system.

[0078] In other embodiments, the payment device can automatically calculate the payment amount and generate a vehicle service bill.

[0079] In other examples, in parking service scenarios, the payment device can be a parking lot fee collection device, which can automatically calculate the amount to be collected based on the vehicle's parking duration, generate and push the vehicle service bill to the vehicle's in-vehicle payment system.

[0080] In some embodiments of this application, the payment device can send vehicle service bills to the vehicle monitoring system via backend, Bluetooth, WiFi wireless communication technology, Electronic Toll Collection (ETC) system, or Near Field Communication (NFC) and other communication methods. This application does not specifically limit the communication method between the payment device and the vehicle payment system.

[0081] Step 220 involves obtaining vehicle monitoring data associated with the billing type of the vehicle service bill.

[0082] In some embodiments of this application, step 220 may specifically include: obtaining vehicle monitoring data associated with the billing type from the vehicle monitoring system.

[0083] Both the vehicle monitoring system and the vehicle payment system are installed in the vehicle. The vehicle monitoring system can include sensors to monitor the vehicle in real time and collect vehicle monitoring data. When the vehicle payment system receives a vehicle service bill, it can send a data retrieval request to the vehicle monitoring system. This request can include the bill type of the vehicle service bill, requesting the vehicle monitoring system to return the vehicle monitoring data corresponding to that bill type to the vehicle payment system.

[0084] In some embodiments of this application, when the bill type is a refueling service bill, the vehicle monitoring data includes the vehicle's fuel level; when the bill type is a parking service bill, the vehicle monitoring data includes the vehicle's parking location and parking time; when the bill type is a vehicle maintenance bill, the vehicle monitoring data includes the vehicle's hardware and software update data; and when the bill type is a charging service bill, the vehicle monitoring data includes at least one of the vehicle's state of charge data and charging time.

[0085] In some examples, in refueling service scenarios, the bill type is a refueling service bill. The bill data for this bill may include the amount of fuel dispensed, type of fuel, unit price, and total amount collected. The in-vehicle payment system can determine the actual amount of fuel dispensed by obtaining the vehicle's fuel levels before and after refueling. By comparing this actual amount with the dispensed amount, it can determine whether the vehicle service bill matches the vehicle monitoring data. For example, if the difference between the actual amount dispensed and the dispensed amount is less than a preset fuel level threshold, the vehicle service bill is confirmed to match the vehicle monitoring data.

[0086] In other examples, in parking service scenarios, the bill type is a parking service bill. The bill data for the parking service bill may include the parking duration, unit price, and amount collected. The in-vehicle payment system can determine the actual parking duration by obtaining the vehicle's parking location and parking time. By comparing the actual parking duration with the billed parking duration, it can determine whether the vehicle service bill matches the vehicle monitoring data. For example, if the difference between the actual parking duration and the billed parking duration is less than a preset duration threshold, it is confirmed that the vehicle service bill matches the vehicle monitoring data.

[0087] In this embodiment, since the specific content of the vehicle monitoring data that the in-vehicle payment system needs to verify differs in different vehicle service scenarios, the in-vehicle payment system can obtain different vehicle monitoring data from the in-vehicle monitoring system to verify the vehicle service results in that scenario. Specifically, the bill types for vehicle service bills corresponding to different vehicle service scenarios are different. Therefore, upon receiving a vehicle service bill, the in-vehicle payment system can obtain vehicle monitoring data related to that bill type from the vehicle monitoring system. Based on this vehicle monitoring data, the in-vehicle payment system can verify the vehicle service bill and the vehicle service result. If the vehicle monitoring data matches the vehicle service bill, the vehicle service result verification is confirmed to be successful, providing users with a convenient bill verification service.

[0088] In some embodiments of this application, in order to verify vehicle service bills, the in-vehicle payment system includes an in-vehicle application and a payment software development kit (SDK) integrated with the in-vehicle application. Figure 3A flowchart of another embodiment of the payment method provided in the first aspect of this application is shown below. Figure 3 As shown, after obtaining vehicle monitoring data associated with the bill type of the vehicle service bill in step 220, the method further includes steps 310 and 320.

[0089] Step 310: The payment SDK verifies whether the billing data of the vehicle service bill matches the vehicle monitoring data.

[0090] The payment function can be integrated into the vehicle application of the vehicle payment system as a software development kit (SDK).

[0091] Billing data can include information related to vehicle services, such as the amount received.

[0092] For example, in the refueling service scenario, the bill type is a refueling service bill, and the bill data of the refueling service bill may include the amount of fuel refueled, the type of fuel, the unit price, and the amount received; in the parking service scenario, the bill type is a parking service bill, and the bill data of the parking service bill may include the parking duration, the unit price, and the amount received.

[0093] In some examples, the server of the in-vehicle application in the in-vehicle payment system can receive the vehicle service bill sent by the payment device and retrieve vehicle monitoring data from the in-vehicle monitoring system. The in-vehicle application server then forwards the vehicle service bill and vehicle monitoring data to the payment SDK, enabling the payment SDK to verify the vehicle service bill based on the vehicle monitoring data.

[0094] Step 320: If the billing data matches the vehicle monitoring data, determine that the vehicle service bill matches the vehicle monitoring data.

[0095] In some examples, within a charging service scenario, the bill type is a charging service bill. This bill data may include the charged amount, charging duration, unit price, and total amount collected. Vehicle monitoring data includes the vehicle's state of charge (SBC) data and charging time. The in-vehicle payment system, by acquiring the vehicle's charging time and SBC data at different charging times, can determine the actual charged amount. By comparing this actual charged amount with the billed charged amount, it can determine whether the vehicle service bill matches the vehicle monitoring data. For example, if the difference between the actual charged amount and the billed charged amount is less than a preset energy threshold, the vehicle service bill is confirmed to match the vehicle monitoring data.

[0096] In this embodiment of the application, the payment SDK in the vehicle payment system can verify the vehicle service bill based on vehicle monitoring data to determine whether the amount received in the vehicle service bill matches the vehicle service result, providing users with an intelligent bill verification function. For example, in the refueling service scenario, the vehicle can automatically verify the refueling service bill without the user having to get out of the car to confirm the refueling amount on the fuel nozzle screen, simplifying the user's payment steps, improving payment efficiency, and enhancing the user experience.

[0097] Step 230 involves generating payment voucher information when the vehicle service bill matches the vehicle monitoring data.

[0098] In some embodiments of this application, in order to pay vehicle service bills, Figure 4 A flowchart of another embodiment of the payment method provided in the first aspect of this application, step 230 may include... Figure 4 Steps 410 and 420 are shown.

[0099] Step 410: If the vehicle service bill matches the vehicle monitoring data, generate a payment bill.

[0100] Specifically, the payment bill includes the amount received and vehicle monitoring data. The payment SDK can generate a payment bill if it determines that the vehicle service bill matches the vehicle monitoring data.

[0101] Step 420: Generate payment voucher information based on the payment bill.

[0102] Specifically, after the payment SDK completes the payment based on the payment bill, it can generate payment voucher information.

[0103] If the funds account associated with the in-vehicle payment system has enabled password-free payment, the in-vehicle payment system can automatically pay based on the payment bill; if the funds account associated with the in-vehicle payment system has not enabled password-free payment, the in-vehicle payment system can display a payment interface so that the user can manually pay the payment bill on the payment interface.

[0104] In some embodiments of this application, in order to complete the payment of a vehicle service bill, the in-vehicle payment system includes an in-vehicle application and a payment SDK integrated with the in-vehicle application. Figure 5 A flowchart of another embodiment of the payment method provided in the first aspect of this application, step 420 may include... Figure 5 Steps 510-530 are shown.

[0105] Step 510: Display the application interface of the in-vehicle application on the vehicle's display screen. The application interface includes the payment bill generated by the payment SDK.

[0106] This application interface is the payment interface, where users can manually pay their bills.

[0107] Step 520: Receive payment input for the payment bill.

[0108] In some examples, the application interface may include not only the payment bill but also a corresponding payment control for the payment bill, which can be entered by the user touching the payment control.

[0109] In other examples, payment input can be a swipe input by the user in the application interface according to a preset gesture, or a click input at a preset location in the application interface.

[0110] Step 530: In response to the payment input, generate payment voucher information.

[0111] Specifically, in response to the payment input, the payment SDK can generate payment voucher information.

[0112] In this embodiment, after the in-vehicle payment system verifies the vehicle service bill, it can display the application interface of the in-vehicle application on the vehicle's display screen. This application interface can include the payment bill generated by the payment SDK. In this way, users can pay for the vehicle service bill through the payment operation on the application interface via the vehicle's display screen, realizing a vehicle-based bill payment method without requiring the user to use a mobile phone. This provides users with a flexible bill payment method in vehicle service scenarios, improving the bill payment experience.

[0113] Step 240: Based on the payment voucher information, pay the amount corresponding to the vehicle service bill.

[0114] Specifically, the in-vehicle payment system can interact with the payment device and payment platform through the payment SDK to complete the payment bill deduction process.

[0115] In some embodiments of this application, in order to complete the deduction process for the payment bill, Figure 6 A flowchart of another embodiment of the payment method provided in the first aspect of this application, step 240 may include... Figure 6 Steps 610 and 620 are shown.

[0116] Step 610: Send payment voucher information to the payment receiving device so that the payment receiving device sends the vehicle service bill and payment voucher information to the payment platform;

[0117] Step 620: If the payment platform successfully verifies the vehicle service bill and payment voucher information and the payment is successfully deducted, receive the payment result sent by the payment platform.

[0118] The payment platform deducts the amount corresponding to the vehicle service bill from the funds account associated with the in-vehicle payment system and transfers the amount to the funds account corresponding to the payment device.

[0119] In this embodiment of the application, after receiving the vehicle service bill and payment voucher information, the payment platform can perform risk verification based on the vehicle service bill and payment voucher information, and deduct the payment after successful verification, thus ensuring the security of the payment process.

[0120] A second aspect of this application provides a payment method applicable to a payment receiving device, meaning that the payment method can be executed by the payment receiving device. Specific details regarding the payment receiving device can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0121] Figure 7 A flowchart illustrating an embodiment of the payment method provided in the second aspect of this application. Figure 7 As shown, the payment method may include steps 710-750.

[0122] Step 710: Generate a vehicle service bill based on the obtained vehicle identifier and payment amount.

[0123] In a vehicle service scenario, the payee can provide vehicle services to the payer. After the service is completed, the payee can set the payment amount for this vehicle service in the payment device. The vehicle identifier can be automatically identified by the payment device through recognition technology, or it can be entered by the user; this application does not specify a particular identifier. After obtaining the vehicle identifier and the payment amount, the payment device can generate a vehicle service bill corresponding to this vehicle service.

[0124] In some examples, the vehicle identifier can be a license plate number, an ETC tag, a Radio Frequency Identification (RFID) tag, etc.

[0125] Step 720: Send a vehicle service bill to the vehicle corresponding to the vehicle identifier, which includes an in-vehicle payment system.

[0126] For details regarding the in-vehicle payment system, please refer to the relevant description of the payment method provided in the first aspect of the above embodiments.

[0127] Step 730: If the vehicle service bill is successfully verified by the in-vehicle payment system, receive the payment voucher information sent by the in-vehicle payment system.

[0128] The payment voucher information is generated based on the vehicle service bill.

[0129] The verification process for vehicle service bills by the in-vehicle payment system can be found in steps 310 and 320 above.

[0130] Payment voucher information can be generated by the payment SDK of the vehicle's in-vehicle payment system.

[0131] Step 740: Send the vehicle service bill and payment voucher information to the payment platform.

[0132] Step 750: If the payment platform successfully verifies the vehicle service bill and payment voucher information and the payment is successfully deducted, receive the payment result sent by the payment platform.

[0133] The payment platform deducts the amount corresponding to the vehicle service bill from the funds account associated with the in-vehicle payment system and transfers the amount to the funds account corresponding to the payment device.

[0134] In this embodiment, in a vehicle service scenario, the payment device can push a vehicle service bill to the vehicle, enabling the in-vehicle payment system to automatically verify the bill. This achieves intelligent bill verification, eliminating the need for manual verification of the bill and service results during the payment process and improving payment efficiency. If the in-vehicle payment system successfully verifies the bill, it returns payment voucher information to the payment device. By uploading the bill and voucher information to the payment platform, the payment platform can perform risk verification. If the risk verification passes, the payment amount can be transferred to the corresponding funds account of the payment device, realizing a vehicle-based bill payment method. This eliminates the need for users to use their mobile phones, providing a flexible bill payment method and enhancing the bill payment experience in vehicle service scenarios.

[0135] A third aspect of this application provides a payment method applicable to a payment platform, meaning that the payment method can be executed by the payment platform. For details regarding the payment platform, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0136] Figure 8 A flowchart illustrating an embodiment of the payment method provided in the third aspect of this application. (See flowchart for example.) Figure 8 As shown, the payment method may include steps 810-840.

[0137] Step 810: Receive the vehicle service bill and payment voucher information sent by the payment device.

[0138] Among them, the vehicle service bill is generated by the payment device based on the vehicle identifier and the payment amount, while the payment voucher information is generated by the in-vehicle payment system in the vehicle corresponding to the vehicle identifier after the vehicle service bill is successfully verified.

[0139] After generating a vehicle service bill based on the vehicle identifier and the amount paid, the payment device can send the vehicle service bill to the vehicle corresponding to the vehicle identifier. The vehicle may include an in-vehicle payment system. The in-vehicle payment system can verify the vehicle service bill. If the vehicle service bill is successfully verified, payment voucher information can be generated and sent to the payment device.

[0140] Step 820: Perform risk verification on vehicle service bills and payment voucher information.

[0141] Step 830: If the verification is successful, deduct the amount corresponding to the vehicle service bill from the funds account associated with the vehicle payment system, transfer the amount to the funds account corresponding to the payment device, and generate a payment result.

[0142] After successful verification, the payment platform deducts the amount received from the vehicle service bill from the funds account associated with the in-vehicle payment system, and adds the deducted amount to the funds account authorized and bound to the payment device to complete the payment.

[0143] Step 840: Send the payment result to the receiving device and the vehicle payment system.

[0144] In this embodiment, the payment device generates a vehicle service bill based on the vehicle identifier and the payment amount. The in-vehicle payment system corresponding to the vehicle identifier can verify the vehicle service bill, achieving intelligent vehicle bill verification. This eliminates the need for manual verification of the vehicle service bill and service results during the payment process, improving payment efficiency. If the in-vehicle payment system successfully verifies the vehicle service bill, the payment platform receives the vehicle service bill and payment voucher information sent by the payment device. Based on this information, a risk check can be performed on the payment. If the risk check passes, the payment amount can be transferred to the corresponding funds account of the payment device, realizing a vehicle-based bill payment method. This eliminates the need for users to use their mobile phones, providing a flexible bill payment method in vehicle service scenarios and enhancing the bill payment experience.

[0145] To facilitate understanding of the payment method in the embodiments of this application, the following uses a vehicle service scenario as an example to illustrate the payment process between the in-vehicle service system, the payment device, and the payment platform.

[0146] Figure 9 A flowchart illustrating an example of a payment process provided in an embodiment of this application.

[0147] like Figure 9 As shown, the payment method may include steps 901 to 909.

[0148] Step 901: The payment device generates a vehicle service bill based on the obtained vehicle identifier and payment amount.

[0149] Step 902: The receiving device sends a vehicle service bill to the in-vehicle payment system in the vehicle corresponding to the vehicle identifier. The vehicle service bill includes the bill type.

[0150] Step 903: The in-vehicle payment system obtains vehicle monitoring data associated with the bill type of the vehicle service bill.

[0151] Step 904: The in-vehicle payment system generates payment voucher information when the vehicle service bill is matched with the vehicle monitoring data.

[0152] Step 905: The vehicle payment system sends payment voucher information to the payment receiving device.

[0153] Step 906: The receiving device sends the vehicle service bill and payment voucher information to the payment platform.

[0154] Step 907: The payment platform performs risk verification on the vehicle service bill and payment voucher information.

[0155] Step 908: If the verification is successful, the payment platform deducts the amount corresponding to the vehicle service bill from the funds account associated with the vehicle payment system, transfers the amount to the funds account corresponding to the payment device, and generates a payment result.

[0156] Step 909: The payment platform sends the payment result to the receiving device and the vehicle payment system.

[0157] The specific details of steps 901 to 909 above can be found in the relevant content of the above embodiments, and will not be repeated here.

[0158] In summary, this application provides a payment method, system, device, platform, medium, and product. An in-vehicle payment system installed in a vehicle can receive vehicle service bills and obtain vehicle monitoring data associated with the bill type of the service bill. Based on this, the in-vehicle payment system can automatically verify the vehicle service bill and vehicle monitoring data, confirming whether they match, eliminating the need for manual verification by the user and simplifying the payment process. Furthermore, if the vehicle service bill and vehicle monitoring data match, i.e., the verification passes, the in-vehicle payment system can generate payment voucher information and pay the corresponding amount on the vehicle service bill based on this voucher information, completing the payment process. Thus, this application can intelligently verify vehicle service results in vehicle service scenarios, simplifying the user's payment process, effectively improving bill payment efficiency, and shortening payment time.

[0159] Based on the same inventive concept, the fourth aspect of this application provides an in-vehicle payment system. Figure 10 This is a schematic diagram of an embodiment of the in-vehicle payment system provided in the fourth aspect of this application.

[0160] like Figure 10 As shown, the in-vehicle payment system 1000 can provide, for example... Figure 1 The in-vehicle payment system 11 shown, and the in-vehicle payment system 1000 specifically may include:

[0161] The receiving module 1010 is used to receive the vehicle service bill sent by the payment device. The vehicle service bill includes the bill type.

[0162] The acquisition module 1020 is used to acquire vehicle monitoring data associated with the bill type of the vehicle service bill;

[0163] The generation module 1030 is used to generate payment voucher information when the vehicle service bill is matched with the vehicle monitoring data;

[0164] The payment module 1040 is used to pay the amount corresponding to the vehicle service bill based on the payment voucher information.

[0165] The in-vehicle payment system provided in this application can receive vehicle service bills and obtain vehicle monitoring data associated with the bill type of the vehicle service bill. Based on this, the in-vehicle payment system can automatically verify the vehicle service bill and vehicle monitoring data, confirming whether they match, without requiring manual verification by the user, thus simplifying the user's payment process. Furthermore, if the vehicle service bill and vehicle monitoring data match, i.e., the verification passes, the in-vehicle payment system can generate payment voucher information, and pay the corresponding amount of the vehicle service bill based on this payment voucher information, completing the payment process. In this way, this application can intelligently verify vehicle service results in vehicle service scenarios, simplifying the user's payment process, effectively improving bill payment efficiency, and shortening payment time.

[0166] The in-vehicle payment system 1000 provided in the embodiments of this application will be described in detail below.

[0167] In some embodiments of this application, the in-vehicle payment system includes an in-vehicle application and a payment software development kit (SDK) integrated with the in-vehicle application. The payment SDK is used to: after obtaining vehicle monitoring data associated with the bill type of the vehicle service bill, verify whether the bill data of the vehicle service bill matches the vehicle monitoring data; and if the bill data matches the vehicle monitoring data, determine that the vehicle service bill matches the vehicle monitoring data.

[0168] In some embodiments of this application, the acquisition module 1020 is specifically used to: acquire vehicle monitoring data associated with the billing type from the vehicle monitoring system.

[0169] In some embodiments of this application, when the bill type is a refueling service bill, the vehicle monitoring data includes the vehicle's fuel level; when the bill type is a parking service bill, the vehicle monitoring data includes the vehicle's parking location and parking time; when the bill type is a vehicle maintenance bill, the vehicle monitoring data includes the vehicle's hardware and software update data; and when the bill type is a charging service bill, the vehicle monitoring data includes at least one of the vehicle's state of charge data and charging time.

[0170] In some embodiments of this application, the generation module 1030 is specifically used to: generate a payment bill when the vehicle service bill matches the vehicle monitoring data, the payment bill including the amount received and the vehicle monitoring data; and generate payment voucher information based on the payment bill.

[0171] In some embodiments of this application, the in-vehicle payment system includes an in-vehicle application and a payment SDK integrated with the in-vehicle application. The generation module 1030 includes: a display unit for displaying the application interface of the in-vehicle application on the vehicle's display screen, the application interface including a payment bill generated by the payment SDK; a receiving unit for receiving payment input for the payment bill; and a generation unit for generating payment voucher information in response to the payment input.

[0172] In some embodiments of this application, the payment module 1040 includes: a sending unit, configured to send payment voucher information to the receiving device, so that the receiving device sends a vehicle service bill and payment voucher information to the payment platform; and a receiving unit, configured to receive a payment result sent by the payment platform when the payment platform successfully verifies the vehicle service bill and payment voucher information and successfully deducts the payment, wherein the payment platform deducts the amount received corresponding to the vehicle service bill from the funds account associated with the vehicle payment system and transfers the amount received to the funds account corresponding to the receiving device.

[0173] Based on the same inventive concept, the fifth aspect of this application provides a payment collection device. Figure 11 A schematic diagram of the structure of an embodiment of the payment collection device provided in the fourth aspect of this application.

[0174] like Figure 11 As shown, the payment collection device 1100 can be used as follows: Figure 1 The payment collection device 12 shown, and the payment collection device 1100 specifically may include:

[0175] The generation module 1110 is used to generate a vehicle service bill based on the obtained vehicle identifier and payment amount.

[0176] The sending module 1120 is used to send a vehicle service bill to the vehicle corresponding to the vehicle identifier, and the vehicle includes an in-vehicle payment system.

[0177] The receiving module 1130 is used to receive payment voucher information sent by the vehicle payment system when the vehicle service bill is successfully verified by the vehicle payment system. The payment voucher information is generated based on the vehicle service bill.

[0178] The sending module 1120 is used to send vehicle service bill and payment voucher information to the payment platform;

[0179] The receiving module 1130 is also used to receive the payment result sent by the payment platform when the payment platform successfully verifies the vehicle service bill and payment voucher information and successfully deducts the payment. In this case, the payment platform deducts the amount of payment corresponding to the vehicle service bill from the fund account associated with the vehicle payment system and transfers the amount of payment to the fund account corresponding to the payment device.

[0180] The payment device provided in this application embodiment can push vehicle service bills to the vehicle in a vehicle service scenario, enabling the in-vehicle payment system to automatically verify the bills. This achieves intelligent vehicle bill verification, eliminating the need for manual verification of the bills and service results during the payment process and improving payment efficiency. If the in-vehicle payment system successfully verifies the vehicle service bill, it returns payment voucher information to the payment device. By uploading the vehicle service bill and payment voucher information to the payment platform, the payment platform can perform risk verification for the payment. If the risk verification passes, the payment amount can be transferred to the corresponding funds account of the payment device, realizing a vehicle-based bill payment method. This eliminates the need for users to use their mobile phones, providing a flexible bill payment method in vehicle service scenarios and improving the bill payment experience.

[0181] Based on the same inventive concept, the sixth aspect of this application provides a payment platform. Figure 12 A schematic diagram of the structure of an embodiment of the payment platform provided in the sixth aspect of this application.

[0182] like Figure 12 As shown, payment platform 1200 can provide services such as... Figure 1 The payment platform 13 and payment platform 1200 shown may specifically include:

[0183] The receiving module 1210 is used to receive vehicle service bill and payment voucher information sent by the receiving device. The vehicle service bill is generated by the receiving device based on the vehicle identifier and the amount received, and the payment voucher information is generated by the in-vehicle payment system in the vehicle corresponding to the vehicle identifier when the vehicle service bill is successfully verified.

[0184] The risk verification module 1220 is used to perform risk verification on vehicle service bills and payment voucher information.

[0185] The payment processing module 1230 is used to deduct the amount corresponding to the vehicle service bill from the fund account associated with the vehicle payment system when the verification is successful, and transfer the amount to the fund account corresponding to the payment device to generate a payment result.

[0186] The sending module 1240 is used to send payment results to the receiving device and the vehicle payment system.

[0187] In this embodiment, the payment device generates a vehicle service bill based on the vehicle identifier and the payment amount. The in-vehicle payment system corresponding to the vehicle identifier can verify the vehicle service bill, achieving intelligent vehicle bill verification. This eliminates the need for manual verification of the vehicle service bill and service results during the payment process, improving payment efficiency. If the in-vehicle payment system successfully verifies the vehicle service bill, the payment platform receives the vehicle service bill and payment voucher information sent by the payment device. Based on this information, a risk check can be performed on the payment. If the risk check passes, the payment amount can be transferred to the corresponding funds account of the payment device, realizing a vehicle-based bill payment method. This eliminates the need for users to use their mobile phones, providing a flexible bill payment method in vehicle service scenarios and enhancing the bill payment experience.

[0188] The seventh aspect of this application also provides a payment device. Figure 13 This is a schematic diagram of the structure of an embodiment of the payment device provided in the seventh aspect of this application. Figure 13 As shown, the payment device 1300 includes a memory 1301, a processor 1302, and a computer program stored on the memory 1301 and executable on the processor 1302.

[0189] In one example, the processor 1302 described above may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits that may be configured to implement the embodiments of this application.

[0190] Memory 1301 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, 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 in the embodiments according to the first, second, or third aspects of this application.

[0191] The processor 1302 runs a computer program corresponding to the executable program code stored in the memory 1301 to implement the payment method in the first, second, or third aspect embodiments described above.

[0192] In some examples, the payment device 1300 may also include a communication interface 1303 and a bus 1304. For example, Figure 13 As shown, the memory 1301, processor 1302, and communication interface 1303 are connected through bus 1304 and complete communication with each other.

[0193] The communication interface 1303 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application. Input devices and / or output devices can also be connected through the communication interface 1303.

[0194] Bus 1304 includes hardware, software, or both, that couples components of user terminal 1300 together. For example, and not limitingly, bus 1304 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 Infinite Bandwidth 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 combinations of two or more of these. Where appropriate, bus 1404 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0195] The eighth aspect of this application provides a computer-readable storage medium storing a program or instructions. When executed by a processor, the program or instructions can implement the payment methods described in the first, second, or third aspects above, and achieve the same technical effects. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.

[0196] The ninth aspect of this application provides a computer program product stored in a non-volatile storage medium. When executed by at least one processor, the computer program product implements the steps of the payment method as shown in the first, second, or third aspect. The specific content of the payment method can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0197] This application may also provide a payment system, which may include the in-vehicle payment system, payment receiving device, and payment platform described in the above embodiments. For details regarding the in-vehicle payment system, payment receiving device, and payment platform, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0198] It should be clarified that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For the device embodiments, user terminal embodiments, equipment embodiments, system embodiments, and computer-readable storage medium embodiments, the relevant parts can be referred to the description section of the method embodiments. This 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 of steps, after understanding the spirit of this application. Furthermore, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

[0199] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. 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 is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0200] Those skilled in the art will understand that the above embodiments are exemplary and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, specification, and 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 means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to identify names and not to indicate any particular order. Any reference numerals in the claims should not be construed as limiting the scope of protection. The functionality 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, characterized in that, The method is applied to a vehicle-mounted payment system, and the method comprises the following steps: receiving a vehicle service bill sent by a payment device, wherein the vehicle service bill comprises a bill type; obtaining vehicle monitoring data associated with the bill type of the vehicle service bill, wherein the bill type is a refueling service bill, and the vehicle monitoring data comprises fuel storage data of the vehicle; the bill type is a parking service bill, and the vehicle monitoring data comprises a parking position and a parking time of the vehicle; the bill type is a vehicle maintenance bill, and the vehicle monitoring data comprises software and hardware update data of the vehicle; the bill type is a charging service bill, and the vehicle monitoring data comprises at least one of state of charge data and charging time of the vehicle; the vehicle-mounted payment system comprises a vehicle-mounted application program and a payment SDK integrated with the vehicle-mounted application program; generating a payment bill in the case that the vehicle service bill matches the vehicle monitoring data, wherein the payment bill comprises a payment amount and the vehicle monitoring data; displaying an application interface of the vehicle-mounted application program on a display screen of the vehicle, wherein the application interface comprises the payment bill generated by the payment SDK; receiving a payment input for the payment bill; and generating payment credential information in response to the payment input; paying the payment amount corresponding to the vehicle service bill based on the payment credential information.

2. The method of claim 1, wherein, The vehicle-mounted payment system comprises a vehicle-mounted application program and a payment software development kit (SDK) integrated with the vehicle-mounted application program, and after the vehicle monitoring data associated with the bill type of the vehicle service bill is obtained, the method further comprises the following steps: verifying, by the payment SDK, whether the bill data of the vehicle service bill matches the vehicle monitoring data; determining that the vehicle service bill matches the vehicle monitoring data in the case that the bill data matches the vehicle monitoring data.

3. The method of claim 1, wherein, The step of obtaining the vehicle monitoring data associated with the bill type of the vehicle service bill comprises the following step: obtaining the vehicle monitoring data associated with the bill type from a vehicle-mounted monitoring system.

4. The method of claim 1, wherein, The step of paying the payment amount corresponding to the vehicle service bill based on the payment credential information comprises the following steps: sending the payment credential information to the payment device, so that the payment device sends the vehicle service bill and the payment credential information to a payment platform; receiving a payment result sent by the payment platform in the case that the payment platform successfully verifies the vehicle service bill and the payment credential information and successfully deducts the payment amount, wherein the payment platform deducts the payment amount corresponding to the vehicle service bill from a fund account associated with the vehicle-mounted payment system and transfers the payment amount to a fund account corresponding to the payment device.

5. A payment method, characterized by, The method is applied to a payment device, and the method comprises the following steps: generating a vehicle service bill based on obtained vehicle identification and a payment amount; sending the vehicle service bill to a vehicle corresponding to the vehicle identification, wherein the vehicle comprises a vehicle-mounted payment system. In a case that the vehicle payment system successfully checks the vehicle service bill, payment voucher information sent by the vehicle payment system is received, the payment voucher information is generated based on a payment bill, the payment bill is generated in a case that the vehicle service bill matches vehicle monitoring data, the payment bill includes the collection amount and vehicle monitoring data, and a bill type of the vehicle service bill is associated with the vehicle monitoring data, wherein the bill type is a refueling service bill, and the vehicle monitoring data includes fuel storage data of the vehicle; the bill type is a parking service bill, and the vehicle monitoring data includes a parking position and a parking time of the vehicle; the bill type is a vehicle maintenance bill, and the vehicle monitoring data includes software and hardware update data of the vehicle; the bill type is a charging service bill, and the vehicle monitoring data includes at least one of state of charge data and charging time of the vehicle; The payment platform sends the vehicle service bill and the payment voucher information to the payment platform; In a case that the payment platform successfully checks the vehicle service bill and the payment voucher information and successfully deducts the amount, a payment result sent by the payment platform is received, wherein the payment platform deducts the collection amount corresponding to the vehicle service bill from a fund account associated with the vehicle payment system and transfers the collection amount to a fund account corresponding to the collection device.

6. A payment method, characterized by The application is applied to a payment platform, and the method comprises the following steps: A vehicle service bill and payment voucher information sent by a collection device are received, the vehicle service bill is generated based on a vehicle identifier and a collection amount by the collection device, and the payment voucher information is generated by a vehicle payment system in a vehicle corresponding to the vehicle identifier in a case that the vehicle payment system successfully checks the vehicle service bill; Risk checking is performed on the vehicle service bill and the payment voucher information; In a case that the checking is successful, the collection amount corresponding to the vehicle service bill is deducted from a fund account associated with the vehicle payment system, the collection amount is transferred to a fund account corresponding to the collection device, and a payment result is generated; The payment result is sent to the collection device and the vehicle payment system; the payment voucher information is generated based on a payment bill, the payment bill is generated in a case that the vehicle service bill matches vehicle monitoring data, the payment bill includes the collection amount and vehicle monitoring data, and a bill type of the vehicle service bill is associated with the vehicle monitoring data, wherein the bill type is a refueling service bill, and the vehicle monitoring data includes fuel storage data of the vehicle; the bill type is a parking service bill, and the vehicle monitoring data includes a parking position and a parking time of the vehicle; the bill type is a vehicle maintenance bill, and the vehicle monitoring data includes software and hardware update data of the vehicle; the bill type is a charging service bill, and the vehicle monitoring data includes at least one of state of charge data and charging time of the vehicle.

7. An in-vehicle payment system characterized by comprising: Comprise: A receiving module is used for receiving a vehicle service bill sent by a collection device, and the vehicle service bill includes a bill type. The acquisition module is configured to acquire vehicle monitoring data associated with a bill type of the vehicle service bill, wherein the bill type is a refueling service bill, and the vehicle monitoring data includes fuel storage data of the vehicle; the bill type is a parking service bill, and the vehicle monitoring data includes a parking position and a parking time of the vehicle; the bill type is a vehicle maintenance bill, and the vehicle monitoring data includes software and hardware update data of the vehicle; the bill type is a charging service bill, and the vehicle monitoring data includes at least one of state of charge data and a charging time of the vehicle; and the in-vehicle payment system includes an in-vehicle application and a payment SDK integrated with the in-vehicle application. The generation module is configured to generate a payment bill including a payment amount and the vehicle monitoring data, in a case where the vehicle service bill matches the vehicle monitoring data; display, on a display screen of the vehicle, an application interface of the in-vehicle application, the application interface including the payment bill generated by the payment SDK; receive a payment input for the payment bill; and generate payment credential information in response to the payment input. The payment module is configured to pay the payment amount corresponding to the vehicle service bill based on the payment credential information.

8. A cash collection apparatus characterized by comprising: The generation module is configured to generate a vehicle service bill based on the acquired vehicle identifier and the payment amount. The sending module is configured to send the vehicle service bill to a vehicle corresponding to the vehicle identifier, the vehicle including an in-vehicle payment system. The receiving module is configured to receive payment credential information sent by the in-vehicle payment system in a case where the in-vehicle payment system successfully verifies the vehicle service bill, the payment credential information being generated based on a payment bill, the payment bill being generated in a case where the vehicle service bill matches vehicle monitoring data, the payment bill including the payment amount and the vehicle monitoring data, and a bill type of the vehicle service bill being associated with the vehicle monitoring data, wherein the bill type is a refueling service bill, and the vehicle monitoring data includes fuel storage data of the vehicle; the bill type is a parking service bill, and the vehicle monitoring data includes a parking position and a parking time of the vehicle; the bill type is a vehicle maintenance bill, and the vehicle monitoring data includes software and hardware update data of the vehicle; and the bill type is a charging service bill, and the vehicle monitoring data includes at least one of state of charge data and a charging time of the vehicle. The sending module is configured to send the vehicle service bill and the payment credential information to a payment platform. The receiving module is further configured to receive a payment result sent by the payment platform in a case where the payment platform successfully verifies the vehicle service bill and the payment credential information and successfully deducts the payment amount, wherein the payment platform deducts the payment amount corresponding to the vehicle service bill from a fund account associated with the in-vehicle payment system and transfers the payment amount to a fund account corresponding to the payment device. The generation module is configured to generate a vehicle service bill based on the acquired vehicle identifier and the payment amount.

9. A payment platform, characterized by ​ The receiving module is configured to receive a vehicle service bill and payment voucher information sent by a payment device, wherein the vehicle service bill is generated by the payment device based on a vehicle identifier and a payment amount, and the payment voucher information is generated by a vehicle-mounted payment system in a vehicle corresponding to the vehicle identifier, in a case where the vehicle-mounted payment system successfully verifies the vehicle service bill; The risk verification module is configured to perform risk verification on the vehicle service bill and the payment voucher information; The payment processing module is configured to, in a case where the verification is successful, deduct the payment amount corresponding to the vehicle service bill from a fund account associated with the vehicle-mounted payment system, transfer the payment amount to a fund account corresponding to the payment device, and generate a payment result; The sending module is configured to send the payment result to the payment device and the vehicle-mounted payment system; the payment voucher information is generated based on a payment bill, wherein the payment bill is generated in a case where the vehicle service bill matches vehicle monitoring data, the payment bill includes the payment amount and the vehicle monitoring data, and a bill type of the vehicle service bill is associated with the vehicle monitoring data, wherein the bill type is a refueling service bill, and the vehicle monitoring data includes fuel storage data of the vehicle; the bill type is a parking service bill, and the vehicle monitoring data includes a parking position and a parking time of the vehicle; the bill type is a vehicle maintenance bill, and the vehicle monitoring data includes software and hardware update data of the vehicle; and the bill type is a charging service bill, and the vehicle monitoring data includes at least one of state of charge data and charging time of the vehicle.

10. A payment device, characterized by The device includes a processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the payment method of any one of claims 1 to 6.

11. A computer readable storage medium, characterized in that, The computer readable storage medium stores programs or instructions, and the programs or instructions are executed by the processor to implement the payment method of any one of claims 1 to 6.

12. A computer program product, characterised in that, The computer program product is stored in a non-volatile storage medium, and the computer program product is executed by at least one processor to implement the payment method of any one of claims 1 to 6.

Images