CN117371999A - Account binding processing method and device, computer equipment and storage medium - Google Patents
Account binding processing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN117371999A CN117371999A CN202311187999.0A CN202311187999A CN117371999A CN 117371999 A CN117371999 A CN 117371999A CN 202311187999 A CN202311187999 A CN 202311187999A CN 117371999 A CN117371999 A CN 117371999A
- Authority
- CN
- China
- Prior art keywords
- application
- account
- binding
- operation request
- accounts
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 14
- 238000012545 processing Methods 0.000 claims abstract description 46
- 238000000034 method Methods 0.000 claims abstract description 39
- 230000004044 response Effects 0.000 claims abstract description 18
- 238000012795 verification Methods 0.000 claims description 36
- 238000004590 computer program Methods 0.000 claims description 22
- 238000004891 communication Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000013475 authorization Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000001815 facial effect Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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/04—Payment circuits
- G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
-
- 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/382—Payment protocols; Details thereof insuring higher security of transaction
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Computer Security & Cryptography (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application relates to the technical field of Internet, and relates to an account binding processing method, an account binding processing device, computer equipment and a storage medium. The method comprises the following steps: acquiring a first operation request which is sent by a user side and displays a first application interface; responding to a first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface; acquiring a second operation request sent by a user side for selecting and binding other application accounts; and binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts are both applied to a payment port of the first application. Through the scheme, a user can add and manage a plurality of other application accounts in one application, and can easily manage and view different account information without downloading and switching a plurality of independent application programs.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method and apparatus for processing account binding, a computer device, and a storage medium.
Background
In the digital living context, people have multiple debit or credit cards, and these cards come from different banks. In order to use these cards, the user needs to download the corresponding mobile banking application or credit card application.
The increasing number of applications on mobile phones has led to crowding of the user's interface and the need to constantly switch applications when the user needs to pay or pay back using different bank cards. For example, the user may need to open the application of bank a and then switch to the application of bank B, which is not only cumbersome but also takes up the user's time and effort.
Therefore, there is a need for an account binding processing method, apparatus, computer device, and storage medium, which can improve the use efficiency when a user needs to use different bank cards.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an account binding processing method, apparatus, computer device, and storage medium that can improve the convenience of using different application accounts to pay out virtual resources.
In a first aspect, the present application provides an account binding processing method. The method comprises the following steps:
Acquiring a first operation request which is sent by a user side and displays a first application interface;
responding to the first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
acquiring a second operation request sent by the user side for selecting and binding other application accounts;
and binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts both act on a payment port of the first application.
In one embodiment, the obtaining the second operation request sent by the user side to selectively bind other application accounts includes:
acquiring basic information of all application accounts registered in history, and displaying the basic information of all application accounts in a display area of the first application interface; all application accounts are adapted to the payment port of the first application, and the basic information comprises an account name, an account type, an account balance and a use record;
sending a request to be selected for binding other application accounts to the user side, wherein the request to be selected is used for indicating the user side to send a second operation request for selecting the bound other application accounts;
And acquiring the second operation request.
In one embodiment, after the obtaining the second operation request sent by the user side to bind the other application account, the method further includes:
acquiring the binding number of other application account numbers and corresponding account number binding verification modes, wherein the account number binding verification modes are at least divided into a password verification mode and an identification code verification mode;
if the binding number is greater than a preset number threshold, sending a request to be added for adding a biometric authentication mode to a user side, wherein the request to be added is used for indicating the user side to return a third operation request for indicating the selection consent or the selection rejection;
and under the condition that the third operation request is used for indicating the selection consent, responding to the third operation request, and adding the biological identification verification mode into the account binding verification mode.
In one embodiment, after binding the other application account to the first application, the binding includes:
acquiring an operation request of expenditure virtual resources sent by the user side;
judging whether the first application is provided with a default virtual resource expenditure account;
if not, virtual resource expenditure deduction information of the first application and other applications is obtained;
And determining a target virtual resource expenditure account according to the virtual resource expenditure deduction information, wherein the target virtual resource expenditure account comprises at least one application account.
In one embodiment, after determining the target virtual resource expense account, the method includes:
acquiring historical use frequency of at least one application account contained in the target virtual resource expenditure account;
and setting a default virtual resource expenditure account according to the historical use frequency, wherein the default virtual resource expenditure account comprises at least one application account.
In one embodiment, after the binding of the other application account to the first application, the binding further includes;
acquiring an account processing operation request sent by the user side;
and responding to the account processing operation request, and sending a corresponding processing link to a user side, wherein the account processing request comprises an application account inquiry request or an application account unbinding request.
In a second aspect, the application further provides an account binding processing device. The device comprises:
the acquisition module is used for acquiring a first operation request which is sent by the user side and enters the first application interface;
the sending module is used for responding to the first operation request and sending the binding link and the display link of the first application interface to the user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
The acquisition module is also used for acquiring a second operation request which is sent by the user side and used for selecting and binding other application accounts;
and the binding module is used for binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts are both applied to a payment port of the first application.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:
acquiring a first operation request which is sent by a user side and displays a first application interface;
responding to the first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
acquiring a second operation request sent by the user side for selecting and binding other application accounts;
and binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts both act on a payment port of the first application.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
acquiring a first operation request which is sent by a user side and displays a first application interface;
responding to the first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
acquiring a second operation request sent by the user side for selecting and binding other application accounts;
and binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts both act on a payment port of the first application.
In a fifth aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:
acquiring a first operation request which is sent by a user side and displays a first application interface;
Responding to the first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
acquiring a second operation request sent by the user side for selecting and binding other application accounts;
and binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts both act on a payment port of the first application.
According to the account binding processing method, the account binding processing device, the computer equipment and the storage medium, a user can add and manage a plurality of bank cards in the mobile banking application program, and account information of different banks can be easily managed and checked in the same application program without downloading and switching a plurality of independent banking application programs. The user can perform various banking services such as inquiring balance, transferring accounts, paying, etc. through the mobile banking application. No matter which bank card, the user can finish the operation in the same application program, thereby avoiding the trouble of frequently switching the application programs. The user can manage the payment account more conveniently and enjoy more convenient service. Meanwhile, according to the preference and consumption habit of the user, the system can intelligently select the most suitable payment account to pay so as to ensure the maximum rights and interests of the client.
Drawings
FIG. 1 is an application environment diagram of an account binding process method in one embodiment;
FIG. 2 is a flow chart of a method for account binding processing in one embodiment;
FIG. 3 is a flowchart illustrating a method for account binding processing according to another embodiment;
FIG. 4 is a block diagram illustrating an account binding process apparatus in one embodiment;
fig. 5 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The account binding processing method provided by the embodiment of the invention can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The server 104 obtains a first operation request sent by the user side and displaying the first application interface. Then, responding to a first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push content of other application accounts, and the push content is located in a display area of the first application interface. Then, the server 104 obtains a second operation request sent by the user side to selectively bind other application accounts. And binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts are both applied to a payment port of the first application. The terminal 102 is a user end, and the user sends a first operation request and a second operation request to the server 104 through the terminal 102, so as to be used for binding other application accounts to the first application.
The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.
In one embodiment, as shown in fig. 2, an account binding processing method is provided, and the method is applied to the server in fig. 1 for illustration, and includes the following steps:
step S202, a first operation request for displaying a first application interface sent by a user terminal is obtained.
The first application may refer to a mobile banking application program, and may perform operation and management of banking business through a mobile phone. The user can perform account inquiry, account transfer, payment, financial management and other operations through the mobile phone banking application program, and financial transaction and management are performed conveniently and rapidly. Mobile banking applications are typically provided by banks or financial institutions, where users can choose to install and use according to their own needs. The application supports binding agreements of debit and credit cards for different banks.
Specifically, the user can enter the homepage of the first application through the first operation request, which means that the user clicks an icon of the first application on a mobile phone or uses a corresponding gesture to open the application and display a homepage interface thereof. The home page is typically the starting page of the application, providing the main functional portal and navigation of the application. On the homepage, the user can browse various functions of the application, perform corresponding operations or navigate to other pages. The design and layout of the home page is typically customized according to the characteristics of the application and the needs of the user to provide an intuitive, easy-to-use user experience.
Step S204, responding to a first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push content of other application accounts, and the push content is located in a display area of the first application interface.
Specifically, after the user makes the first operation request, the system sends a binding link and a display link of the first application interface to the user. The binding link is used for requesting the user to bind account numbers of other applications, and the push content is displayed in a display area of the first application interface.
Specifically, the binding link is a link for jumping to the binding page, and the user can click on the link to perform the binding operation of the account number. The binding operation can bind the account numbers of the first application and other applications so as to realize data sharing or function expansion between different applications. The display link of the first application interface is a link for opening a homepage or a specific page of the first application. When the user clicks the link, an interface of the first application is displayed on the user side. In the display area of the first application interface, push content is displayed, which may be a notification, message, or other information that the system or application has pushed to the user. By sending the binding link and the display link of the first application interface, the system can guide the user to perform account binding operation, and display push content in the first application interface, so that more convenient and personalized user experience is provided.
Step S206, a second operation request sent by the user terminal for selecting and binding other application accounts is obtained.
Specifically, the step of obtaining the second operation request sent by the user end for selecting to bind other application accounts refers to that when the user selects to bind other application accounts in the first application interface, the system receives the binding request sent by the user. The request may be for the user to click a bind button on the interface, select a bind option, or enter related information to complete the binding operation. After receiving the binding request, the system performs corresponding processing, such as verifying the identity of the user, acquiring account information of the user in other applications, and the like. The system may communicate through interfaces with other applications to enable account binding and data interaction. The specific implementation and details of the binding operation will vary depending on the design and functional requirements of the system. By acquiring the second operation request sent by the user side for selecting and binding other application accounts, the system can realize account binding among different applications under the condition of user authorization, and provides more convenient and integrated user experience.
In step S208, in response to the second operation request, other application accounts are bound to the first application, where both the first application account and the other application account act on the payment port of the first application.
After responding to the second operation request of the user, the account numbers of other applications are bound with the account numbers of the first application, and the account numbers are used for the payment port of the first application.
Specifically, when the user selects to bind the account number of the other application to the first application, the system performs corresponding processing, and associates the account numbers of the other applications with the payment port of the first application. This means that the user can use these bound other application accounts in the first application for payment operations. For example, a user may conduct payment activities such as online shopping, transferring accounts, or paying fees in a first application using account numbers of other applications that are bound.
According to the account binding processing method, the account of other applications is bound to the payment port of the first application, unified management and centralized payment of the account can be achieved, and more convenient and smooth payment experience is provided. The user does not need to switch accounts among a plurality of applications, and only needs to complete payment operation in the first application. Meanwhile, the first application can expand the payment channel and service range by using other bound application accounts, and provide more payment selection and convenience.
In one embodiment, obtaining a second operation request sent by the user side to selectively bind other application accounts includes:
acquiring basic information of all application accounts registered in history, and displaying the basic information of all application accounts in a display area of a first application interface; all application accounts are adapted to the payment port of the first application, and basic information comprises an account name, an account type, an account balance and a use record;
sending a request to be selected for binding other application accounts to a user side, wherein the request to be selected is used for indicating the user side to send a second operation request for selecting the bound other application accounts; a second operation request is obtained.
Specifically, basic information of all application accounts registered in history is obtained: the system needs to acquire basic information of all application accounts registered by the user in the past, including account names, account types, account balances, usage records and the like.
Displaying the basic information of all the application accounts in a display area of the first application interface: the system needs to display the acquired basic information of all the application accounts in the display area of the interface of the first application, so that the user can conveniently view and manage the information of the accounts.
Sending a request to be selected for binding other application accounts to a user: the system needs to send a request to be selected to the user side, and the request is used for indicating the user to select other application accounts which need to be bound to the first application. This request may be a message or notification informing the user that a binding operation is required.
Acquiring a second operation request: the system needs to acquire the second operation request for selecting and binding other application accounts in time after the user side sends the request. In this way, the system can perform subsequent binding operation, adapt other application account numbers to the payment port of the first application, and record relevant information.
Through the operation, the system can adapt other application accounts to the payment port of the first application, and basic information of the accounts is displayed and managed in the first application interface. In this way, the user can conveniently perform payment operations in the first application and view the relevant balance and usage records.
In one embodiment, referring to fig. 3, after obtaining the second operation request sent by the user side to bind other application account, the method further includes:
step S302, the binding number of other application account numbers and corresponding account number binding verification modes are obtained, wherein the account number binding verification modes are at least divided into a password verification mode and an identification code verification mode.
The binding number refers to the number of other application accounts that the system needs to acquire the user's selection of binding. This number indicates how many other application accounts the user wishes to bind with the first application.
The account binding verification mode refers to an account binding verification mode corresponding to other application accounts which need to be obtained by the system and are bound. This verification method is used to ensure the accuracy and security of account information provided by the user. The account binding verification method at least comprises a password verification method and an identification code verification method.
The password verification mode comprises the following steps: the user needs to input passwords corresponding to other application account numbers bound with the user to verify the authenticity and legality of the account numbers. Identification code verification mode: the user may need to enter a specific identification code provided by other applications, such as a verification code, a short message verification code, or a security question answer, etc., to verify account binding.
By acquiring the binding number and the account binding verification mode, the system can accurately acquire and verify account information provided by the user when the user selects to bind other application accounts, and ensure the safety and the effectiveness of binding operation.
Step S304, if the binding number is greater than the preset number threshold, a request to be added for adding the biometric authentication mode is sent to the user side, and the request to be added is used for indicating the user side to return a third operation request for indicating the selection consent or the selection rejection.
Specifically, if the number of other application accounts selected to be bound by the user exceeds a preset number threshold, the fact that the user needs to bind more application accounts in a traditional verification mode when binding other application accounts is troublesome is indicated. Based on the above, the system sends a request to be added to the user side, which is used for indicating whether the user wants to add the biometric authentication mode. The request to be added may have the user choose to agree or refuse to add the biometric authentication mode and return a third operation request to indicate the user's choice.
The biometric authentication method is a method for performing authentication by biometric information (such as fingerprint, facial recognition, iris, etc.) of a user. If the user agrees to add the biometric authentication mode, the system can also use the biometric information to authenticate when binding other application account numbers besides the password and the identification code authentication mode.
By sending the request to be added and obtaining the third operation request, the system can enable the user to decide whether to add the biometric authentication mode or not, and perform subsequent account binding operation according to the selection of the user. Therefore, when binding other application accounts, the user can select a safer and more convenient biological identification verification mode to improve the safety of the account.
In step S306, in the case where the third operation request is used to indicate the selection consent, the biometric authentication method is added to the account binding authentication method in response to the third operation request.
If the user selects to agree to add the biometric authentication mode in the request to be added, the system responds to the third operation request and adds the biometric authentication mode to the account binding authentication mode.
Specifically, the system updates the account binding setting of the user and adds the biometric authentication mode to the account binding authentication option. After that, when the user performs an account binding operation, the user can select to use the biometric information for authentication in addition to the password authentication method and the identification code authentication method. By adding the biometric authentication mode to the account binding authentication mode, the system can provide a more diversified and secure authentication mode to ensure the security and credibility of the user account. The user can choose to use the biological identification information for verification when binding other application accounts, so that convenience is provided, and meanwhile, the safety of the accounts is improved.
In one embodiment, after binding the other application account to the first application, the method includes:
And acquiring an operation request of expenditure virtual resources sent by the user side.
Judging whether a default virtual resource expenditure account is set by the first application; if yes, arranging virtual resource expenditure according to a default virtual resource expenditure account; if not, virtual resource expenditure deduction information of the first application and other applications is obtained.
And determining a target virtual resource expenditure account according to the virtual resource expenditure deduction information, wherein the target virtual resource expenditure account comprises at least one application account.
In particular, virtual resources refer to various resources that exist in digitized form in a computer system or network environment. Such as virtual currency, virtual assets, etc.
First, the system determines whether a default virtual resource payout account has been set by the first application. If the default account number has been set, the system will schedule the expenditure of virtual resources according to the default account number. If the first application does not set the default virtual resource expense account, the system can acquire virtual resource expense deduction information of the first application and other applications. The virtual resource spending derate information may include the spending amount, derate mode, etc. of different application accounts. Based on the virtual resource payout amount reduction information, the system determines a target virtual resource payout account. The target virtual resource expense account may include at least one application account.
Illustrating: assuming that the user wants to purchase a piece of virtual goods, an operation request to pay out the virtual resource is initiated in the first application. The system will first check if the default virtual resource payout account has been set. If the default account number is set, the system deducts the virtual resource according to the default account number. If the default account number is not set, the system may obtain virtual resource expense deduction information for the first application and other applications. For example, the first application has a payout amount of 100, and the other applications have a payout amount of 50. The system determines a target virtual resource payout account based on the derating information. It may be that the system selects the account of the first application as the target virtual resource expenditure account.
The system can judge the preference of the user according to the historical payment record, the preference and the habit of the user. For example, if a user makes payments often using a particular payment account, the system may prioritize that account. The system can check the balance condition of each payment account and preferentially select the account with higher balance to pay so as to avoid the condition of insufficient balance of the account of the user. The system may select the most favorable payment account for payment based on the offers of the different payment accounts, such as discounts, cashbacks, etc. Some platforms may have specific requirements for payment accounts, for example, only specific payment means or specific payment accounts may be supported, and the system may intelligently select a payment account based on the platform requirements. The system may require the user to authorize when initially setting the payment account to obtain the user's payment account list and permissions, and then intelligently select the payment account based on the authorization information.
By comprehensively considering the above factors, the system can intelligently allocate the payment accounts through intelligent algorithms and rules so as to provide the payment experience which is most convenient for users, accords with preference and maximizes economic benefit.
In one embodiment, after determining the target virtual resource expense account, comprising:
acquiring historical use frequency of at least one application account contained in the target virtual resource expenditure account; and setting a default virtual resource expenditure account according to the historical use frequency, wherein the default virtual resource expenditure account comprises at least one application account.
Specifically, a target virtual resource expenditure account number for which historical usage frequency needs to be acquired is determined. And acquiring an application account list contained in the target virtual resource expenditure account through an interface provided by a system or a user. And inquiring the historical use frequency of each application account according to the application account list. The historical usage frequency data of each application account can be obtained by using database query or log analysis and the like. For each application account, the historical usage frequency data is analyzed, and indexes such as average usage frequency, highest usage frequency, lowest usage frequency and the like can be calculated. And selecting the application account with higher use frequency as a default virtual resource expenditure account according to the historical use frequency data. The threshold may be set according to requirements, for example, an application account with the top three usage frequency ranks is selected as a default account. In the process, the privacy and safety of the user are required to be protected, and legal and safe processing and storage of sensitive information such as historical use frequency are ensured.
In one embodiment, after binding the other application account to the first application, further comprising;
acquiring an account processing operation request sent by a user side; and responding to an account processing operation request, and sending a corresponding processing link to a user terminal, wherein the account processing request comprises an application account inquiry request or an application account unbinding request.
Specifically, in the server side or the application program, a monitoring mechanism is set to monitor an account processing operation request sent by the user side. When an account processing operation request is received, the content of the request, including the request type and related parameters, is parsed to determine whether to apply an account query request or an application account unbinding request. And executing corresponding account processing operation according to the request type and the parameters. For example, if the application account query request is an application account query request, a database or other storage system may be queried to obtain relevant application account information. If the application account unbinding request is, unbinding operation can be executed, and the application account is unbinding with the user. And generating a corresponding processing link according to the processing result and the operation requirement of the user. The processing link may be a URL address containing information of the processing result and directions of related operations. And sending the generated processing link to the user terminal, and sending the link to the user terminal in a network transmission mode (such as HTTP response), push notification and the like.
In this process, it should be noted that for sensitive account number operations (e.g., unbinding operations), authentication and authorization of the user is required to prevent unauthorized operations. Meanwhile, for processing links transmitted, security and validity of a link address need to be ensured to protect account numbers and personal information of users.
Through the embodiments, a user can add and manage a plurality of bank cards in the mobile banking application program, and easily manage and view account information of different banks in the same application program without downloading and switching a plurality of independent banking application programs. The user can perform various banking services such as inquiring balance, transferring accounts, paying, etc. through the mobile banking application. No matter which bank card, the user can finish the operation in the same application program, thereby avoiding the trouble of frequently switching the application programs. The user can manage the payment account more conveniently and enjoy more convenient service. Meanwhile, according to the preference and consumption habit of the user, the system can intelligently select the most suitable payment account to pay so as to ensure the maximum rights and interests of the client.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides an account binding processing device for realizing the account binding processing method. The implementation scheme of the device for solving the problem is similar to the implementation scheme described in the above method, so the specific limitation in the embodiments of the account binding processing device or devices provided below may refer to the limitation of the account binding processing method hereinabove, and will not be described herein.
In one embodiment, as shown in fig. 4, there is provided an account binding processing device, including: an obtaining module 402, configured to obtain a first operation request sent by a user side and entering a first application interface;
a sending module 404, configured to send, in response to the first operation request, the binding link and the display link of the first application interface to the user terminal; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
the obtaining module 402 is further configured to obtain a second operation request sent by the user side to selectively bind other application accounts;
and the binding module 406 is configured to bind the other application account to the first application in response to the second operation request, where the first application account and the other application account both act on a payment port of the first application.
In one embodiment, obtaining a second operation request sent by the user side to selectively bind other application accounts includes:
the acquiring module 402 is further configured to acquire basic information of all application accounts registered in the history;
the display module is used for displaying the basic information of all the application accounts in the display area of the first application interface; all application accounts are adapted to the payment port of the first application, and basic information comprises an account name, an account type, an account balance and a use record;
the sending module 404 is further configured to send a request to be selected for binding other application accounts to the user side, where the request to be selected is used to instruct the user side to send a second operation request for selecting the other application accounts to be bound;
the obtaining module 402 is further configured to obtain a second operation request.
In one embodiment, after obtaining the second operation request sent by the user end to selectively bind other application accounts, the method further includes:
the obtaining module 402 is further configured to obtain a binding number of the other application account selected to be bound and a corresponding account binding verification mode, where the account binding verification mode is at least divided into a password verification mode and an identification code verification mode;
the sending module 404 is further configured to send a request to be added for adding the biometric authentication mode to the user side if the binding number is greater than the preset number threshold, where the request to be added is used to instruct the user side to return a third operation request for instructing to select agreement or selection rejection;
And the processing module is used for responding to the third operation request and adding the biological identification verification mode into the account binding verification mode under the condition that the third operation request is used for indicating the selection consent.
In one embodiment, after binding the other application account to the first application, the method includes:
the obtaining module 402 is further configured to obtain an operation request sent by the user side to pay out the virtual resource;
the processing module is also used for judging whether the first application is provided with a default virtual resource expenditure account;
if not, the obtaining module 402 is further configured to obtain virtual resource expense deduction information of the first application and other applications;
the processing module is further configured to determine a target virtual resource expense account according to the virtual resource expense deduction information, where the target virtual resource expense account includes at least one application account.
In one embodiment, after determining the target virtual resource expense account, comprising:
the obtaining module 402 is further configured to obtain a historical usage frequency of at least one application account included in the target virtual resource expenditure account;
the processing module is further configured to set a default virtual resource expenditure account according to the historical usage frequency, where the default virtual resource expenditure account includes at least one application account.
In one embodiment, after binding the other application account to the first application, further comprising;
the obtaining module 402 is further configured to obtain an account processing operation request sent by the user side;
the sending module 404 is further configured to send a corresponding processing link to the user terminal in response to an account processing operation request, where the account processing request includes an application account query request or an application account unbinding request.
The above modules in the account binding processing device may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements an account binding processing method. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 5 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
step S202, a first operation request for displaying a first application interface, which is sent by a user side, is obtained;
step S204, responding to a first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
step S206, a second operation request which is sent by the user terminal and used for selecting and binding other application accounts is obtained;
in step S208, in response to the second operation request, other application accounts are bound to the first application, where both the first application account and the other application account act on the payment port of the first application.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
step S202, a first operation request for displaying a first application interface, which is sent by a user side, is obtained;
step S204, responding to a first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
step S206, a second operation request which is sent by the user terminal and used for selecting and binding other application accounts is obtained;
in step S208, in response to the second operation request, other application accounts are bound to the first application, where both the first application account and the other application account act on the payment port of the first application.
In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, performs the steps of:
step S202, a first operation request for displaying a first application interface, which is sent by a user side, is obtained;
step S204, responding to a first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
Step S206, a second operation request which is sent by the user terminal and used for selecting and binding other application accounts is obtained;
in step S208, in response to the second operation request, other application accounts are bound to the first application, where both the first application account and the other application account act on the payment port of the first application.
It should be noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related countries and regions.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.
Claims (10)
1. An account binding processing method, which is characterized by comprising the following steps:
acquiring a first operation request which is sent by a user side and displays a first application interface;
responding to the first operation request, and sending a binding link and a display link of a first application interface to a user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
Acquiring a second operation request sent by the user side for selecting and binding other application accounts;
and binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts both act on a payment port of the first application.
2. The method of claim 1, wherein the obtaining the second operation request sent by the user side to selectively bind other application accounts includes:
acquiring basic information of all application accounts registered in history, and displaying the basic information of all application accounts in a display area of the first application interface; all application accounts are adapted to the payment port of the first application, and the basic information comprises an account name, an account type, an account balance and a use record;
sending a request to be selected for binding other application accounts to the user side, wherein the request to be selected is used for indicating the user side to send a second operation request for selecting the bound other application accounts;
and acquiring the second operation request.
3. The method of claim 2, wherein after the second operation request sent by the user side to select to bind other application accounts is obtained, further comprising:
Acquiring the binding number of other application account numbers and corresponding account number binding verification modes, wherein the account number binding verification modes are at least divided into a password verification mode and an identification code verification mode;
if the binding number is greater than a preset number threshold, sending a request to be added for adding a biometric authentication mode to a user side, wherein the request to be added is used for indicating the user side to return a third operation request for indicating the selection consent or the selection rejection;
and under the condition that the third operation request is used for indicating the selection consent, responding to the third operation request, and adding the biological identification verification mode into the account binding verification mode.
4. The method of claim 1, wherein after binding the other application account to the first application, comprising:
acquiring an operation request of expenditure virtual resources sent by the user side;
judging whether the first application is provided with a default virtual resource expenditure account;
if not, virtual resource expenditure deduction information of the first application and other applications is obtained;
and determining a target virtual resource expenditure account according to the virtual resource expenditure deduction information, wherein the target virtual resource expenditure account comprises at least one application account.
5. The method of any one of claims 4, wherein after determining the target virtual resource payout account, comprising:
acquiring historical use frequency of at least one application account contained in the target virtual resource expenditure account;
and setting a default virtual resource expenditure account according to the historical use frequency, wherein the default virtual resource expenditure account comprises at least one application account.
6. The method of claim 2, wherein after binding the other application account to the first application, further comprising;
acquiring an account processing operation request sent by the user side;
and responding to the account processing operation request, and sending a corresponding processing link to a user side, wherein the account processing request comprises an application account inquiry request or an application account unbinding request.
7. An account binding processing device, the device comprising:
the acquisition module is used for acquiring a first operation request which is sent by the user side and enters the first application interface;
the sending module is used for responding to the first operation request and sending the binding link and the display link of the first application interface to the user side; the binding link is used for requesting to bind push contents of other application accounts, and the push contents are positioned in a display area of the first application interface;
The acquisition module is also used for acquiring a second operation request which is sent by the user side and used for selecting and binding other application accounts;
and the binding module is used for binding other application accounts to the first application in response to the second operation request, wherein the first application account and the other application accounts are both applied to a payment port of the first application.
8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311187999.0A CN117371999A (en) | 2023-09-14 | 2023-09-14 | Account binding processing method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311187999.0A CN117371999A (en) | 2023-09-14 | 2023-09-14 | Account binding processing method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117371999A true CN117371999A (en) | 2024-01-09 |
Family
ID=89401208
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311187999.0A Pending CN117371999A (en) | 2023-09-14 | 2023-09-14 | Account binding processing method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117371999A (en) |
-
2023
- 2023-09-14 CN CN202311187999.0A patent/CN117371999A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11755773B1 (en) | Access control tower | |
| US10097558B2 (en) | Delegated permissions in a distributed electronic environment | |
| US8016192B2 (en) | User-configurable priority list for mobile device electronic payment applications | |
| US9466051B1 (en) | Funding access in a distributed electronic environment | |
| CA3050656C (en) | File format and platform for storage and verification of credentials | |
| JP5850587B1 (en) | Personal information account banking | |
| US20140068706A1 (en) | Protecting Assets on a Device | |
| US8984596B2 (en) | Electronic device for displaying a plurality of web links based upon finger authentication and associated methods | |
| US20150350192A1 (en) | Dynamic Secure Login Authentication | |
| CN107615798B (en) | Method and system for personal data sharing applications | |
| US20180005276A1 (en) | User controlled profiles | |
| EP3180899A1 (en) | Data security system and method | |
| KR20180114549A (en) | Financial transaction management system, method, storage medium and server | |
| JPWO2010050406A1 (en) | Service provision system | |
| CN111402069B (en) | Accumulation fund data acquisition method and device, computer equipment and storage medium | |
| US20230259565A1 (en) | System and method for facilitating presentation modification of a user interface | |
| CN109643353A (en) | Automatic access data change detection | |
| CN117371999A (en) | Account binding processing method and device, computer equipment and storage medium | |
| US20210133727A1 (en) | System and Method for Importing Electronic Credentials with a Third-party Application | |
| US20210192074A1 (en) | System and method for controlling access to account transaction information | |
| US10757216B1 (en) | Group profiles for group item recommendations | |
| JP2021117667A (en) | Settlement management device, control method, and program | |
| US11935020B1 (en) | Control tower for prospective transactions | |
| US20240184917A1 (en) | Access control interface for managing entities and permissions | |
| US20080208965A1 (en) | System, method and computer program for inputting information relating to a service or a product selected online by a user into a portable short-range wireless communication capable device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |