WO2020228367A1 - 移动支付自助签约方法、装置和系统 - Google Patents

移动支付自助签约方法、装置和系统 Download PDF

Info

Publication number
WO2020228367A1
WO2020228367A1 PCT/CN2020/070941 CN2020070941W WO2020228367A1 WO 2020228367 A1 WO2020228367 A1 WO 2020228367A1 CN 2020070941 W CN2020070941 W CN 2020070941W WO 2020228367 A1 WO2020228367 A1 WO 2020228367A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile payment
user
service
contract
self
Prior art date
Application number
PCT/CN2020/070941
Other languages
English (en)
French (fr)
Inventor
卢川
Original Assignee
创新先进技术有限公司
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 创新先进技术有限公司 filed Critical 创新先进技术有限公司
Priority to US16/830,057 priority Critical patent/US20200242712A1/en
Publication of WO2020228367A1 publication Critical patent/WO2020228367A1/zh

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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
    • 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
    • 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

Definitions

  • the present disclosure relates to mobile payment, and more specifically to mobile payment self-service signing.
  • Various representative payment tools in the mobile payment era provide many payment methods. Taking withholding as an example, the user and the service provider sign a withholding agreement through the H5 page. After that, the service provider can initiate deductions through the deduction interface provided by these mobile payment tools and complete the payment according to the actual consumption of the user under any circumstances such as when the user does not have a network. Users will perceive deductions through notifications/billings sent by these mobile payment tools, which greatly improves the convenience of users in certain specific scenarios.
  • a mobile payment self-service signing terminal including: a scanning device for scanning an identification code generated by a mobile payment application, wherein the scanning device includes a camera; A touch-sensitive display screen for receiving touch input from a user, wherein the touch-sensitive display screen displays a prompt message for prompting the user to perform one or more of the following operations: place the identification code in the The scanning area of the scanning device, inputting personal identification information, and making an authorization signature; a communication device for communicating with a mobile payment server and a service provider server; and a processing device configured to: via the communication The device transmits the scanning result from the scanning device to the mobile payment server for verification; in response to the communication device receiving a notification of successful verification from the mobile payment server, prompts the user via the touch-sensitive display screen Input personal identification information; receive personal identification information input by the user via the touch-sensitive display screen and transmit it to the service provider server via the communication device for verification; in response to the communication device receiving The notification of successful verification from the service provider server prompts
  • the identification code is a two-dimensional code, a barcode, or other electronic tags.
  • the touch-sensitive display screen is further configured to display a notification of a successful contract.
  • the authorized signature is a handwritten signature of the user.
  • the mobile payment self-service signing terminal further includes a stylus, and wherein the handwritten signature is written by the user using the stylus on the touch-sensitive display screen.
  • the contract request is a contract withholding request.
  • the mobile payment self-service subscription terminal further includes an input device for receiving user input, wherein the user input includes personal identification information and the user's authorization signature for the contract.
  • the input device includes a card reader, and wherein the personal identification information is read by using the card reader to read services associated with the service provider server Obtained by the smart card provided to the user by the provider.
  • a mobile payment self-service contracting method including: scanning an identification code generated by a mobile payment application; transmitting the scanning result to a mobile payment server for verification; The notification of successful verification of the mobile payment server prompts the user to input personal identification information; receives the personal identification information input by the user and transmits it to the service provider server for verification; in response to receiving the personal identification information from the service provider server A notification of successful verification, prompting the user to authorize and sign the contract agreement; receive an authorized signature from the user and use the authorized signature to send a contract request to the mobile payment server; and receive a contract from the mobile payment server Notification of success or failure.
  • the contract agreement is a contract withholding agreement
  • the contract request is a contract withholding request
  • the user is prompted to show the identification code generated by the mobile payment application again.
  • an operation flow screen showing the identification code generated by the mobile payment application is displayed on the display screen.
  • prompting the user to input personal identification information includes providing various options for the user to choose to input personal identification information, and the options include at least inputting through a keyboard and reading a card through a card reader. enter.
  • the authorized signature is a handwritten signature of the user.
  • the handwritten signature is input by the user on a touch-sensitive display screen using a stylus pen or a finger.
  • the contract agreement is displayed for a predetermined period of time.
  • the method further includes, in response to receiving a notification of a verification failure from the service provider server, incrementing the first counter by one, and comparing the count of the first counter to the first threshold Compare; when the count is greater than the first threshold, return to scan the identification code generated by the mobile payment application, and when the count is not greater than the first threshold, prompt the user to re-enter personal identification information.
  • the method further includes, in response to receiving a notification of a verification failure from the mobile payment server, incrementing a second counter by one, and comparing the count of the second counter with a second threshold. Compare; when the count is greater than the second threshold, return to scan the identification code generated by the mobile payment application, and when the count is not greater than the second threshold, prompt the user to re-enter the authorization signature.
  • a mobile payment self-service signing method including: using a mobile payment application to generate and provide a mobile payment identification code; scanning the mobile payment self-service signing terminal according to the first aspect of the present disclosure Mobile payment identification code and transmitting the scanning result to the mobile payment server; in response to receiving the scanning result, the mobile payment server verifies the related mobile payment account and transmits the verification result to the mobile payment self-service contract terminal; In the case of a successful verification of the mobile payment account, the mobile payment self-service signing terminal prompts the user to input personal identification information; the mobile payment self-service signing terminal transmits the obtained personal identification information to the service provider server for verification; In response to receiving the personal identification information, the service provider server verifies the validity of the personal identification information and transmits the verification result to the mobile payment self-service contract terminal; in the case of successful personal identification verification, the The mobile payment self-service signing terminal prompts the user to authorize the signing agreement; after receiving the user’s authorized signature, the mobile payment self-service signing terminal uses the authorized signature to
  • the personal identification information is input as follows: the mobile payment self-service signing is performed by the user placing the smart card in the reading area of the card reader of the mobile payment self-service signing terminal The terminal reads the card information to obtain the personal identification information.
  • the contract request is a contract withholding request.
  • a mobile payment self-service signing system including: one or more mobile payment self-service signing terminals according to the first aspect of the present disclosure; a service provider server; and a mobile payment server .
  • Figure 1 is a diagram of an example mobile payment self-service subscription terminal according to certain aspects of the present disclosure.
  • FIGS. 2A-2C are flowcharts of an example mobile payment self-service signing method executed by a mobile payment self-service signing terminal according to certain aspects of the present disclosure.
  • FIG. 3 is a diagram of an operation flow of an example mobile payment self-service signing system according to various aspects of the present disclosure.
  • Figure 4 is a diagram of an example mobile payment self-service subscription system according to aspects of the present disclosure.
  • Mobile payment Use mobile devices (for example, smart phones, tablet devices, etc.) to scan codes through mobile payment applications (for example, WeChat payment applications, Apple Pay applications, etc.) or through technologies such as NFC to realize payment.
  • mobile payment applications for example, WeChat payment applications, Apple Pay applications, etc.
  • technologies such as NFC to realize payment.
  • Contract withholding also known as contract withholding, which means signing an agreement with the payment institution to withhold fees for the bound service providers, services, software applications, etc., to achieve automatic withholding of fees.
  • mobile payment contracting for example, contract withholding
  • the bandwidth allocated to each user will be very low, resulting in a very low success rate of user subscriptions. This also gave users a very poor experience.
  • the existing mobile payment cross-border billing has a contract success rate of about 20%, and the reason for the contract failure is mainly due to limited network resources, which leads to user contract failure.
  • the present disclosure provides a mobile payment self-service signing terminal.
  • network bandwidth resources can be used more effectively, the signing success rate can be increased, and the user experience can be improved.
  • the mobile payment self-service signing terminal can be allocated with a fixed proportion of network bandwidth resources sufficient to ensure the success of the signing, so that the success rate of the signing can be guaranteed.
  • FIG. 1 is a diagram of an example mobile payment self-service subscription terminal 100 according to certain aspects of the present disclosure.
  • the example mobile payment self-service subscription terminal 100 shown in FIG. 1 is used to initiate a subscription request to a mobile payment server on behalf of a user, which can effectively prevent many users from competing with each other for limited network bandwidth resources, thereby improving the success of the contract. Rate and improve user experience.
  • an exemplary mobile payment self-service subscription terminal 100 may include a scanning device 102, a touch-sensitive display 104, a communication device 106, and a processing device 108.
  • the scanning device 102 of the mobile payment self-service contract terminal 100 is used to scan the identification code generated by the mobile payment application (for example, WeChat payment application, Apple Pay application, etc.).
  • the scanning device 102 includes a camera for scanning identification codes such as QR codes.
  • the identification code may be any of a two-dimensional code, a barcode, and various other electronic tags.
  • the touch-sensitive display screen 104 of the mobile payment self-service signing terminal 100 is used to display various prompts to the user and to receive the user's touch input.
  • the touch-sensitive display 104 may display a prompt message for prompting the user to perform one or more of the following operations: placing the identification code in the scanning area of the scanning device, inputting personal identification information, and making an authorization signature .
  • the touch-sensitive display screen 104 may display a prompt message prompting the user to place the QR code generated by his WeChat payment application under the camera of the scanning device.
  • the touch-sensitive display 104 may also display a virtual keyboard, handwriting area, etc. for the user to input this information. .
  • the mobile payment self-service subscription terminal 100 may optionally include a speaker (not shown in FIG. 1) for sounding a prompt to the user.
  • a speaker for sounding a prompt to the user.
  • the speaker can emit prompt voices such as "Please enter the room number", "Please show the QR code of WeChat payment account” and so on.
  • the communication device 106 of the mobile payment self-service contract terminal 100 is used to communicate with a mobile payment server and a service provider server to convey user input received from the user and receive input from the mobile payment server and the The response from the service provider server.
  • the processing device 108 of the mobile payment self-service contract terminal 100 has corresponding processing functions, and is configured to interact with the scanning device 102, the touch-sensitive display 104, and the communication device 106 to process, display, or send and receive Various information.
  • the processing device 108 of the mobile payment self-service contract terminal 100 may be configured to transmit the scanning result via the communication device 106
  • the mobile payment server is provided for verification (for example, for account validity verification and/or identity verification, etc.), and then the verification result is received from the mobile payment server via the communication device 106.
  • the processing device 108 may also be configured to prompt the user to enter personal identification information via the touch-sensitive display 104, for example by The touch-sensitive display 104 displays a prompt message prompting the user to input personal identification information, and so on.
  • the processing device 108 may also be configured to transmit the received personal identification information to the service provider server via the communication device 106 for verification and receive the verification result.
  • the processing device 108 may also be configured to prompt the user via the touch-sensitive display 104 to authorize and sign the contract (for example, contract withholding) agreement.
  • the processing device 108 may also be configured to use the received authorization signature of the user via the communication device 106 to send a contract request to the mobile payment server and receive a notification of whether the contract is successful or not. .
  • the mobile payment self-service subscription terminal 100 may also optionally include an input device 110.
  • the input device 110 may optionally include one or more of a card reader 110a, a keyboard 110b, a stylus 110c, and the like.
  • the input device 110 is used by the user to input various information, such as personal identification information, the user's authorized signature for the contract, and so on.
  • the user can place a smart card allocated by the corresponding service provider in the reading area of the card reader 110a to input personal identification information.
  • a smart card allocated by the corresponding service provider in the reading area of the card reader 110a to input personal identification information.
  • each user has a room card for the corresponding room assigned by the cruise ship company; in this scenario, the user can put the room card in the reading area of the card reader 110a in order to input their personal Identification information (for example, room number, etc.).
  • the user can input his personal identification information, such as an ID number, house number, etc., through the keyboard 110b.
  • the user can use the stylus 110c to manually write in the handwriting area on the touch-sensitive display 104 to input various information and perform handwritten signatures.
  • the authorized signature is the user's handwritten signature.
  • the user can also use the stylus 110c to touch virtual keypads, interface elements, etc. on the touch-sensitive display 104 to make input.
  • the touch-sensitive display 104 also displays a notification of whether the contract is successful or not.
  • the mobile payment self-service signing terminal 100 will receive the result from the mobile payment server, and the touch-sensitive display 104 can A notification of "signing successful" is displayed to the user.
  • the mobile payment self-service subscription terminal 100 may optionally include a speaker (not shown in FIG. 1) for playing notifications.
  • the corresponding notification can also be played through the speaker, for example, "Congratulations, the contract is successful".
  • FIG. 2A is a flowchart of an example mobile payment self-service signing method 200 executed by a mobile payment self-service signing terminal according to certain aspects of the present disclosure.
  • the method 200 may be executed by, for example, the mobile payment self-service subscription terminal 100 shown in FIG. 1.
  • the method 200 may include, at block 205, scanning an identification code generated by the user's mobile payment application.
  • the touch-sensitive display screen 104 of the mobile payment self-service signing terminal 100 may display a prompt to prompt the user to use his mobile payment application to generate an identification code and place the generated identification code on the mobile payment self-service signing terminal 100 under the scanning device 102 (for example, a camera). Subsequently, after the user correctly generates and places the identification code, the scanning device 102 of the mobile payment self-service subscription terminal 100 can scan the identification code.
  • the mobile payment self-service signing terminal 100 can prompt the user to log in to their WeChat payment account, generate an account identification code (e.g., QR code, barcode, etc.), and transfer the generated
  • the identification code is placed under a scanning device (for example, a camera), and then the scanning device 102 can scan the identification code displayed by the user.
  • the method 200 may further include in block 210, transmitting the scanning result to the mobile payment server for account validity verification.
  • the communication device 106 of the mobile payment self-service contract terminal 100 can transmit the results of the above scanning to the corresponding mobile payment server, so that the mobile payment server can verify the validity of the corresponding user account and user identity.
  • the mobile payment self-service signing terminal 100 can prompt the user again to provide the correct identification code.
  • the mobile payment self-service signing terminal 100 can optionally provide the user with the reason for the verification failure (for example, the provided identification code is not generated by the expected mobile payment application (for example, WeChat Pay, etc.) Identification code) to guide the user to take the correct action.
  • the mobile payment self-service signing terminal 100 may use voice prompts, display text prompts on the display screen, display action flow screens, and so on to guide the user.
  • the mobile payment self-service signing terminal 100 may respond to this verification failure by issuing a voice prompt "Identification code error. Please provide the identification code of your WeChat payment account.”.
  • the mobile payment self-service signing terminal 100 may also display on its touch-sensitive display 104 a flow screen of how to display the identification code generated by the WeChat payment application to further guide the user.
  • the method 200 may further include, in block 215, prompting the user to input personal identification information in response to receiving a notification of successful verification from the mobile payment server.
  • the mobile payment self-service signing terminal 100 will receive a notification of the verification result from the mobile payment server. If the verification is successful, the mobile payment self-service signing terminal 100 will prompt the user to input personal identification information.
  • the mobile payment self-service signing terminal 100 may prompt the user to choose which way to input personal identification information first, such as using a room card, manually inputting personal identification information (for example, ID card number, room number, phone number, etc.) and many more.
  • personal identification information for example, ID card number, room number, phone number, etc.
  • the mobile payment self-service signing terminal 100 may prompt the user to place his house card near the card reader or perform a swipe operation on the card reader for reading Enter the user’s personal identification information.
  • the user may also choose to manually input personal identification information (for example, in the case that the user does not carry a house card with him).
  • the mobile payment self-service subscription terminal 100 may display a prompt on its display screen for the user to provide his personal identification information through an input device 110 such as a physical or virtual keyboard.
  • the mobile payment self-service signing terminal 100 may prompt the user to input personal identification information such as the cruise ship room number, ID number, visa number, and phone number for verification.
  • the method 200 may include at block 220, receiving personal identification information input by the user and transmitting it to the service provider server for verification.
  • the mobile payment self-service signing terminal 100 can read the user's house card information through the card reader 110a and transmit it to the associated service provider server, or can send the user via the keyboard
  • the personal identification information input by the input device is transmitted to the associated service provider server.
  • the method 200 may further include in block 225, in response to receiving a notification of successful verification from the service provider server, prompting the user to authorize signing the contract (for example, contract withholding) agreement.
  • the mobile payment self-service signing terminal 100 may display the signing agreement through its touch-sensitive display 104 for the user to review and sign. The user can use a finger or a stylus to write a signature on the signature area on the touch-sensitive display 104 to authorize.
  • the mobile payment self-service contract terminal 100 may require the user to fully understand the contract agreement before the user can make a signature. For example, before allowing the user to make a signature, the mobile payment self-service contract terminal 100 may display the contract agreement for a predetermined period of time (for example, 20 seconds, 30 seconds, etc.). Alternatively, the mobile payment self-service signing terminal 100 may also require the user to check the check box for agreeing to the agreement before signing.
  • the mobile payment self-service signing terminal 100 may prompt the user to provide the personal identification information again (for example, swipe the room card again), and repeat the operation in block 220.
  • this repeated operation may have an associated threshold number of times (for example, 3 times, 5 times, etc.), that is, after the threshold number of times is repeated, the mobile payment self-service subscription terminal 100 may return to box 205 to Restart. This is shown in detail in FIG. 2B, which shows in detail the operation flow after receiving the notification of the verification failure from the service provider server.
  • the first counter is incremented by one.
  • the initial value of the first counter is set to zero, and the count is increased by one every time the verification fails.
  • the mobile payment self-service subscription terminal 100 determines whether the count of the first counter is greater than a threshold. If it is, the mobile payment self-service subscription terminal 100 returns to the box 205 of FIG. 2A to prompt and wait to scan the identification code provided by the user. If not, in block 223, the mobile payment self-service subscription terminal 100 prompts the user to re-enter personal identification information, and returns to block 220 of FIG. 2A to receive the information.
  • the method 200 may further include receiving an authorization signature from the user at block 230 and using the authorization signature to send a contract withholding request to the mobile payment server.
  • the mobile payment self-service signing terminal 100 uses the authorized signature and other information after receiving an authorized signature from the user (for example, a handwritten signature made by the user with a finger or a stylus) (for example, the WeChat payment account scanned in step 205 above, etc.) sends a contract withholding request to the WeChat server.
  • an authorized signature for example, a handwritten signature made by the user with a finger or a stylus
  • the method 200 may further include receiving, at block 235, a notification of whether the contract is successful or not from the mobile payment server. For example, in the above example scenario of a large cruise ship, if the mobile payment server determines that the contract withholding request is successful, it sends a notification of the successful contract to the mobile payment self-service contract terminal 100. Subsequently, the mobile payment self-service signing terminal 100 may display the notification on its touch-sensitive display 104. In an embodiment in which the mobile payment self-service signing terminal 100 has a speaker, it can also play a notification of successful signing through the speaker.
  • the mobile payment self-service contract terminal 100 Send notification of contract failure.
  • the mobile payment self-service subscription terminal 100 may display a notification of the contract failure, and may alternatively display the reason for the contract failure, such as a signature error.
  • the mobile payment self-service signing terminal 100 may also prompt the user to further input his handwritten signature, and continue the above-mentioned operations in boxes 230-235.
  • the mobile payment self-service signing terminal 100 can also set a threshold number of contract failures (for example, 3 times, 5 times, etc.); if the number of contract failures exceeds the threshold number of times, the mobile payment self-service signing terminal 100 can Terminate this self-service contract and return to block 205 to restart the self-service contract process. This is shown in detail in FIG. 2C, which shows in detail the operation flow after receiving the notification of the contract failure from the mobile payment server.
  • a threshold number of contract failures for example, 3 times, 5 times, etc.
  • the second counter is incremented by one.
  • the initial value of the second counter is set to zero, and the count is increased by one every time the contract fails.
  • the mobile payment self-service subscription terminal 100 determines whether the count of the second counter is greater than the second threshold. If it is, the mobile payment self-service subscription terminal 100 returns to the box 205 of FIG. 2A to prompt and wait to scan the identification code provided by the user. If not, then in block 241, the mobile payment self-service signing terminal 100 prompts the user to re-enter the authorization signature, and returns to block 230 of FIG. 2A to receive the signature.
  • first threshold and “second threshold” here only mean that these are two separate thresholds, and the two may be the same or different values.
  • the mobile payment self-service contract terminal 100 clears the first counter and the second counter.
  • the present disclosure only provides the operation flow when the service provider server fails to verify the user's personal identification information and the mobile payment server fails to verify the authorized signature, for mobile payment
  • the server's verification failure process for the identification code can also be handled in a similar manner. For example, if a notification that the verification of the identification code fails is received from the mobile payment server, the mobile payment self-service subscription terminal 100 may also increment the corresponding third counter by one, and prompt the user to change after the third counter exceeds the threshold. Mobile payment identification code, seeking help from the service staff of the service provider, etc.
  • the counter can be cancelled, so that whenever the mobile payment self-service subscription terminal receives any notification of verification or contract failure, it will return to rescan the mobile payment identification code.
  • FIG. 3 is a diagram of an operation flow 300 of an example mobile payment self-service subscription system according to various aspects of the present disclosure.
  • the operation process shown in FIG. 3 will be described in conjunction with the example scene of a large cruise ship given above.
  • each operation in FIG. 3 can adopt the operations in any of the alternative embodiments described above in conjunction with FIGS. 1-2.
  • the user can swipe the room card to input the room number, card number, ID number, telephone number, etc. through a virtual or physical keyboard.
  • the process 300 starts with the user using his mobile device to generate and provide a mobile payment identification code.
  • the user can generate a mobile payment identification code according to the prompt of the mobile payment self-service signing terminal 302 using a mobile payment application installed on the user's mobile device and provide it to the mobile payment self-service signing terminal for scanning.
  • the user can open the WeChat payment application on his mobile device and generate a corresponding two-dimensional code, and place the two-dimensional code under the scanning device (for example, camera) of the mobile payment self-service contract terminal for scanning.
  • the mobile payment self-service signing terminal 302 then scans the two-dimensional code provided by the user, and transmits the scanning result to the mobile payment server 303.
  • the mobile payment server 303 receives the scanning result and verifies the user's mobile payment account. For example, the mobile payment server 303 can verify the validity of the corresponding mobile payment account, and so on.
  • the mobile payment server 303 may return the verification result to the mobile payment self-service signing terminal 302.
  • the mobile payment self-service signing terminal 302 may prompt the user to associate a house card. "Associated house card” is to prompt the user to place the smart house card assigned by the large cruise ship in the reading area of his card reader in order to obtain the card information and associate the house card with the mobile payment account.
  • the user can swipe the room card after obtaining the above prompt.
  • the mobile payment self-service signing terminal 302 then transmits the obtained house card information to the service provider server 304 (ie, the server associated with the large cruise ship) for verification.
  • the service provider server 304 then transmits the verification result to the mobile payment self-service signing terminal 302.
  • the mobile payment self-service signing terminal 302 can prompt the user to make an authorized signature through its touch-sensitive display screen, speaker and other devices. After receiving the user's signature (for example, the user's handwritten signature), the mobile payment self-service contract terminal 302 uses the signature to send a contract withholding request to the mobile payment server 303.
  • the mobile payment self-service contract terminal 302 uses the signature to send a contract withholding request to the mobile payment server 303.
  • the mobile payment server 303 processes the contract withholding request to determine whether to approve the contract withholding request. For example, the mobile payment server 303 may compare the user's authorized signature with a pre-stored user signature or with the user's real name to determine whether to approve the contract withholding request. In this example, the mobile payment server 303 may compare the handwriting of the user's signature with the stored handwriting of the user's signature in advance to determine whether the signature is from the same user. Alternatively, the mobile payment server 303 may adopt character recognition technology such as OCR to recognize each character of the user's signature and compare it with pre-stored information such as the user's name to verify the user.
  • character recognition technology such as OCR
  • the mobile payment server 303 determines that the user signature is authentic, it can determine that the contract is successful and then send a notification of the successful contract to the mobile payment self-service contract terminal 302 and the service provider server 304.
  • the mobile payment server 303 may optionally send a notification of the successful subscription to the user's mobile device.
  • the mobile payment server 303 may use short message, email, or the like to send a notification of successful signing to the user's mobile device.
  • FIG. 4 is a diagram of an example mobile payment self-service signing system 400 according to various aspects of the present disclosure.
  • the mobile payment self-service signing system 400 includes one or more mobile payment self-service signing terminals 402 (in an example, it may be the mobile payment self-service signing terminal 100), a mobile payment server 404, and a service provider server 406.
  • the mobile payment self-service contract terminal 402, the mobile payment server 404, and the service provider server 406 can operate according to the various processes described above in conjunction with FIGS. 1-3 to implement mobile payment contract withholding.
  • one or more mobile payment self-service subscription terminals 402 jointly communicate with a mobile payment server through a limited network bandwidth, wherein the limited network bandwidth is evenly distributed among these mobile payment self-service subscription terminals.
  • the ellipsis 403 indicates that the mobile payment self-service signing system 400 may include any greater number of mobile payment self-service signing terminals or only one mobile payment self-service signing terminal .

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种移动支付自助签约方法，包括扫描由移动支付应用所生成的识别码（205）；将扫描结果传送给移动支付服务器以进行验证（210）；响应于接收到来自所述移动支付服务器的验证成功的通知，提示用户输入个人标识信息（215）；接收由所述用户输入的个人标识信息并将其传送给服务提供方服务器以供验证（220）；响应于接收到来自所述服务提供方服务器的验证成功的通知，提示所述用户对签约协议进行授权签名（225）；接收来自所述用户的授权签名并使用该授权签名向所述移动支付服务器发出签约代扣请求（230）；以及接收来自所述移动支付服务器的签约成功与否的通知（235）。

Description

移动支付自助签约方法、装置和系统 技术领域
本公开涉及移动支付，且更具体地涉及移动支付自助签约。
背景技术
移动支付时代的各种代表性支付工具(例如，腾讯公司的微信支付、苹果公司的Apple Pay，等等)提供了众多支付类型的支付方式。以代扣为例，用户与服务提供方之间通过H5页面签订代扣协议。此后，服务提供方可以在用户没有网络等任何情况下，根据用户的实际消费，通过这些移动支付工具提供的扣款接口发起扣款，完成支付。用户将通过这些移动支付工具发送的通知/账单等方式来感知扣款，极大地提高了用户在某些特定场景下消费的便利。
发明内容
根据本公开的第一方面，提供了一种移动支付自助签约终端，包括：用于扫描移动支付应用所生成的识别码的扫描装置，其中所述扫描装置包括摄像头；用于向用户显示提示以及用于接收用户的触摸输入的触敏显示屏，其中所述触敏显示屏显示用于提示用户进行以下各项操作中的一者或多者的提示消息：将所述识别码置于所述扫描装置的扫描区域内、输入个人标识信息、和作出授权签名；用于与移动支付服务器和服务提供方服务器进行通信的通信装置；以及处理装置，所述处理装置被配置成：经由所述通信装置将来自所述扫描装置的扫描结果传送给所述移动支付服务器以进行验证；响应于所述通信装置接收到来自所述移动支付服务器的验证成功的通知，经由所述触敏显示屏提示用户输入个人标识信息；经由所述触敏显示屏接收由所述用户输入的个人标识信息并经由所述通信装置将其传送给所述服务提供方服务器以供验证；响应于所述通信装置接收到来自所述服务提供方服务器的验证成功的通知，经由所述触敏显示屏提示所述用户对签约协议进行授权签名；经由所述触敏显示屏接收来自所述用户的授权签名并经由所述通信装置使用该授权签名向所述移动支付服务器发出签约请求；以及经由所述通信装置接收来自所述移动支付服务器的签约成功与否的通知。
在根据本公开的一实施例中，所述识别码是二维码、条形码、或其他电子标签。
在根据本公开的另一实施例中，所述触敏显示屏还被配置成显示签约成功的通知。
在根据本公开的又一实施例中，所述授权签名是所述用户的手写签名。
在根据本公开的又一实施例中，移动支付自助签约终端还包括触控笔，并且其中所述手写签名是所述用户使用所述触控笔在所述触敏显示屏上书写的。
在根据本公开的又一实施例中，所述签约请求是签约代扣请求。
在根据本公开的又一实施例中，移动支付自助签约终端还包括用于接收用户输入的输入装置，其中所述用户输入包括个人标识信息以及用户对签约的授权签名。
在根据本公开的又一实施例中，所述输入装置包括读卡器，并且其中所述个人标识信息是通过使用所述读卡器来读取由与所述服务提供方服务器相关联的服务提供方提供给所述用户的智能卡来获得的。
根据本公开的第二方面，提供了一种移动支付自助签约方法，包括：扫描由移动支付应用所生成的识别码；将扫描结果传送给移动支付服务器以进行验证；响应于接收到来自所述移动支付服务器的验证成功的通知，提示用户输入个人标识信息；接收由所述用户输入的个人标识信息并将其传送给服务提供方服务器以供验证；响应于接收到来自所述服务提供方服务器的验证成功的通知，提示所述用户对签约协议进行授权签名；接收来自所述用户的授权签名并使用该授权签名向所述移动支付服务器发出签约请求；以及接收来自所述移动支付服务器的签约成功与否的通知。
在根据本公开的一实施例中，所述签约协议是签约代扣协议，并且所述签约请求是签约代扣请求。
在根据本公开的另一实施例中，如果针对所述扫描结果的验证不成功，则提示所述用户再次展示移动支付应用所生成的识别码。
在根据本公开的另一实施例中，在提示所述用户再次展示所述移动支付应用生成的识别码的同时，在显示屏上显示展示所述移动支付应用所生成的识别码的操作流程画面以辅助所述用户。
在根据本公开的又一实施例中，提示用户输入个人标识信息包括提供各种选项供用户选择来输入个人标识信息，所述选项至少包括通过键盘进行输入以及通过读卡器读取卡片来进行输入。
在根据本公开的又一实施例中，所述授权签名是所述用户的手写签名。
在根据本公开的又一实施例中，所述手写签名是所述用户使用触控笔或手指在触敏 显示屏上输入的。
在根据本公开的又一实施例中，在允许所述用户作出手写签名之前，显示签约协议达预定时长。
在根据本公开的又一实施例中，该方法还包括响应于接收到来自服务提供方服务器的验证失败的通知，使第一计数器递增一，并将所述第一计数器的计数与第一阈值相比较；在计数大于所述第一阈值时，返回扫描由移动支付应用所生成的识别码，并且在计数不大于所述第一阈值时，提示用户重新输入个人标识信息。
在根据本公开的又一实施例中，该方法还包括响应于接收到来自移动支付服务器的验证失败的通知，使第二计数器递增一，并将所述第二计数器的计数与第二阈值相比较；在计数大于所述第二阈值时，返回扫描由移动支付应用所生成的识别码，并且在计数不大于所述第二阈值时，提示用户重新输入授权签名。
根据本公开的第三方面，提供了一种移动支付自助签约方法，包括：使用移支付应用来生成并提供移动支付识别码；由根据本公开的第一方面的移动支付自助签约终端扫描所述移动支付识别码并将扫描结果传送给移动支付服务器；响应于接收到所述扫描结果，所述移动支付服务器对相关的移动支付账户进行验证并将验证结果传送给所述移动支付自助签约终端；在针对移动支付账户的验证成功的情况下，所述移动支付自助签约终端提示用户输入个人标识信息；由所述移动支付自助签约终端将获得的个人标识信息传送给服务提供方服务器以进行验证；响应于接收到所述个人标识信息，所述服务提供方服务器验证所述个人标识信息的有效性并将验证结果传送给所述移动支付自助签约终端；在个人标识验证成功的情况下，所述移动支付自助签约终端提示所述用户对签约协议作出授权签名；在接收到所述用户的授权签名之后，所述移动支付自助签约终端使用所述授权签名向所述移动支付服务器发出签约请求；由所述移动支付服务器对所述签约请求进行处理以确定是否准许所述签约请求；以及将签约结果传送给所述移动支付自助签约终端和所述服务提供方服务器。
在根据本公开的一实施例中，所述个人标识信息是如下输入的：通过用户将智能卡片置于所述移动支付自助签约终端的读卡器的读取区来由所述移动支付自助签约终端读取卡片信息，从而获得所述个人标识信息。
在根据本公开的又一实施例中，所述签约请求是签约代扣请求。
根据本公开的第四方面，提供了一种移动支付自助签约系统，包括：一个或多个如 根据本公开的第一方面所述的移动支付自助签约终端；服务提供方服务器；以及移动支付服务器。
各方面一般包括如基本上在本文参照附图所描述并且如通过附图所解说的方法、装备、系统、计算机程序产品和处理系统。
前述内容已较宽泛地勾勒出根据本公开的示例的特征和技术优势以使下面的详细描述可以被更好地理解。附加的特征和优势将在此后描述。所公开的概念和具体示例可容易地被用作修改或设计用于实施与本公开相同的目的的其他结构的基础。此类等效构造并不背离所附权利要求书的范围。本文所公开的概念的特性在其组织和操作方法两方面以及相关联的优势将因结合附图来考虑以下描述而被更好地理解。每一附图是出于解说和描述目的来提供的，且并不定义对权利要求的限定。
附图说明
为了能详细理解本公开的以上陈述的特征所用的方式，可参照各方面来对以上简要概述的内容进行更具体的描述，其中一些方面在附图中解说。然而应该注意，附图仅解说了本公开的某些典型方面，故不应被认为限定其范围，因为本描述可允许有其他等同有效的方面。不同附图中的相同附图标记可标识相同或相似的元素。
图1是根据本公开的某些方面的示例移动支付自助签约终端的示图。
图2A-2C是根据本公开的某些方面的由移动支付自助签约终端执行的示例移动支付自助签约方法的流程图。
图3是根据本公开的各方面的示例移动支付自助签约系统的操作流程的示图。
图4是根据本公开的各方面的示例移动支付自助签约系统的示图。
具体实施方式
以下结合附图阐述的详细描述旨在作为各种配置的描述，而无意表示可实践本文中所描述的概念的仅有的配置。本详细描述包括具体细节以提供对各种概念的透彻理解。然而，对于本领域技术人员将显而易见的是，没有这些具体细节也可实践这些概念。
术语解释：
移动支付：利用移动设备(例如，智能手机、平板设备，等等)通过移动支付应用 (例如，微信支付应用、Apple Pay应用等等)扫码或通过NFC等技术来实现支付。
签约代扣：亦称签约扣款，即与支付机构签订协议，就所绑定的服务提供方、服务、软件应用等等进行代扣费用，实现费用的自动扣缴。
在网络资源有限的情况下，移动支付签约(例如，签约代扣)将存在问题。例如，由于带宽受限，如果众多用户同时发起签约(例如，签约代扣)，则分配给每个用户的带宽将很低，从而导致用户签约的成功率非常低。这也给用户带来了极差的体验。例如，据统计，在具有有限网络带宽的大型游轮场景中，现有移动支付跨境代扣的签约成功率在20％左右，并且签约失败的原因主要是因为网络资源有限从而导致用户签约失败。
为此，本公开提供了一种移动支付自助签约终端。通过使用该移动支付自助签约终端来代用户发起签约请求，可以更有效地利用网络带宽资源，提高签约成功率，从而改进用户体验。例如，该移动支付自助签约终端可分配有足以保证签约成功所需的、固定比例的网络带宽资源，从而可以保证签约成功率。
图1是根据本公开的某些方面的示例移动支付自助签约终端100的示图。根据本公开的一实施例，图1所示的示例移动支付自助签约终端100用于代用户向移动支付服务器发起签约请求，能有效防止众多用户彼此争用有限的网络带宽资源，从而提高签约成功率并改进用户体验。
如图1所示，示例移动支付自助签约终端100可包括扫描装置102、触敏显示屏104、通信装置106以及处理装置108。
在本公开的一实施例中，移动支付自助签约终端100的扫描装置102用于扫描移动支付应用(例如，微信支付应用、Apple Pay应用等等)所生成的识别码。例如，扫描装置102包括用于扫描二维码等识别码的摄像头。在一示例中，识别码可以是二维码、条形码、各种其他电子标签中的任一者。
在本公开的一实施例中，移动支付自助签约终端100的触敏显示屏104用于向用户显示各种提示以及用于接收用户的触摸输入。例如，触敏显示屏104可以显示用于提示用户进行以下各项操作中的一者或多者的提示消息：将识别码置于扫描装置的扫描区域内、输入个人标识信息、和作出授权签名。例如，触敏显示屏104可以显示提示用户将其微信支付应用所生成的二维码置于扫描装置的摄像头下的提示消息。在一示例中，在触敏显示屏104提示用户输入个人标识信息和/或授权签名的场景中，触敏显示屏104还可以显示用于供用户输入这一信息的虚拟键盘、手写区等等。
在一替换实施例中，作为显示提示的补充，移动支付自助签约终端100还可任选地包括扬声器(图1中未示出)，以用于以声音来向用户发出提示。例如，在大型游轮应用中，作为示例，扬声器可以发出“请输入房号”、“请展示微信支付账户二维码”等等提示语音。
在一实施例中，移动支付自助签约终端100的通信装置106用于与移动支付服务器和服务提供方服务器进行通信，以传达从用户接收到的用户输入以及接收来自所述移动支付服务器和所述服务提供方服务器的响应。
在该实施例中，移动支付自助签约终端100的处理装置108具备相应的处理功能，其被配置成与扫描装置102、触敏显示屏104、以及通信装置106进行交互以处理、显示、或收发各种信息。
例如，在以上大型游轮的示例场景中，在扫描装置102扫描了用户提供的微信支付账户的识别码之后，移动支付自助签约终端100的处理装置108可被配置成经由通信装置106将扫描结果传送给移动支付服务器以进行验证(例如，以供进行账户有效性验证和/或身份验证等等)，并随后经由通信装置106从移动支付服务器接收验证结果。在这一验证成功之后(例如，响应于通信装置106接收到来自移动支付服务器的验证成功的通知)，处理装置108还可被配置成经由触敏显示屏104提示用户输入个人标识信息，例如通过触敏显示屏104显示提示用户输入个人标识信息的提示消息，等等。在触敏显示屏104接收到用户输入的个人标识信息之后，处理装置108还可被配置成经由通信装置106将接收到的个人标识信息传送给服务提供方服务器以供验证并接收验证结果。此外，在通信装置106接收到来自服务提供方服务器的验证成功的通知之后，处理装置108还可被配置成经由触敏显示屏104提示用户对签约(例如，签约代扣)协议进行授权签名。在触敏显示屏104接收到来自用户的授权签名之后，处理装置108还可被配置成经由通信装置106使用接收到的用户的授权签名向移动支付服务器发出签约请求并接收签约成功与否的通知。
在本公开的一替换实施例中，作为触敏显示屏104的输入功能的补充或替换，移动支付自助签约终端100还可任选地包括输入装置110。例如，输入装置110可任选地包括读卡器110a、键盘110b、触控笔110c等中的一者或多者。在一示例中，输入装置110用于由用户使用来输入各种信息，诸如个人标识信息、用户对签约的授权签名，等等。
在输入装置110包括读卡器110a的替换实施例中，用户可以将相应服务提供方所分配的智能卡置于读卡器110a的读取区以便输入其个人标识信息。例如，在大型游轮场 景中，每一用户都具有游轮公司所分配的相应房间的房卡；在这一场景中，用户可以将房卡置于读卡器110a的读取区，以便输入其个人标识信息(例如，房号等等)。
在输入装置110包括键盘110b的替换实施例中，用户可以通过键盘110b来输入其个人标识信息，诸如身份证号、房号等等。
在输入装置110包括触控笔110c的替换实施例中，用户可以使用该触控笔110c在触敏显示屏104上的手写区进行手工书写来输入各种信息并进行手写签名。在该示例中，授权签名是用户的手写签名。在另一示例中，用户还可以使用触控笔110c来触摸触敏显示屏104上的虚拟键区、界面元素等来作出输入。
在进一步的实施例中，触敏显示屏104还显示签约成功与否的通知。例如，在微信支付应用被用于大型游轮的场景中，如果用户的授权签名得到验证，则移动支付自助签约终端100将会从移动支付服务器接收到这一结果，并且从而触敏显示屏104可以向用户显示“签约成功”的通知。在一替换实施例中，移动支付自助签约终端100可任选地包括用于播放通知的扬声器(图1中未示出)。在这一示例中，作为在触敏显示屏104上显示通知的替换或补充，还可以通过扬声器来播放相应通知，例如“恭喜您，签约成功”。
图2A是根据本公开的某些方面的由移动支付自助签约终端执行的示例移动支付自助签约方法200的流程图。根据一实施例，方法200可例如由图1所示的移动支付自助签约终端100来执行。
如图所示，方法200可包括在框205，扫描由用户的移动支付应用所生成的识别码。根据本公开的一实施例，移动支付自助签约终端100的触敏显示屏104可显示提示，以便提示用户使用其移动支付应用来生成识别码并将所生成的识别码置于移动支付自助签约终端100的扫描装置102(例如，摄像头)下。随后，在用户正确生成并放置了识别码之后，移动支付自助签约终端100的扫描装置102就可以扫描该识别码。
例如，在微信支付被用于大型游轮的场景中，移动支付自助签约终端100可以提示用户登录其微信支付账户、生成账户识别码(例如，二维码、条形码等等)、并将所生成的识别码置于扫描装置(例如，摄像头)下，随后扫描装置102就可扫描用户所展示的识别码。
方法200还可包括在框210，将扫描结果传送给移动支付服务器以进行账户有效性验证。继续以上实施例，移动支付自助签约终端100的通信装置106可以将上述扫描的 结果传送给相应的移动支付服务器，以便由移动支付服务器对相对应的用户账户的有效性以及用户身份等进行验证。
在一替换实施例中，如果用户错误地将另一应用(例如，社交网络应用、游戏应用等等)所生成的识别码置于移动支付自助签约终端100的扫描装置下，上述验证将不成功并且移动支付服务器会通知移动支付自助签约终端100验证失败。在这种情况下，移动支付自助签约终端100可以再次提示用户提供正确的识别码。在这一实施例中，移动支付自助签约终端100可任选地将验证失败的原因提供给用户(例如，所提供的识别码并非预期移动支付应用(例如，微信支付，等等)所生成的识别码)，从而指导用户采取正确的动作。在该示例中，移动支付自助签约终端100可以采取语音提示、在显示屏上显示文本提示、显示动作流程画面等等来指导用户。
例如，在上述大型游轮场景中，如果用户错误地将某一游戏应用所生成的识别码置于扫描装置102下，则验证将会失败。移动支付自助签约终端100可响应于这一验证失败来发出语音提示“识别码错误。请提供您微信支付账户的识别码。”。作为替换或补充，移动支付自助签约终端100还可以在其触敏显示屏104上显示如何展示使用微信支付应用所生成的识别码的流程画面，以进一步指导用户。
继续参考图2A，方法200还可包括在框215，响应于接收到来自移动支付服务器的验证成功的通知，提示用户输入个人标识信息。在一实施例中，移动支付自助签约终端100将接收到来自移动支付服务器的验证结果的通知。如果验证成功，则移动支付自助签约终端100将提示用户输入个人标识信息。
在一示例中，移动支付自助签约终端100可以提示用户首先选择采取何种方式来输入个人标识信息，例如使用房卡、手动输入个人标识信息(例如，身份证号、房号、电话号码，等等)等。
在以上大型游轮的场景中，用户一般具有相关联的智能房卡。在该示例场景中，如果用户选择了使用房卡来输入个人标识信息，则移动支付自助签约终端100可以提示用户将其房卡放置在读卡器附近或针对读卡器执行刷扫操作，以便读入用户的个人标识信息。
或者，在一替换实施例中，用户也可以选择手动输入个人标识信息(例如，在用户没有随身携带房卡的情况下)。在这一示例中，响应于用户的这一选择，移动支付自助签约终端100可以在其显示屏上显示提示以供用户通过物理或虚拟的键盘之类的输入装 置110来提供其个人标识信息。例如，在大型游轮场景中，移动支付自助签约终端100可以提示用户输入游轮房间号、身份证号、签证号、电话号码等个人标识信息，以便验证。
继续参考图2A，方法200可包括在框220，接收由用户输入的个人标识信息并将其传送给服务提供方服务器以供验证。例如，在以上大型游轮的示例场景中，移动支付自助签约终端100可以通过读卡器110a来读取用户房卡的信息并将其传送给相关联的服务提供方服务器，或者可以将用户经由键盘等输入装置输入的个人标识信息传送给相关联的服务提供方服务器。
方法200还可包括在框225，响应于接收到来自服务提供方服务器的验证成功的通知，提示用户对签约(例如，签约代扣)协议进行授权签名。在一示例中，移动支付自助签约终端100可以通过其触敏显示屏104显示签约协议以供用户审阅和签名。用户可以使用手指或触控笔在触敏显示屏104上的签名区域书写签名以作出授权。
在一实施例中，在用户能够作出签名之前，移动支付自助签约终端100可要求用户充分理解签约协议。例如，在允许用户作出签名之前，移动支付自助签约终端100可以显示签约协议达预定时长(例如，20秒、30秒等等)。或者，移动支付自助签约终端100也可以要求用户必须勾选同意该协议的复选框，此后才能作出签名。
在另一实施例中，如果接收到来自服务提供方服务器的验证失败的通知(例如，房卡信息有误或任何其他原因)，则移动支付自助签约终端100可以提示用户重新提供个人标识信息(例如，再次刷扫房卡)，并重复在框220的操作。在该实施例中，这一重复操作可具有相关联的阈值次数(例如，3次、5次，等等)，即在重复达该阈值次数之后，移动支付自助签约终端100可以返回框205以重新开始。这在图2B中详细地示出，其详细示出了在接收到来自服务提供方服务器的验证失败的通知之后的操作流程。
如图2B所示，在框221，响应于接收到来自服务提供方服务器的验证失败的通知，使第一计数器递增一。在一示例中，该第一计数器初始值被设置成零，且每次验证失败都使得计数加一。随后，在框222，移动支付自助签约终端100确定第一计数器的计数是否大于阈值。如果是，则移动支付自助签约终端100返回图2A的框205，以提示并等待扫描用户提供的识别码。如果否，则在框223，移动支付自助签约终端100提示用户重新输入个人标识信息，并返回图2A的框220以接收该信息。
继续参考图2A，方法200还可包括在框230接收来自用户的授权签名并使用该授权 签名向移动支付服务器发出签约代扣请求。
例如，在以上大型游轮的示例场景中，移动支付自助签约终端100在接收到来自用户的授权签名(例如，用户使用手指或触控笔作出的手写签名)之后，使用该授权签名以及其他信息(例如，以上在步骤205中扫描的微信支付账户，等等)向微信服务器发出签约代扣请求。
方法200还可包括在框235接收来自移动支付服务器的签约成功与否的通知。例如，在以上大型游轮的示例场景中，如果移动支付服务器确定签约代扣请求成功，则向移动支付自助签约终端100发出签约成功的通知。随后，移动支付自助签约终端100可以在其触敏显示屏104上显示该通知。在移动支付自助签约终端100具有扬声器的实施例中，其还可以通过扬声器来播放签约成功的通知。
在另一示例中，如果移动支付服务器确定签约代扣请求不成功，例如由于用户的签名未获通过(例如，非微信支付账户的用户本人的签名，等等)，则向移动支付自助签约终端100发送签约失败的通知。在该示例中，移动支付自助签约终端100可以显示该签约失败的通知，并可另选地显示签约失败的原因，例如签名错误。在这种情况下，移动支付自助签约终端100还可提示用户进一步输入其手写签名，并继续上述在框230-235中的操作。在该示例中，移动支付自助签约终端100还可设定签约失败的阈值次数(例如，3次、5次，等等)；如果签约失败次数超过该阈值次数，则移动支付自助签约终端100可以终止本次自助签约并返回至框205，以重新开始自助签约流程。这在图2C中详细地示出，其详细示出了在接收到来自移动支付服务器的签约失败的通知之后的操作流程。
如图2C所示，在框237，响应于接收到来自移动支付服务器的签约失败的通知，使第二计数器递增一。在一示例中，该第二计数器初始值被设置成零，且每次签约失败都使得计数加一。随后，在框239，移动支付自助签约终端100确定第二计数器的计数是否大于第二阈值。如果是，则移动支付自助签约终端100返回图2A的框205，以提示并等待扫描用户提供的识别码。如果否，则在框241，移动支付自助签约终端100提示用户重新输入授权签名，并返回图2A的框230以接收该签名。
本领域技术人员可以明白，“第一阈值”和“第二阈值”在此仅仅表示这是两个分开的阈值，这两者可以是相同或不同的值。
此外，在根据本公开的一实施例中，在接收到来自移动支付服务器的签约成功的通 知之后，移动支付自助签约终端100使得第一计数器和第二计数器清零。
另外，本领域技术人员可以明白，尽管本公开仅仅给出了在服务提供方服务器对用户的个人标识信息的验证失败以及移动支付服务器对授权签名的验证失败的情况下的操作流程，对于移动支付服务器针对识别码的验证失败流程也可按相似的方式来处理。例如，如果接收到来自移动支付服务器的针对识别码的验证失败的通知，移动支付自助签约终端100也可以使得相应的第三计数器递增一，并且在第三计数器的计数超过阈值之后，提示用户更换移动支付识别码、向服务提供方的服务人员寻求帮助，等等。
在又一替换实施例中，计数器可被取消，从而每当移动支付自助签约终端收到任何验证或签约失败的通知时，都会返回重新扫描移动支付识别码。
图3是根据本公开的各方面的示例移动支付自助签约系统的操作流程300的示图。为简明起见，将结合以上给出的大型游轮示例场景来描述图3所示的操作流程。但本领域技术人员可以明白，图3中的各个操作可以采取以上结合图1-2描述的任何替换实施例中的操作。例如，用户刷扫房卡可以改为用户通过虚拟或物理键盘来输入房号、卡号、身份证号、电话号码等等。
如图3所示，流程300始于用户使用其移动设备来生成并提供移动支付识别码。在一实施例中，用户可以根据移动支付自助签约终端302的提示，使用安装在用户的移动设备上的移动支付应用生成移动支付识别码并将其提供给移动支付自助签约终端，以供扫描。例如，用户可以打开其移动设备上的微信支付应用并生成相应的二维码，将该二维码置于移动支付自助签约终端的扫描装置(例如，摄像头)下，以供扫描。
移动支付自助签约终端302随后扫描用户所提供的二维码，并将扫描结果传送给移动支付服务器303。移动支付服务器303接收该扫描结果并对用户的移动支付账户进行验证。例如，移动支付服务器303可以验证相应移动支付账户的有效性，等等。
随后，移动支付服务器303可以将验证结果返回给移动支付自助签约终端302。在验证成功的情况下，移动支付自助签约终端302可以提示用户关联房卡。“关联房卡”即是提示用户将其由大型游轮分配的智能房卡置于其读卡器的读取区，以便获取卡片信息，从而将该房卡与移动支付账户进行关联。
用户在获得上述提示后，可以刷扫房卡。移动支付自助签约终端302随后将获得的房卡信息传送给服务提供方服务器304(即，与大型游轮相关联的服务器)以进行验证。服务提供方服务器304随后将验证结果传送给移动支付自助签约终端302。
如果验证成功，则移动支付自助签约终端302可以通过其触敏显示屏、扬声器等等设备来提示用户作出授权签名。在接收到用户的签名(例如，用户的手写签名)之后，移动支付自助签约终端302使用该签名向移动支付服务器303发出签约代扣请求。
移动支付服务器303对该签约代扣请求进行处理以确定是否准许该签约代扣请求。例如，移动支付服务器303可以将用户的授权签名与预先储存的用户签名进行比较或者与用户的真实姓名进行比较以确定是否准许该签约代扣请求。在该示例中，移动支付服务器303可以比较用户签名的笔迹与所存储的预先储存的用户签名的笔迹，以确定签名是否来自同一用户。或者，移动支付服务器303可以采取OCR等字符识别技术来识别用户签名的各个字符并将其与预先储存的用户姓名等信息相比较，以验证该用户。
如果移动支付服务器303确定用户签名是真实的，则可确定签约成功并随后向移动支付自助签约终端302和服务提供方服务器304发送签约成功的通知。
在一替换实施例中，移动支付服务器303还可任选地向用户的移动设备发送签约成功的通知。例如，移动支付服务器303可以使用短消息、电子邮件等等方式向用户的移动设备发送签约成功的通知。
图4是根据本公开的各方面的示例移动支付自助签约系统400的示图。如图所示，移动支付自助签约系统400包括一个或多个移动支付自助签约终端402(在一示例中，其可以是移动支付自助签约终端100)、移动支付服务器404以及服务提供方服务器406。
在一实施例中，移动支付自助签约终端402、移动支付服务器404以及服务提供方服务器406可以按以上结合图1-3描述的各个流程来操作，以实现移动支付签约代扣。在该实施例中，一个或多个移动支付自助签约终端402共同通过有限的网络带宽与移动支付服务器进行通信，其中该有限的网络带宽在这些移动支付自助签约终端之间平均分配。尽管图4中为简明起见只示出了两个移动支付自助签约终端，但省略号403表明移动支付自助签约系统400可包括任何更多数目的移动支付自助签约终端或仅包括一个移动支付自助签约终端。
以上具体实施方式包括对附图的引用，附图形成具体实施方式的部分。附图通过说明来示出可实践的特定实施例。这些实施例在本文中也称为“示例”。此类示例可以包括除所示或所述的那些元件以外的元件。然而，还构想了包括所示或所述元件的示例。此外，还构想出的是使用所示或所述的那些元件的任何组合或排列的示例，或参照本文中示出或描述的特定示例(或其一个或多个方面)，或参照本文中示出或描述的其他示例 (或其一个或多个方面)。
在所附权利要求书中，术语“包括”和“包含”是开放式的，也就是说，在权利要求中除此类术语之后列举的那些元件之外的元件的系统、设备、制品或过程仍被视为落在那项权利要求的范围内。此外，在所附权利要求书中，术语“第一”、“第二”和“第三”等仅被用作标记，并且不旨在表明对它们的对象的数字顺序。
另外，本说明书中所解说的各操作的次序是示例性的。在替换实施例中，各操作可以按与附图所示的不同次序执行，且各操作可以合并成单个操作或拆分成更多操作。
以上描述旨在是说明性的，而非限制性的。例如，可结合其他实施例来使用以上描述的示例(或者其一个或多个方面)。例如，尽管本说明书中给出了微信支付应用在大型游轮上签约代扣的示例场景，但本领域技术人员可以明白，本公开的各技术方案也可应用于各种网络资源差的应用场景中，例如大型赛事、聚会等等，并可使用各种其他移动支付工具。可诸如由本领域普通技术人员在审阅以上描述之后来使用其他实施例。摘要允许读者快速地确定本技术公开的性质。提交该摘要，并且理解该摘要将不用于解释或限制权利要求的范围或含义。此外，在以上具体实施方式中，各种特征可以共同成组以使本公开流畅。然而，权利要求可以不陈述本文中公开的每一特征，因为实施例可以表征所述特征的子集。此外，实施例可以包括比特定示例中公开的特征更少的特征。因此，所附权利要求书由此被结合到具体实施方式中，一项权利要求作为单独的实施例而独立存在。本文中公开的实施例的范围应当参照所附权利要求书以及此类权利要求所赋予权利的等价方案的完整范围来确定。

Claims (22)

  1. 一种移动支付自助签约终端，包括：
    用于扫描移动支付应用所生成的识别码的扫描装置，其中所述扫描装置包括摄像头；
    用于向用户显示提示以及用于接收用户的触摸输入的触敏显示屏，其中所述触敏显示屏显示用于提示用户进行以下各项操作中的一者或多者的提示消息：将所述识别码置于所述扫描装置的扫描区域内、输入个人标识信息、和作出授权签名；
    用于与移动支付服务器和服务提供方服务器进行通信的通信装置；以及
    处理装置，所述处理装置被配置成：
    经由所述通信装置将来自所述扫描装置的扫描结果传送给所述移动支付服务器以进行验证；
    响应于所述通信装置接收到来自所述移动支付服务器的验证成功的通知，经由所述触敏显示屏提示用户输入个人标识信息；
    经由所述触敏显示屏接收由所述用户输入的个人标识信息并经由所述通信装置将其传送给所述服务提供方服务器以供验证；
    响应于所述通信装置接收到来自所述服务提供方服务器的验证成功的通知，经由所述触敏显示屏提示所述用户对签约协议进行授权签名；
    经由所述触敏显示屏接收来自所述用户的授权签名并经由所述通信装置使用该授权签名向所述移动支付服务器发出签约请求；以及
    经由所述通信装置接收来自所述移动支付服务器的签约成功与否的通知。
  2. 如权利要求1所述的移动支付自助签约终端，其特征在于，所述识别码是二维码、条形码、或其他电子标签。
  3. 如权利要求1所述的移动支付自助签约终端，其特征在于，所述触敏显示屏还被配置成显示签约成功的通知。
  4. 如权利要求1所述的移动支付自助签约终端，其特征在于，所述授权签名是所述用户的手写签名。
  5. 如权利要求4所述的移动支付自助签约终端，其特征在于，还包括触控笔，并且其中所述手写签名是所述用户使用所述触控笔在所述触敏显示屏上书写的。
  6. 如权利要求1所述的移动支付自助签约终端，其特征在于，所述签约请求是签约代扣请求。
  7. 如权利要求1所述的移动支付自助签约终端，其特征在于，还包括用于接收用户输入的输入装置，其中所述用户输入包括个人标识信息以及用户对签约的授权签名。
  8. 如权利要求7所述的移动支付自助签约终端，其特征在于，所述输入装置包括读卡器，并且其中所述个人标识信息是通过使用所述读卡器来读取由与所述服务提供方服务器相关联的服务提供方提供给所述用户的智能卡来获得的。
  9. 一种移动支付自助签约方法，包括：
    扫描由移动支付应用所生成的识别码；
    将扫描结果传送给移动支付服务器以进行验证；
    响应于接收到来自所述移动支付服务器的验证成功的通知，提示用户输入个人标识信息；
    接收由所述用户输入的个人标识信息并将其传送给服务提供方服务器以供验证；
    响应于接收到来自所述服务提供方服务器的验证成功的通知，提示所述用户对签约协议进行授权签名；
    接收来自所述用户的授权签名并使用该授权签名向所述移动支付服务器发出签约请求；以及
    接收来自所述移动支付服务器的签约成功与否的通知。
  10. 如权利要求9所述的方法，其特征在于，所述签约协议是签约代扣协议，并且所述签约请求是签约代扣请求。
  11. 如权利要求9所述的方法，其特征在于，如果针对所述扫描结果的验证不成功，则提示所述用户再次展示移动支付应用所生成的识别码。
  12. 如权利要求11所述的方法，其特征在于，在提示所述用户再次展示所述移动支付应用生成的识别码的同时，在显示屏上显示展示所述移动支付应用所生成的识别码的操作流程画面以辅助所述用户。
  13. 如权利要求9所述的方法，其特征在于，提示用户输入个人标识信息包括提供各种选项供用户选择来输入个人标识信息，所述选项至少包括通过键盘进行输入以及通过读卡器读取卡片来进行输入。
  14. 如权利要求9所述的方法，其特征在于，所述授权签名是所述用户的手写签名。
  15. 如权利要求14所述的方法，其特征在于，所述手写签名是所述用户使用触控笔或手指在触敏显示屏上输入的。
  16. 如权利要求15所述的方法，其特征在于，在允许所述用户作出手写签名之前，显示签约协议达预定时长。
  17. 如权利要求9所述的方法，其特征在于，还包括响应于接收到来自服务提供方服务器的验证失败的通知，使第一计数器递增一，并将所述第一计数器的计数与第一阈值相比较；在计数大于所述第一阈值时，返回扫描由移动支付应用所生成的识别码，并且在计数不大于所述第一阈值时，提示用户重新输入个人标识信息。
  18. 如权利要求9所述的方法，其特征在于，还包括响应于接收到来自移动支付服务器的验证失败的通知，使第二计数器递增一，并将所述第二计数器的计数与第二阈值相比较；在计数大于所述第二阈值时，返回扫描由移动支付应用所生成的识别码，并且在计数不大于所述第二阈值时，提示用户重新输入授权签名。
  19. 一种移动支付自助签约方法，包括：
    使用移动支付应用来生成并提供移动支付识别码；
    由如权利要求1-8中的任一项所述的移动支付自助签约终端扫描所述移动支付识别码并将扫描结果传送给移动支付服务器；
    响应于接收到所述扫描结果，所述移动支付服务器对相关的移动支付账户进行验证并将验证结果传送给所述移动支付自助签约终端；
    在针对移动支付账户的验证成功的情况下，所述移动支付自助签约终端提示用户输入个人标识信息；
    由所述移动支付自助签约终端将获得的个人标识信息传送给服务提供方服务器以进行验证；
    响应于接收到所述个人标识信息，所述服务提供方服务器验证所述个人标识信息的有效性并将验证结果传送给所述移动支付自助签约终端；
    在个人标识信息验证成功的情况下，所述移动支付自助签约终端提示所述用户对签约协议作出授权签名；
    在接收到所述用户的授权签名之后，所述移动支付自助签约终端使用所述授权签名向所述移动支付服务器发出签约请求；
    由所述移动支付服务器对所述签约请求进行处理以确定是否准许所述签约请求；以及
    将签约结果传送给所述移动支付自助签约终端和所述服务提供方服务器。
  20. 如权利要求19所述的移动支付自助签约方法，其特征在于，所述个人标识信息是如下输入的：通过用户将智能卡片置于所述移动支付自助签约终端的读卡器的读取区来由所述移动支付自助签约终端读取卡片信息，从而获得所述个人标识信息。
  21. 如权利要求19所述的移动支付自助签约方法，其特征在于，所述签约请求是签约代扣请求。
  22. 一种移动支付自助签约系统，包括：
    一个或多个如权利要求1-8中的任一项所述的移动支付自助签约终端；
    服务提供方服务器；以及
    移动支付服务器。
PCT/CN2020/070941 2019-05-14 2020-01-08 移动支付自助签约方法、装置和系统 WO2020228367A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/830,057 US20200242712A1 (en) 2019-05-14 2020-03-25 Method, apparatus and system for self-service contract for mobile payments

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910400049.9A CN110245936A (zh) 2019-05-14 2019-05-14 移动支付自助签约方法、装置和系统
CN201910400049.9 2019-05-14

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/830,057 Continuation US20200242712A1 (en) 2019-05-14 2020-03-25 Method, apparatus and system for self-service contract for mobile payments

Publications (1)

Publication Number Publication Date
WO2020228367A1 true WO2020228367A1 (zh) 2020-11-19

Family

ID=67884386

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/070941 WO2020228367A1 (zh) 2019-05-14 2020-01-08 移动支付自助签约方法、装置和系统

Country Status (3)

Country Link
CN (1) CN110245936A (zh)
TW (1) TW202042136A (zh)
WO (1) WO2020228367A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110245936A (zh) * 2019-05-14 2019-09-17 阿里巴巴集团控股有限公司 移动支付自助签约方法、装置和系统
CN112995244B (zh) * 2019-12-02 2022-04-22 华为技术有限公司 一种签约代扣方法、资源访问方法及设备
CN111260344B (zh) * 2020-01-21 2022-04-29 支付宝(杭州)信息技术有限公司 一种签约方法、装置及设备
CN111612469A (zh) * 2020-06-01 2020-09-01 支付宝(杭州)信息技术有限公司 签约方法、支付系统及移动电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101004809A (zh) * 2006-08-25 2007-07-25 刘明晶 基于身份证的信用卡支付方法
CN101071490A (zh) * 2007-03-23 2007-11-14 田小平 会员名称与银行卡绑定的电子商务系统和方法
US20140108261A1 (en) * 2012-07-31 2014-04-17 Mercury Payment Systems, Llc Systems and methods for payment management for supporting mobile payments
CN107895256A (zh) * 2017-11-08 2018-04-10 平安科技（深圳）有限公司 银行账户解挂失业务处理方法、系统、终端及存储介质
CN110245936A (zh) * 2019-05-14 2019-09-17 阿里巴巴集团控股有限公司 移动支付自助签约方法、装置和系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104063790B (zh) * 2013-09-18 2017-07-07 腾讯科技（深圳）有限公司 通过移动终端提供授权的方法及系统
US10482461B2 (en) * 2014-05-29 2019-11-19 Apple Inc. User interface for payments
CN107274176A (zh) * 2017-06-16 2017-10-20 深圳市熙博尔电子科技有限公司 多功能互联网信息显示自助服务方法和系统
CN109215254B (zh) * 2017-06-30 2022-05-10 阿里巴巴集团控股有限公司 实体店铺应用系统、用户信息处理方法及装置
CN109377237A (zh) * 2018-11-21 2019-02-22 广东长虹电子有限公司 一种指纹识别支付方法及应用其的支付终端机
CN109658622A (zh) * 2018-12-14 2019-04-19 武汉菲奥达物联科技有限公司 一种公寓自助服务终端、系统及自助签约入住方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101004809A (zh) * 2006-08-25 2007-07-25 刘明晶 基于身份证的信用卡支付方法
CN101071490A (zh) * 2007-03-23 2007-11-14 田小平 会员名称与银行卡绑定的电子商务系统和方法
US20140108261A1 (en) * 2012-07-31 2014-04-17 Mercury Payment Systems, Llc Systems and methods for payment management for supporting mobile payments
CN107895256A (zh) * 2017-11-08 2018-04-10 平安科技（深圳）有限公司 银行账户解挂失业务处理方法、系统、终端及存储介质
CN110245936A (zh) * 2019-05-14 2019-09-17 阿里巴巴集团控股有限公司 移动支付自助签约方法、装置和系统

Also Published As

Publication number Publication date
TW202042136A (zh) 2020-11-16
CN110245936A (zh) 2019-09-17

Similar Documents

Publication Publication Date Title
WO2020228367A1 (zh) 移动支付自助签约方法、装置和系统
US8990909B2 (en) Out-of-band challenge question authentication
US9560033B2 (en) Method and system for authenticating user identity
US8325889B2 (en) Efficient authentication of a user for conduct of a transaction initiated via mobile telephone
US20150186892A1 (en) Methods and systems for verifying a transaction
US20150088760A1 (en) Automatic injection of security confirmation
CN104065639A (zh) 银行卡的绑定方法及系统
US20130312073A1 (en) Methods and systems for authentication of multiple sign-in accounts
CN109035536A (zh) 访客系统及其实现方法、实现设备及可读存储介质
US10719844B2 (en) Service processing method, terminal and server
CN112950219B (zh) 支付处理方法和系统
CN106778290A (zh) 一种基于微信平台的应用软件验证方法和系统
EP3928488A1 (en) System and apparatus for providing authenticable electronic communication
US10270771B1 (en) Mid-session live user authentication
CN104079527A (zh) 一种信息处理方法及电子设备
US10129266B2 (en) Identity information systems and methods
US10667128B1 (en) Techniques for call authentication
CN111669744A (zh) 信息处理方法、装置和电子设备
CN109525485A (zh) 一种留言方法及终端设备
US11816674B2 (en) Methods, mediums, and systems for document authorization
US20200242712A1 (en) Method, apparatus and system for self-service contract for mobile payments
CN116057892A (zh) 经由短程收发器进行经验证的消息收发的系统和方法
CN109801050B (zh) 一种用于在线商城的移动支付sdk和支付方法
CN106936840B (zh) 一种信息提示方法及装置
CN102542696A (zh) 安全性信息交互系统及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20806321

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20806321

Country of ref document: EP

Kind code of ref document: A1