CN113128508B - License plate number-based payment processing method and device - Google Patents
License plate number-based payment processing method and device Download PDFInfo
- Publication number
- CN113128508B CN113128508B CN202110546332.XA CN202110546332A CN113128508B CN 113128508 B CN113128508 B CN 113128508B CN 202110546332 A CN202110546332 A CN 202110546332A CN 113128508 B CN113128508 B CN 113128508B
- Authority
- CN
- China
- Prior art keywords
- merchant
- license plate
- plate number
- user account
- user
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 29
- 238000012545 processing Methods 0.000 claims abstract description 58
- 238000000034 method Methods 0.000 claims description 37
- 238000012795 verification Methods 0.000 claims description 20
- 238000013475 authorization Methods 0.000 claims description 18
- 238000012790 confirmation Methods 0.000 claims description 4
- 238000013507 mapping Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 9
- 230000006872 improvement Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000005406 washing Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V20/00—Scenes; Scene-specific elements
- G06V20/60—Type of objects
- G06V20/62—Text, e.g. of license plates, overlay texts or captions on TV images
- G06V20/625—License plates
-
- 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q20/023—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] the neutral party being a clearing house
-
- 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/017—Detecting movement of traffic to be counted or controlled identifying vehicles
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Computer Security & Cryptography (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Multimedia (AREA)
- Traffic Control Systems (AREA)
Abstract
The embodiment of the specification provides a license plate number-based payment processing method and device, wherein the license plate number-based payment processing method comprises the following steps: acquiring a license plate number acquired by a vehicle picture of a target vehicle and identifying the image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number; inquiring a user account with a binding relation with the license plate number; judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located; if yes, carrying out payment processing of the to-be-paid fee based on the user account.
Description
Technical Field
The present document relates to the field of data processing technologies, and in particular, to a license plate number-based payment processing method and device.
Background
With the development of internet technology, users all adopt the internet to carry out data transmission or service communication, and with the improvement of living standard, automobiles are becoming more popular in our lives, and a series of automobile-related services, such as parking service, oiling service, car washing service and the like, are naturally generated, and after the services are provided, the cost payment problem is necessarily involved. With the development of payment technology, how to realize convenient and safe payment has become a trend for users to pursue. Therefore, it is important to simplify various payment processes during the course of the car service and to secure the payment.
Disclosure of Invention
One or more embodiments of the present specification provide a license plate number-based payment processing method. The license plate number-based payment processing method comprises the following steps: the method comprises the steps of acquiring a license plate number obtained by a vehicle picture of a target vehicle and acquired and identified by an image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number. And inquiring the user account with binding relation with the license plate number. Judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located; if yes, carrying out payment processing of the to-be-paid fee based on the user account.
One or more embodiments of the present specification provide a license plate number-based payment processing apparatus including: the acquisition module is configured to acquire a license plate number acquired by a vehicle picture of the target vehicle and identified by the image acquisition component of the merchant, and determine a fee to be paid corresponding to the license plate number. And the inquiring module is configured to inquire the user account with the binding relation with the license plate number. A judging module configured to judge whether a terminal position of a user terminal associated with the user account is in a geofence area where the merchant is located; if yes, a payment module is operated, and the payment module is configured to conduct payment processing of the to-be-paid fee based on the user account.
One or more embodiments of the present specification provide a license plate number-based payment processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: the method comprises the steps of acquiring a license plate number obtained by a vehicle picture of a target vehicle and acquired and identified by an image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number. And inquiring the user account with binding relation with the license plate number. Judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located; if yes, carrying out payment processing of the to-be-paid fee based on the user account.
One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following: the method comprises the steps of acquiring a license plate number obtained by a vehicle picture of a target vehicle and acquired and identified by an image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number. And inquiring the user account with binding relation with the license plate number. Judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located; if yes, carrying out payment processing of the to-be-paid fee based on the user account.
Drawings
For a clearer description of one or more embodiments of the present description or of the solutions of the prior art, the drawings that are needed in the description of the embodiments or of the prior art will be briefly described below, it being obvious that the drawings in the description that follow are only some of the embodiments described in the present description, from which other drawings can be obtained, without inventive faculty, for a person skilled in the art;
FIG. 1 is a process flow diagram of a license plate number based payment processing method provided in one or more embodiments of the present disclosure;
FIG. 2 is a process flow diagram of a license plate number based payment processing method for use in a vehicle service scenario according to one or more embodiments of the present disclosure;
FIG. 3 is a schematic diagram of a license plate number based payment processing apparatus according to one or more embodiments of the present disclosure;
fig. 4 is a schematic structural diagram of a license plate number-based payment processing apparatus according to one or more embodiments of the present disclosure.
Detailed Description
In order to enable a person skilled in the art to better understand the technical solutions in one or more embodiments of the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in one or more embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one or more embodiments of the present disclosure without inventive effort, are intended to be within the scope of the present disclosure.
The embodiment of the payment processing method based on the license plate number is provided in the specification:
referring to fig. 1, a processing flow chart of a license plate number-based payment processing method provided by the present embodiment is shown, and referring to fig. 2, a processing flow chart of a license plate number-based payment processing method applied to a vehicle service scenario is shown.
Referring to fig. 1, the license plate number-based payment processing method provided in the present embodiment specifically includes steps S102 to S108.
Step S102, a license plate number obtained by acquiring and identifying a vehicle picture of a target vehicle by an image acquisition component of a merchant is obtained, and a fee to be paid corresponding to the determined license plate number is determined.
In the license plate number-based payment processing method, in the license plate number payment process, firstly, the payment account corresponding to the license plate number is confirmed, then the positioning information is further checked, the payment is performed through the corresponding payment account under the condition that the position check is passed, specifically, the user account with binding relation with the license plate number is inquired according to the license plate number acquired by the image acquisition equipment, the positioning position of the user terminal associated with the user account is further read on the basis of inquiring the user account, if yes, the payment to be paid is performed through the inquired user account, on the basis that the license plate number is matched with the payment account, the payment account is further checked through the positioning information, the license plate payment accuracy is improved, and the user experience of paying for license plate payment service is prevented from being reduced due to license plate number identification errors.
The image acquisition component in this embodiment refers to a component configured by a merchant and used for acquiring a license plate number image. The merchants include merchants that offer services and support license plate payments, such as parking lots, ETC (Electronic Toll Collection, electronic toll collection system), and other consumer sites.
In a specific implementation, if a user pays a fee generated by a vehicle by using a vehicle license plate payment manner in a vehicle service (such as a parking service, ETC service, car washing service, etc.), the user needs to bind a license plate number with a user account, and in order to improve the simplicity of user operation, in an alternative implementation provided in this embodiment, a binding relationship between the license plate number and the user account is specifically created by:
identifying a travel license image of the target vehicle submitted through the user account, and obtaining travel license information;
generating a verification request based on the driving license information and sending the verification request to a vehicle management system through a verification interface;
and if the verification result returned by the vehicle management system is verification passing, establishing a binding relation between the license plate number and the user account.
Specifically, a user collects and submits a travel license image aiming at a target vehicle through a user terminal associated with a user account, a server identifies information in the travel license image, travel license information is obtained, and in order to ensure the authenticity and effectiveness of the travel license information submitted by the user, a vehicle management system is invoked to verify the travel license information in the travel license image submitted by the user. In addition, the user can bind the license plate number with the appointed bank card.
For example, a user submits a license image of a vehicle through a license plate payment applet in a third party payment platform, a server of the third party payment platform receives the license image and then identifies the license image, obtains related information such as license number, engine number, vin code and the like of the license, generates a verification request according to the related information, sends the verification request to a vehicle management system through an interface provided by a vehicle management system issuing the license, verifies whether the license is authentic according to the related information of the license, returns a verification result to the server through the interface, establishes a binding relation between the license number in the license and a user account submitting the license image if the verification result received by the server is verification passing, and sends a prompt of information verification abnormality to the user if the verification result received by the server is verification failing.
In specific implementation, after the vehicle is served, the merchant identifies the vehicle picture of the target vehicle acquired by the image acquisition component, obtains the license plate number, the merchant matches the license plate number according to the to-be-paid order, determines the to-be-paid order corresponding to the license plate number, and reads the corresponding to-be-paid cost, and in an alternative implementation provided by the embodiment, the to-be-paid cost is determined by the following method:
Identifying the vehicle picture after the vehicle picture acquired by the image acquisition component is acquired to acquire the license plate number;
and matching the order to be paid of the merchant with the license plate number, and reading the order to be paid of the matched order to be paid as the expense to be paid, or determining the expense to be paid based on the order to be paid of the target vehicle.
Specifically, in the process of carrying out payment processing on the to-be-paid fee generated by the vehicle service on the target vehicle, the to-be-paid fee needs to be acquired firstly, after the to-be-paid fee is acquired by a merchant, the vehicle image is identified to acquire a license plate number, the license plate number is associated with an order to be paid, the to-be-paid fee of the target vehicle is acquired, and the license plate number and the to-be-paid fee are sent to a server. In addition, the fee to be paid may be determined as follows: after the vehicle image acquired by the image acquisition component is identified, the license plate number and the corresponding order mark are uploaded to the server by the merchant, and the server reads the to-be-paid fee of the to-be-paid order corresponding to the order mark according to the information uploaded by the merchant.
For example, a user parks in a parking lot, an image acquisition component at the entrance of the parking lot acquires a vehicle image of the vehicle when entering the parking lot, the vehicle image is submitted to a merchant, the merchant identifies the vehicle image to obtain a license plate number of the vehicle, the parking time length of the vehicle is calculated based on the license plate number, the merchant determines the parking time length of the vehicle after the merchant identifies the license plate number of the vehicle after acquiring the vehicle image of the vehicle acquired by the image acquisition component at the exit of the parking lot, the parking cost of the vehicle is determined according to the parking time length, and the license plate number and the parking cost of the vehicle are sent to a server so that the server carries out payment processing.
In addition, the fee to be paid is determined according to the user service order and/or the vehicle service order, wherein the fee to be paid can be determined according to the vehicle service order of the vehicle service, can be determined according to the user service order of the user service, and can be determined according to the user service order and the vehicle service order together. For example, when a user stays in a hotel, the generated hotel fees and parking fees of the user form fees to be paid together, and when the user leaves the hotel, the fees to be paid formed by the hotel fees and the parking fees are paid by using a license plate.
Step S104, inquiring the user account with binding relation with the license plate number.
The user account in this embodiment is an account bound with a license plate number, and paid for a fee to be paid corresponding to the license plate number.
In the specific implementation, in order to realize license plate payment, the operation flow of a user in vehicle service is reduced, the user experience is improved, and after the license plate submitted by a merchant is acquired, a user account with binding relation with the license plate is inquired, so that the user account is utilized to pay the to-be-paid fee corresponding to the license plate. After inquiring a user account bound with a license plate number, in order to ensure the validity and accuracy of license plate payment, further checking the position of the user, and under the condition that the position check is passed, carrying out payment processing by using the inquired user account; in addition, if the user account bound with the license plate number is not queried, a prompt is sent to the merchant so that the merchant performs downlink charging, and the merchant can be reminded to guide the user to open license plate payment service. In an optional implementation manner provided in this embodiment, if a query result of querying a user account having a binding relationship with a license plate number is null, the following steps are executed: and sending an unopened prompt that the target vehicle does not open license plate payment service to the merchant, so that the merchant performs charging under a line based on the to-be-paid fee and prompts a user to open license plate payment service.
Specifically, after sending a non-opening prompt to a merchant, the merchant prompts a user to open license plate payment service, and the user opens the license plate payment service by uploading a driving license plate; the merchant can submit the payment request again after the user opens the license plate payment service, and the server inquires the user account with binding relation with the license plate number according to the payment request.
For example, a user parks in a parking lot, acquires a license plate number and parking cost uploaded by a merchant when a vehicle leaves the parking lot, inquires a user account with binding relation with the license plate number according to the license plate number, and pays the parking cost by using the user account if the user account with binding relation with the license plate number is inquired; if the user account with the binding relation with the license plate number is not queried, a prompt that the license plate payment service is not opened by the user is sent to the merchant, so that the merchant guides the user to pay in a downlink manner, and the merchant can prompt the user to open the license plate payment service.
In practical application, the vehicle collects and identifies the license plate number through image collection equipment (such as a camera) of a merchant, and a bank card or a third party payment account with binding relation with the license plate number is inquired according to the license plate number to finish deduction.
In the specific implementation, after the user account with the binding relation with the license plate number is determined, the positioning information of the user terminal is further checked, and the problem of user experience caused by license plate recognition errors is solved. Therefore, after the user account with the binding relation with the license plate number is determined, whether the user account is an effective account for payment processing is judged according to the positioning information of the user terminal associated with the user account. Because the location information of the user terminal belongs to the privacy of the user to a certain extent, the user needs to be authorized to read the terminal location of the user terminal through the location sensor of the user terminal, so as to ensure the privacy security of the user, and in an optional implementation provided in this embodiment, after the user account is queried, the following steps are further executed:
querying whether a position authorization protocol signed by the user account exists;
if yes, calling a positioning sensor of the user terminal to read the terminal position;
if not, according to a signing instruction of the position authorization protocol submitted by a user of the target vehicle, writing the account identifier of the user account into the position authorization protocol, and calling a positioning sensor of the user terminal to read the terminal position.
In the case of confirming the user to sign the location authorization protocol, the validity of the queried user account is determined by reading the terminal location of the user terminal, and in an alternative implementation provided in this embodiment, after the location authorization protocol signed by the user account is queried, the following operations are performed:
calling a positioning sensor of the user terminal to read the terminal position;
if the terminal position is not read, sending a position access prompt to the user terminal or the merchant;
and calling the positioning sensor to read the terminal position under the condition that the position access permission of the user terminal is opened based on the position access prompt is detected.
Specifically, the user terminal may not open the position access right, so that the position of the reading terminal fails, if the position of the reading terminal fails, a position access prompt is sent to a merchant or the user terminal to remind the user to open the position access right, and after the user opens the position access right, the position of the reading terminal is read through the positioning sensor.
For example, after a user account is queried, whether the user account signs a location authorization protocol is queried, if so, a location sensor of a user terminal associated with the user account is called to read the terminal location, if the reading fails, a location access reminder is sent to a merchant and the user terminal to remind the user to open the access right of the location sensor, and after the access right of the user to open the location sensor is detected, the location sensor is called to read the terminal location.
Step S106, judging whether the terminal position of the user terminal associated with the user account is in the geofence area where the merchant is located.
The geofence area in this embodiment includes an area with a longitude and latitude as a center and a specific distance as a radius; in addition, a grid area is included that is determined based on the merchant location. In an alternative implementation manner provided in this embodiment, the geofence area is determined in the following manner:
reading a merchant location of the merchant;
determining a geographic area according to a preset fence threshold based on the merchant location and taking the geographic area as the geographic fence area.
For example, a circle is constructed with the merchant location as the center of a circle and a radius of 100 meters, the geofence area of the merchant is determined, and in determining whether the terminal location is within the geofence area, it is determined whether the terminal location is within the circle.
For another example, the longitude and latitude of the merchant position are read, the merchant longitude and latitude are expressed on the map according to a certain proportion, a circle is constructed on the map by taking the merchant longitude and latitude position as the circle center and the display proportion of 100 meters on the map as the radius, the geographical fence area of the merchant is determined, and in the process of judging whether the terminal position is in the geographical fence area, whether the longitude and latitude of the terminal position is in the constructed circle is judged if the longitude and latitude of the terminal position are expressed on the map according to a certain proportion.
In addition, in an alternative implementation manner provided in this embodiment, the geofence area may be determined in the following manner:
reading a merchant location of the merchant and mapping the merchant location into a grid map;
determining a target grid where the merchant is located;
and acquiring a grid position area of the target grid, and taking the grid position area as the geofence area where the merchant is located.
For example, the longitude and latitude of the merchant are read, the longitude and latitude of the merchant are mapped in a grid map, the longitude and latitude of the grid position of the merchant are determined, a grid area formed by the longitude and latitude of the grid position is used as the geofence area of the merchant, in the process of judging whether the terminal position is in the geofence area, the longitude and latitude of the terminal position are mapped in the grid map, and whether the longitude and latitude of the merchant in the grid map and the longitude and latitude of the terminal position are in the same grid is judged.
In the implementation, whether the terminal position of the user terminal is in the geofence area of the merchant is determined, if yes, the following step S108 is executed, the payment processing of the to-be-paid fee is performed based on the user account, and if not, a matching failure prompt is sent to the merchant, so that the merchant can further verify. In an optional implementation manner provided in this embodiment, if the execution result of the step of determining whether the terminal position of the user terminal associated with the user account is in the geofence area where the merchant is located is no, the following operations are executed:
Sending the user account and a position matching failure prompt to the merchant so that the merchant performs downlink verification on the user account;
and carrying out payment processing of the to-be-paid fee based on the user account according to a payment confirmation request submitted under the condition that the merchant verifies passing under the online condition.
Specifically, after the user account and the location matching failure reminder are sent to the merchant, the merchant checks whether the user account is authentic, after the user account is authenticated, the merchant can guide the user to pay offline or submit a payment confirmation request, and when the server receives the payment confirmation request for the user account, the server executes the following step S108 to perform the payment processing of the to-be-paid fee based on the user account.
And step S108, carrying out payment processing of the to-be-paid fee based on the user account.
When the terminal position of the user terminal associated with the user account is in the geofence area where the merchant is located, the user account is utilized to pay the fee to be paid generated by the target vehicle. In order to improve the perception degree of the user to the payment result, in an optional implementation manner provided in this embodiment, after the payment processing is performed on the fee to be paid based on the user account, the payment result is sent to the merchant, so that the merchant displays the payment result through a display component; and/or sending the payment result to a user to which the target vehicle belongs. The display component is a component associated with a merchant and used for displaying payment results, and it should be noted that the display component and the image acquisition component of the merchant may be the same component.
For example, after confirming that the terminal position of the user terminal associated with the user account is in the geofence area of the merchant, transferring the resource corresponding to the to-be-paid fee of the vehicle generated by the user in the user account to the account corresponding to the merchant to complete payment processing of the to-be-paid fee, and after the payment processing, sending a processing result of the payment processing to the merchant and the user terminal to enable the merchant to display through the display component and display on the user terminal for the user to view.
The application of the license plate number-based payment processing method provided in the present embodiment to a vehicle service scenario is taken as an example, and further description is given to the license plate number-based payment processing method provided in the present embodiment, referring to fig. 2, and the license plate number-based payment processing method applied to the vehicle service scenario specifically includes steps S202 to S212.
Step S202, a license plate number obtained by acquiring and identifying a vehicle picture of a target vehicle by an image acquisition component of a merchant is obtained, and a fee to be paid corresponding to the determined license plate number is obtained.
Step S204, inquiring the user account with binding relation with the license plate number.
Step S206, detecting whether the user terminal associated with the user account opens the position access right;
If yes, go to step S208 to step S210;
if not, sending a position access prompt to the user terminal or the merchant to prompt the user to open the position access authority.
Step S208, calling a positioning sensor of the user terminal to read the terminal position.
Step S210, judging whether the terminal position is in a geofence area where a merchant is located;
if yes, go to step S212;
if not, sending a prompt of failure in matching allocation to the merchant so as to enable the merchant to charge in line.
Step S212, payment processing is carried out on the fees to be paid by using the user account.
In summary, in the license plate number-based payment processing method provided by the embodiment, firstly, the image acquisition component of the merchant acquires and identifies the vehicle picture of the target vehicle to obtain the license plate number, and the determined to-be-paid fee corresponding to the license plate number, queries the user account with binding relation with the license plate number, determines whether the terminal position of the user terminal associated with the user account is in the geofence area where the merchant is located, if so, performs payment processing on the to-be-paid fee based on the user account, thereby ensuring the accuracy of the queried user account through the determination of the terminal position.
The embodiment of the payment processing device based on license plate numbers provided in the specification is as follows:
in the above-described embodiments, a license plate number-based payment processing method is provided, and a license plate number-based payment processing apparatus is provided corresponding thereto, which will be described below with reference to the accompanying drawings.
Referring to fig. 3, a schematic diagram of a license plate number-based payment processing apparatus according to the present embodiment is shown.
Since the apparatus embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions should be referred to the corresponding descriptions of the method embodiments provided above. The device embodiments described below are merely illustrative.
The embodiment provides a payment processing apparatus based on license plate number, including:
the acquisition module 302 is configured to acquire a license plate number acquired by a vehicle picture of a target vehicle and identified by an image acquisition component of a merchant, and determine a fee to be paid corresponding to the license plate number;
a query module 304 configured to query a user account having a binding relationship with the license plate number;
a determining module 306 configured to determine whether a terminal location of a user terminal associated with the user account is in a geofence area in which the merchant is located;
If yes, a payment module 308 is operated, and the payment module 308 is configured to perform payment processing of the fee to be paid based on the user account.
The embodiment of the payment processing equipment based on license plate numbers provided in the specification is as follows:
in correspondence to the above-described license plate number-based payment processing method, one or more embodiments of the present disclosure further provide a license plate number-based payment processing apparatus, based on the same technical concept, for executing the above-provided license plate number-based payment processing method, and fig. 4 is a schematic structural diagram of a license plate number-based payment processing apparatus provided by one or more embodiments of the present disclosure.
The embodiment provides a payment processing equipment based on license plate number, includes:
as shown in fig. 4, the license plate number-based payment processing apparatus may have a relatively large difference in configuration or performance, may include one or more processors 401 and a memory 402, and may store one or more storage applications or data in the memory 402. Wherein the memory 402 may be transient storage or persistent storage. The application program stored in the memory 402 may include one or more modules (not shown in the figures), each of which may include a series of computer-executable instructions in a license plate number based payment processing device. Still further, the processor 401 may be arranged to communicate with the memory 402 to execute a series of computer executable instructions in the memory 402 on a license plate number based payment processing device. The license plate number based payment processing apparatus may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input/output interfaces 405, one or more keyboards 406, etc.
In one particular embodiment, a license plate number based payment processing device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions for use in the license plate number based payment processing device, and configured to be executed by one or more processors, the one or more programs comprising computer executable instructions for:
acquiring a license plate number acquired by a vehicle picture of a target vehicle and identifying the image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number;
inquiring a user account with a binding relation with the license plate number;
judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located;
if yes, carrying out payment processing of the to-be-paid fee based on the user account.
An embodiment of a storage medium provided in the present specification is as follows:
corresponding to the above-described license plate number-based payment processing method, one or more embodiments of the present specification further provide a storage medium based on the same technical idea.
The storage medium provided in this embodiment is configured to store computer executable instructions, where the computer executable instructions when executed implement the following procedures:
acquiring a license plate number acquired by a vehicle picture of a target vehicle and identifying the image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number;
inquiring a user account with a binding relation with the license plate number;
judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located;
if yes, carrying out payment processing of the to-be-paid fee based on the user account.
It should be noted that, in the present specification, the embodiment about the storage medium and the embodiment about the license plate number-based payment processing method in the present specification are based on the same inventive concept, so that the specific implementation of this embodiment may refer to the implementation of the foregoing corresponding method, and the repetition is omitted.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
In the 30 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each unit may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present specification.
One skilled in the relevant art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
One or more embodiments of the present specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing description is by way of example only and is not intended to limit the present disclosure. Various modifications and changes may occur to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. that fall within the spirit and principles of the present document are intended to be included within the scope of the claims of the present document.
Claims (9)
1. A license plate number-based payment processing method comprises the following steps:
acquiring a license plate number acquired by a vehicle picture of a target vehicle and identifying the image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number;
inquiring a user account with a binding relation with the license plate number;
querying whether a position authorization protocol signed by the user account exists;
if yes, calling a positioning sensor of the user terminal to read the terminal position;
If not, writing the account identifier of the user account into the position authorization protocol according to a signing instruction of the position authorization protocol submitted by the user of the target vehicle, and calling a positioning sensor of the user terminal to read the terminal position; if the terminal position is not read, sending a position access prompt to the user terminal or the merchant; under the condition that the position access permission of the user terminal is opened based on the position access prompt is detected, calling the positioning sensor to read the position of the terminal;
judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located;
if yes, carrying out payment processing of the to-be-paid fee based on the user account;
wherein the geofence area is determined by one of the following means:
reading a merchant location of the merchant; determining a geographic area according to a preset fence threshold based on the merchant location and taking the geographic area as the geographic fence area;
reading a merchant location of the merchant and mapping the merchant location into a grid map; determining a target grid where the merchant is located; and acquiring a grid position area of the target grid, and taking the grid position area as the geofence area where the merchant is located.
2. The license plate number-based payment processing method according to claim 1, wherein the binding relationship between the license plate number and the user account is established by:
identifying a travel license image of the target vehicle submitted through the user account, and obtaining travel license information;
generating a verification request based on the driving license information and sending the verification request to a vehicle management system through a verification interface;
and if the verification result returned by the vehicle management system is verification passing, establishing a binding relation between the license plate number and the user account.
3. The license plate number-based payment processing method according to claim 1, wherein if the execution result after the step of inquiring the user account having a binding relationship with the license plate number is empty, the following operations are executed:
and sending an unopened prompt that the target vehicle does not open license plate payment service to the merchant, so that the merchant performs charging under a line based on the to-be-paid fee and prompts a user to open license plate payment service.
4. The license plate number-based payment processing method according to claim 1, further comprising, after the payment processing step of making the fee to be paid based on the user account is performed:
Sending a payment result to the merchant so that the merchant can display the payment result through a display component;
and/or the number of the groups of groups,
and sending the payment result to a user to which the target vehicle belongs.
5. The license plate number-based payment processing method according to claim 1, wherein if the result of the step of determining whether the terminal position of the user terminal associated with the user account is in the geofence area where the merchant is located is no, the following operations are performed:
sending the user account and a position matching failure prompt to the merchant so that the merchant performs downlink verification on the user account;
and carrying out payment processing of the to-be-paid fee based on the user account according to a payment confirmation request submitted under the condition that the merchant verifies passing under the online condition.
6. The license plate number-based payment processing method according to claim 1, the fee to be paid being determined by:
identifying the vehicle picture after the vehicle picture acquired by the image acquisition component is acquired to acquire the license plate number;
and matching the order to be paid of the merchant with the license plate number, and reading the order to be paid of the matched order to be paid as the expense to be paid, or determining the expense to be paid based on the order to be paid of the target vehicle.
7. A license plate number-based payment processing apparatus comprising:
the acquisition module is configured to acquire a license plate number acquired by a vehicle picture of a target vehicle and identified by an image acquisition component of a merchant, and determine a fee to be paid corresponding to the license plate number;
the inquiry module is configured to inquire a user account with a binding relation with the license plate number; and querying whether a location authorization agreement signed by the user account exists;
if yes, calling a positioning sensor of the user terminal to read the terminal position;
if not, writing the account identifier of the user account into the position authorization protocol according to a signing instruction of the position authorization protocol submitted by the user of the target vehicle, and calling a positioning sensor of the user terminal to read the terminal position; if the terminal position is not read, sending a position access prompt to the user terminal or the merchant; under the condition that the position access permission of the user terminal is opened based on the position access prompt is detected, calling the positioning sensor to read the position of the terminal;
a judging module configured to judge whether a terminal position of a user terminal associated with the user account is in a geofence area where the merchant is located;
If yes, a payment module is operated, and the payment module is configured to conduct payment processing of the to-be-paid fee based on the user account.
8. A license plate number-based payment processing apparatus comprising:
a processor; the method comprises the steps of,
a memory configured to store computer-executable instructions that, when executed, cause the processor to:
acquiring a license plate number acquired by a vehicle picture of a target vehicle and identifying the image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number;
inquiring a user account with a binding relation with the license plate number;
querying whether a position authorization protocol signed by the user account exists;
if yes, calling a positioning sensor of the user terminal to read the terminal position;
if not, writing the account identifier of the user account into the position authorization protocol according to a signing instruction of the position authorization protocol submitted by the user of the target vehicle, and calling a positioning sensor of the user terminal to read the terminal position; if the terminal position is not read, sending a position access prompt to the user terminal or the merchant; under the condition that the position access permission of the user terminal is opened based on the position access prompt is detected, calling the positioning sensor to read the position of the terminal;
Judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located;
if yes, carrying out payment processing of the to-be-paid fee based on the user account;
wherein the geofence area is determined by one of the following means:
reading a merchant location of the merchant; determining a geographic area according to a preset fence threshold based on the merchant location and taking the geographic area as the geographic fence area;
reading a merchant location of the merchant and mapping the merchant location into a grid map; determining a target grid where the merchant is located; and acquiring a grid position area of the target grid, and taking the grid position area as the geofence area where the merchant is located.
9. A storage medium storing computer-executable instructions that when executed implement the following:
acquiring a license plate number acquired by a vehicle picture of a target vehicle and identifying the image acquisition component of a merchant, and determining a fee to be paid corresponding to the license plate number;
inquiring a user account with a binding relation with the license plate number;
Querying whether a position authorization protocol signed by the user account exists;
if yes, calling a positioning sensor of the user terminal to read the terminal position;
if not, writing the account identifier of the user account into the position authorization protocol according to a signing instruction of the position authorization protocol submitted by the user of the target vehicle, and calling a positioning sensor of the user terminal to read the terminal position; if the terminal position is not read, sending a position access prompt to the user terminal or the merchant; under the condition that the position access permission of the user terminal is opened based on the position access prompt is detected, calling the positioning sensor to read the position of the terminal;
judging whether the terminal position of the user terminal associated with the user account is in a geofence area where the merchant is located;
if yes, carrying out payment processing of the to-be-paid fee based on the user account;
wherein the geofence area is determined by one of the following means:
reading a merchant location of the merchant; determining a geographic area according to a preset fence threshold based on the merchant location and taking the geographic area as the geographic fence area;
Reading a merchant location of the merchant and mapping the merchant location into a grid map; determining a target grid where the merchant is located; and acquiring a grid position area of the target grid, and taking the grid position area as the geofence area where the merchant is located.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110546332.XA CN113128508B (en) | 2021-05-19 | 2021-05-19 | License plate number-based payment processing method and device |
| CN202310753777.4A CN116777437A (en) | 2021-05-19 | 2021-05-19 | License plate number-based payment processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110546332.XA CN113128508B (en) | 2021-05-19 | 2021-05-19 | License plate number-based payment processing method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310753777.4A Division CN116777437A (en) | 2021-05-19 | 2021-05-19 | License plate number-based payment processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113128508A CN113128508A (en) | 2021-07-16 |
| CN113128508B true CN113128508B (en) | 2023-07-18 |
Family
ID=76782484
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110546332.XA Active CN113128508B (en) | 2021-05-19 | 2021-05-19 | License plate number-based payment processing method and device |
| CN202310753777.4A Pending CN116777437A (en) | 2021-05-19 | 2021-05-19 | License plate number-based payment processing method and device |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310753777.4A Pending CN116777437A (en) | 2021-05-19 | 2021-05-19 | License plate number-based payment processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN113128508B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113673975A (en) * | 2021-08-13 | 2021-11-19 | 支付宝(杭州)信息技术有限公司 | Data processing method and device |
| CN114373235A (en) * | 2021-11-30 | 2022-04-19 | 深圳市顺易通信息科技有限公司 | Processing method and processing device for parking lot payment and storage medium |
| CN114760335A (en) * | 2022-03-24 | 2022-07-15 | 中国银行股份有限公司 | Vehicle data processing method and device based on block chain and server |
| CN114900552A (en) * | 2022-04-13 | 2022-08-12 | 支付宝(杭州)信息技术有限公司 | Driving reminding pushing processing method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111652607A (en) * | 2020-04-22 | 2020-09-11 | 支付宝(杭州)信息技术有限公司 | Outdoor fuel payment method, equipment and system |
| CN112200968A (en) * | 2020-09-07 | 2021-01-08 | 汉海信息技术(上海)有限公司 | Code scanning payment method and device, electronic equipment and storage medium |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107545416A (en) * | 2017-07-28 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Refuel, refuel clearing, oiling method of payment, device and electronic equipment |
| CN107622536A (en) * | 2017-08-16 | 2018-01-23 | 齐鲁交通信息有限公司 | Highway toll collection system and method with Car license recognition is applied based on mobile terminal |
| CN108389275A (en) * | 2018-02-05 | 2018-08-10 | 杭州安芯科技有限公司 | Internet toll collection system based on handheld device positioning and Car license recognition |
| CN109493022A (en) * | 2018-09-20 | 2019-03-19 | 西安艾润物联网技术服务有限责任公司 | Fee payment method, system, terminal and storage medium based on intelligent vehicle mounted terminal |
| CN109767507A (en) * | 2019-03-01 | 2019-05-17 | 河北交通职业技术学院 | A kind of highway non-parking charge payment system based on fence |
| CN110223402A (en) * | 2019-06-05 | 2019-09-10 | 段属光 | Charging method based on Car license recognition and user location positioning |
| CN112150710B (en) * | 2019-06-28 | 2023-01-31 | 西安光启智能技术有限公司 | Method and device for providing energy, storage medium and electronic device |
| CN111696218A (en) * | 2020-04-27 | 2020-09-22 | 平安国际智慧城市科技股份有限公司 | Online payment method, device and equipment for high-speed toll and storage medium |
-
2021
- 2021-05-19 CN CN202110546332.XA patent/CN113128508B/en active Active
- 2021-05-19 CN CN202310753777.4A patent/CN116777437A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111652607A (en) * | 2020-04-22 | 2020-09-11 | 支付宝(杭州)信息技术有限公司 | Outdoor fuel payment method, equipment and system |
| CN112200968A (en) * | 2020-09-07 | 2021-01-08 | 汉海信息技术(上海)有限公司 | Code scanning payment method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116777437A (en) | 2023-09-19 |
| CN113128508A (en) | 2021-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113128508B (en) | License plate number-based payment processing method and device | |
| KR102230431B1 (en) | Transportation section fare payment method, fare system and payment system | |
| CN110349281A (en) | A kind of charging method, apparatus and system | |
| US20200126069A1 (en) | Data processing method, apparatus and device | |
| CN108805601B (en) | Method, device and equipment for identifying user and account registration | |
| TWI775076B (en) | Vehicle payment method, device, system and electronic device | |
| CN112288502B (en) | Electronic riding invoice processing method and device | |
| CN112396707B (en) | Riding fee calculation method and device | |
| CN115408705A (en) | Vehicle passing data processing method, device, equipment and system | |
| CN113411385B (en) | Vehicle information acquisition method and device and vehicle order processing method and device | |
| CN112862480B (en) | Traffic card processing method and device based on near field communication | |
| CN115392889A (en) | Service processing method and device | |
| CN114550322A (en) | Vehicle service fee processing method and device | |
| CN113673975A (en) | Data processing method and device | |
| CN113240428B (en) | Payment processing method and device | |
| CN112884925B (en) | Multi-account switching processing method and device | |
| CN116013089A (en) | Vehicle reminding method and device | |
| CN114491470A (en) | Service identifier processing method and device | |
| CN113807810A (en) | Electronic license plate sharing method and device | |
| CN116151819A (en) | Method and device for paying traffic in reserved place | |
| CN116385135A (en) | Credit service admittance processing method and apparatus | |
| CN116384983A (en) | Payment processing method and device | |
| CN116091252A (en) | Medical fee payment method and device | |
| CN117034301A (en) | Application authentication processing method and device | |
| CN117094711A (en) | Electronic certificate-based payment processing method and device |
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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40056195 Country of ref document: HK |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230110 Address after: 200120 Floor 15, No. 447, Nanquan North Road, China (Shanghai) Pilot Free Trade Zone, Pudong New Area, Shanghai Applicant after: Alipay.com Co.,Ltd. Address before: 310000 801-11 section B, 8th floor, 556 Xixi Road, Xihu District, Hangzhou City, Zhejiang Province Applicant before: Alipay (Hangzhou) Information Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |