Payment method and apparatus

Abstract

Provided in one or multiple embodiments of the present disclosure are a payment method and apparatus. In the method, a service platform can receive a first payment request sent by a client and, when the first payment request does not comprise a payment amount and a payment account is provided with a voice payment mode, push first interface information to the client, so that the client displays a payment interface containing a voice input control; then, on the basis of the voice input control, the client can receive first voice information input by a user and send same to the service platform; then, the service platform can determine the payment amount on the basis of the first voice information, and push second interface information to the client, so that the client announces the payment amount, prompts the user to confirm, and sends to the service platform first confirmation information confirmed by the user; and then, on the basis of the first voice information, an identifier of the payment account and an identifier of a receiving account, the service platform can perform a payment operation.

Description

Payment method and device TECHNICAL FIELD

[0001] One or more embodiments of the present disclosure relate to the technical field of electronic payment, and in particular to a payment method and device. BACKGROUND

[0002] With the development of electronic payment technology, more and more users choose to use electronic payment to make payments. For example, a user can pay a merchant by scanning the electronic payment code of the merchant. However, after scanning the electronic payment code of the merchant, the user usually needs to manually input the payment amount and the payment password, and then the payment can be completed. In this process, for visually impaired users, the input of the payment amount and the payment password is difficult, and personal information is easily leaked. Therefore, a more convenient and secure payment method is needed to improve the payment experience of visually impaired users. SUMMARY

[0003] In order to improve the convenience and security of electronic payment and thus improve the payment experience of visually impaired users, one or more embodiments of the present disclosure provide a payment method and device.

[0004] In a first aspect, one or more embodiments of the present disclosure provide a payment method, which includes: receiving a first payment request sent by a user terminal; the first payment request is a payment request triggered by the user terminal by scanning a payment electronic code of a collection account, and includes an identifier of a payment account and an identifier of the collection account; in the case that the first payment request does not include a payment amount, determining at least one payment method set by the payment account based on the identifier of the payment account; in the case that the at least one payment method includes a voice payment method, pushing first interface information to the user terminal, so that the user terminal displays a payment interface including a voice input control based on the first interface information; determining a payment amount based on first voice information sent by the user terminal; the first voice information is voice payment information input by the user terminal through the voice input control; pushing second interface information containing the payment amount to the user terminal, so that the user terminal displays a confirmation interface including the payment amount and a confirmation control based on the second interface information and voice broadcasts the payment amount; after receiving first confirmation information sent by the user terminal, performing a payment operation based on the first voice information, the identifier of the payment account and the identifier of the collection account; the first confirmation information is payment confirmation information generated by the user terminal after the confirmation control is triggered.

[0005] In a possible implementation manner, the payment operation is performed based on the first voice information, the identifier of the payment account, and the identifier of the payment account, and includes: obtaining a first voiceprint feature from a subscription system of the service platform based on the identifier of the payment account; the first voiceprint feature is a voiceprint feature stored in the subscription system and corresponding to the identifier of the payment account; obtaining a second voiceprint feature from the first voice information; in a case where the first voiceprint feature matches the second voiceprint feature, deducting the payment amount from the payment account based on the identifier of the payment account, and transferring the payment amount to the payment account based on the identifier of the payment account, to complete the payment.

[0006] In a possible implementation manner, in a case where the first voiceprint feature matches the second voiceprint feature, the payment amount is deducted from the payment account based on the identifier of the payment account, and the payment amount is transferred to the payment account based on the identifier of the payment account, and includes: in a case where the first voiceprint feature matches the second voiceprint feature, determining whether the payment amount is less than or equal to a preset amount threshold; in a case where the payment amount is less than or equal to the preset amount threshold, deducting the payment amount from the payment account based on the identifier of the payment account, and transferring the payment amount to the payment account based on the identifier of the payment account.

[0007] In a possible implementation manner, the method further includes: in a case where the payment amount is greater than the preset amount threshold, pushing a payment failure prompt information to the user end, so that the user end voice broadcasts a payment failure and an excess prompt based on the payment failure prompt information.

[0008] In a possible implementation manner, the method further includes: receiving a subscription request sent by the user end; the subscription request includes the identifier of the payment account and information of a voice payment method; pushing subscription data corresponding to the voice payment method to the user end, so that the user end voice broadcasts a payment rule corresponding to the voice payment method based on the subscription data and displays a subscription interface including an agreement control; after receiving second confirmation information sent by the user end, pushing voiceprint extraction information to the user end, so that the user end displays reading content based on the voiceprint extraction information and obtains second voice information of a user reading the reading content; the second confirmation information is subscription confirmation information generated by the user end after the agreement control is triggered; after receiving the second voice information sent by the user end, extracting a first voiceprint feature from the second voice information; storing the first voiceprint feature in a subscription system of the service platform and corresponding to the identifier of the payment account.

[0009] In a possible implementation, the method further includes: pushing, to the user terminal, third interface information including a plurality of alternative amounts, so that the user terminal displays an amount confirmation interface including the plurality of alternative amounts based on the third interface information and voice broadcasts the plurality of alternative amounts; determining, after receiving third confirmation information sent by the user terminal, a target amount included in the third confirmation information as a preset amount threshold; the third confirmation information is confirmation information generated by the user terminal after receiving a selection operation of the user on the target amount; the target amount is an alternative amount selected from the plurality of alternative amounts; and storing the preset amount threshold and the identifier of the payment account in the signing system in correspondence.

[0010] In a possible implementation, the method further includes: generating a payment record and a collection record; sending the payment record to the user terminal; and sending the collection record to a terminal of the collection account.

[0011] In a second aspect, one or more embodiments of the present disclosure further provide a payment device, which includes: a first receiving module configured to receive a first payment request sent by a user terminal; the first payment request is a payment request triggered by the user terminal by scanning a payment electronic code of a collection account, and includes an identifier of a payment account and an identifier of the collection account; a first determining module configured to, in a case where the first payment request does not include a payment amount, determine at least one payment method set by the payment account based on the identifier of the payment account; a first pushing module configured to, in a case where the at least one payment method includes a voice payment method, push, to the user terminal, first interface information, so that the user terminal displays a payment interface including a voice input control based on the first interface information; a second determining module configured to determine a payment amount based on first voice information sent by the user terminal; the first voice information is voice payment information input by the user and received by the user terminal through the voice input control; a second pushing module configured to push, to the user terminal, second interface information including the payment amount, so that the user terminal displays a confirmation interface including the payment amount and a confirmation control based on the second interface information and voice broadcasts the payment amount; and a payment module configured to, after receiving first confirmation information sent by the user terminal, perform a payment operation based on the first voice information, the identifier of the payment account, and the identifier of the collection account; the first confirmation information is payment confirmation information generated by the user terminal after the confirmation control is triggered.

[0012] In a possible implementation, the payment module is configured to perform a payment operation based on the first voice information, the identifier of the payment account, and the identifier of the receiving account, specifically, the payment module is configured to: obtain a first voiceprint feature from a subscription system of the service platform based on the identifier of the payment account, the first voiceprint feature being a voiceprint feature corresponding to the identifier of the payment account and stored in the subscription system; obtain a second voiceprint feature from the first voice information; and in a case where the first voiceprint feature matches the second voiceprint feature, deduct the payment amount from the payment account based on the identifier of the payment account, and transfer the payment amount to the receiving account based on the identifier of the receiving account, to complete the payment.

[0013] In a possible implementation, the payment module is configured to, in a case where the first voiceprint feature matches the second voiceprint feature, deduct the payment amount from the payment account based on the identifier of the payment account, and transfer the payment amount to the receiving account based on the identifier of the receiving account, specifically, the payment module is configured to: in a case where the first voiceprint feature matches the second voiceprint feature, determine whether the payment amount is less than or equal to a preset amount threshold; and in a case where the payment amount is less than or equal to the preset amount threshold, deduct the payment amount from the payment account based on the identifier of the payment account, and transfer the payment amount to the receiving account based on the identifier of the receiving account.

[0014] In a possible implementation, the apparatus further includes a third pushing module configured to, in a case where the payment amount is greater than the preset amount threshold, push, to the user side, prompt information of payment failure, to enable the user side to voice broadcast a reminder of payment failure and excess based on the prompt information of payment failure.

[0015] In a possible implementation, the apparatus further includes: a second receiving module, configured to receive a subscription request sent by the user terminal; the subscription request includes identification of the payment account and information of the voice payment method; a fourth pushing module, configured to push, to the user terminal, subscription data corresponding to the voice payment method, so that the user terminal voice broadcasts payment rules corresponding to the voice payment method based on the subscription data and displays a subscription interface including an agreement control; a fifth pushing module, configured to, after receiving second confirmation information sent by the user terminal, push, to the user terminal, voiceprint extraction information, so that the user terminal displays reading content based on the voiceprint extraction information and acquires second voice information of the user reading the reading content; the second confirmation information is subscription confirmation information generated by the user terminal after the agreement control is triggered; an extraction module, configured to, after receiving the second voice information sent by the user terminal, extract first voiceprint features from the second voice information; and a first storage module, configured to store the first voiceprint features and the identification of the payment account in the subscription system of the service platform.

[0016] In a possible implementation, the apparatus further includes: a sixth pushing module, configured to push, to the user terminal, third interface information including a plurality of alternative amounts, so that the user terminal displays an amount confirmation interface including the plurality of alternative amounts based on the third interface information and voice broadcasts the plurality of alternative amounts; a third determining module, configured to, after receiving third confirmation information sent by the user terminal, determine a target amount included in the third confirmation information as a preset amount threshold; the third confirmation information is confirmation information generated by the user terminal after receiving a selection operation of the user on the target amount; the target amount is an alternative amount selected from the plurality of alternative amounts; and a second storage module, configured to store the preset amount threshold and the identification of the payment account in the subscription system.

[0017] In a possible implementation, the apparatus further includes: a generation module, configured to generate a payment record and a collection record; and a sending module, configured to send the payment record to the user terminal and send the collection record to a terminal of the collection account.

[0018] In a third aspect, one or more embodiments of the present disclosure further provide an electronic device including a memory and a processor; the memory is configured to store a computer program product; the processor is configured to execute the computer program product stored in the memory, and the computer program product, when executed, implements the payment method of the first aspect.

[0019] In a fourth aspect, the one or more embodiments of the present disclosure further provide a computer-readable storage medium storing computer program instructions, which, when executed, implement the payment method of the first aspect.

[0020] To sum up, in order to facilitate and secure payment and improve the usability of the payment in the field of barrier-free payment, the one or more embodiments of the present disclosure provide a payment method and device. In the method, after the payment device receives a first payment request triggered by the user end by scanning the payment electronic code of the payee account, the payment device can obtain the identifier of the payer account and the identifier of the payee account from the first payment request. Then, the payment device can determine at least one payment method set by the payer account based on the identifier of the payer account, without including the payment amount in the first payment request. Then, if the at least one payment method includes a voice payment method, the payment device can push first interface information including a voice input control to the user end, so that the user end displays a payment interface including the voice input control based on the first interface information. Then, the payment device can determine the payment amount based on the voice payment information input by the user through the voice input control and sent by the user end, and push second interface information including the payment amount to the user end, so that the user end displays a confirmation interface including the payment amount and a confirmation control based on the second interface information, and the payment device voice broadcasts the payment amount to the user. Then, after receiving the first confirmation information generated by the user end after the confirmation control is triggered, the payment device can perform a payment operation based on the first voice information, the identifier of the payer account, and the identifier of the payee account.

[0021] In this way, the payment device can determine whether the payment method set by the payer account includes a voice payment method based on the identifier of the payer account, and then push first interface information including a voice input control to the user end. After receiving the first voice information input by the user through the voice input control, the payment device automatically and quickly identifies the payment amount contained in the first voice information and pushes second interface information including the payment amount to the user end, i.e., without the user inputting the payment amount, effectively improving the convenience of payment. After receiving the first confirmation information sent by the user end, the payment device effectively implements a more secure payment method through the first voice information, thereby improving the usability of the voice payment method in the field of barrier-free payment and providing the user with a more intelligent and personalized payment experience with better applicability. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions of the one or more embodiments of the present disclosure, the drawings needed in the following embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the one or more embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creating any inventive labor.

[0023] FIG. 1 is a flowchart of a payment method according to one or more embodiments of the present disclosure;

[0024] FIG. 2 is a flowchart of a payment method according to one or more embodiments of the present disclosure;

[0025] FIG. 3 is a structural block diagram of a payment device according to one or more embodiments of the present disclosure;

[0026] FIG. 4 is a structural block diagram of an electronic device according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0027] The features and advantages of the one or more embodiments of the present disclosure will become more apparent from the detailed description in conjunction with the accompanying drawings.

[0028] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations. Although the various aspects of the embodiments are illustrated and described as though their parts were initially arranged in the illustrative configuration, the embodiments are not limited to the illustrative arrangements.

[0029] Furthermore, the technology features involved in the different implementations of the one or more embodiments of the present disclosure described below can be combined with each other as long as there is no conflict.

[0030] In an optional code scanning payment scenario, a user needs to scan a payment electronic code of a merchant through a terminal device (e.g., a mobile phone), and then manually input a payment amount and a payment password to complete the payment. For a visually impaired user, in this scenario, the user needs to constantly touch the electronic screen of the terminal device to input the payment amount and the payment password. In this process, the user may need to repeatedly touch the electronic screen for multiple times to correctly find the characters to be input, and in the process of the user touching the electronic screen, the terminal device may perform voice broadcast to assist the user in accurately finding the characters. In this way, the process is time-consuming, and the user's personal information may be disclosed, which poses a security risk of information disclosure, and the user's payment experience is poor.

[0031] To improve the convenience and security of payment and thus improve the payment experience of a visually impaired user, the one or more embodiments of the present disclosure provide a payment method and device. The embodiments of the payment method provided by the one or more embodiments of the present disclosure are described below.

[0032] Referring to FIG. 1, FIG. 1 is a flowchart of a payment method provided by one or more embodiments of the present disclosure. The method can be applied to a service platform, a server, or a management terminal, etc. In the following, the content of the embodiments will be introduced by taking the service platform as an example. As shown in FIG. 1, the method can include the following steps.

[0033] In step S102, a first payment request sent by a user terminal is received.

[0034] In an optional code scanning payment scenario, the user terminal can scan a payment electronic code (for example, a two-dimensional code of a merchant, etc.) of a payee account through a payment application (application, APP) to initiate a payment request to a corresponding service platform providing payment services. In one or more embodiments of the present disclosure, the payment request triggered by the user terminal by scanning the payment electronic code of the payee account is referred to as a first payment request. Optionally, the first payment request can include an identifier of a payer account and an identifier of the payee account. It should be understood that the first payment request can also include other information, which is not limited in one or more embodiments of the present disclosure.

[0035] Optionally, the identifier of the payer account is used to identify the payer account. In one or more embodiments of the present disclosure, the specific content of the identifier of the payer account and the specific content of the payer account are not limited. Optionally, the identifier of the payer account can be a payment account number (identity document, ID) assigned by the service platform to the payer user when the payer user registers on the service platform. For example, the payment account number assigned by the service platform to the payer user can be a string of numbers, letters, symbols, etc. Alternatively, the payment account number assigned by the service platform to the payer user can also be a combination of numbers, letters, and symbols. Optionally, the payer account can be a bank card account corresponding to the identifier of the payer account. Alternatively, the payer account can also be a payment account number assigned by the service platform to the payer user. It should be understood that the identifier of the payer account and the payer account can also be other contents, which are not listed one by one here.

[0036] Similarly, the identifier of the payee account is used to identify the payee account. In one or more embodiments of the present disclosure, the specific content of the identifier of the payee account and the specific content of the payee account are also not limited. Optionally, the identifier of the payee account can be a payment account number assigned by the service platform to the payee user when the payee user registers on the service platform. Optionally, the payment account number assigned by the service platform to the payee user can also be a string of numbers, letters, symbols, etc. Alternatively, the payment account number assigned by the service platform to the payee user can also be a combination of numbers, letters, and symbols. Optionally, the payee account can be a bank card account corresponding to the identifier of the payee account. Alternatively, the payee account can also be a payment account number assigned by the service platform to the payee user. It should be understood that the identifier of the payee account and the payee account can also be other contents, which are not listed one by one here.

[0037] Step S104: If the first payment request does not include a payment amount, determine at least one payment method set by the payment account based on the identifier of the payment account.

[0038] In one optional QR code payment scenario, after the user initiates a payment request, the request may include a payment amount. For example, in a scenario where the user scans the electronic payment code on a merchant's payment device, the payment request typically includes a payment amount. In this scenario, the user does not need to manually enter the payment amount. However, in another optional QR code payment scenario, after the user initiates a payment request, the request may not include a payment amount. For example, in a scenario where the user scans a merchant's paper QR code, the payment request typically does not include a payment amount. In this scenario, the user needs to manually enter the payment amount. Therefore, upon receiving a first payment request, the service platform first determines whether the first payment request includes a payment amount. If the first payment request does not include a payment amount, the service platform can determine at least one payment method set by the payment account based on the payment account's identifier. For cases where the first payment request includes a payment amount, the service platform's payment process is not limited in one or more embodiments of this disclosure.

[0039] Optionally, the payment account may include at least one payment method such as fingerprint payment, facial recognition payment, or password-free payment. Fingerprint payment refers to a payment method that uses the user's fingerprint for identity verification. Facial recognition payment refers to a payment method that uses the user's facial features for identity verification. Password-free payment refers to a payment method that does not require the user to enter a payment password. It should be understood that the payment account may also include other payment methods, which will not be listed here.

[0040] In practical applications, paying users can set at least one of the aforementioned payment methods in their payment app. The service platform can then associate the at least one payment method set by the paying user with the identifier of the paying account. Therefore, if the first payment request does not include a payment amount, the service platform can determine the at least one payment method set by the paying account based on the paying account's identifier.

[0041] Step S106: When at least one payment method includes voice payment, push first interface information to the user terminal so that the user terminal can display a payment interface including voice input controls based on the first interface information.

[0042] In one or more embodiments of this disclosure, voice payment refers to a payment method in which the amount is entered by voice and the identity is verified by voiceprint features.

[0043] In practical applications, users can set up (or register or activate) the voice payment method through their payment app before making a payment. Setting up the voice payment method can involve two stages: a contract signing stage and a voiceprint feature recording stage.

[0044] In one possible implementation, during the signing phase, the paying user can click the voice payment settings control in their payment app. Upon receiving this action, the user's app can send a signing request to the service platform. This request may include the payment account identifier and information about the voice payment method. After receiving the signing request, the service platform can push the signing data corresponding to the voice payment method to the user's app. This data allows the user to verbally announce the payment rules for the voice payment method and display a signing interface including an agreement control. In other words, the signing data corresponding to the voice payment method can include the payment rules and agreement control information, as well as instructions for verbally announcing the payment rules. Once the user receives the signing data from the service platform, they can verbally announce the payment rules and display a signing interface with an agreement control.

[0045] Optionally, the payment rules corresponding to the voice payment method may include user agreements, privacy policies, etc. It should be understood that the payment rules corresponding to the voice payment method may also include other content, and this disclosure does not limit this in one or more embodiments. Similarly, the contract data may also include other content, such as deduction order settings.

[0046] Through voice prompts on the user's device, paying users can understand the payment rules corresponding to the voice payment method. Furthermore, if the paying user agrees to abide by the payment rules, they can click the "agree" control on the signing interface. After receiving the trigger action of the "agree" control being clicked, the user's device can generate a signing confirmation message (hereinafter referred to as the second confirmation message), which the user can then send to the service platform. Upon receiving the second confirmation message from the user's device, the service platform can associate the payment account identifier with the voice payment method and proceed to the voiceprint feature recording stage.

[0047] During the voiceprint feature recording stage, the service platform can push voiceprint extraction information to the user's device. This voiceprint extraction information may include information about the content to be read aloud and instructions to obtain the audio information (hereinafter referred to as the second audio information) of the user reading the aforementioned content. The user's device can then display the content and obtain the second audio information of the user reading the content. Afterward, the user's device can send the second audio information to the service platform. Upon receiving the second audio information from the user's device, the service platform can extract the voiceprint features included in the second audio information, which are denoted as the first voiceprint feature. The service platform can then store the first voiceprint feature in its contract system, corresponding to the payment account identifier.

[0048] Optionally, since voice payment requires determining the payment amount and extracting voiceprint features based on the user's voice information, the content to be read aloud can be set to numbers, such as the numbers "0123456789". It should be understood that the content to be read aloud can also be set to other content, and this disclosure does not limit this in one or more embodiments.

[0049] Optionally, the number of times the user reads the aforementioned content aloud is not limited in one or more embodiments of this disclosure. That is, the second voice information obtained by the user may include a sound sample of the user reading the aforementioned content aloud once, or the second voice information may also include sound samples of the user reading the aforementioned content aloud multiple times.

[0050] However, since the obtained sound samples need to be processed when extracting the first voiceprint feature, if the sound sample is a single recording, it is insufficient to completely capture and represent the user's voice features. Moreover, a single recording may not cover the user's voice features under different environments, emotions, and pronunciation styles. Using multiple recordings of sound samples, the voiceprint model can have stronger adaptability and robustness, and the extracted first voiceprint feature can be more accurate. Furthermore, in one or more embodiments of this disclosure, the reading order of the aforementioned reading content by the user is not restricted.

[0051] For example, the user terminal can extract information based on voiceprint and first display a prompt message to read the number "0123456789" to prompt the paying user to read the aforementioned number. After obtaining the voice information of the user reading the number "0123456789", the prompt message to read the number "9876543210" is displayed again. After obtaining the voice information of the user reading "9876543210", the voice information obtained from the two readings is determined as the second voice information.

[0052] Furthermore, preset amount thresholds can be set for voice payment methods to limit the maximum amount that can be paid via voice payment. Based on this, in addition to storing the first voiceprint feature and the payment account identifier in the contract system, the service platform can also push third-party interface information, including multiple alternative amounts, to the user's device. After receiving the third-party interface information, the user's device can display a confirmation interface with multiple alternative amounts and verbally announce the aforementioned alternative amounts.

[0053] Optionally, the alternative amounts can be set according to the needs of the application scenario. For example, multiple alternative amounts may include 10, 30, 40, 100, etc.

[0054] Optionally, the credit limit confirmation interface may also display a custom control for credit limit settings, allowing payment users to input a preset amount threshold through the custom control.

[0055] The client can announce multiple alternative amounts to the paying user via voice broadcast. The paying user can then select one of these alternatives. Based on the user's selection, the client will use the chosen amount as the target amount and generate a third confirmation message including the target amount. The client can then send this third confirmation message to the service platform. Upon receiving the third confirmation message, the service platform can define the target amount (e.g., 100) as a preset amount threshold and store this threshold along with the paying account's identifier in the contract system. This facilitates subsequent checks during payment to ensure the payment amount does not exceed the preset threshold, thereby controlling the payment limit for voice payments and better protecting the paying user's account security.

[0056] After a paying user successfully sets up a voice payment method, the service platform's contract system can store the payment account's identifier and the corresponding voice payment method. Once the service platform determines that the payment account has set up at least one payment method, it can determine whether voice payment is included among these methods. If it is determined that the payment account has set up at least one payment method including voice payment, the service platform can push a first interface information to the user's device, allowing the user to display a payment interface including voice input controls based on this information.

[0057] Optionally, the first interface information may include information about the interface elements of the payment interface. For example, the first interface information may include information about the voice input control. When the service platform determines that at least one payment method set in the payment account includes voice payment, it may push the first interface information to the user's client. After receiving the first interface information, the user's client can display the payment interface based on the first interface information, and the payment interface displays the voice input control.

[0058] Optionally, the voice input control can be used by the user terminal to receive voice information input by the user. In practical applications, the paying user can continuously press the voice input control on the payment interface to input voice while continuously pressing the voice input control, and then stop pressing the voice input control after the voice input is completed. After receiving the user's start of pressing the voice input control, the user terminal begins recording the voice input by the user. Recording ends when the user stops pressing the voice input control, thus obtaining the voice information input by the user.

[0059] Optionally, the first interface information may also include information about the voiceprint management control, and correspondingly, the voiceprint management control may also be displayed on the payment interface. After the paying user clicks the voiceprint management control on the payment interface, the user terminal can generate a modification request based on the paying user's click operation to request a change to the voice payment method. The user terminal can send the modification request to the service platform. After receiving the modification request, the service platform can push fourth interface information to the user terminal. The fourth interface information may include information about the interface elements of the voiceprint management interface, such as information about deleting the voice payment method control and modifying the preset amount threshold control. After receiving the fourth interface information pushed by the service platform, the user terminal can display the voiceprint management interface, which may display interface elements such as the delete voice payment method control and the modify preset amount threshold control. The paying user can click the delete voice payment method control to trigger the user terminal to delete the voice payment method corresponding to the payment account identifier from the contract system. Similarly, the paying user can click the modify preset amount threshold control to trigger the user terminal to modify the preset amount threshold corresponding to the payment account identifier.

[0060] Optionally, the voiceprint management interface can also display other interface elements, such as a control to enable voice payment and the corresponding payment rules. This allows users to easily enable or disable voice payment and manage related payment functions, resulting in a better user experience.

[0061] It should be understood that the first interface information may also include information about other interface elements, such as information about a character input keyboard. Correspondingly, the user's payment interface may also display other interface elements, such as a character input keyboard. This disclosure does not impose limitations in one or more embodiments.

[0062] Step S108: Determine the payment amount based on the first voice information sent by the user terminal.

[0063] The first voice information is the voice payment information input by the user and received by the user terminal through the voice input control.

[0064] Based on the foregoing, after the service platform pushes the first interface information to the user's device, the user can display a payment interface including a voice input control based on this information. Furthermore, while the user is long-pressing the voice input control, the platform can record the user's voice payment information using a recording device. The user can then send this recorded voice payment information as the first voice message to the service platform. Upon receiving the first voice message from the user, the service platform can identify the payment amount contained within it.

[0065] Optionally, the recording device includes, but is not limited to, the microphone on the user's end. For example, when the user's voice payment information is received for the first time via the voice input control, it is necessary to determine whether to authorize the use of the microphone. For instance, an access permission box such as "Want to access your microphone?" can pop up on the user's interface. After receiving permission from the user, the user can receive the user's voice payment information via the voice input control.

[0066] Optionally, to identify the payment amount contained in the first voice information, Chinese / English voice recognition technology can be used to convert the first voice information into text format. Then, keywords related to the payment amount are extracted from the converted first voice information. Optionally, Natural Language Processing (NLP) technology can be used to recognize and extract keywords related to the payment amount from the converted first voice information, such as the payment amount "20". The extracted keywords can then be used to identify the payment amount using amount recognition technology. Converting the first voice information into text format using Natural Language Processing (NLP) technology can enhance the reliability and usability of voice payment methods and improve the user experience.

[0067] For example, monetary amount recognition technology can be implemented through regular expression matching, natural language processing technology, numerical recognition technology, etc. The appropriate recognition method can be selected according to different monetary amount expressions.

[0068] By analyzing a user's initial voice information and extracting the payment amount, the payment process can be simplified, eliminating the need for users to manually enter the amount. For visually impaired users, this not only improves the payment experience but also prevents information leakage during manual input, thus enhancing payment security.

[0069] Step S110: Push second interface information containing the payment amount to the user terminal, so that the user terminal can display a confirmation interface including the payment amount and confirmation control based on the second interface information and announce the payment amount by voice.

[0070] After recognizing the payment amount contained in the first voice message, to ensure the accuracy of the payment amount and to further improve the payment experience for visually impaired users, the service platform can also send a second interface message to the user's terminal. This second interface message can include information about the interface elements of the confirmation interface, such as the payment amount, confirmation controls, and instructions for the voice announcement of the payment amount. Upon receiving the second interface message, the user's terminal can display the confirmation interface, which shows the payment amount and confirmation controls. The user's terminal then announces the payment amount to the paying user to assist them in confirming its accuracy. After confirming the payment amount is accurate, the paying user can click the confirmation control to confirm. Upon receiving the user's confirmation, the user's terminal can generate payment confirmation information and send this information as the first confirmation message to the service platform.

[0071] Optionally, after receiving the second interface information containing the payment amount, the user can use speech synthesis technology to announce the payment amount aloud. That is, the payment amount can be used as input to call a speech synthesis model to generate a corresponding speech file, which is then passed as an audio source to an audio player for playback. Alternatively, the payment amount can also be announced to the paying user via the user's built-in monologue function. By pushing the payment amount to the user and announcing it aloud, the accuracy and security of the payment amount can be ensured.

[0072] Optionally, in addition to the payment amount and confirmation control information, the second interface may also include information about a cancellation control. Accordingly, a cancellation control may be displayed on the confirmation interface. The cancellation control can be used to cancel the current payment operation and re-enter the payment amount. The cancellation control is typically placed in a prominent position on the confirmation interface so that the paying user can easily find and use it. For example, the cancellation control can be a cancellation button or a cancellation control with an "X". Setting up a cancellation control helps improve the paying user's sense of control and satisfaction with the payment process and reduces payment security issues caused by operational errors.

[0073] In other words, after pushing the second interface information to the user's terminal, a cancellation control can also be displayed on the confirmation interface based on the second interface information. After receiving the user's click on the cancellation control, the user's terminal can send a cancellation request to the service platform. After receiving the cancellation request from the user's terminal, the service platform can re-push the first interface information to the user's terminal, so that the user's terminal can re-display the payment interface including the voice input control based on the first interface information, and re-receive the user's voice payment information for subsequent confirmation. The specific implementation method can be referred to the content of the aforementioned embodiments, and will not be repeated here.

[0074] It should be understood that the second interface information may also include information about other interface elements, and this is not limited in one or more embodiments of this disclosure.

[0075] Step S112: After receiving the first confirmation information sent by the user terminal, perform the payment operation based on the first voice information, the identifier of the payment account and the identifier of the receiving account.

[0076] Based on the foregoing, after the user clicks the confirmation control, the client can generate payment confirmation information and send this information as the first confirmation to the service platform. In other words, the first confirmation is the payment confirmation information generated by the client after the confirmation control is triggered.

[0077] Optionally, before making a payment, the service platform can also verify the identity of the paying user's current payment operation based on the identifier of the paying account.

[0078] Referring to Figure 2, Figure 2 is a flowchart illustrating a method for performing a payment operation based on first voice information, an identifier of a payment account, and an identifier of a receiving account, according to one or more embodiments of this disclosure. As shown in Figure 2, the method may include the following steps.

[0079] Step S202: Based on the identifier of the payment account, obtain the first voiceprint feature from the service platform's signing system.

[0080] The first voiceprint feature is the voiceprint feature stored in the signing system that corresponds to the identifier of the payment account.

[0081] Step S204: Obtain the second voiceprint feature from the first voice information.

[0082] After receiving the first voice message from the user, the service platform can determine the payment amount from the first voice message and extract voiceprint features from it, using these extracted voiceprint features as the second voiceprint features. Optionally, the second voiceprint features may include information such as tone and frequency.

[0083] Step S206: If the first voiceprint feature matches the second voiceprint feature, the payment amount is deducted from the payment account based on the identifier of the payment account, and the payment amount is transferred to the receiving account based on the identifier of the receiving account, thus completing the payment.

[0084] Optionally, the service platform can employ a vector similarity matching algorithm to calculate the similarity between the first voiceprint feature and the second voiceprint feature, thereby determining whether the first voiceprint feature and the second voiceprint feature match. The similarity matching algorithm may include algorithms such as cosine similarity or Euclidean distance.

[0085] Optionally, if the similarity between the second voiceprint feature and the first voiceprint feature is greater than or equal to a preset similarity threshold, then the first voiceprint feature and the second voiceprint feature are considered to match, or the first voiceprint feature and the second voiceprint feature may be considered to have successfully matched. Conversely, if the similarity between the first voiceprint feature and the second voiceprint feature is less than the preset similarity threshold, then the first voiceprint feature and the second voiceprint feature are considered to not match, or the first voiceprint feature and the second voiceprint feature may be considered to have failed to match. In this case, the service platform may send an authentication failure message to the user and prompt the user to authenticate using other authentication methods; no restrictions are placed on other authentication methods here.

[0086] In one possible implementation, if the first voiceprint feature matches the second voiceprint feature, the service platform can also determine whether the payment amount is less than or equal to a preset amount threshold; if the payment amount is less than or equal to the preset amount threshold, the payment amount is deducted from the payment account based on the identifier of the payment account, and the payment amount is transferred to the receiving account based on the identifier of the receiving account.

[0087] In other words, in addition to comparing the second voiceprint feature with the first voiceprint feature, the payment amount is also compared with a preset amount threshold. This way, even if identity verification is successful, payment will only be completed if the amount is less than or equal to the preset threshold, further protecting the user's funds and preventing significant financial losses.

[0088] In one possible implementation, if the payment amount exceeds a preset threshold, the service platform can push a payment failure notification to the user's device. The user can then receive a voice message announcing the payment failure and exceeding the limit. This effectively prevents unexpected expenses, protects user rights, and improves user satisfaction.

[0089] In one possible implementation, after deducting the payment amount from the payment account based on the payment account identifier and transferring the payment amount to the receiving account based on the receiving account identifier, the service platform can also generate payment records and receiving records, and send the payment records to the user's terminal and the receiving records to the receiving account's terminal.

[0090] Generating payment records after payment is completed helps payers manage their accounts, allowing them to record detailed payment information, including payment time, amount, and payee, thus facilitating the tracking and management of their spending. Similarly, receiving records help payees track and manage their receiving activities.

[0091] In the payment method provided by one or more embodiments of this disclosure, after receiving a first payment request sent by a user terminal, the service platform can determine whether the first payment request includes a payment amount. If the first payment request does not include a payment amount, it can determine whether the at least one payment method set by the payment account included in the first payment request includes a voice payment method. If the at least one payment method set by the payment account includes a voice payment method, it pushes first interface information including a voice input control to the user terminal. After receiving the first voice information received by the user terminal based on the user input control, it can determine the payment amount based on the first voice information and extract the second voiceprint feature in the first voice information. Then, it can push second interface information including the payment amount and a confirmation control to the user terminal. After receiving the first confirmation information generated after the confirmation control is triggered by the user terminal, it can verify and match the second voiceprint feature in the first voice information with the first voiceprint feature stored in the contract system corresponding to the payment account identifier. If the match is successful and the payment amount is less than or equal to a preset amount threshold, the payment operation can be performed to complete the payment. In this way, once the voice payment method is set up, payments can be made via voice input without the need to manually enter the payment amount and password. This effectively improves the convenience and security of payments for visually impaired users, resulting in a better payment experience.

[0092] It is understood that the above embodiments are merely examples, and modifications can be made to the above embodiments in actual implementation. Those skilled in the art will understand that any modifications to the above embodiments that do not require creative effort fall within the protection scope of one or more embodiments of this disclosure, and will not be described in detail in the embodiments.

[0093] Based on the same inventive concept, one or more embodiments of this disclosure also provide a payment device. Since the principle of the payment device in solving the problem is similar to that of the aforementioned payment method, the implementation of the payment device can refer to the implementation of the aforementioned payment method, and the repeated parts will not be described again.

[0094] Referring to Figure 3, which is a structural block diagram of a payment device provided in one or more embodiments of this disclosure, the payment device 300 may include: a first receiving module 301, a first determining module 302, a first pushing module 303, a second determining module 304, a second pushing module 305, and a payment module 306.

[0095] The first receiving module 301 can be used to receive a first payment request sent by the user terminal; the first payment request is a payment request triggered by the user terminal by scanning the electronic payment code of the receiving account, including the identifier of the paying account and the identifier of the receiving account.

[0096] The first determining module 302 can be used to determine at least one payment method set by the payment account based on the identifier of the payment account when the payment amount is not included in the first payment request.

[0097] The first push module 303 can be used to push first interface information to the user terminal when at least one payment method includes voice payment, so that the user terminal can display a payment interface including voice input controls based on the first interface information.

[0098] The second determining module 304 can be used to determine the payment amount based on the first voice information sent by the user terminal; the first voice information is the voice payment information input by the user terminal through the voice input control.

[0099] The second push module 305 can be used to push second interface information containing the payment amount to the user terminal, so that the user terminal can display a confirmation interface including the payment amount and confirmation control based on the second interface information and announce the payment amount by voice.

[0100] The payment module 306 can be used to perform a payment operation based on the first voice information, the identifier of the payment account, and the identifier of the receiving account after receiving the first confirmation information sent by the user terminal; the first confirmation information is the payment confirmation information generated by the user terminal after the confirmation control is triggered.

[0101] In one possible implementation, the payment module 306 is used to perform a payment operation based on the first voice information, the identifier of the payment account, and the identifier of the receiving account. Specifically, the payment module 306 is used to: obtain a first voiceprint feature from the service platform's contract system based on the identifier of the payment account; the first voiceprint feature is a voiceprint feature stored in the contract system corresponding to the identifier of the payment account; obtain a second voiceprint feature from the first voice information; if the first voiceprint feature matches the second voiceprint feature, deduct the payment amount from the payment account based on the identifier of the payment account, and transfer the payment amount to the receiving account based on the identifier of the receiving account, thereby completing the payment.

[0102] In one possible implementation, the payment module 306 is used to deduct the payment amount from the payment account based on the identifier of the payment account when the first voiceprint feature matches the second voiceprint feature, and to transfer the payment amount to the receiving account based on the identifier of the receiving account. Specifically, the payment module 306 is used to: determine whether the payment amount is less than or equal to a preset amount threshold when the first voiceprint feature matches the second voiceprint feature; and deduct the payment amount from the payment account based on the identifier of the payment account and transfer the payment amount to the receiving account based on the identifier of the receiving account when the payment amount is less than or equal to the preset amount threshold.

[0103] In one possible implementation, the payment device 300 further includes a third push module, used to push a payment failure notification to the user terminal when the payment amount exceeds a preset threshold, so that the user terminal can verbally announce the payment failure and the excess amount reminder based on the payment failure notification.

[0104] In one possible implementation, the payment device 300 further includes: a second receiving module for receiving a contract request sent by a user terminal; the contract request includes the identifier of the payment account and information about the voice payment method; a fourth push module for pushing contract data corresponding to the voice payment method to the user terminal, so that the user terminal can read out the payment rules corresponding to the voice payment method based on the contract data and display a contract interface including an agreement control; a fifth push module for pushing voiceprint extraction information to the user terminal after receiving the second confirmation information sent by the user terminal, so that the user terminal can display the reading content based on the voiceprint extraction information and obtain the second voice information of the user reading the content; the second confirmation information is the contract confirmation information generated by the user terminal after the agreement control is triggered; an extraction module for extracting a first voiceprint feature from the second voice information after receiving the second voice information sent by the user terminal; and a first storage module for storing the first voiceprint feature and the identifier of the payment account in the contract system of the service platform.

[0105] In one possible implementation, the payment device 300 further includes: a sixth push module, used to push third interface information including multiple alternative amounts to the user terminal, so that the user terminal can display a limit confirmation interface including multiple alternative amounts and announce multiple alternative amounts via voice based on the third interface information; a third determination module, used to determine the target amount included in the third confirmation information as a preset amount threshold after receiving the third confirmation information sent by the user terminal; the third confirmation information is the confirmation information generated by the user terminal after receiving the user's selection operation on the target amount; the target amount is the selected alternative amount among multiple alternative amounts; and a second storage module, used to store the preset amount threshold and the identifier of the payment account in the contract system.

[0106] In one possible implementation, the payment device 300 further includes: a generation module for generating payment records and receipt records; a sending module for sending payment records to the user terminal; and sending receipt records to the terminal of the receiving account.

[0107] Referring to Figure 4, which is a structural block diagram of an electronic device provided in one or more embodiments of this disclosure, the electronic device 400 may include a processor 401 and a memory 402; the memory 402 may be coupled to the processor 401. It is worth noting that Figure 4 is exemplary; other types of structures may be used to supplement or replace this structure to achieve telecommunications functions or other functions.

[0108] In one possible implementation, the functionality of the payment device 300 can be integrated into the processor 401. The processor 401 can be configured to perform the following operations: receive alarm information regarding a prize activity for a first activity entity in an online venue; the first activity entity is any activity entity participating in prize distribution in the online venue; the alarm information includes an activity identifier of the first activity entity; based on the activity identifier, obtain the remaining prize budget of the first activity entity; obtain at least one first monitoring message obtained by monitoring each activity node of the prize activity, and at least one second monitoring message obtained by monitoring the activity monitoring equipment and activity management equipment of each activity node; determine a first fault category based on the remaining prize budget, the at least one first monitoring message, and the at least one second monitoring message; and perform fault handling on the prize configuration of the first activity entity in the online venue based on a first processing rule; the first processing rule refers to the fault handling rule corresponding to the first fault category among the fault handling rules configured for the first activity entity.

[0109] In another possible implementation, the payment device 300 can be configured separately from the processor 401. For example, the payment device 300 can be configured as a chip connected to the processor 401, and the payment can be implemented through the control of the processor 401.

[0110] In addition, in some alternative implementations, the electronic device 400 may also include: a communication module, an input unit, an audio processor, a display, a power supply, etc. It is worth noting that the electronic device 400 is not necessarily required to include all the components shown in Figure 4; furthermore, the electronic device 400 may also include components not shown in Figure 4, which can be found in related technologies.

[0111] In some alternative implementations, the processor 401, sometimes also referred to as a controller or operating control, may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of the electronic device 400.

[0112] The memory 402 may be, for example, one or more of a cache, flash memory, hard drive, removable medium, volatile memory, non-volatile memory, or other suitable device. It may store the aforementioned information related to the payment device 300, and may also store a program for executing that information. The processor 401 may execute the program stored in the memory 402 to perform information storage or processing, etc.

[0113] An input unit can provide input to the processor 401. This input unit may be, for example, a button or touch input device. A power supply can be used to provide power to the electronic device 400. A display can be used to display images and text, etc. This display may be, for example, an LCD display, but is not limited to this.

[0114] Memory 402 can be a solid-state memory, such as read-only memory (ROM), random access memory (RAM), SIM card, etc. It can also be a memory that retains information even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROM, etc. Memory 402 can also be some other type of device. Memory 402 includes buffer memory (sometimes referred to as a buffer). Memory 402 may include an application / function storage unit for storing application programs and function programs or processes for executing the operation of electronic device 400 via processor 401.

[0115] The memory 402 may also include a data storage unit for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit of the memory 402 may include various drivers for the computer device for communication functions and / or for performing other functions of the computer device (such as messaging applications, address book applications, etc.).

[0116] The communication module is a transmitter / receiver that sends and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor 401 to provide input signals and receive output signals, which can be the same as in a conventional mobile communication terminal.

[0117] Based on different communication technologies, multiple communication modules can be configured in the same computer device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) is also coupled to a speaker and microphone via an audio processor to provide audio output through the speaker and receive audio input from the microphone, thereby enabling typical telecommunications functions. The audio processor may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor is coupled to processor 401, enabling on-device recording via the microphone and on-device playback of stored sound via the speakers.

[0118] This disclosure provides one or more embodiments of a computer-readable storage medium capable of implementing all steps of the payment method in the above embodiments. The computer-readable storage medium stores a computer program that, when executed by a processor, implements all steps of the payment method in the above embodiments. For example, when the processor executes the computer program, it implements the following steps: receiving alarm information for a prize activity of a first activity subject in an online venue; the first activity subject is any activity subject participating in prize distribution in the online venue; the alarm information includes an activity identifier of the first activity subject; based on the activity identifier, obtaining the remaining prize budget of the first activity subject; obtaining at least one first monitoring message obtained by monitoring each activity node of the prize activity, and at least one second monitoring message obtained by monitoring the activity monitoring device and activity management device of each activity node; determining a first fault category based on the remaining prize budget, the at least one first monitoring message, and the at least one second monitoring message; and performing fault handling on the prize configuration of the first activity subject in the online venue based on a first processing rule; the first processing rule refers to the fault handling rule corresponding to the first fault category among the fault handling rules configured for the first activity subject.

[0119] While this disclosure provides one or more embodiments of the method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-inventive labor. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only possible execution order. In actual device or client product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment).

[0120] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus (systems), or computer program products. Therefore, embodiments of this disclosure can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, one or more embodiments of this disclosure can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0121] This disclosure describes one or more embodiments of a method, apparatus (system), and computer program product according to one or more embodiments of this disclosure with reference to flowchart illustrations and / or block diagrams. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, 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 one or more flowchart illustrations and / or one or more block diagrams.

[0122] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0123] 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 one or more flowcharts and / or one or more block diagrams.

[0124] The various embodiments in this disclosure are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and system embodiments are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0125] In this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Those skilled in the art will understand the specific meaning of the above terms in one or more embodiments of this disclosure, depending on the specific circumstances.

[0126] It should be noted that, unless otherwise specified, one or more embodiments of this disclosure and the features thereof can be combined with each other. This disclosure is not limited to any single aspect, nor to any single embodiment, nor to any combination and / or substitution of such aspects and / or embodiments. Furthermore, each aspect and / or embodiment of one or more embodiments of this disclosure can be used alone or in combination with one or more other aspects and / or embodiments thereof.

[0127] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of one or more embodiments of this disclosure, and are not intended to limit them. Although one or more embodiments of this disclosure have been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of one or more embodiments of this disclosure, and they should all be covered within the scope of the claims and description of one or more embodiments of this disclosure.

[0128] The foregoing description of one or more embodiments of this disclosure, in conjunction with optional implementation methods, is merely exemplary and illustrative. Various substitutions and modifications can be made to one or more embodiments of this disclosure, all of which fall within the protection scope of the one or more embodiments of this disclosure.

Claims

1. A payment method for a service platform, the method comprising: receiving a first payment request sent by a user terminal; the first payment request being a payment request triggered by the user terminal by scanning a payment electronic code of a payee account, and comprising an identifier of a payer account and an identifier of the payee account; in a case where the first payment request does not comprise a payment amount, determining at least one payment method set by the payer account based on the identifier of the payer account; in a case where the at least one payment method comprises a voice payment method, pushing first interface information to the user terminal, so that the user terminal displays a payment interface comprising a voice input control based on the first interface information; determining a payment amount based on first voice information sent by the user terminal; the first voice information being voice payment information input by the user terminal through the voice input control; pushing second interface information comprising the payment amount to the user terminal, so that the user terminal displays a confirmation interface comprising the payment amount and a confirmation control based on the second interface information and voice broadcasts the payment amount; after receiving first confirmation information sent by the user terminal, performing a payment operation based on the first voice information, the identifier of the payer account and the identifier of the payee account; the first confirmation information being payment confirmation information generated by the user terminal after the confirmation control is triggered.

2. The method of claim 1, wherein, performing a payment operation based on the first voice information, the identifier of the payer account and the identifier of the payee account, comprising: obtaining a first voiceprint feature from a subscription system of the service platform based on the identifier of the payer account; the first voiceprint feature being a voiceprint feature stored in the subscription system corresponding to the identifier of the payer account; obtaining a second voiceprint feature from the first voice information; in a case where the first voiceprint feature matches the second voiceprint feature, deducting the payment amount from the payer account based on the identifier of the payer account, and transferring the payment amount to the payee account based on the identifier of the payee account, to complete the payment.

3. The method of claim 2, wherein, in a case where the first voiceprint feature matches the second voiceprint feature, deducting the payment amount from the payer account based on the identifier of the payer account, and transferring the payment amount to the payee account based on the identifier of the payee account, comprising: in a case where the first voiceprint feature matches the second voiceprint feature, determining whether the payment amount is less than or equal to a preset amount threshold; in a case where the payment amount is less than or equal to the preset amount threshold, deducting the payment amount from the payer account based on the identifier of the payer account, and transferring the payment amount to the payee account based on the identifier of the payee account.

4. The method of claim 3, further comprising: in a case where the payment amount is greater than the preset amount threshold, pushing prompt information of a payment failure to the user terminal, so that the user terminal voice broadcasts a reminder of the payment failure and an excess based on the prompt information of the payment failure.

5. The method of claim 1, further comprising: receiving a subscription request sent by the user terminal; the subscription request comprises an identifier of the payment account and information of the voice payment method; pushing, to the user terminal, subscription data corresponding to the voice payment method, so that the user terminal plays payment rules corresponding to the voice payment method based on the subscription data and displays a subscription interface comprising an agreement control; after receiving second confirmation information sent by the user terminal, associating the identifier of the payment account with the voice payment method, and pushing, to the user terminal, voiceprint extraction information, so that the user terminal displays reading content based on the voiceprint extraction information and acquires second voice information of the user reading the reading content; the second confirmation information is subscription confirmation information generated by the user terminal after the agreement control is triggered; after receiving the second voice information sent by the user terminal, extracting first voiceprint features from the second voice information; storing the first voiceprint features corresponding to the identifier of the payment account in a subscription system of the service platform.

6. The method of claim 5, further comprising: pushing, to the user terminal, third interface information comprising a plurality of alternative amounts, so that the user terminal displays an amount confirmation interface comprising the plurality of alternative amounts based on the third interface information and plays the plurality of alternative amounts; after receiving third confirmation information sent by the user terminal, determining a target amount included in the third confirmation information as a preset amount threshold; the third confirmation information is confirmation information generated by the user terminal after receiving a selection operation of the user on the target amount; the target amount is a selected alternative amount in the plurality of alternative amounts; storing the preset amount threshold corresponding to the identifier of the payment account in the subscription system.

7. The method of claim 1, further comprising: generating a payment record and a collection record; sending, to the user terminal, the payment record; sending, to a terminal of the collection account, the collection record.

8. A payment device for a service platform, the device comprising: a first receiving module configured to receive a first payment request sent by a user terminal; the first payment request is a payment request triggered by the user terminal by scanning a payment electronic code of a collection account, and comprises an identifier of a payment account and an identifier of the collection account; a first determining module configured to, in a case where the first payment request does not comprise a payment amount, determine at least one payment method set by the payment account based on the identifier of the payment account; a first pushing module configured to, in a case where the at least one payment method comprises a voice payment method, push, to the user terminal, first interface information, so that the user terminal displays a payment interface comprising a voice input control based on the first interface information; a second determining module configured to determine a payment amount based on first voice information sent by the user terminal; the first voice information is voice payment information input by the user through the voice input control. The second pushing module is configured to push second interface information containing the payment amount to the user terminal, so that the user terminal displays a confirmation interface including the payment amount and a confirmation control based on the second interface information and voice broadcasts the payment amount. The payment module is configured to, after receiving first confirmation information sent by the user terminal, perform a payment operation based on the first voice information, the identifier of the payment account, and the identifier of the payment account. The first confirmation information is payment confirmation information generated by the user terminal after the confirmation control is triggered.

9. The apparatus of claim 8, wherein, The payment module is configured to, based on the first voice information, the identifier of the payment account, and the identifier of the payment account, perform a payment operation, specifically as follows: Based on the identifier of the payment account, the payment module is configured to acquire a first voiceprint feature from a subscription system of the service platform. The first voiceprint feature is a voiceprint feature stored in the subscription system corresponding to the identifier of the payment account. The payment module is configured to acquire a second voiceprint feature from the first voice information. In a case where the first voiceprint feature matches the second voiceprint feature, the payment module is configured to, based on the identifier of the payment account, deduct the payment amount from the payment account, and based on the identifier of the payment account, transfer the payment amount to the payment account, to complete the payment.

10. The apparatus of claim 9, wherein, The payment module is configured to, in a case where the first voiceprint feature matches the second voiceprint feature, based on the identifier of the payment account, deduct the payment amount from the payment account, and based on the identifier of the payment account, transfer the payment amount to the payment account, specifically as follows: In a case where the first voiceprint feature matches the second voiceprint feature, the payment module is configured to determine whether the payment amount is less than or equal to a preset amount threshold. In a case where the payment amount is less than or equal to the preset amount threshold, the payment module is configured to, based on the identifier of the payment account, deduct the payment amount from the payment account, and based on the identifier of the payment account, transfer the payment amount to the payment account.

11. The apparatus of claim 10, further comprising: The third pushing module is configured to, in a case where the payment amount is greater than the preset amount threshold, push a payment failure prompt to the user terminal, so that the user terminal voice broadcasts a payment failure and an excess reminder based on the payment failure prompt.

12. The apparatus of claim 8, further comprising: The second receiving module is configured to receive a subscription request sent by the user terminal. The subscription request includes the identifier of the payment account and information of a voice payment method. The fourth pushing module is configured to push subscription data corresponding to the voice payment method to the user terminal, so that the user terminal voice broadcasts payment rules corresponding to the voice payment method based on the subscription data and displays a subscription interface including an agreement control. The fifth pushing module is configured to push, after receiving the second confirmation information sent by the user terminal, voiceprint extraction information to the user terminal, so that the user terminal displays reading content based on the voiceprint extraction information and acquires second voice information of the user reading the reading content; the second confirmation information is a subscription confirmation information generated by the user terminal after the consent control is triggered; The extraction module is configured to extract, after receiving the second voice information sent by the user terminal, first voiceprint features from the second voice information; The first storage module is configured to store the first voiceprint features and the identifier of the payment account in a subscription system of the service platform.

13. The apparatus of claim 12, further comprising: The sixth pushing module is configured to push, to the user terminal, third interface information including a plurality of alternative amounts, so that the user terminal displays an amount confirmation interface including the plurality of alternative amounts based on the third interface information and voice broadcasts the plurality of alternative amounts; The third determination module is configured to determine, after receiving third confirmation information sent by the user terminal, a target amount included in the third confirmation information as a preset amount threshold; The third confirmation information is confirmation information generated by the user terminal after receiving a selection operation of the user on the target amount; The target amount is a selected alternative amount in the plurality of alternative amounts; The second storage module is configured to store the preset amount threshold and the identifier of the payment account in the subscription system.

14. The apparatus of claim 8, further comprising: The generation module is configured to generate a payment record and a collection record; The sending module is configured to send, to the user terminal, the payment record; The sending module is configured to send, to a terminal of the collection account, the collection record.

15. An electronic device, comprising: a memory configured to store a computer program product; a processor configured to execute the computer program product stored in the memory, and the computer program product, when executed, implements the method of any one of claims 1-7.

16. A computer readable storage medium, wherein, The computer readable storage medium stores computer program instructions, and the computer program instructions, when executed, implement the method of any one of claims 1-7.

Images