CN112288417A - Payment method for vehicle, computer device, and storage medium - Google Patents

Payment method for vehicle, computer device, and storage medium Download PDF

Info

Publication number
CN112288417A
CN112288417A CN202011167968.5A CN202011167968A CN112288417A CN 112288417 A CN112288417 A CN 112288417A CN 202011167968 A CN202011167968 A CN 202011167968A CN 112288417 A CN112288417 A CN 112288417A
Authority
CN
China
Prior art keywords
payment
vehicle
account
platform
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011167968.5A
Other languages
Chinese (zh)
Inventor
朱朝卓
欧嘉权
谭绍龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Xiaopeng Motors Technology Co Ltd
Original Assignee
Guangzhou Xiaopeng Motors Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangzhou Xiaopeng Motors Technology Co Ltd filed Critical Guangzhou Xiaopeng Motors Technology Co Ltd
Priority to CN202011167968.5A priority Critical patent/CN112288417A/en
Publication of CN112288417A publication Critical patent/CN112288417A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G06Q20/40145—Biometric identity checks

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application discloses a payment method of a vehicle, a computer device and a storage medium. The payment method comprises the following steps: generating a payment event in response to the first user input; determining a current payment platform according to a second user input of the payment mode list generated aiming at the payment event to generate a payment request and sending the payment request to the current payment platform; and determining account information corresponding to the current payment platform according to the binding relationship between the vehicle account and the user account of the payment platform so that the current payment platform completes a payment request according to the account information. According to the payment method, the computer device and the storage medium of the vehicle, vehicle-end payment in the driving process can be achieved, vehicle-end payment experience of a user is improved, the user can focus on driving, and driving safety can be guaranteed.

Description

Payment method for vehicle, computer device, and storage medium
Technical Field
The present application relates to the field of vehicle technologies, and in particular, to a payment method for a vehicle, a computer device, and a storage medium.
Background
With the development of new energy automobile technology and increasingly wide application of mobile communication in the technical field of automobiles, new application scenes and application requirements gradually appear to meet various requirements of people on communication, entertainment, navigation and the like in the driving process. With the increasing travel demands of users, service scenes paid in a vehicle are more and more, however, the current payment service is mainly realized through mobile terminals such as mobile phones, the experience degree of the vehicle-end payment scene is poor due to frequent dependence on the mobile phones, and potential safety hazards are often brought by using mobile phone payment in the vehicle driving process.
Disclosure of Invention
In view of this, embodiments of the present application provide a payment method for a vehicle, a computer device, and a storage medium.
The application provides a payment method of a vehicle, which comprises the following steps:
generating a payment event in response to the first user input;
determining a current payment platform according to a second user input of the payment mode list aiming at the payment event to generate a payment request and sending the payment request to the current payment platform;
and determining account information corresponding to the current payment platform according to the binding relationship between the vehicle account and the user account of the payment platform, so that the current payment platform completes the payment request according to the account information.
In some embodiments, the determining account information corresponding to the current payment platform according to a binding relationship between a vehicle account and a user account of a payment platform so that the current payment platform completes the payment request according to the account information includes:
judging whether account information of the current payment platform having a binding relationship with the vehicle account exists or not;
if the current payment platform exists, determining account information of the current payment platform according to the binding relationship;
and if the current payment platform does not exist, triggering and binding the vehicle account and the account information of the current payment platform.
In some embodiments, the determining account information of the current payment platform according to the binding relationship includes:
initiating an acquisition request for acquiring account information corresponding to the current payment platform;
receiving an acquisition request result fed back according to the binding relationship;
and taking the acquisition request result as account information corresponding to the current payment platform.
In some embodiments, the determining a current payment platform to generate a payment request and sending the payment request to the current payment platform according to a second user input to the list of payment methods for the payment event comprises:
initiating a validation request for the vehicle account number in response to the payment event;
and receiving a payment mode list aiming at the payment event generated according to the verification request.
In some embodiments, the determining account information corresponding to the current payment platform according to a binding relationship between a vehicle account and a user account of a payment platform so that the current payment platform completes the payment request according to the account information includes:
receiving a payment confirmation request fed back by the current payment platform according to the payment request and the account information;
and receiving payment confirmation information generated by the user aiming at the third user input of the payment confirmation request.
In some embodiments, the generating a payment event in response to the first user input comprises:
generating the payment event in response to a voice input by a user.
In some embodiments, the determining account information corresponding to the current payment platform according to a binding relationship between a vehicle account and a user account of a payment platform so that the current payment platform completes the payment request according to the account information includes:
and sending account information corresponding to the current payment platform and determined according to the binding relationship between the vehicle account and a user account of a payment platform and voiceprint information acquired according to the voice input so that the current payment platform can complete the payment request according to the account information and the voiceprint information.
The application provides a payment method of a vehicle, which comprises the following steps:
receiving a payment request sent by the vehicle, wherein the payment request is generated according to the input of a payment mode list generated by a user aiming at a payment event;
and receiving account information which is sent by the vehicle and corresponds to the current payment platform so as to complete the payment request, wherein the account information is determined according to the binding relationship between the vehicle account and the user account of the payment platform.
The application provides a vehicle system, the vehicle system comprises a vehicle and a vehicle service end, the vehicle and/or the vehicle service end comprises a memory and a processor, the memory stores a computer program, and the processor realizes the payment method of the vehicle of any one of the above embodiments when executing the computer program.
One or more non-transitory computer-readable storage media storing a computer program that, when executed by one or more processors, implements a payment method for a vehicle of any of the above embodiments.
In the vehicle payment method, the computer device and the storage medium in the embodiment of the application, when a payment event is generated, the current payment platform is determined according to the input of a user and a payment request is sent to the current payment platform, and then the account information of the current payment platform is determined according to the binding relationship between the vehicle account and the user account of the payment platform, so that the payment request is completed by using the account information, the vehicle-end payment in the driving process can be realized, the vehicle-end payment experience of the user is improved, the user can concentrate on the driving, and the driving safety can be ensured.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a schematic flow chart diagram of a payment method for a vehicle according to some embodiments of the present disclosure.
FIG. 2 is a schematic illustration of a vehicle according to certain embodiments of the present application.
FIG. 3 is a block schematic diagram of a payment device of a vehicle according to certain embodiments of the present application.
FIG. 4 is an interactive flow diagram of a payment method for a vehicle according to some embodiments of the present disclosure.
FIG. 5 is a flow chart illustrating a payment method for a vehicle according to some embodiments of the present disclosure.
FIG. 6 is a flow chart illustrating a payment method for a vehicle according to some embodiments of the present disclosure.
FIG. 7 is a flow chart illustrating a payment method for a vehicle according to some embodiments of the present disclosure.
FIG. 8 is a flow chart illustrating a payment method for a vehicle according to some embodiments of the present disclosure.
FIG. 9 is a schematic flow chart diagram of a payment method for a vehicle according to some embodiments of the present application.
FIG. 10 is a schematic flow chart diagram of a payment method for a vehicle according to some embodiments of the present application.
FIG. 11 is a flow chart illustrating a payment method for a vehicle according to some embodiments of the present disclosure.
FIG. 12 is a block diagram of a payment platform in accordance with certain embodiments of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.
Referring to fig. 1, the present application provides a payment method for a vehicle, including:
s11: generating a payment event in response to the first user input;
s12: determining a current payment platform according to a second user input of the payment mode list aiming at the payment event to generate a payment request and sending the payment request to the current payment platform;
s13: and determining account information corresponding to the current payment platform according to the binding relationship between the vehicle account and the user account of the payment platform so that the current payment platform completes a payment request according to the account information.
Referring to fig. 2, the present embodiment provides a vehicle 100. The vehicle 100 includes a processor 102 and a first communication element 104. The processor 102 is configured to generate a payment event according to the first user input, and determine account information corresponding to the current payment platform according to a binding relationship between the vehicle account and a user account of the payment platform, so that the current payment platform completes a payment request according to the account information. The first communication element 104 is configured to determine a current payment platform from the second user input of the list of payment methods for the payment event to generate a payment request and send the payment request to the current payment platform. The processor 102 may be a processor 102 independently configured to implement a payment method of a vehicle, or may be a processor 102 of a vehicle driving system, which is not limited herein.
Referring to fig. 3, the present application also provides a payment device 110 for a vehicle, and a payment method for a vehicle according to the present application may be implemented by the payment device 110 for a vehicle. The payment device 110 of the vehicle includes a generation module 112, a first communication module 114, and a first payment module 116. S11 may be implemented by the generation module 112, S12 may be implemented by the first communication module 114, and S13 may be implemented by the first payment module 116. Alternatively, the generating module 112 is configured to generate the payment event according to the first user input. The first communication module 114 is configured to determine a current payment platform according to a second user input of the payment method list for the payment event to generate a payment request and send the payment request to the current payment platform. The first payment module 116 is configured to determine account information corresponding to a current payment platform according to a binding relationship between a vehicle account and a user account of the payment platform, so that the current payment platform completes a payment request according to the account information.
The embodiment of the present application further provides a vehicle system 10, where the vehicle system 10 includes a vehicle 100 and a vehicle service end 120, and the vehicle 100 and/or the vehicle service end 120 includes a memory and a processor, where the memory stores a computer program, and the processor implements the vehicle payment method of any of the above embodiments when executing the computer program.
In particular, as mobile communication is increasingly used in the field of automotive technology, a user may register and log in a vehicle account at a central control platform of the vehicle 100 during a vehicle using process. In the vehicle payment method in the embodiment of the application, one vehicle account can be bound with user accounts of one or more payment platforms. The vehicle account may be an account registered in a vehicle user management system during a vehicle using process. The payment platform includes but is not limited to various entity banks, internet banks, application programs with payment function, and the like. It is understood that the same payment platform may also bind one or more user accounts.
After the user logs in the vehicle account in the vehicle 100, a first user input may be performed through a service side client installed on a vehicle central control platform during a driving process. The vehicle 100 generates a payment event according to the first user input, generates a payment mode list according to the payment event, requests the user to perform second user input, and determines to select a current payment platform for payment settlement according to the second user input.
After the current payment platform is determined, the vehicle 100 generates a payment request, sends the payment request to the current payment platform, and determines account information of the current payment platform corresponding to the vehicle account according to the binding relationship between the vehicle account and the user account of the payment platform, so that the current payment platform completes the payment request according to the account information.
In some embodiments, the vehicle account number three binds one or more user accounts of the first payment platform, the second payment platform and the third payment platform.
And the user logs in a third vehicle account number on the vehicle central control platform, and performs first user input through a shopping platform application program client installed on the vehicle central control platform in the driving process. The first user input may be vehicle account number three selecting a good and creating an order at the shopping platform application client. The vehicle 100 communicates with the vehicle service end 200, so that the vehicle service end 120 generates a corresponding payment event according to the behavior of opening three selected commodities by the vehicle account, generates a payment mode list according to the payment event, and sends the payment mode list to the vehicle 100. The vehicle 100 requests a second user input for the vehicle account number three times according to the payment method list. The second user input may be the vehicle account number three-choice first payment platform settling the payment for the selected goods. The vehicle 100 determines to select the first payment platform for payment settlement according to the behavior of selecting the first payment platform from the third account number of the vehicle.
After the first payment platform is determined to be selected, the vehicle 100 generates a corresponding payment request, sends the payment request to the first payment platform, and determines account information a of the first payment platform corresponding to the third vehicle account according to the binding relationship between the third vehicle account and one or more user accounts of the first payment platform, the second payment platform and the third payment platform, so that the first payment platform completes the payment request according to the account information a.
Therefore, in the driving process, payment can be realized through the vehicle 100, and the vehicle-end payment experience of the user is improved. Meanwhile, compared with a scheme of using a mobile phone for payment in the driving process, the payment method is carried out at the vehicle end, so that the user can concentrate on driving, and the driving safety can be ensured.
Further, referring to fig. 4, when the user performs the first user input at the service side client, the service side server creates a pre-order-placing request and sends the pre-order-placing request to the vehicle server 120. The vehicle server 120 receives the order pre-ordering request, generates an order pre-ordering result, and returns the order pre-ordering result to the service side server. The service side server returns the order pre-ordering result to the service side client, and the service side client generates and transmits a TOKEN parameter and calls a Software Development Kit (SDK) corresponding to the vehicle 100 according to the order pre-ordering result, so that the vehicle 100 generates a payment event.
In the vehicle payment method, the vehicle 100, the vehicle payment device 110 and the vehicle system 10 according to the embodiment of the application, when a payment event is generated, the current payment platform is determined according to the user input and a payment request is sent to the current payment platform, and then the account information of the current payment platform is determined according to the binding relationship between the vehicle account and the user account of the payment platform, so that the payment request is completed by using the account information, vehicle-end payment in a driving process can be realized, vehicle-end payment experience of a user is improved, the user can be helped to concentrate on driving, and driving safety can be ensured.
Referring to fig. 5, in some embodiments, S13 includes:
s131: judging whether account information of a current payment platform having a binding relationship with a vehicle account exists or not;
s132: if the current account number exists, determining account number information of the current payment platform according to the binding relationship;
s133: and if the current account information does not exist, triggering the account information of the bound vehicle and the current payment platform.
In some embodiments, S131-133 may be implemented by first payment module 116. Or, the first payment module 116 is configured to determine whether account information of the current payment platform having a binding relationship with the vehicle account exists, determine the account information of the current payment platform according to the binding relationship when the account information of the current payment platform having the binding relationship with the vehicle account exists, and trigger the account information of the current payment platform and the vehicle account when the account information of the current payment platform having the binding relationship with the vehicle account does not exist.
In some embodiments, the processor 102 is configured to determine whether account information of a current payment platform having a binding relationship with a vehicle account exists, determine account information of the current payment platform according to the binding relationship when the account information of the current payment platform having the binding relationship with the vehicle account exists, and trigger to bind the vehicle account and the account information of the current payment platform when the account information of the current payment platform having the binding relationship with the vehicle account does not exist.
Specifically, after the payment event is generated, the vehicle 100 determines whether account information of the current payment platform having a binding relationship with the vehicle account exists, and performs corresponding processing according to a determination result.
In some embodiments, the vehicle account is bound with account information of a current payment platform, that is, the vehicle account is bound with account information of a first payment platform, and the account information of the first payment platform is determined according to the binding relationship. It is to be appreciated that the first payment platform may bind one or more account number information. In the case where one account information a1 is bound to the first payment platform, the payment request may be completed by default using the account information a 1. In the case where the first payment platform binds a plurality of account information a1, a2, a3, the user may be requested to make an input to determine that the account information completes the payment request.
In other embodiments, if the vehicle account is not bound to the account information of the current payment platform, that is, the vehicle account is bound to the account information of any one of the three unbound payment platforms, or if other conditions that the account information of the current payment platform cannot be detected occur, the account information of the bound vehicle account and the current payment platform is triggered, and the user is requested to bind the vehicle account and the account information of the current payment platform.
Therefore, according to whether the binding relationship exists or not, the user is prompted to bind the vehicle account and the user account of the payment platform, the payment experience under a vehicle end payment scene can be improved after the binding is completed, the user can be helped to concentrate on driving, and the driving safety can be guaranteed.
Referring to fig. 6, in some embodiments, S132 includes:
s1321: initiating an acquisition request for acquiring account information corresponding to the current payment platform;
s1322: receiving an acquisition request result fed back according to the binding relationship;
s1323: and taking the acquired request result as account information corresponding to the current payment platform.
In some embodiments, S1321-S1323 may be implemented by first payment module 116. Or, the first payment module 116 is configured to initiate an acquisition request for acquiring account information corresponding to the current payment platform, receive an acquisition request result fed back according to the binding relationship, and use the acquisition request result as the account information corresponding to the current payment platform.
In some embodiments, the processor 102 is configured to initiate an acquisition request for acquiring account information corresponding to the current payment platform, receive an acquisition request result fed back according to the binding relationship, and use the acquisition request result as the account information corresponding to the current payment platform.
Specifically, after the payment event is generated, the vehicle service end 120 queries that the vehicle account is bound with account information of the current payment platform, and then the vehicle 100 initiates a request to the vehicle service end 120 to obtain one or more account information corresponding to the current payment platform.
In some embodiments, after the payment event is generated, the vehicle server 120 queries that the vehicle account number is bound with the account number information a1 of the first payment platform, and then the vehicle 100 initiates a request to the vehicle server 120 to obtain the account number information a1 of the first payment platform. At this time, the first payment platform only binds one account information a1, and after receiving the account information a1 fed back by the vehicle service end 120 according to the binding relationship, the account information a1 is used as the account information of the first payment platform, and the account information a1 is used to complete the payment request.
In other embodiments, after the payment event is generated, the vehicle service end 120 queries that the vehicle account number is bound with account number information a1, a2 and a3 of the first payment platform, and then the vehicle 100 initiates a request to the vehicle service end 120 to obtain account number information a1, a2 and a3 of the first payment platform. Because the first payment platform binds a plurality of account information, the user can be requested to input at this time so as to determine the account information of the first payment platform. And then, taking the account information input by the user as the account information of the first payment platform, and completing the payment request according to the account information.
Therefore, the account information of the current payment platform can be obtained according to the binding relationship between the vehicle account and the current payment platform, and the payment request is completed by using the account information.
Referring to fig. 7, in some embodiments, S12 includes:
s121: initiating a request for verification of the vehicle account number in response to the payment event;
s122: and generating a payment mode list aiming at the payment event according to the verification request.
In some embodiments, S121 and S122 may be implemented by the first communication module 114. In other words, the first communication module 114 is configured to initiate a verification request of the vehicle account according to the payment event, and generate a payment method list for the payment event according to the verification request.
In some embodiments, the processor 102 is configured to initiate a validation request for the vehicle account number based on the payment event, and to generate a payment method list for the payment event based on the validation request.
Specifically, after the payment event is generated, the vehicle service 120 initiates a verification request for the vehicle account number to the vehicle 100. The mode of the authentication request may be set according to factors such as the processor performance of the vehicle 100, the processor performance of the vehicle service end 120, and the communication mode between the vehicle 100 and the vehicle service end 120, and may be performed, for example, by a static password or a dynamic password, which is not particularly limited. The authentication by means of the dynamic password may be performed by using a dynamic password based on time synchronization, a dynamic password based on event synchronization, a dynamic password based on challenge/response, or the like.
After the vehicle account passes the verification request, the vehicle service end 200 generates a payment mode list for the payment event according to the verification request and sends the payment mode list to the vehicle 100. The vehicle 100 generates a first sub-payment method list according to the vehicle account and the binding relationship between the vehicle account and the user account of the payment platform, and sends the first sub-payment method list to the vehicle service end 120. The vehicle service end 200 generates a second sub payment method list according to the configuration of the service party and sends the second sub payment method list to the vehicle 100. The configuration of the service party includes, but is not limited to, information such as payment methods supported by the service party. The vehicle 100 receives the second sub-payment method list sent by the vehicle service end 120 and presents the second sub-payment method list to the user.
Referring again to fig. 4, in some embodiments, after the payment event is generated, the vehicle service 120 initiates a verification request of vehicle account number three to the vehicle 100. After the vehicle account number three passes the verification request, the vehicle 100 generates a first sub-payment mode list according to the vehicle account number three and the binding relationship between the vehicle account number three and one or more user accounts of the first payment platform, the second payment platform and the third payment platform: and a, transmitting the first sub-payment mode list to the vehicle service end 120. Since the shopping platform application client does not support payment settlement using the third payment platform, the second sub-payment method list generated by the vehicle service end 120 is: and (4) performing reaction between the component A and the component B. The vehicle 100 receives the second sub-payment method list sent by the vehicle service end 120 and presents the second sub-payment method list to the user.
Therefore, a corresponding payment mode list can be generated according to the setting of the vehicle account and the configuration of the business party, the operation of a user in the payment process is reduced, and the convenience of vehicle-end payment is improved.
Referring to fig. 8, in some embodiments, S13 includes:
s134: receiving a payment confirmation request fed back by a current payment platform according to the payment request and the account information;
s135: the generated payment confirmation information is received for a third user input of the payment confirmation request by the user.
In some embodiments, S134-135 may be implemented by first payment module 116. In other words, the first payment module 116 is configured to receive a payment confirmation request fed back by the current payment platform according to the payment request and the account information, and is configured to receive payment confirmation information generated by a user for a third user input of the payment confirmation request.
In some embodiments, the processor 102 is configured to receive a payment confirmation request fed back by the current payment platform according to the payment request and the account information, and is configured to receive payment confirmation information generated by the user for a third user input of the payment confirmation request.
Specifically, referring again to fig. 4, the user logs in the vehicle account at the vehicle central control platform, and performs the first user input at the service client through the vehicle account. The vehicle 100 generates a payment event according to the first user input, generates a payment mode list according to the payment event, requests the user to perform second user input, and determines to select a current payment platform for payment settlement according to the second user input. After the current payment platform is determined, a payment request is generated and sent to the current payment platform through the vehicle service end 120.
The current payment platform receives a payment request sent by the vehicle service terminal 200, and feeds back a payment confirmation request according to the payment request and account information of the current payment platform. After receiving the payment confirmation request, the vehicle 100 requests the user to perform a third user input, generates payment confirmation information, and sends the payment confirmation information to the current payment platform. The third user input may be a payment key set by the user for account information of the current payment platform, and the key may be in the form of voice, fingerprint, iris, digital password, and the like, which is not limited specifically.
In some embodiments, a password is preset in the account information of the first payment platform bound to the vehicle account number zhangsan. The third vehicle account selects a commodity and creates an order at the client of the shopping platform application program, and after the first payment platform is selected to perform payment settlement on the selected commodity, the vehicle 100 generates a corresponding payment request and sends the payment request to the first payment platform through the vehicle server 120. And the first payment platform feeds back a payment confirmation request according to the payment request and the account information of the current payment platform. The vehicle 100 receives the payment confirmation request fed back by the first payment platform and requests the vehicle account number three to input a password. In the case where the password is correct, the vehicle 100 generates payment confirmation information and transmits the payment confirmation information to the first payment platform.
In other embodiments, a password is preset in the account information of the first payment platform bound to the vehicle account number three. The third vehicle account selects a commodity and creates an order at the client of the shopping platform application program, and after the first payment platform is selected to perform payment settlement on the selected commodity, the vehicle 100 generates a corresponding payment request and sends the payment request to the first payment platform through the vehicle server 120. And the first payment platform feeds back a payment confirmation request according to the payment request and the account information of the current payment platform. The vehicle 100 receives the payment confirmation request fed back by the first payment platform and requests the vehicle account number three to input a password. In the case where the input password is incorrect, the vehicle 100 does not generate payment confirmation information and makes a corresponding prompt.
Therefore, by initiating a verification request of the vehicle account, the legality of the account information is ensured, and the communication safety inside each system and among each system is ensured.
Referring to fig. 9, in some embodiments, S11 includes:
s111: a payment event is generated in response to a voice input by a user.
In some embodiments, S111 may be implemented by the generation module 112. Alternatively, the generating module 112 is configured to generate the payment event according to the voice input of the user.
In some embodiments, the processor 102 is configured to generate a payment event based on a voice input of a user.
In particular, the first user input may be a speech input. The user can select goods or services, confirm purchase and the like through voice input.
In some embodiments, the user enters "book single room at hotel a near guangzhou tower tonight" by voice, and the vehicle 100 generates and sends a payment event for the book hotel to the vehicle service 120 in response to the user input. The vehicle service end 120 generates a payment mode list according to the payment event, and requests the user to select a payment platform for payment settlement. After the user selects the first payment platform, the vehicle 100 generates a payment request, sends the payment request to the first payment platform through the vehicle server 120, and determines account information of the first payment platform corresponding to the third vehicle account so that the first payment platform completes the payment request for reserving the hotel according to the account information.
Therefore, the operation of the user in the driving process is reduced by inputting the command through voice, and the driving safety can be ensured.
Referring to fig. 10, in some embodiments, S13 includes:
s136: and sending account information corresponding to the current payment platform and determined according to the binding relationship between the vehicle account and the user account of the payment platform and voiceprint information acquired according to voice input so that the current payment platform can complete a payment request according to the account information and the voiceprint information.
In some embodiments, S136 may be implemented by the first payment module 116. Or, the first payment module 116 is configured to send account information corresponding to the current payment platform, which is determined according to a binding relationship between a vehicle account and a user account of the payment platform, and voiceprint information acquired according to voice input, so that the current payment platform can complete a payment request according to the account information and the voiceprint information.
In some embodiments, the processor 102 is configured to send account information corresponding to the current payment platform, which is determined according to a binding relationship between a vehicle account and a user account of the payment platform, and voiceprint information acquired according to voice input, so that the current payment platform can complete a payment request according to the account information and the voiceprint information.
Specifically, account information of a current payment platform is determined according to a binding relation between a vehicle account and a user account of the payment platform, voiceprint information of a user is obtained according to voice input and serves as a payment password of the current payment platform, and when the voiceprint payment password of the user is received, the account information and the voiceprint payment password are sent to the current payment platform, so that the current payment platform can complete a payment request according to the account information and the voiceprint information.
In some embodiments, a voiceprint payment password is preset in account information of a first payment platform bound to a vehicle account number three. The third vehicle account selects goods and creates an order in a voice input mode at a client of the shopping platform application program, and the vehicle 100 acquires voiceprint information of the third vehicle account as a payment password of the first payment platform according to the voice input. After the vehicle account number three selects the first payment platform to pay and settle the selected goods, the vehicle service end 120 generates a corresponding payment request and sends the payment request to the first payment platform. And the first payment platform feeds back a payment confirmation request according to the payment request and the account information of the first payment platform. The vehicle 100 receives the payment confirmation request fed back by the first payment platform, requests the vehicle account number to input the voiceprint payment password in three, and sends the account number information and the voiceprint payment password to the first payment platform, so that the first payment platform completes the payment request according to the account number information and the voiceprint payment password.
So, the user can be through order and payment under the voice realization at the driving in-process, promotes user's car end payment and experiences, and helps the user to concentrate on the driving, can guarantee driving safety.
Referring to fig. 11, the present application provides a payment method for a vehicle, including:
s21: receiving a payment request sent by a vehicle;
s22: and receiving account information which is sent by the vehicle and corresponds to the current payment platform so as to complete the payment request.
The embodiment of the application provides a payment platform 200. The payment platform 200 comprises a second communication element 202 and a processor 204. The second communication element 202 is used to receive payment requests sent by the vehicle. The processor 204 is configured to receive account information corresponding to a current payment platform sent by the vehicle to complete the payment request. The processor 204 may be a processor 204 independently configured to implement the above payment method, or may be a processor 204 of a payment system, which is not limited herein.
Referring to fig. 12, an embodiment of the present application further provides a payment platform 210, and a payment method for a vehicle in an embodiment of the present application may be implemented by the payment platform 210. The payment platform 210 includes a second communication module 212 and a second payment module 214. S21 may be implemented by the second communication module 212 and S22 may be implemented by the second payment module 214. Alternatively, the second communication module 212 is configured to receive a payment request from a vehicle. The second payment module 214 is configured to receive account information corresponding to the current payment platform sent by the vehicle to complete the payment request.
Specifically, referring again to fig. 4, during driving, the vehicle 100 generates a payment request according to the user input, and sends the payment request to the payment platform 200 through the vehicle service end 120. The payment platform 200 receives the payment request sent by the vehicle service end 120, and feeds back a payment confirmation request to the vehicle 100 according to the payment request and the account information. The vehicle 100 receives the payment confirmation information and sends the account information to the payment platform, so that the payment platform completes the payment request.
In some embodiments, the user logs into vehicle 100 for vehicle account number three, making a first user input through the shopping platform application client. The first user input may be vehicle account number three selecting a good and creating an order at the shopping platform application client. The vehicle 100 generates a corresponding payment event according to the behavior of the selected commodity with the third vehicle account, and the vehicle server 120 generates a payment mode list according to the payment event to request the third vehicle account for the second user input. The second user input may be the vehicle account number three-choice first payment platform settling the payment for the selected goods. The vehicle 100 determines to select the first payment platform for payment settlement according to the behavior of selecting the first payment platform from the third account number of the vehicle.
After determining that the first payment platform is selected, the vehicle 100 generates a corresponding payment request, and sends the payment request to the first payment platform through the vehicle service end 120. The first payment platform receives a payment request for purchasing goods sent by the vehicle service end 120, and feeds back a payment confirmation request to the vehicle 100 according to the payment request and the account information. The vehicle 100 receives the payment confirmation information and sends the account information to the payment platform, so that the payment platform completes the payment request.
So, can realize the car end payment of driving the vehicle in-process, promote user's car end payment and experience, and help the user to concentrate on the driving, can guarantee driving safety.
The embodiment of the application also provides a computer readable storage medium. One or more non-transitory computer-readable storage media storing a computer program that, when executed by one or more processors, implements the payment method for a vehicle of any of the above embodiments.
The embodiment of the application also provides a vehicle. The vehicle includes a memory and one or more processors, one or more programs being stored in the memory and configured to be executed by the one or more processors. The program includes instructions for executing the payment method of the vehicle of any one of the above embodiments.
The processor may be used to provide computational and control capabilities to support the operation of the entire vehicle. The memory of the vehicle provides an environment for the computer readable instructions in the memory to operate.
It will be understood by those of ordinary skill in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in one or more non-volatile computer-readable storage media, and when executed, may include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), or the like.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A payment method for a vehicle, the payment method comprising:
generating a payment event in response to the first user input;
determining a current payment platform according to a second user input of the payment mode list aiming at the payment event to generate a payment request and sending the payment request to the current payment platform;
and determining account information corresponding to the current payment platform according to the binding relationship between the vehicle account and the user account of the payment platform, so that the current payment platform completes the payment request according to the account information.
2. The payment method according to claim 1, wherein the determining account information corresponding to the current payment platform according to the binding relationship between the vehicle account and the user account of the payment platform so that the current payment platform completes the payment request according to the account information comprises:
judging whether account information of the current payment platform having a binding relationship with the vehicle account exists or not;
if the current payment platform exists, determining account information of the current payment platform according to the binding relationship;
and if the current payment platform does not exist, triggering and binding the vehicle account and the account information of the current payment platform.
3. The payment method according to claim 2, wherein the determining account information of the current payment platform according to the binding relationship comprises:
initiating an acquisition request for acquiring account information corresponding to the current payment platform;
receiving an acquisition request result fed back according to the binding relationship;
and taking the acquisition request result as account information corresponding to the current payment platform.
4. The payment method of claim 1, wherein determining a current payment platform to generate a payment request and sending the payment request to the current payment platform according to a second user input of the list of payment methods for the payment event comprises:
initiating a validation request for the vehicle account number in response to the payment event;
and generating a payment mode list aiming at the payment event according to the verification request.
5. The payment method according to claim 1, wherein the determining account information corresponding to the current payment platform according to the binding relationship between the vehicle account and the user account of the payment platform so that the current payment platform completes the payment request according to the account information comprises:
receiving a payment confirmation request fed back by the current payment platform according to the payment request and the account information;
and receiving payment confirmation information generated by the user aiming at the third user input of the payment confirmation request.
6. The payment method of claim 1, wherein generating the payment event in response to the first user input comprises:
generating the payment event in response to a voice input by a user.
7. The payment method according to claim 6, wherein the determining account information corresponding to the current payment platform according to the binding relationship between the vehicle account and the user account of the payment platform so that the current payment platform completes the payment request according to the account information comprises:
and sending account information corresponding to the current payment platform and determined according to the binding relationship between the vehicle account and a user account of a payment platform and voiceprint information acquired according to the voice input so that the current payment platform can complete the payment request according to the account information and the voiceprint information.
8. A payment method for a vehicle, the payment method comprising:
receiving a payment request sent by the vehicle, wherein the payment request is generated according to the input of a payment mode list generated by a user aiming at a payment event;
and receiving account information which is sent by the vehicle and corresponds to the current payment platform so as to complete the payment request, wherein the account information is determined according to the binding relationship between the vehicle account and the user account of the payment platform.
9. A vehicle system comprising a vehicle and a vehicle service terminal, the vehicle and/or the vehicle service terminal comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements a payment method for a vehicle according to any one of claims 1-7 or 8.
10. One or more non-transitory computer-readable storage media storing a computer program that, when executed by one or more processors, implements a method of payment for a vehicle as recited in any one of claims 1-7 or 8.
CN202011167968.5A 2020-10-27 2020-10-27 Payment method for vehicle, computer device, and storage medium Pending CN112288417A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011167968.5A CN112288417A (en) 2020-10-27 2020-10-27 Payment method for vehicle, computer device, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011167968.5A CN112288417A (en) 2020-10-27 2020-10-27 Payment method for vehicle, computer device, and storage medium

Publications (1)

Publication Number Publication Date
CN112288417A true CN112288417A (en) 2021-01-29

Family

ID=74373382

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011167968.5A Pending CN112288417A (en) 2020-10-27 2020-10-27 Payment method for vehicle, computer device, and storage medium

Country Status (1)

Country Link
CN (1) CN112288417A (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106340131A (en) * 2016-08-12 2017-01-18 上海智接电气设备有限公司 Intelligent charging management system and method of electric automobile
CN108985739A (en) * 2018-07-06 2018-12-11 上海博泰悦臻电子设备制造有限公司 Processing method, system, computer storage medium and the engine end of car payment
WO2019095462A1 (en) * 2017-11-16 2019-05-23 湖南深拓智能设备股份有限公司 Parking management system and parking space management method
EP3560751A1 (en) * 2018-04-27 2019-10-30 Panasonic Intellectual Property Corporation of America Control method, server, in-vehicle device, and program

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106340131A (en) * 2016-08-12 2017-01-18 上海智接电气设备有限公司 Intelligent charging management system and method of electric automobile
WO2019095462A1 (en) * 2017-11-16 2019-05-23 湖南深拓智能设备股份有限公司 Parking management system and parking space management method
EP3560751A1 (en) * 2018-04-27 2019-10-30 Panasonic Intellectual Property Corporation of America Control method, server, in-vehicle device, and program
CN108985739A (en) * 2018-07-06 2018-12-11 上海博泰悦臻电子设备制造有限公司 Processing method, system, computer storage medium and the engine end of car payment

Similar Documents

Publication Publication Date Title
CN114863578B (en) Parking lot control method, system and computer readable storage medium
CN108650098B (en) Method and device for user-defined verification mode
CN107423979B (en) Payment method and device, computer device and readable storage medium
KR101839346B1 (en) Cloud payment system
CN105554003A (en) Method and system for enabling on-board cloud service
CN108876340B (en) Virtual asset transfer method and device based on biological characteristic recognition and storage medium
CN109829273B (en) Identity authentication method, device, system, equipment and readable storage medium
WO2016188249A1 (en) Payment method, device and system
CN112448925B (en) Account management method, device and system
US20150127546A1 (en) Methods for providing internet services through a toll free connection to a user and devices thereof
CN112288417A (en) Payment method for vehicle, computer device, and storage medium
CN111669745A (en) Security verification method and device based on 5G information, storage medium and equipment
CN111582871A (en) Public transport charging method, device and system
KR20140089730A (en) Method and System for Registering Payment Means by using Alliance Application
KR101772358B1 (en) Method for Automatic Identifying Other Companies Application for Registration of Payment Means
CN112288418A (en) Payment method, payment device and storage medium for vehicle
US20230032549A1 (en) Method for Authenticating a User, and Artificial Intelligence System Operating According to the Method
KR20200041631A (en) Apparatus and method for providing a simple settlement service of a corporation account
GB2476054A (en) Voice authentication of bill payment transactions
CN110414974B (en) Virtual payment card generation control method and background service platform
CN111784325A (en) Voice payment method and device, electronic equipment and storage medium
KR20170049289A (en) Method and apparatus for processing overseas remittance
WO2018209623A1 (en) Systems, devices, and methods for performing verification of communications received from one or more computing devices
KR101924834B1 (en) User authentication apparatus for call-based occupancy authentication and operating method thereof
KR20150022298A (en) System and method of payment confirmation using auto-call dialing

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination