A payment account renewal method, electronic device, medium and product

Abstract

The specification discloses a payment account renewal method, an electronic device, a medium and a product. In the scheme, when it is detected that a user accesses a specified page of a client, the client can send a query request to a business platform to query whether the user is located in a list of payment accounts to be renewed. When it is determined that the user is located in the list, renewal prompt information is displayed to the user in the specified page. Then, based on a renewal operation performed by the user on the renewal prompt information, a renewal request is sent to an account provider corresponding to a payment account to be renewed by the user, so that the account provider renews the payment account to be renewed by the user based on the renewal request.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, electronic device, medium, and product for renewing a payment account. Background Technology

[0002] Currently, users can link their credit cards to various online platforms, thereby enabling them to conduct various transactions through the linked credit card accounts.

[0003] However, in practice, once a credit card expires, the user will be unable to use it, causing great inconvenience.

[0004] Therefore, how to effectively remind users to renew their soon-to-expire credit cards is a technical problem that urgently needs to be solved. Summary of the Invention

[0005] This specification implements a method, electronic device, medium, and product for renewing payment accounts, in order to partially solve the problem of inconvenience caused to users by expired credit cards in the prior art.

[0006] The embodiments in this specification adopt the following technical solutions: This specification provides an embodiment of a method for renewing a payment account. The method is applied to a client provided by a business platform. Users bind a payment account issued by an account provider to a platform account registered on the business platform through the client, enabling them to perform business transactions on the platform using the bound payment account. The method includes: When a user is detected accessing a specified page of the client, a query request is sent to the business platform to check whether the user is on the list of payment accounts awaiting renewal. In response to the user being on the list, a renewal reminder message is displayed to the user on the designated page; Based on the user's renewal operation in response to the renewal prompt information, a renewal request is sent to the account provider corresponding to the user's payment account to be renewed, so that the account provider can renew the user's payment account based on the renewal request.

[0007] Furthermore, in some implementations, in response to the user being on the list, a renewal prompt message is displayed to the user on the designated page, including: The system receives a prompt instruction sent by the business platform. The prompt instruction is sent to the client by the business platform after determining that the user is in the list based on the obtained query results and that the user meets the preset renewal prompt conditions based on the user profile. Based on the prompt instruction, a renewal prompt message is displayed to the user on the designated page.

[0008] Furthermore, in some embodiments, based on the renewal operation performed by the user in response to the renewal prompt information, a renewal request is sent to the account provider corresponding to the user's payment account to be renewed, so that the account provider renews the user's payment account based on the renewal request, including: Based on the user's renewal operation in response to the renewal prompt information, a renewal request is sent to the account provider to obtain a first login-free link for the account provider. The first login-free link is generated based on a first token corresponding to the user. The first token is generated based on the user's identification data, which includes at least one of the user's user identifier and the account identifier of the payment account issued by the account provider held by the user. Based on the first login-free link, a first access request is sent to the account provider, so that the account provider determines that the user has completed login verification based on the first token carried in the first access request, and returns the renewal page provided by the account provider to the client; The user is shown the renewal page so that they can renew their payment account.

[0009] Furthermore, in some implementations, obtaining a first login-free link for the account provider includes: The business platform sends the user's de-identified identifier to the account provider, so that the account provider can determine the user's identifier data based on the user's de-identified identifier, generate a first token corresponding to the user based on the user's identifier data, and return the first login-free link according to the first token corresponding to the user and the page link corresponding to the renewal page. The user's de-identified identifier is obtained by de-identifying the user's identifier data; The account provider matches the user's de-identified identifier with each identifier to be matched to determine the user's identifier data. Each identifier to be matched is obtained by de-identifying the identifier data of each user stored locally by the account provider.

[0010] Furthermore, in some implementations, obtaining a first login-free link for the account provider includes: The business platform sends the user's de-identified identifier and the first bounce link to the account provider, so that the account provider generates the first token based on the user's de-identified identifier, and returns the first login-free link based on the first token, the page link corresponding to the renewal page, and the first bounce link; The method further includes: After the user completes the payment account renewal based on the renewal page, a response message carrying a first redirection instruction is received from the account provider; The first redirection instruction is executed to display the renewal result page provided by the business platform to the user based on the redirection of the first bounce link.

[0011] Furthermore, in some implementations, displaying renewal prompt information to the user on the designated page includes: A pop-up notification window is displayed to the user on the designated page, and the renewal notification information is displayed in the pop-up notification window.

[0012] Furthermore, in some embodiments, the renewal prompt information includes visual presentation resources of the user's payment account to be renewed, the visual presentation resources being used to represent the appearance of the payment account; On the designated page, display renewal notification information to the user, including: Based on the organization identification code corresponding to the user's payment account with pending renewal, determine the visual presentation resources corresponding to the organization identification code. Different account organizations correspond to different organization identification codes. Based on the determined visual presentation resources, a renewal prompt message is displayed to the user on the designated page.

[0013] Furthermore, in some embodiments, the method further includes: After the user completes the payment account renewal, an activation prompt message is displayed to the user; Based on the activation operation performed by the user in response to the activation prompt information, an activation request is sent to the account provider so that the account provider can activate the user's payment account to be activated based on the activation request.

[0014] Furthermore, in some implementations, based on the activation operation performed by the user in response to the activation prompt information, an activation request is sent to the account provider, so that the account provider activates the user's payment account to be activated based on the activation request, including: Based on the activation operation performed by the user in response to the activation prompt information, an activation request is sent to the account provider to obtain a second login-free link for the account provider. The second login-free link is generated based on a second token corresponding to the user. The second token is generated based on the user's identification data, which includes at least one of the user's user identifier and the account identifier of the payment account issued by the account provider held by the user. Based on the second login-free link, a second access request is sent to the account provider, so that the account provider determines that the user has completed login verification based on the second token carried in the second access request, and returns the activation page provided by the account provider to the client; The activation page is displayed to the user so that the user can activate their payment account.

[0015] Furthermore, in some implementations, obtaining a second login-free link for the account provider includes: The business platform sends the user's de-identified identifier to the account provider, so that the account provider can determine the user's identifier data based on the de-identified identifier, generate the second token based on the user's identifier data, and return the second login-free link according to the second token and the page link corresponding to the activation page; The user's de-identified identifier is obtained by de-identifying the user's identifier data; The account provider matches the user's de-identified identifier with each identifier to be matched to determine the user's identifier data. Each identifier to be matched is obtained by de-identifying the identifier data of each user stored locally by the account provider.

[0016] Furthermore, in some implementations, obtaining a second login-free link for the account provider includes: The business platform sends the user's de-identified identifier and the second bounce link to the account provider, so that the account provider generates the second token based on the user's de-identified identifier, and returns the second login-free link according to the second token, the page link corresponding to the activation page, and the second bounce link; The method further includes: After the user completes the payment account activation based on the activation page, a response message carrying a second redirection instruction is received from the account provider; The second redirection instruction is executed to display the activation result page provided by the business platform to the user based on the redirection of the second bounce link.

[0017] This specification provides an embodiment of a payment account renewal method applied to a business platform. The method involves a user binding a payment account issued by an account provider to the user's platform account registered on the platform via a client provided by the business platform. The user then uses the bound payment account to perform business transactions on the business platform. The method includes: The client receives a query request sent by a user through the client, the query request being sent when the client detects that the user has accessed a specified page; Based on the query request, check whether the user is on the pre-obtained list of payment accounts awaiting renewal; In response to the user being on the list, the client is instructed to display a renewal prompt to the user on the designated page so that the user can renew their payment account.

[0018] Furthermore, in some implementations, obtaining the list of payment accounts awaiting renewal includes: Obtain renewal documents sent by each account provider; Parse out each matching identifier recorded in the renewal file. For each matching identifier, the matching identifier is obtained by de-identifying the user's identifier data. The identifier data includes at least one of the user's user identifier and the account identifier of the payment account held by the user. The business platform locally matches each identifier to be matched with each de-identified identifier, and obtains the list based on the matching results. Each de-identified identifier is obtained by de-identifying the identifier data of each user stored in the business platform.

[0019] Furthermore, in some implementations, in response to the user being on the list, the client is instructed to display a renewal prompt message to the user on the designated page so that the user can renew their payment account, including: The client receives a first authorization request, which is generated by the client based on the user's renewal authorization operation in response to the renewal prompt information. Based on the first authorization request, the account provider corresponding to the user's payment account to be renewed is determined, and the first dedicated interface between the business platform and the account provider is called. The first dedicated interface is called after the first authorization request confirms that the user authorizes the business platform to complete the payment account renewal on behalf of the user. Based on the first dedicated interface, a renewal request is sent to the account provider, so that the account provider can renew the user's payment account pending renewal based on the renewal request.

[0020] Furthermore, in some embodiments, the method further includes: The client receives a second authorization request, which is generated by the client based on the activation authorization operation performed by the user in response to the activation prompt information. The activation prompt information is displayed to the user on the designated page after the user completes the renewal of the payment account. According to the second authorization request, the second dedicated interface between the business platform and the account provider is invoked. The second dedicated interface is invoked after the second authorization request confirms that the user authorizes the business platform to complete the payment account activation on behalf of the user. Based on the second dedicated interface, an activation request is sent to the account provider so that the account provider can activate the user's payment account to be activated based on the activation request.

[0021] This specification provides an electronic device, including: a processor; and a memory for storing processor-executable instructions; wherein the processor executes the executable instructions to implement the steps of the above-described payment account renewal method.

[0022] This specification provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for renewing a payment account.

[0023] This specification provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the payment account renewal method described above.

[0024] The above-mentioned technical solutions adopted in this specification can achieve the following beneficial effects: As provided in the embodiments of this specification, when a user is detected accessing a designated page of the client, the client can send a query request to the business platform to check whether the user is on the list of payment accounts awaiting renewal. When it is determined that the user is on the list, a renewal prompt message is displayed to the user on the designated page. Then, based on the renewal operation performed by the user in response to the renewal prompt message, a renewal request is sent to the account provider corresponding to the user's payment account awaiting renewal, so that the account provider can renew the user's payment account based on the renewal request.

[0025] The payment account renewal method provided in the embodiments of this specification can promptly remind users when their payment accounts are pending renewal, thereby enabling users to complete the renewal of their payment accounts in a timely manner based on the reminder, thus ensuring the normal use of the payment accounts. Attached Figure Description

[0026] Figure 1 A flowchart illustrating a method for renewing a payment account as provided in an embodiment of this specification; Figure 2 This is a schematic diagram illustrating an embodiment of the present specification, using the credit card repayment page in the client as the designated page; Figure 3A and Figure 3B Schematic diagrams illustrating two different ways of displaying renewal reminder information provided in the embodiments of this specification; Figure 4 This is a schematic diagram illustrating the user's authorization operation based on the renewal prompt information displayed on the client, as provided in the embodiments of this specification. Figure 5A This is a schematic diagram of a bank's renewal page displayed in a client, as provided in an embodiment of this specification. Figure 5B This is a schematic diagram of the page displayed in the client to complete the renewal, provided as an embodiment of this specification. Figure 6A and Figure 6B This specification provides an example of displaying renewal pages for different institutions' credit cards in a client-side environment, showcasing resources for different visual presentations. Figure 7A A schematic diagram of the activation page of a banking institution displayed in a client, provided as an embodiment of this specification; Figure 7B This is a schematic diagram of the activation completion page displayed in the client as provided in the embodiments of this specification; Figure 8 A flowchart illustrating a method for renewing a payment account as provided in an embodiment of this specification; Figure 9 A schematic diagram illustrating the process by which the business platform provided in the embodiments of this specification obtains a list of payment accounts awaiting renewal in advance; Figure 10A This is a detailed schematic diagram illustrating the process of renewing a credit card by redirecting to the renewal page of a bank, as provided in the embodiments of this specification. Figure 10B A detailed interactive diagram illustrating the process of activating a credit card by redirecting to a bank's activation page, as provided in the embodiments of this specification. Figure 11 Detailed interactive diagrams illustrating how to complete credit card renewal and activation without redirecting to a bank's page, as provided in the embodiments of this specification; Figure 12 A schematic diagram of a payment account renewal device provided in the embodiments of this specification; Figure 13 A schematic diagram of a payment account renewal device provided in the embodiments of this specification; Figure 14 This is a schematic structural diagram of a device provided in this manual. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.

[0028] In this manual, the specific form of the payment account can be various, such as a credit card or debit card issued by the user, an electronic Class II / Class III account, a digital currency wallet (such as e-CNY Wallets) (digital wallet certificates often have an expiration date, and once expired, the digital currency wallet will be temporarily unusable), or an electronic gift card with an expiration date that can be extended for a period of time.

[0029] For ease of description, the following explanation uses a credit card as the payment account as an example to illustrate the various examples involved in this manual.

[0030] The payment account renewal method provided in this specification will be described from both the client-side and business platform perspectives in the following sections. The client-side perspective will primarily illustrate the interactions between the user and the client during the payment account renewal process, as well as the various pages displayed by the client. The business platform perspective will focus more on the backend logic of the payment account renewal process.

[0031] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0032] Client: Figure 1 This is a flowchart illustrating a method for renewing a payment account, as provided in an embodiment of this specification. The method specifically includes the following steps: S100: When a user is detected accessing a specified page of the client, a query request is sent to the business platform to query whether the user is on the list of payment accounts awaiting renewal.

[0033] In practice, users can register an account on the business platform and link it to their existing payment account (such as a credit card). This allows users to use their payment account to complete various transactions mentioned on the platform, based on this linked relationship.

[0034] Since payment accounts have a certain expiration date, users need to renew their payment accounts in a timely manner when they are about to expire or have already expired, in order to ensure that they can continue to use a valid payment account to carry out business on the business platform.

[0035] Currently, payment account renewals often require users to check them periodically, which often leads to many users failing to renew their accounts on time. While some account providers (such as banks) can remind users to renew their payment accounts via SMS, users frequently ignore these reminders, and some phones even block these messages as spam, further preventing timely account renewals.

[0036] Therefore, this specification provides a method for renewing a payment account. When a user uses a client provided by a business platform, the client will detect whether the user has browsed a specified page. Once it is detected that the user has visited the specified page of the client, the client can send a query request to the remote business platform to query whether the user is in the list of payment accounts pending renewal.

[0037] In this specification, the designated page is not limited to a fixed page in the client; its specific form can be various. For example, the homepage displayed to the user by the client can be used as the designated page; another example is the page displayed after entering a designated business entry point, where the designated business entry point can refer to an online business involving the use of a payment account; yet another example is the page in the client used to view account information for the payment account, such as... Figure 2 As shown.

[0038] Figure 2 This is a schematic diagram illustrating an embodiment of the present specification, using the credit card repayment page in the client as the designated page.

[0039] Since users can link their credit cards to their client accounts, the platform has developed a credit card repayment service within the client application to facilitate credit card transactions. Users can complete credit card repayments by accessing the credit card repayment page within the client application.

[0040] Figure 2 This refers to the credit card repayment page displayed to the user by the client, which is the designated page mentioned above. Therefore, when a user visits this page, the client can send a query request to the business platform to check whether the user is on the list of credit cards awaiting renewal, and then remind the user to renew their credit card based on the query results.

[0041] S102: In response to the user being in the list, display renewal reminder information to the user on the designated page.

[0042] In the embodiments described in this specification, the business platform can obtain a list of payment accounts with pending renewals in advance, which can be obtained from the account providers. The actual process by which the business platform obtains this list will be described in detail later in the introduction of the business platform side.

[0043] Therefore, when a client sends a query request to the business platform, the business platform will check whether the user is in the list based on the query request. Being in the list can refer to the user's identifier (such as the user's name) being in the list, or it can refer to the user's payment account identifier (such as a credit card number) being in the list.

[0044] Once a user is confirmed to be on the list, the business platform can send a notification to the client. Upon receiving this notification, the client can then display a renewal reminder to the user on a designated page.

[0045] In the embodiments provided in this specification, the client can display renewal reminder information to the user in different ways, such as Figure 3A and Figure 3B As shown.

[0046] Figure 3A and Figure 3B These are schematic diagrams illustrating two different ways of displaying renewal notification information as provided in the embodiments of this specification.

[0047] exist Figure 3A In the process, when the client determines that a user's credit card needs to be renewed, a prompt box can be displayed below the credit card control shown on the designated page, and the prompt box can display a renewal reminder message to remind the user that the credit card is about to expire.

[0048] Users can access the subsequent credit card renewal process by touching the "Renew Card" control displayed in the prompt box.

[0049] exist Figure 3B In contrast, the renewal reminder information is displayed in the form of a pop-up window. That is, once the client determines that the user's credit card needs to be renewed, it can display a pop-up window on a designated page, which can display the renewal reminder information.

[0050] Furthermore, users can use touch... Figure 3B Use the "Renew Now" button to start the card renewal process and complete the final credit card renewal.

[0051] Of course, in practical applications, the client can also display renewal reminder information to the user in other ways, which will not be listed here.

[0052] It should be noted that, to ensure user information security, the business platform needs to ensure that all business operations performed on users comply with laws and regulations. Therefore, when a user performs a payment account renewal operation in the client, the business platform needs to obtain the user's authorization through the client before it can complete the subsequent payment account renewal process. Figure 4 As shown.

[0053] Figure 4 This is a schematic diagram illustrating how a user performs an authorization operation based on a renewal prompt message displayed on the client, as provided in the embodiments of this specification.

[0054] exist Figure 4 In the context of a mobile application, when a user confirms credit card renewal based on the renewal prompt displayed on the client, the client can display a pop-up window explaining the credit card renewal authorization. Once the user reads this explanation and agrees to authorize the platform, they can tap the [interface / button]. Figure 4 The system displays an "Authorize and Renew Card" control, which then initiates the subsequent credit card renewal process. If the user does not agree to authorize the platform, they can use a touch... Figure 4 If the "Reject" control is displayed, the client will not continue the credit card renewal process, and the user will need to go to the bank or access the bank's application to complete the credit card renewal.

[0055] It should be pointed out that, Figure 4 The pop-up window shown can be accessed by the user through touch. Figure 3A The "Renew Card" control displayed in the image can also be accessed by the user via touch. Figure 3B The "Renew Card Now" control is shown in the image. In practical applications, Figure 4 There are various ways to display pop-up windows in a client application, which can be adapted to the way the client displays renewal prompts to the user. Examples will not be given here.

[0056] To further ensure a better user experience when using the client, in the embodiments provided in this specification, in addition to sending prompts to users based on the user or payment account being on the aforementioned list, the business platform can also determine whether to send prompts to users based on the user profile.

[0057] Once the business platform determines that a user is on the list based on the query results, and determines that the user meets the preset renewal prompt conditions based on the user profile, it can send the aforementioned prompt instruction to the client.

[0058] In practical applications, there are various specific scenarios in which user profiles are used to determine whether a user meets the preset renewal reminder conditions. For example, if the user profile determines that the number of times a user has used their payment account to perform payment transactions exceeds a preset threshold, then the user meets the preset renewal reminder conditions. Another example is if the user profile determines that the frequency of a user's use of their payment account within a given time period exceeds a set frequency threshold; in this case, the user also meets the preset renewal reminder conditions. Other scenarios will not be elaborated upon here.

[0059] S104: Based on the renewal operation performed by the user in response to the renewal prompt information, a renewal request is sent to the account provider corresponding to the user's payment account to be renewed, so that the account provider renews the user's payment account to be renewed based on the renewal request.

[0060] When the client detects that the user has initiated a renewal action in response to the displayed renewal prompt, it can send a renewal request to the account provider corresponding to the payment account to be renewed in order to complete the renewal of the payment account.

[0061] Because the business platform and the account provider are two different entities, when a user needs to renew their payment account on the page provided by the account provider, the account provider must first verify the user's identity and confirm that the user's identity verification is successful before showing the user the payment account renewal page. This greatly reduces the efficiency of the user's payment account renewal.

[0062] Therefore, in the embodiments provided in this specification, the client can send a renewal request to the account provider to obtain a first login-free link for the account provider.

[0063] The so-called first login-free link refers to a link through which users can directly access the account provider's renewal page using the client, without needing to go through an identity verification process.

[0064] Therefore, the first login-free link actually contains a first token that exempts the user from authentication. Thus, when the client sends a first access request to the account provider based on the first login-free link, the account provider can determine that the user has completed login verification based on the first token carried in the first access request, and then return the renewal page provided by the account provider to the client.

[0065] The first token mentioned above can be generated based on the user's identification data, which may include at least one of the following: the user's user identifier (such as the user's name) and the account identifier of the payment account issued by the account provider held by the user (such as a credit card number).

[0066] Therefore, once the account provider obtains the user's identifier and / or account identifier, it can determine that the payment account renewal operation is completed through the credit-granted business platform. Then, it can generate the first token based on the user's identifier data and carry the first token in a specified position in the page link of the renewal page (such as at the end of the page link) to generate the aforementioned first login-free link.

[0067] During the process of obtaining the first login-free link on the client side, the business platform needs to send the user's identification data to the account provider. Since the user's identification data is sensitive privacy data, it needs to be anonymized before it can be sent.

[0068] Therefore, when the client determines that the user needs to renew the payment account, it will send a request to the business platform. The business platform will then send the user's de-identified identifier to the account provider based on the received request. This allows the account provider to determine the user's identifier data locally based on the de-identified identifier, thereby generating the aforementioned first token. The first login-free link generated based on the first token will then be returned to the user's client via the business platform.

[0069] During this process, the account provider can de-identify the locally stored user identification data using the same de-identification method to obtain each matching identifier. Then, by comparing the obtained de-identified identifiers with each matching identifier, the identifier data corresponding to the matched identifier is determined to be the user's identifier data.

[0070] In the embodiments provided in this specification, there can be various specific de-identification methods. For example, the business platform can concatenate the user's identifier and the payment account's identifier to obtain a concatenated string, and then use a hash algorithm to hash this string to obtain the de-identified identifier. When the account provider obtains the de-identified identifier, it can use the same method to concatenate the user identifiers of each user and their corresponding payment account identifiers stored locally, and then use a hash algorithm to hash them to obtain various hashed strings, which are the identifiers to be matched. Then, by comparing the de-identified identifiers with the identifiers to be matched, the user's identifier data can be determined. Other methods will not be illustrated here.

[0071] Based on the aforementioned first login-free link, the client can display a renewal page provided by the account provider to the user, allowing the user to renew their payment account. The renewal page is as follows: Figure 5A As shown.

[0072] Figure 5AThis is a schematic diagram of a bank's renewal page displayed in a client, as provided in an embodiment of this specification.

[0073] In practical applications, the client comes with a browser. The client can then use the browser to parse the first login-free link and generate a first access request for the renewal page provided by the banking institution.

[0074] Upon receiving the first access request, the banking institution can use the first token carried in the request to confirm that the user has completed login verification, and then display the information to the user. Figure 5A The renewal page shown.

[0075] It should be noted that, in Figure 5A The displayed page also includes options to prompt users whether they need to renew their physical card, allowing them to choose according to their needs. This instruction manual primarily focuses on the electronic renewal and activation process for payment accounts; the renewal and activation of physical cards requires selection... Figure 5A The option to renew a physical card is available on the bank's website, where users can fill in information such as the card delivery address.

[0076] Furthermore, to further improve the efficiency of users' payment account renewals, in the embodiments provided in this specification, the business platform can send a first bounce link along with the aforementioned de-identified identifier to the account provider. In this way, the account provider can return a first login-free link to the client based on the page link of the renewal page, the first token generated based on the de-identified identifier, and the first bounce link.

[0077] Once the user completes the payment account renewal on the renewal page, the client can receive a response message from the account provider carrying a first redirect instruction. By executing this first redirect instruction, the aforementioned first bounce link can be redirected, thereby displaying the renewal result page provided by the business platform to the user. The renewal result page is as follows: Figure 5B As shown.

[0078] Figure 5B This is a schematic diagram of the page displayed in the client to complete the renewal, provided as an embodiment of this specification.

[0079] Figure 5B The renewal result page displayed is provided by the business platform. Therefore, the first redirect link mentioned above is actually a link that the business platform will use to redirect from the bank's page back to the business platform page as a redirect parameter, which is pre-embedded in the first login-free link. In this way, once the user completes the credit card renewal, the client can automatically redirect back to the business platform page without the user having to manually perform the redirect operation, thus improving the efficiency of the user's credit card renewal.

[0080] The payment account renewal method provided in the embodiments of this specification can promptly remind users when their payment accounts are pending renewal, thereby enabling users to complete the renewal of their payment accounts in a timely manner based on the reminder, thus ensuring the normal use of the payment accounts.

[0081] In addition, since there are many payment account organizations in practical applications, and payment accounts under different account organizations have their own style characteristics, in order to further present the differences in renewal styles for different account organizations to users, in the embodiments provided in this specification, the client obtains the organization identification code corresponding to the payment account to be renewed by the user, and determines the visual presentation resources corresponding to the organization identification code. Different account organizations correspond to different organization identification codes.

[0082] In this context, account organizations and account providers are distinct concepts. Account organizations are primarily responsible for specifying the various transaction rules for payment accounts within their organization, while account providers are the institutions that actually issue payment accounts. For example, UnionPay is an account organization, while banks are account providers.

[0083] For example, for credit cards, different card bins correspond to different card organizations (i.e., account organizations). For instance, when the card bin is 6, it means that the card organization for the credit card is UnionPay, and when the card bin is 4, it means that the card organization for the credit card is VISA.

[0084] The visual presentation resources mentioned above are primarily used to demonstrate the specific style or visual effects used to present the payment account to the user. For example, a visual presentation resource could be a two-dimensional image; in this case, identifying the visual presentation resource based on the organization's identification code essentially means identifying the two-dimensional image of the user's credit card to be renewed. Alternatively, a visual presentation resource could be a three-dimensional model; in this case, identifying the visual presentation resource based on the organization's identification code essentially means identifying the three-dimensional model of the user's credit card to be renewed. Figure 6A and 6B As shown.

[0085] Figure 6A and Figure 6B This specification provides an example of displaying renewal pages for credit cards from different institutions in the client application using different visual presentation resources.

[0086] When the user's credit card is identified as a UnionPay card based on the organization code of the card to be renewed, the system can then display the relevant information to the user. Figure 6A The renewal notification shown displays an image of a credit card from the UnionPay card organization.

[0087] When the user's credit card is identified as a VISA card based on the organization code of the card to be renewed, the system can then display the relevant information to the user. Figure 6B The renewal notification shown displays an image of a VISA credit card.

[0088] The specific forms of visual presentation resources under other account organizations will not be listed one by one.

[0089] After a user renews their payment account, they usually need to activate it. Therefore, the client can display an activation prompt message to the user after detecting that the payment account has been renewed. The client can display the activation prompt message in several locations, such as on the designated page mentioned above, or on the renewal result page displayed after the user completes the account renewal.

[0090] Once the client detects that the user has performed an activation operation in response to the activation prompt, it can send an activation request to the account provider, which can then activate the user's payment account based on the activation request.

[0091] Similar to the account renewal mentioned above, to facilitate user activation, the client can obtain a second login-free link from the account provider based on the activation request sent to the account provider. This second login-free link is generated based on the user's second token, which is generated based on the user's identification data.

[0092] Therefore, the client can send a second access request to the account provider based on the second login-free link. The account provider can determine that the user has completed login verification through the second token carried in the second access request, and then return the activation page provided by the account provider to the client.

[0093] The generation method for the second token mentioned above is essentially the same as the generation method for the first token mentioned above. It can be implemented based on the user's identifier data determined by the de-identified identifier provided by the business platform to the account provider. The entire process is similar to the payment account renewal stage described above, and will not be detailed here.

[0094] The second login-free link mentioned above is generated based on the second token and the activation page link provided by the account provider. The activation page displayed by the account provider is as follows: Figure 7A As shown.

[0095] Figure 7AThis is a schematic diagram of the activation page of a banking institution displayed in the client, provided as an embodiment of this specification.

[0096] Based on the second login-free link mentioned above, the client can display the following to the user: Figure 7A The activation page shown is a bank's page, where users can activate their credit cards.

[0097] Of course, the second login-free link mentioned above can also carry a second jump link. This second jump link has a similar function to the first jump link mentioned above, so that when the user completes the activation operation on the activation page displayed on the client, he / she can be automatically redirected back to the activation result page displayed on the business platform.

[0098] The entire redirection process is essentially the same as that based on the first redirect link. That is, after the user activates their payment account on the activation page, the client receives a response message from the account provider carrying a second redirection instruction. The client executes this second redirection instruction to redirect the second redirect link, thereby displaying the activation result page provided by the business platform to the user, such as... Figure 7B As shown.

[0099] Figure 7B This is a schematic diagram of the activated page displayed in the client as provided in the embodiments of this specification.

[0100] Figure 7B The activation result page displayed is provided by the business platform. Therefore, the second redirect link mentioned above is actually a link that the business platform pre-embeds as a redirect parameter into the second login-free link, redirecting the user from the bank's page back to the business platform page. This way, once the user completes credit card activation, the client automatically redirects back to the business platform page without requiring the user to manually perform the redirection, thus improving the efficiency of credit card activation.

[0101] The above describes the basic process of the client executing the payment account renewal method. Below, we will describe the payment account renewal method provided in the embodiments of this specification from the perspective of the business platform.

[0102] Business Platform: Figure 8 This is a flowchart illustrating a method for renewing a payment account, as provided in an embodiment of this specification. The method specifically includes the following steps: S800: Receives a query request sent by the user through the client.

[0103] As mentioned above, when a user visits a designated page on the client, a query can be triggered to check with the business platform whether the user is on the list of pending renewals. At this time, the business platform will receive the query request sent by the user through the client.

[0104] It should be noted that the execution logic of the business platform described in this specification is actually completed by the devices of the business platform. The devices of the business platform may include electronic devices such as servers or server clusters. For ease of description, this specification refers to the devices that actually perform each operation as the business platform.

[0105] S802: Based on the query request, query whether the user is in the pre-obtained list of payment accounts awaiting renewal.

[0106] As mentioned in step S102 above, the business platform needs to obtain the list of payment accounts to be renewed in advance. Therefore, the business platform can obtain the renewal files sent by each account provider in advance and parse out each matching identifier from the renewal files.

[0107] The matching identifiers mentioned here actually serve a similar purpose to the de-identified identifiers mentioned above. That is, in order to ensure the security of users' privacy data, account providers cannot directly send users' identifier data in plaintext to the business platform. They need to de-identify the data to obtain the various matching identifiers.

[0108] Once the business platform parses out the aforementioned identifiers to be matched, it can perform the same de-identification process on the locally stored identifier data for each user, thereby obtaining each de-identified identifier. Then, by matching each identifier to be matched with each de-identified identifier, the list of users awaiting renewal is determined. The specific process is as follows: Figure 9 As shown.

[0109] Figure 9 This is a schematic diagram illustrating the process by which the business platform, as provided in the embodiments of this specification, obtains a list of payment accounts awaiting renewal in advance.

[0110] Banks can anonymize the list of cardholders whose cards are due for renewal compiled on the previous day (i.e., day T) in the early morning of day T+1, obtain the renewal document, and send the renewal document to the Secure File Transfer Protocol (SFTP) platform.

[0111] The SFTP platform employs encrypted network protocols to ensure that data transmission is not intercepted or tampered with during the bank's data transmission process, thereby improving the security of data transmission.

[0112] Afterwards, the data warehouse in the business platform can download and parse the renewal file from the SFTP platform, and use the locally stored uid and card index to associate the uid and card index recorded in the renewal file.

[0113] Afterwards, the data warehouse can send the associated UID and card index to the data platform, which will then determine the list of users who actually need to renew their cards based on the UID and card index and return it to the data warehouse.

[0114] The above process is actually completed in an offline environment. Therefore, the data warehouse also needs to send the list of users with pending card renewals to the online database so that the business platform can query the online database to see if the user is in the list of users with pending card renewals after receiving the query request.

[0115] S804: In response to the user being in the list, instruct the client to display a renewal prompt to the user on the designated page so that the user can renew their payment account.

[0116] Once the business platform determines that a user is on the list, it can send a prompt instruction to the client, which will then display a renewal prompt to the user so that the user can renew their payment account.

[0117] The general process for renewing a payment account has been covered above. The following section will detail the process, which is mainly divided into the account renewal stage and the account activation stage, respectively. Figure 10A and Figure 10B .

[0118] Figure 10A This is a detailed schematic diagram illustrating the process of renewing a credit card by redirecting to the renewal page of a banking institution, as provided in the embodiments of this specification.

[0119] When a user visits a designated page on the client, the client can display a renewal prompt message. Based on this message, the user can confirm the renewal, allowing the business platform to send an authorization reminder (e.g., ...) to the user via the client. Figure 4 (The page).

[0120] Once the business platform confirms that the user has agreed to the authorization, it can record the user's authorization record locally and query the renewal status of the credit card.

[0121] The business platform checks the credit card renewal status here to prevent situations where users have already completed the renewal by visiting the bank's website (because between the time the business platform receives the renewal document sent by the bank and the time the user visits the specified page on the client, the user may have already completed the renewal process).

[0122] Therefore, when the user's credit card is confirmed to be pending renewal based on the credit card renewal status returned by the bank, a request can be sent to the bank to obtain the first login-free link, and the user's de-identified identifier and the first bounce link can be transmitted.

[0123] The bank, by processing the anonymized identifier transmitted from the business platform, can determine the user's identification data, thereby identifying the user's first token. Based on the user's first token, the first redirect link, and the page link on the card renewal page, the bank returns the first login-free link to the business platform. The business platform then returns the first login-free link to the client.

[0124] The client's browser will parse the first login-free link and generate a first access request carrying the first token, which will be sent to the bank, thereby redirecting the user to the bank's card renewal page.

[0125] During this process, the bank uses the first token carried in the first access request to confirm that the user has completed the login verification, and then returns the card renewal page to the client.

[0126] After the user completes the card renewal, the client displays the card renewal result page of the business platform to the user by redirecting the first bounce link.

[0127] During this process, the business platform also needs to send a request to the bank to check the credit card renewal status to ensure that the user has actually completed the renewal. Based on the credit card renewal status returned by the bank, the business platform can update the locally stored credit card renewal status. This update only concerns whether the renewal has been completed and does not involve updating other information (such as the new expiration date of the credit card after renewal).

[0128] Once the local status update is complete, the renewal result page of the business platform can be displayed to the user.

[0129] Afterwards, the business platform will receive a status notification from the bank, which includes an anonymized identifier, credit card status, expiration date, etc. Using this anonymized identifier, the business platform can determine which user's credit card the bank is sending the status information for, and then further update the credit card status locally based on the information contained in the status notification.

[0130] Because banks need time to determine data such as the expiration date after credit card renewal and generate anonymized labels, the business platform can... Figure 10AIn steps S113 and S114, it is first determined whether the user has completed the card renewal. Compared with the business platform having to wait to receive the above status notification before showing the card renewal result page to the user, this method can quickly show the card renewal result page to the user, reducing the user's waiting time.

[0131] Figure 10B This is a detailed interactive diagram illustrating how credit card activation is completed by redirecting to a bank's activation page, as provided in the embodiments of this specification.

[0132] Figure 10B and Figure 10A The process is basically similar, except that some actions and acquired information are replaced with activation-related information. The entire process can be found in [link to documentation]. Figure 10A The details of that will not be elaborated upon here.

[0133] Furthermore, as can be seen from the account renewal and activation process described above, users need to access the payment account page in the client to complete the renewal and activation, which actually reduces the efficiency of user renewal and activation to some extent.

[0134] Therefore, this specification provides an embodiment that allows users to renew and activate their accounts without having to do so on their payment accounts.

[0135] Specifically, after receiving the first authorization request from the client, the business platform can determine the account provider corresponding to the user's payment account to be renewed based on this first authorization request. This first authorization request is generated by the client based on the user's renewal authorization operation in response to the renewal prompt information (e.g., the user can authorize it via touch). Figure 4 The "Authorize and Renew Card" control in the document generates the first authorization request through the client.

[0136] The business platform can pre-build dedicated interfaces with various account providers. These dedicated interfaces can ensure that the business platform and the account providers transmit data in a secure network environment. Moreover, these dedicated interfaces actually enable the business platform to complete the subsequent processes of renewal or activation on behalf of the user.

[0137] Therefore, after identifying the account provider corresponding to the user's payment account to be renewed, the business platform can call the first dedicated interface with that account provider. However, the business platform can only call this first dedicated interface if the user authorizes the business platform to complete the account renewal on their behalf. Otherwise, the business platform will not call the first dedicated interface and can instead redirect the user to the account provider's page to complete the account renewal operation, as described above.

[0138] The business platform can send a renewal request to the account provider based on this first dedicated interface, thereby enabling the account provider to renew the user's payment account that is pending renewal based on the renewal request.

[0139] The activation process is basically the same as the renewal process described above.

[0140] In other words, after receiving a second authorization request from the client, the business platform can invoke a second dedicated interface between the business platform and the account provider based on this second authorization request. This second authorization request is generated by the client based on the activation authorization operation performed by the user in response to the activation prompt information.

[0141] Similarly, the business platform can only call the second dedicated interface if the user authorizes the business platform to complete the account activation on their behalf. Otherwise, the business platform will not call the second dedicated interface and can redirect the user to the account provider's page as described above, allowing the user to complete the account activation operation.

[0142] Afterwards, the business platform can send an activation request to the account provider based on this second dedicated interface, thereby enabling the account provider to activate the user's payment account to be activated based on the activation request.

[0143] The entire renewal and activation process is as follows: Figure 11 As shown.

[0144] Figure 11 This is a detailed interactive diagram illustrating how to complete credit card renewal and activation without redirecting to a bank's page, as provided in the embodiments of this specification.

[0145] Figure 11 The process shown is basically already in Figure 10A and Figure 10B This is reflected in [the text], but the difference is that [the text] is [not specified]. Figure 11 The process shown does not involve the client displaying the bank's pages (including the card renewal page and the activation page) based on the login-free links (including the first login-free link and the second login-free link).

[0146] Users only need to send an authorized request to the business platform through the client, and the business platform can complete the subsequent card renewal and activation process on their behalf. The business platform only needs to display the final result page (such as the card renewal result page and the activation result page) to the user through the client, which brings great convenience to the user's card renewal and activation process.

[0147] It should be noted that, for activation prompts, the client can also use the identified organization identifier to determine the corresponding visual presentation resources, and thus display activation prompts for payment accounts under different account organizations according to their style characteristics.

[0148] The above describes one or more embodiments of a payment account renewal method provided in this specification. Based on the same concept, this specification also provides a payment account renewal device, such as... Figure 12 and Figure 13 As shown.

[0149] Figure 12 A schematic diagram of a payment account renewal device provided in this specification embodiment specifically includes: The query module 1200, when it detects that a user has accessed a specified page of the client, sends a query request to the business platform to query whether the user is on the list of payment accounts pending renewal; Display module 1202, in response to the user being in the list, displays renewal prompt information to the user on the designated page; The request module 1204, based on the renewal operation performed by the user in response to the renewal prompt information, sends a renewal request to the account provider corresponding to the user's payment account to be renewed, so that the account provider renews the user's payment account to be renewed based on the renewal request.

[0150] Optionally, the display module 1202 is specifically used to: receive a prompt instruction sent by the business platform, wherein the prompt instruction is sent by the business platform to the client after determining that the user is in the list based on the obtained query results and that the user meets the preset renewal prompt conditions based on the user profile; and display renewal prompt information to the user on the specified page based on the prompt instruction.

[0151] Optionally, the request module 1204 is specifically configured to: send a renewal request to the account provider based on the renewal operation performed by the user in response to the renewal prompt information, to obtain a first login-free link for the account provider, the first login-free link being generated based on a first token corresponding to the user, the first token being generated based on the user's identification data, the identification data including at least one of: the user's user identifier and the account identifier of the payment account issued by the account provider held by the user; send a first access request to the account provider based on the first login-free link, so that the account provider determines that the user has completed login verification based on the first token carried in the first access request, and returns the renewal page provided by the account provider to the client; and display the renewal page to the user for the user to renew the payment account.

[0152] Optionally, the request module 1204 is specifically configured to send the user's de-identified identifier to the account provider through the business platform, so that the account provider can determine the user's identifier data based on the user's de-identified identifier, generate a first token corresponding to the user based on the user's identifier data, and return the first login-free link according to the first token corresponding to the user and the page link corresponding to the renewal page. The user's de-identified identifier is obtained by de-identifying the user's identifier data; the account provider matches the user's de-identified identifier with each matching identifier to determine the user's identifier data, and each matching identifier is obtained by de-identifying the identifier data of each user stored locally by the account provider.

[0153] Optionally, the request module 1204 is specifically used to send the user's de-identified identifier and the first bounce link to the account provider through the business platform, so that the account provider generates the first token based on the user's de-identified identifier, and returns the first login-free link according to the first token, the page link corresponding to the renewal page and the first bounce link; The request module 1204 is further configured to, after the user completes the payment account renewal based on the renewal page, receive a response message carrying a first redirection instruction sent by the account provider; execute the first redirection instruction to display the renewal result page provided by the business platform to the user based on the redirection of the first bounce link.

[0154] Optionally, the display module 1202 is specifically used to display a prompt pop-up window to the user on the designated page, and to display the renewal prompt information in the prompt pop-up window.

[0155] Optionally, the renewal prompt information includes visual presentation resources of the user's payment account to be renewed, and the visual presentation resources are used to represent the appearance of the payment account; The display module 1202 is specifically used to determine the visual presentation resources corresponding to the organization identification code of the user's payment account to be renewed, with different organization identification codes corresponding to different account organizations; and to display renewal prompt information to the user on the designated page according to the determined visual presentation resources.

[0156] Optionally, the display module 1202 is further configured to display an activation prompt message to the user after the user completes the renewal of the payment account; The request module 1204 is further configured to send an activation request to the account provider based on the activation operation performed by the user in response to the activation prompt information, so that the account provider activates the user's payment account to be activated based on the activation request.

[0157] Optionally, the request module 1204 is specifically configured to: send an activation request to the account provider based on the activation operation performed by the user in response to the activation prompt information, to obtain a second login-free link for the account provider, the second login-free link being generated based on a second token corresponding to the user, the second token being generated based on the user's identification data, the identification data including at least one of: the user's user identifier and the account identifier of the payment account issued by the account provider held by the user; send a second access request to the account provider based on the second login-free link, so that the account provider determines that the user has completed login verification based on the second token carried in the second access request, and returns the activation page provided by the account provider to the client; and display the activation page to the user for the user to activate the payment account.

[0158] Optionally, the request module 1204 is specifically configured to send the user's de-identified identifier to the account provider through the business platform, so that the account provider can determine the user's identifier data based on the user's de-identified identifier, generate the second token based on the user's identifier data, and return the second login-free link according to the second token and the page link corresponding to the activation page; The user's de-identified identifier is obtained by de-identifying the user's identifier data; the account provider matches the user's de-identified identifier with each matching identifier to determine the user's identifier data, and each matching identifier is obtained by de-identifying the identifier data of each user stored locally by the account provider.

[0159] Optionally, the request module 1204 is specifically used to send the user's de-identified identifier and the second bounce link to the account provider through the business platform, so that the account provider generates the second token based on the user's de-identified identifier, and returns the second login-free link according to the second token, the page link corresponding to the activation page, and the second bounce link; The request module 1204 is further configured to, after the user completes payment account activation based on the activation page, receive a response message carrying a second redirection instruction sent by the account provider; execute the second redirection instruction to display the activation result page provided by the business platform to the user based on the redirection of the second bounce link.

[0160] Figure 13 A schematic diagram of a payment account renewal device provided in this specification embodiment specifically includes: The receiving module 1300 receives a query request sent by a user through the client, the query request being sent by the client when it detects that the user has accessed a specified page; The query module 1302 queries whether the user is in the pre-acquired list of payment accounts awaiting renewal, based on the query request. The instruction module 1304, in response to the user being in the list, instructs the client to display a renewal prompt message to the user on the designated page so that the user can renew their payment account.

[0161] Optionally, before receiving a query request sent by a user through the client, the receiving module 1300 is further configured to obtain a list of payment accounts awaiting renewal; wherein Obtain renewal documents sent by each account provider; parse out each matching identifier recorded in the renewal documents. For each matching identifier, the matching identifier is obtained by anonymizing the user's identifier data, which includes at least one of the user's user identifier and the account identifier of the payment account held by the user; match each matching identifier with each anonymized identifier locally on the business platform, and obtain the list based on the matching results. Each anonymized identifier is obtained by anonymizing the identifier data of each user stored on the business platform.

[0162] Optionally, the instruction module 1304 is specifically configured to: receive a first authorization request sent by the client, the first authorization request being generated by the client based on the renewal authorization operation performed by the user in response to the renewal prompt information; determine the account provider corresponding to the user's payment account to be renewed according to the first authorization request, and call a first dedicated interface between the business platform and the account provider, the first dedicated interface being called after the first authorization request confirms that the user authorizes the business platform to complete the payment account renewal on behalf of the user; and send a renewal request to the account provider based on the first dedicated interface, so that the account provider renews the user's payment account to be renewed based on the renewal request.

[0163] Optionally, the receiving module 1300 is specifically configured to: receive a second authorization request sent by the client, the second authorization request being generated by the client based on the activation authorization operation performed by the user in response to the activation prompt information, the activation prompt information being displayed to the user on the designated page after the user completes the renewal of the payment account; according to the second authorization request, call a second dedicated interface between the business platform and the account provider, the second dedicated interface being called after the second authorization request confirms that the user authorizes the business platform to complete the payment account activation on behalf of the user; and based on the second dedicated interface, send an activation request to the account provider, so that the account provider activates the user's payment account to be activated based on the activation request.

[0164] The above-described device embodiments correspond to the embodiments of the payment account renewal method. For detailed explanations, please refer to the description in the embodiments section of the payment account renewal method; further details will not be repeated here. The device embodiments are based on the payment account renewal method and have the same technical effects as the corresponding payment account renewal method embodiments. For detailed explanations, please refer to the corresponding payment account renewal method embodiments.

[0165] This specification also provides an embodiment of a computer storage medium that can store multiple instructions adapted to be loaded and executed by a processor as described above. Figure 1 or Figure 8 The method described in the illustrated embodiment can be found in the following document for a detailed execution process. Figure 1 or Figure 8 The specific details of the illustrated embodiments will not be elaborated here.

[0166] This specification also provides a computer program product that stores at least one instruction, said at least one instruction being loaded and executed by the processor as described above. Figure 1 or Figure 8The method described in the illustrated embodiment can be found in the following document for a detailed execution process. Figure 1 or Figure 8 The specific details of the illustrated embodiments will not be elaborated here.

[0167] Based on the same concept as the methods described above, embodiments of this specification also provide an electronic device, including: a processor; and a memory for storing processor-executable instructions; wherein the processor executes the executable instructions to implement the steps of the method as described in any of the above embodiments, and the specific execution process can be found in [reference needed]. Figure 1 or Figure 8 The specific details of the illustrated embodiments will not be elaborated here.

[0168] Figure 14 This is a schematic structural diagram of a device provided in this manual. Please refer to it. Figure 14 At the hardware level, the device includes a processor 1402, an internal bus 1404, a network interface 1406, memory 1408, and non-volatile memory 1410, and may also include other hardware required for its functions. One or more embodiments of this specification can be implemented in software, for example, the processor 1402 reads the corresponding computer program from the non-volatile memory 1410 into memory 1408 and then runs it. Of course, besides software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution entity of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0169] Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0170] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0171] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0172] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0173] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware components.

[0174] Those skilled in the art will understand that embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied 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.

[0175] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. 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, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0176] 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, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0177] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0178] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0179] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0180] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0181] It should also be noted that 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. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0182] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied 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.

[0183] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0184] The various embodiments in this specification 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 system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0185] The above description is merely an embodiment of this specification and is not intended to limit this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for renewing a payment account, the method being applied to a client provided by a business platform, wherein a user binds a payment account issued by an account provider to the user with a platform account registered by the user on the business platform through the client, so as to perform business on the business platform through the bound payment account, comprising: When a user is detected accessing a specified page of the client, a query request is sent to the business platform to check whether the user is on the list of payment accounts awaiting renewal. In response to the user being on the list, a renewal reminder message is displayed to the user on the designated page; Based on the user's renewal operation in response to the renewal prompt information, a renewal request is sent to the account provider corresponding to the user's payment account to be renewed, so that the account provider can renew the user's payment account based on the renewal request.

2. The method of claim 1, wherein in response to the user being in the list, displaying a renewal prompt message to the user on the designated page includes: The system receives a prompt instruction sent by the business platform. The prompt instruction is sent to the client by the business platform after determining that the user is in the list based on the obtained query results and that the user meets the preset renewal prompt conditions based on the user profile. Based on the prompt instruction, a renewal prompt message is displayed to the user on the designated page.

3. The method as described in claim 1, wherein based on the renewal operation performed by the user in response to the renewal prompt information, a renewal request is sent to the account provider corresponding to the user's payment account to be renewed, so that the account provider renews the user's payment account to be renewed based on the renewal request, comprising: Based on the user's renewal operation in response to the renewal prompt information, a renewal request is sent to the account provider to obtain a first login-free link for the account provider. The first login-free link is generated based on a first token corresponding to the user. The first token is generated based on the user's identification data, which includes at least one of the user's user identifier and the account identifier of the payment account issued by the account provider held by the user. Based on the first login-free link, a first access request is sent to the account provider, so that the account provider determines that the user has completed login verification based on the first token carried in the first access request, and returns the renewal page provided by the account provider to the client; The user is shown the renewal page so that they can renew their payment account.

4. The method of claim 3, wherein obtaining the first login-free link for the account provider includes: The business platform sends the user's de-identified identifier to the account provider, so that the account provider can determine the user's identifier data based on the user's de-identified identifier, generate a first token corresponding to the user based on the user's identifier data, and return the first login-free link according to the first token corresponding to the user and the page link corresponding to the renewal page. The user's de-identified identifier is obtained by de-identifying the user's identifier data; The account provider matches the user's de-identified identifier with each identifier to be matched to determine the user's identifier data. Each identifier to be matched is obtained by de-identifying the identifier data of each user stored locally by the account provider.

5. The method of claim 4, wherein obtaining the first login-free link for the account provider includes: The business platform sends the user's de-identified identifier and the first bounce link to the account provider, so that the account provider generates the first token based on the user's de-identified identifier, and returns the first login-free link based on the first token, the page link corresponding to the renewal page, and the first bounce link; The method further includes: After the user completes the payment account renewal based on the renewal page, a response message carrying a first redirection instruction is received from the account provider; The first redirection instruction is executed to display the renewal result page provided by the business platform to the user based on the redirection of the first bounce link.

6. The method of claim 1, wherein displaying renewal prompt information to the user on the designated page includes: A pop-up notification window is displayed to the user on the designated page, and the renewal notification information is displayed in the pop-up notification window.

7. The method as described in claim 1 or 6, wherein the renewal prompt information includes visual presentation resources of the user's payment account to be renewed, and the visual presentation resources are used to represent the appearance of the payment account; On the designated page, display renewal notification information to the user, including: Based on the organization identification code corresponding to the user's payment account pending renewal, determine the visual presentation resources corresponding to the organization identification code, with different organization identification codes corresponding to different account providers; Based on the determined visual presentation resources, a renewal prompt message is displayed to the user on the designated page.

8. The method of claim 1, further comprising: After the user completes the payment account renewal, an activation prompt message is displayed to the user; Based on the activation operation performed by the user in response to the activation prompt information, an activation request is sent to the account provider so that the account provider can activate the user's payment account to be activated based on the activation request.

9. The method of claim 8, wherein based on the activation operation performed by the user in response to the activation prompt information, an activation request is sent to the account provider, so that the account provider activates the user's payment account to be activated based on the activation request, comprising: Based on the activation operation performed by the user in response to the activation prompt information, an activation request is sent to the account provider to obtain a second login-free link for the account provider. The second login-free link is generated based on a second token corresponding to the user. The second token is generated based on the user's identification data, which includes at least one of the user's user identifier and the account identifier of the payment account issued by the account provider held by the user. Based on the second login-free link, a second access request is sent to the account provider, so that the account provider determines that the user has completed login verification based on the second token carried in the second access request, and returns the activation page provided by the account provider to the client; The activation page is displayed to the user so that the user can activate their payment account.

10. The method of claim 9, wherein obtaining a second login-free link for the account provider includes: The business platform sends the user's de-identified identifier to the account provider, so that the account provider can determine the user's identifier data based on the de-identified identifier, generate the second token based on the user's identifier data, and return the second login-free link according to the second token and the page link corresponding to the activation page; The user's de-identified identifier is obtained by de-identifying the user's identifier data; The account provider matches the user's de-identified identifier with each identifier to be matched to determine the user's identifier data. Each identifier to be matched is obtained by de-identifying the identifier data of each user stored locally by the account provider.

11. The method of claim 10, wherein obtaining a second login-free link for the account provider includes: The business platform sends the user's de-identified identifier and the second bounce link to the account provider, so that the account provider generates the second token based on the user's de-identified identifier, and returns the second login-free link according to the second token, the page link corresponding to the activation page, and the second bounce link; The method further includes: After the user completes payment account activation based on the activation page, a response message carrying a second redirection instruction is received from the account provider; The second redirection instruction is executed to display the activation result page provided by the business platform to the user based on the redirection of the second bounce link.

12. A method for renewing a payment account, the method being applied to a business platform, wherein a user, through a client provided by the business platform, binds a payment account issued by an account provider to the user to a platform account registered by the user on the business platform, so as to perform business on the business platform through the bound payment account, comprising: The client receives a query request sent by a user through the client, the query request being sent when the client detects that the user has accessed a specified page; Based on the query request, check whether the user is on the pre-obtained list of payment accounts awaiting renewal; In response to the user being on the list, the client is instructed to display a renewal prompt to the user on the designated page so that the user can renew their payment account.

13. The method as described in claim 1, wherein obtaining the list of payment accounts awaiting renewal includes: Obtain renewal documents sent by each account provider; Parse out each matching identifier recorded in the renewal file. For each matching identifier, the matching identifier is obtained by de-identifying the user's identifier data. The identifier data includes at least one of the user's user identifier and the account identifier of the payment account held by the user. The business platform locally matches each identifier to be matched with each de-identified identifier, and obtains the list based on the matching results. Each de-identified identifier is obtained by de-identifying the identifier data of each user stored in the business platform.

14. The method of claim 12, wherein in response to the user being in the list, the client is instructed to display a renewal prompt message to the user on the designated page for the user to renew their payment account, comprising: The client receives a first authorization request, which is generated by the client based on the user's renewal authorization operation in response to the renewal prompt information. Based on the first authorization request, the account provider corresponding to the user's payment account to be renewed is determined, and the first dedicated interface between the business platform and the account provider is called. The first dedicated interface is called after the first authorization request confirms that the user authorizes the business platform to complete the payment account renewal on behalf of the user. Based on the first dedicated interface, a renewal request is sent to the account provider, so that the account provider can renew the user's payment account pending renewal based on the renewal request.

15. The method of claim 12, further comprising: The client receives a second authorization request, which is generated by the client based on the activation authorization operation performed by the user in response to the activation prompt information. The activation prompt information is displayed to the user on the designated page after the user completes the renewal of the payment account. According to the second authorization request, the second dedicated interface between the business platform and the account provider is invoked. The second dedicated interface is invoked after the second authorization request confirms that the user authorizes the business platform to complete the payment account activation on behalf of the user. Based on the second dedicated interface, an activation request is sent to the account provider so that the account provider can activate the user's payment account to be activated based on the activation request.

16. An electronic device comprising: processor; A memory for storing processor-executable instructions; wherein the processor implements the steps of the method as described in any one of claims 1 to 15 by executing the executable instructions.

17. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any one of claims 1 to 15.

18. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 15.

Images