Payment card binding method, device, equipment, system and medium

Abstract

The invention discloses a payment card binding method, device, equipment, system and medium, and belongs to the technical field of payment. The method comprises the following steps: after a third-party payment platform completes user identity authorization, forwarding a payment card information request message of the third-party payment platform to at least one card management platform; a payment card information response message is sent to the third-party payment platform, the payment card information response message is generated according to fed-back card information of multiple payment cards matched with the user identity information, and the payment card information response message is used for indicating the third-party payment platform to display related information of the multiple payment cards to the user; and under the condition that the verification code corresponding to the target payment card indicated by the selection input of the user passes verification, forwarding a card binding message generated by binding the target payment card with the third-party payment platform to the target card management platform, the card binding message being used for binding the third-party payment platform and the target payment card with the target card management platform. According to the embodiment of the invention, the payment card binding operation can be simplified.

Description

Technical Field

[0001] This application belongs to the field of payment technology, and in particular relates to a payment card binding method, device, equipment, system and medium. Background Technology

[0002] With the continuous development of electronic payment technology, users can bind their payment cards to third-party payment platforms, enabling them to make payments through these platforms. The binding process requires users to manually enter their card number, user information, and other details for authorization. Verification using dynamic information completes the binding process. However, each authorization and verification session only binds one payment card. If a user needs to bind multiple payment cards to a third-party payment platform, multiple authorizations and verifications are required, making the process cumbersome. Summary of the Invention

[0003] This application provides a payment card binding method, apparatus, device, system, and medium that can simplify the payment card binding process.

[0004] In a first aspect, embodiments of this application provide a payment card binding method applied to a payment switching platform. The method includes: after a third-party payment platform completes user identity authorization, forwarding a payment card information request message from the third-party payment platform to at least one card management platform, the payment card information request message including user identity information; sending a payment card information response message to the third-party payment platform, the payment card information response message being generated based on card information of multiple payment cards matching the user identity information fed back by at least one card management platform, the payment card information response message being used to instruct the third-party payment platform to display relevant information of the multiple payment cards matching the user identity information to the user; and, if the verification code corresponding to the target payment card selected and entered by the user is successfully verified, forwarding a card binding message generated by the third-party payment platform to the target card management platform, the card binding message being used to bind the third-party payment platform and the target payment card to the target card management platform, the target card management platform corresponding to the target payment card indicated by the card binding message.

[0005] Secondly, embodiments of this application provide a payment card binding method applied to a third-party payment platform. The method includes: after completing user identity authorization, sending a payment card information request message to a payment switching platform, causing the payment switching platform to forward the payment card information request message to at least one card management platform; the payment card information request message includes user identity information; receiving a payment card information response message sent by the payment switching platform, the payment card information response message being generated based on card information of multiple payment cards matching the user identity information fed back by at least one card management platform; displaying relevant information of the multiple payment cards matching the user identity information to the user based on the payment card information response message; and, if the verification code corresponding to the target payment card indicated by the user's selected input is successfully verified, sending a binding message generated by binding the target payment card to the payment switching platform, causing the payment switching platform to forward the binding message to the target card management platform, the binding message being used to bind the third-party payment platform and the target payment card to the target card, the target card management platform corresponding to the target payment card indicated by the binding message.

[0006] Thirdly, embodiments of this application provide a payment card binding device applied to a payment switching platform. The device includes a receiving module and a sending module. The receiving and sending modules are configured to forward a payment card information request message from the third-party payment platform to at least one card management platform after the third-party payment platform completes user identity authorization. The payment card information request message includes user identity information. The sending module is further configured to send a payment card information response message to the third-party payment platform. The payment card information response message is generated based on card information of multiple payment cards matching the user's identity information fed back by at least one card management platform. The payment card information response message is used to instruct the third-party payment platform to display relevant information of the multiple payment cards matching the user's identity information to the user. The receiving and sending modules are also configured to forward a card binding message generated by the third-party payment platform to the target card management platform when the verification code corresponding to the target payment card indicated by the user's selection input is successfully verified. The card binding message is used to bind the third-party payment platform and the target payment card to the target card management platform, and the target card management platform corresponds to the target payment card indicated by the card binding message.

[0007] Fourthly, this application provides a payment card binding device applied to a third-party payment platform. The device includes: a sending module, configured to send a payment card information request message to a payment transfer platform after user identity authorization is completed, so that the payment transfer platform forwards the payment card information request message to at least one card management platform; the payment card information request message includes user identity information; a receiving module, configured to receive a payment card information response message sent by the payment transfer platform, the payment card information response message being generated based on card information of multiple payment cards matching the user identity information fed back by at least one card management platform; a display module, configured to display relevant information of the multiple payment cards matching the user identity information to the user based on the payment card information response message; the sending module is further configured to send a binding message generated by binding the target payment card to the payment transfer platform when the verification code corresponding to the target payment card indicated by the user's selected input is successfully verified, so that the payment transfer platform forwards the binding message to the target card management platform; the binding message is used to bind the third-party payment platform and the target payment card to the target card, and the target card management platform corresponds to the target payment card indicated by the binding message.

[0008] Fifthly, embodiments of this application provide a payment card binding device, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, it implements the payment card binding method of the first aspect or the payment card binding method of the second aspect.

[0009] Sixthly, embodiments of this application provide a payment card binding system, comprising: a third-party payment platform, configured to send a payment card information request message to a payment transfer platform after completing user identity authorization, the payment card information request message including user identity information; a payment transfer platform, configured to forward the payment card information request message from the third-party payment platform to at least one card management platform; the payment transfer platform is further configured to send a payment card information response message to the third-party payment platform, the payment card information response message being generated based on card information of multiple payment cards matching the user identity information fed back by at least one card management platform; the third-party payment platform is further configured to display relevant information of multiple payment cards matching the user identity information to the user based on the payment card information response message; the third-party payment platform is further configured to send a binding message generated by binding the target payment card to the payment transfer platform when the verification code corresponding to the target payment card indicated by the user's selection input is successfully verified; the payment transfer platform is further configured to forward the binding message generated by binding the target payment card from the third-party payment platform to the target card management platform, the binding message being used to bind the third-party payment platform and the target payment card to the target card management platform, the target card management platform corresponding to the target payment card indicated by the binding message.

[0010] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the payment card binding method of the first aspect or the payment card binding method of the second aspect.

[0011] Eighthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements either the payment card binding method of the first aspect or the payment card binding method of the second aspect.

[0012] This application provides a payment card binding method, apparatus, device, system, and medium. After a user identity authorization is completed on a third-party payment platform, a payment switching platform forwards the payment card information request message from the third-party payment platform to at least one card management platform. This allows each card management platform to provide the payment switching platform with card information for multiple payment cards matching the user identity information in the payment card information request message. The payment switching platform then sends a payment card information response message to the third-party payment platform based on this card information. The third-party payment platform then displays the relevant information of the multiple payment cards matching the user's identity information to the user based on the response message. After the user selects a target payment card from the multiple payment cards matching their identity information, only one verification code is required for all target payment cards. If the verification code verification is successful, the payment switching platform forwards the binding message generated by the third-party payment platform to the target card management platform. This allows the target card management platform to also complete the binding between the third-party payment platform and the target payment card. Thus, multiple payment cards can be bound to a third-party payment platform with only one user identity authorization and one verification code verification, simplifying the payment card binding process. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a schematic diagram of the structure of a payment card binding system provided in an embodiment of this application; Figure 2 A flowchart illustrating a payment card binding method provided in an embodiment of this application; Figure 3 A schematic diagram illustrating an example of a card selection interface provided in an embodiment of this application; Figure 4 A schematic diagram illustrating another example of a card selection interface provided in an embodiment of this application; Figure 5A flowchart illustrating a payment card binding method provided in another embodiment of this application; Figure 6 This is a schematic diagram illustrating an example of information interaction between various platforms in the payment card binding process provided in this application embodiment; Figure 7 This is a schematic diagram of the structure of a payment card binding device provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a payment card binding device provided in another embodiment of this application; Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0015] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples. It should be noted that the acquisition, storage, use, and processing of information and data in the embodiments of this application are all authorized by users or relevant organizations and comply with the relevant provisions of national laws and regulations.

[0016] With the continuous development of electronic payment technology, users can bind their payment cards to third-party payment platforms, enabling them to make payments through these platforms. The binding process requires users to manually enter their card number, user information, and other details for authorization. Verification using dynamic information completes the binding process. However, each authorization and verification session only binds one payment card. If a user needs to bind multiple cards to a third-party payment platform, multiple authorizations and verifications are required, making the process cumbersome. For example, if a user wants to bind three of their payment cards to a third-party payment platform, they will need to complete three authorizations and three verifications to achieve the desired binding.

[0017] This application provides a payment card binding method, apparatus, device, system, and medium. It enables the user to obtain all payment cards activated by the user on the card management platform using a single user authorization and verification code verification. One or more payment cards selected by the user can then be bound to a third-party payment platform, eliminating the need for multiple user authorizations and verification codes. This simplifies the payment card binding process, improves efficiency, and enhances user experience. For example, if a user wishes to bind three of their payment cards to a third-party payment platform, they only need one authorization and one verification code to bind all three cards, significantly simplifying the process.

[0018] The payment card binding method, device, equipment, system, medium, and program products provided in this application are described below.

[0019] To facilitate understanding, the payment card binding system provided in this application will be explained below. Figure 1 This is a schematic diagram of the structure of a payment card binding system provided in an embodiment of this application, as shown below. Figure 1 As shown, the payment card binding system may include a third-party payment platform 11 and a payment transfer platform 12.

[0020] Third-party payment platform 11 is a platform that provides independent and neutral payment services between the payer and the payee. Third-party payment platform 11 also includes acquiring institution platforms, but is not limited thereto. For example, third-party payment platform 11 may include, but is not limited to, e-commerce platforms, payment service providers, and social platforms with payment functions. In some examples, third-party payment platform 11 may include a front-end application and a back-end system. The front-end application may be an application (APP) installed on the user's terminal, and the back-end system may include a remote server. Users can interact with third-party payment platform 11 and initiate various payment-related requests through it.

[0021] Payment switching platform 12 can provide standardized information switching and clearing services between payment institutions such as card management platforms and third-party payment platforms. Payment switching platform 12 can communicate and interact with third-party payment platform 11. The functions of payment switching platform 12 can be implemented through hardware devices, and there is no limitation on the type and number of hardware devices used to implement the functions of payment switching platform 12.

[0022] In some embodiments, the payment card binding system may further include a card management platform 13, which manages payment card accounts. The card management platform 13 may belong to the payment card issuer, for example, a bank. The payment card binding system may include one or more card management platforms 13, and the owners of different card management platforms 13 may be different. The card management platform 13 can communicate and interact with the payment switching platform 12. The card management platform can be implemented through hardware devices, and the type and number of hardware devices implementing the functions of the card management platform 13 are not limited herein.

[0023] The payment card binding methods implemented by the aforementioned third-party payment platform 11, payment transfer platform 12, and card management platform 13 will be described in detail below.

[0024] This application also provides a payment card binding method that can be applied to a payment switching platform, that is, the payment card binding method can be executed by the payment switching platform. Figure 2 A flowchart of a payment card binding method provided in an embodiment of this application is shown below. Figure 2 As shown, the payment card binding method may include steps S201 to S203.

[0025] In step S201, after the third-party payment platform completes the user identity authorization, the payment card information request message of the third-party payment platform is forwarded to at least one card management platform.

[0026] User authorization verifies the user's identity to ensure that the payment card binding operation was initiated by the user, thus authorizing the user to perform the binding. Real-person authentication can be performed using the user's identity information; if authentication is successful, user authorization is complete. Real-person authentication can be achieved by sending the user's identity information to a trusted third-party authentication source, allowing the source to authenticate the user based on that information; alternatively, real-person authentication can be supplemented by the card management platform using information from the user's already activated payment cards.

[0027] In some examples, user authentication can be achieved by a third-party payment platform based on at least one of the following: user identity information, payment knowledge elements, holding elements, and biometric elements. User identity information may include, but is not limited to, the user's name and ID number. Payment instruction elements are elements that the user already possesses and that only the user knows before the payment occurs. Examples include, but are not limited to, query passwords, payment card passwords, payment application passwords, and verification question answers. Holding elements are elements that the user possesses and that are unique, non-copyable, and non-reusable. Examples include, but are not limited to, securely certified digital certificates, electronic signatures, and one-time passwords. To ensure the security of one-time passwords, they must be generated and transmitted through secure channels. Biometric elements include the user's own biometric features, which may include, but are not limited to, facial features, iris features, fingerprint features, genetic features, voiceprint features, body posture features, palm print features, ear features, and iris print features.

[0028] A third-party payment platform can generate and send a payment card information request message to a payment switching platform, which then forwards the message to at least one card management platform. The scope of the forwarding card management platforms is not limited here. For example, the payment switching platform can forward the message to one or more pre-designated card management platforms, or it can forward the message to the card management platform that has enabled the function corresponding to the payment card binding method in this embodiment.

[0029] Payment card information request messages may include user identity information. These messages can be used to request card information from the card management platform that matches the user's identity information. Card information may include, but is not limited to, one or more of the following: payment card number, registered mobile phone number, payment card type, payment card product type, payment card status, and payment card design.

[0030] In step S202, a payment card information response message is sent to the third-party payment platform.

[0031] After receiving a payment card information request message, the card management platform can query the card information of payment cards that match the user's identity information in the request message, and then send the retrieved card information back to the payment switching platform. The payment card information response message is generated based on the card information of multiple payment cards matching the user's identity information returned by at least one card management platform. In some examples, the card management platform can transmit the card information of payment cards matching the user's identity information returned by the card management platform to the payment switching platform via a card information exchange message. This message may include the card information of payment cards matching the user's identity information returned by the card management platform; if the card management platform returns the card information of multiple payment cards, the message may include the card information of all payment cards matching the user's identity information returned by the card management platform. The payment switching platform can receive the card information of payment cards matching the user's identity information returned by each card management platform and generate a payment card information response message based on this information. The payment card information response message may include relevant information about multiple payment cards matching the user's identity information. This relevant information can be obtained from the card information of the payment cards matching the user's identity information returned by various card management platforms. This relevant information may include at least a portion of the card information of the payment cards matching the user's identity information returned by the card management platform, and may also include information obtained after processing the card information of the payment cards matching the user's identity information returned by the card management platform; this is not limited to this. The payment card information response message is used to instruct the third-party payment platform to display relevant information about multiple payment cards matching the user's identity information to the user. Upon receiving the payment card information response message, the third-party payment platform, in response to the message, may display the relevant information about multiple payment cards matching the user's identity information to the user through display or voice broadcast. The third-party payment platform may include a front-end application installed on the user's terminal, which can display the relevant information about multiple payment cards matching the user's identity information to the user, allowing the user to select the target payment card for binding. The target payment card is the payment card selected by the user for binding. The third-party payment platform may group and display the relevant information of the payment cards to the user according to information such as payment card type and registered mobile phone number. The user terminal can receive user input and determine the target payment card selected from among multiple displayed payment card information. For example, in response to a payment card information response message, the front-end application of a third-party payment platform installed on the user terminal can display a card selection interface. Figure 3 A schematic diagram illustrating an example of a card selection interface provided in an embodiment of this application, as shown below. Figure 3As shown, the card selection interface displays relevant information of payment cards in groups according to payment card type. The card selection interface includes the payment card number 31 after the mask of two debit cards and the payment card number 32 after the mask of three credit cards. Each payment card has a checkbox 33 in front of the payment card number after the mask, and the user can select the target payment card by operating the checkbox 33.

[0032] In step S203, if the verification code corresponding to the target payment card indicated by the user's selection input is successfully verified, the card binding message generated by the third-party payment platform for binding the target payment card is forwarded to the target card management platform.

[0033] After the user selects and inputs the target payment card, the payment switching platform or card management platform sends a verification code corresponding to the target payment card to the user's terminal for verification. Verification via the verification code confirms that the user is indeed performing the payment card binding operation, allowing the payment card binding process to continue. If the verification code verification is successful, the third-party payment platform can bind the target payment card and generate a binding message. The binding message may include information representing the binding relationship between the target payment card and the third-party payment platform; for example, it may include the target payment card's payment card token and the third-party payment platform's platform identifier, which is not limited here. The third-party payment platform sends the binding message to the payment switching platform, which forwards it to the target card management platform. The binding message enables the target card management platform to bind the third-party payment platform and the target payment card. The target card management platform corresponds to the target payment card indicated in the binding message; that is, the target card management platform includes the card management platform that manages the target payment card. The payment switching platform can synchronize the binding relationship between the third-party payment platform and the target payment card based on the binding message. The target card management platform receives the card binding message and binds the third-party payment platform and the target payment card in the target card management platform according to the card binding message, thus completing the binding of the payment card.

[0034] If you select to input multiple target payment cards, and all target payment cards belong to the same card management platform, then the number of target card management platforms will be one, and the card binding message will be forwarded to this single target card management platform. If you select to input multiple target payment cards, and these target payment cards belong to two or more card management platforms, then the number of target card management platforms will be two or more, and the card binding message will be forwarded to both of these platforms. If you select to input only one target payment card, then the number of target card management platforms will be one, and the card binding message will be forwarded to this single target card management platform.

[0035] In this embodiment, after the third-party payment platform completes user identity authorization, the payment transfer platform forwards the payment card information request message from the third-party payment platform to at least one card management platform. This allows each card management platform to provide the payment transfer platform with card information for multiple payment cards matching the user identity information in the payment card information request message. Based on this card information, the payment transfer platform sends a payment card information response message to the third-party payment platform. The third-party payment platform then displays the relevant information of the multiple payment cards matching the user's identity information to the user based on the response message. After the user selects a target payment card from the list of cards matching their identity information, only one verification code is required for all target payment cards. If the verification code verification is successful, the payment transfer platform forwards the card binding message generated by the third-party payment platform to the target card management platform. This allows the target card management platform to also complete the binding between the third-party payment platform and the target payment card. Thus, multiple payment cards can be bound to the third-party payment platform with only one user identity authorization and one verification code verification, simplifying the card binding process, improving efficiency, and enhancing the user experience.

[0036] In some embodiments, the card information includes a reserved mobile phone number, which is the mobile phone number reserved by the user on the card management platform when activating the payment card. The verification code can be issued by the payment transfer platform, and this can be applied in scenarios where there are one or more target card management platforms. Specifically, the payment transfer platform can receive a target mobile phone number sent by a third-party payment platform, where the target mobile phone number is the reserved mobile phone number used by the user to input operation instructions; issue a verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number; receive verification code input information sent by the third-party payment platform; and verify the verification code input information based on the verification code corresponding to the target payment card.

[0037] The information displayed by a third-party payment platform to a user, matching the user's identity across multiple payment cards, may include the respective registered mobile phone numbers for each payment card. In some examples, the registered mobile phone numbers in the information may also be masked, which is not a limitation here. The third-party payment platform can receive user input regarding the registered mobile phone number. In response to this user input, the platform identifies the registered mobile phone number indicated by the user's input operation among the registered mobile phone numbers displayed by the third-party payment platform as the target mobile phone number. The third-party payment platform sends the target mobile phone number to the payment forwarding platform, which can then send an SMS verification code to that target mobile phone number. The third-party payment platform can also receive the user's verification code input information and send it to the payment forwarding platform. The verification code input information may be the verification code entered by the user. The payment forwarding platform can compare the verification code input information with a previously issued verification code to determine whether the verification code verification is successful. If the verification code input information matches the previously issued verification code, the verification code verification is successful; if the verification code input information does not match the previously issued verification code, the verification code verification is unsuccessful.

[0038] In some embodiments, the card information includes a reserved mobile phone number. The specific details of the reserved mobile phone number can be found in the relevant descriptions in the above embodiments, and will not be repeated here. The verification code can be issued by the card management platform, applicable to scenarios where there is only one target card management platform. Specifically, the payment switching platform can forward the target mobile phone number sent by the third-party payment platform to the target card management platform, so that the target card management platform can issue the verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number. The target mobile phone number is the reserved mobile phone number used by the user to input the operation instruction. The platform also forwards the verification code input information sent by the third-party payment platform to the target card management platform, so that the target card management platform can verify the verification code input information based on the verification code corresponding to the target payment card.

[0039] The information displayed by a third-party payment platform to users, matching the user's identity across multiple payment cards, may include the respective registered mobile phone numbers for each payment card. The third-party payment platform can receive user input for a registered mobile phone number. In response to this input, the platform identifies the registered mobile phone number indicated by the user's input among the displayed numbers as the target mobile phone number. The third-party payment platform sends this target mobile phone number to a payment forwarding platform, which then forwards it to a target card management platform. The target card management platform sends an SMS verification code to this target mobile phone number. Alternatively, the third-party payment platform can receive the verification code input from the user and send it to the payment forwarding platform, which then forwards it to the target card management platform. The target card management platform compares the input verification code with a previously issued verification code to determine if the verification has passed. If the input verification code matches, the verification passes; otherwise, it fails.

[0040] In the above embodiments, the card information includes the reserved mobile phone number. Correspondingly, the relevant information of multiple payment cards in the payment card information response message may include the reserved mobile phone number or the reserved mobile phone number after masking. In response to the payment card information response message, the front-end application of the third-party payment platform installed on the user's terminal can display a card selection interface, such as... Figure 3 As shown, the card selection interface also includes two reserved mobile phone numbers behind the mask. Each reserved mobile phone number behind the mask may have a checkbox 34 in front of it, and the user can select the target mobile phone number by operating the checkbox 34.

[0041] In the above embodiments, the verification code can be completed by the user specifying any of the reserved mobile phone numbers in the card management platform as the target mobile phone number through user input. The user can specify the mobile phone number of the user terminal they carry as the target mobile phone number, thereby avoiding the situation where the payment card binding process cannot be completed because the user terminal corresponding to the reserved mobile phone number of a certain payment card is not carried with them.

[0042] In some embodiments, the payment card information request message may also include a mobile phone number. The mobile phone number in the payment card information request message may be the mobile phone number of the user terminal where the front-end application of the third-party payment platform is located, or it may be the mobile phone number associated with the front-end application of the third-party payment platform, and is not limited thereto.

[0043] In some examples, the payment switching platform can send a verification code corresponding to the target payment card to the user terminal corresponding to the mobile phone number in the payment card information request message; receive verification code input information sent by the third-party payment platform, and verify the verification code input information according to the verification code corresponding to the target payment card. The payment switching platform can directly send an SMS verification code to the mobile phone number in the payment card information request message. The third-party payment platform can receive the verification code input information entered by the user and send the verification code input information to the payment switching platform. The payment switching platform can compare whether the verification code input information is consistent with the previously sent verification code to determine whether the verification code verification is successful; if the verification code input information is consistent with the previously sent verification code, the verification code verification is successful; if the verification code input information is inconsistent with the previously sent verification code, the verification code verification is unsuccessful.

[0044] In other examples, the payment switching platform can forward the verification code input information sent by the third-party payment platform to the target card management platform. The target card management platform then verifies the verification code input information based on the verification code corresponding to the target payment card. The verification code corresponding to the target payment card is sent by the target card management platform to the user terminal corresponding to the mobile phone number in the payment card information request message. After receiving the payment card information request message, the target card management platform can send an SMS verification code to the mobile phone number in the payment card information request message. The third-party payment platform can receive the verification code input information entered by the user and send it to the payment switching platform, which then forwards the verification code input information to the target card management platform. The target card management platform can compare the verification code input information with the previously sent verification code to determine whether the verification code verification is successful. If the verification code input information matches the previously sent verification code, the verification code verification is successful; if the verification code input information does not match the previously sent verification code, the verification code verification is unsuccessful.

[0045] In some embodiments, card information includes a registered mobile phone number. Correspondingly, the relevant information for multiple payment cards in the payment card information response message may include the registered mobile phone number or a masked registered mobile phone number, which is not limited here. The relevant information for multiple payment cards in the payment card information response message is displayed by the third-party payment platform in groups according to the registered mobile phone number. For example, Figure 4 A schematic diagram illustrating another example of the card selection interface provided in the embodiments of this application, such as... Figure 4As shown, the card selection interface displays payment card information grouped by the reserved mobile phone number. The card selection interface displays reserved mobile phone number 35 and reserved mobile phone number 36 after masking. Reserved mobile phone number 35 after masking corresponds to two masked payment card numbers 37, and reserved mobile phone number 36 after masking corresponds to three masked payment card numbers 38. A checkbox 391 is set in front of the masked payment card number, and the user can select the target payment card by operating the checkbox 391. Each reserved mobile phone number after masking may have a checkbox 392 in front of it, and the user can select the target mobile phone number by operating the checkbox 392.

[0046] In some embodiments, the card management platform can transmit card information of the payment card matching the user's identity information, fed back by the card management platform, to the payment switching platform via a card information exchange message. That is, the card information exchange message is used by the card management platform to transmit card information of the payment card matching the user's identity information to the payment switching platform. The card information exchange message can be generated by the card management platform based on the card information of the payment card matching the user's identity information obtained from a query on the card management platform. At least one of the payment card information response message and the card information exchange message includes primary information and secondary information, with the secondary information being a sub-information of the primary information. At least one of the payment card information response message and the card information exchange message can be implemented as a list-type message structure for transmitting de-identified card information. Through the list-type message structure, the card management platform, the payment switching platform, and the third-party payment platform can transmit card information of multiple payment cards in a single online interaction, no longer limited to transmitting only one payment card's card information in a single online interaction, thus improving information transmission efficiency and consequently improving payment card binding efficiency. In some examples, the payment card information response message may include card information exchange messages sent by each card management platform. In other examples, the payment card information response message may be reassembled by the payment switching system based on the information in the card information exchange messages sent by each card management platform, or the payment card information response message may be generated by the payment switching platform by processing at least part of the card information sent by each card management platform, based on the card information and the processed information.

[0047] Level 1 information includes a card information list label. This label indicates that the message or datagram transmits payment card information using a list-based method. Level 2 information may include, but is not limited to, a payment card token, a masked payment card number, and may also include one or more of the following: payment card serial number, payment card type, registered mobile phone number token, masked registered mobile phone number, payment card product type, payment card status, and payment card design information. The payment card token is a payment card identifier obtained by tokenizing the payment card number; it does not reveal the plaintext of the payment card number. The masked payment card number is the card number obtained by masking the payment card number; it is not the complete plaintext of the payment card number. The payment card type may include, but is not limited to, debit cards and credit cards. The payment card type can be represented by characters or strings; for example, 01 for debit cards and 02 for credit cards. The registered mobile phone number token is a mobile phone number identifier obtained by tokenizing the registered mobile phone number; it does not reveal the plaintext of the registered mobile phone number. The masked registered mobile phone number is the mobile phone number obtained after masking the registered mobile phone number; it is not the complete plaintext of the registered mobile phone number. Payment card product type may include, but is not limited to, information indicating the payment card product type such as regular card, platinum card, and diamond card. Payment card status may include, but is not limited to, normal status and abnormal status, which can be represented by characters or strings; for example, normal status is 02, and abnormal status is 03. Payment card face pattern information can represent the payment card face pattern, and this information may include, but is not limited to, the Uniform Resource Locator (URL) of the payment card face pattern and the encoding information of the payment card face pattern. For example, the structure of payment card information response messages and card information interaction messages can be as follows: "<Card Information List Label>" <Payment Card Serial Number="A001"> <Payment Card Token>62123456789123<Payment Card Token> <Payment Card Type>01<Payment Card Type> <Payment card number after mask>6200****000001<Payment card number after mask> <Reserved Mobile Number Token> 26875463215 <Reserved Mobile Number Token> <Mobile number behind mask> 188****0001 <Mobile number behind mask> <Payment Card Product Type> Platinum Card <Payment Card Product Type> <Payment Card Status>02<Payment Card Status> <Payment Card Image Information> www.xxx.com <Payment Card Image Information> <End symbol for single payment card information> <Payment Card Serial Number="A001"="A002"> <Payment Card Token>62234567891234<Payment Card Token> <Payment Card Type>02<Payment Card Type> <Payment card number after mask>6200****000002<Payment card number after mask> <Reserved Mobile Number Token> 79856432458 <Reserved Mobile Number Token> <Mobile number behind mask> 188****0002 <Mobile number behind mask> <Payment Card Product Type> Diamond Card <Payment Card Product Type> <Payment Card Status>03<Payment Card Status> <Payment Card Image Information>*(Base64 Encoded)<Payment Card Image Information> <End symbol for single payment card information> <End of Card Information List> The structure of the payment card information response message and card information interaction message includes card information for two payment cards. In practice, the structure may also include card information for more payment cards. `<Single Payment Card Information End Marker>` indicates the end of card information for one payment card. `<Card Information List End Marker>` indicates the end of card information for all returned payment cards. "www.xxx.com" is the URL of the payment card's face image for the first payment card. "(Base64 Encoding)" is the encoding information for the payment card's face image for the second payment card. The meanings of the remaining information can be found in the relevant descriptions in the above embodiments and will not be repeated here.

[0048] In some embodiments, the card information returned by at least one card management platform includes the payment card number. The payment card number can be processed by the payment switching platform. The payment card-related information transmitted by the payment switching platform to the third-party payment platform includes a payment card token and a masked payment card number, preventing the complete plaintext of the payment card number from being stored on the third-party payment platform and thus avoiding the leakage of users' sensitive information. The payment switching platform can perform tokenization processing on the payment card number returned by at least one card management platform to obtain a payment card token and a masked payment card number; based on the payment card token and the masked payment card number, a payment card information response message is generated. Tokenization processing can convert the payment card number into a string that is not the complete plaintext of the payment card number. The payment card information response message may include the payment card token and the masked payment card number. The payment card token can be used to bind the payment card on the third-party payment platform. The masked payment card number can be used to display the payment card to the user, allowing the user to select the payment card to be bound to the third-party payment platform.

[0049] In other embodiments, the card management platform can pre-decode the payment card number to obtain a payment card token and a masked payment card number. At least one card management platform can provide card information including the payment card token and the masked payment card number; that is, the card management platform can directly provide the payment card token and the masked payment card number to the payment switching platform. The payment switching platform generates a payment card information response message based on the payment card token and the masked payment card number. The payment card information response message can include the payment card token and the masked payment card number. For a detailed explanation of the payment card token and the masked payment card number, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0050] In some embodiments, a third-party payment platform can use a payment card token to bind itself to a target payment card. The payment switching platform needs to synchronize this binding relationship between the third-party payment platform and the target payment card, and the card management platform also needs to perform the binding. Specifically, the payment switching platform can synchronize the binding relationship between the third-party payment platform and the target payment card based on the card binding message. In the third-party payment platform, the binding relationship includes the binding relationship between the third-party payment platform and the target payment card's payment card token. In subsequent payment processes, the third-party payment platform can also use the target payment card's payment card token for payment. The use of payment card tokens for both binding and payment in the third-party payment platform maximizes the protection of users' sensitive information security.

[0051] This application also provides a payment card binding method that can be applied to a third-party payment platform, that is, the payment card binding method can be executed by the third-party payment platform. Figure 5 A flowchart of a payment card binding method provided in another embodiment of this application is shown below. Figure 5 As shown, the payment card binding method may include steps S401 to S404.

[0052] In step S401, after completing user identity authorization, a payment card information request message is sent to the payment transfer platform so that the payment transfer platform forwards the payment card information request message to at least one card management platform.

[0053] The payment card information request message includes user identity information.

[0054] In step S402, a payment card information response message sent by the payment transfer platform is received.

[0055] The payment card information response message is generated based on card information from multiple payment cards that match the user's identity information, as fed back by at least one card management platform.

[0056] In step S403, based on the payment card information response message, relevant information of multiple payment cards matching the user's identity information is displayed to the user.

[0057] In step S404, if the verification code corresponding to the target payment card indicated by the user's selection input is successfully verified, a card binding message generated by binding the target payment card is sent to the payment transfer platform, so that the payment transfer platform forwards the card binding message to the target card management platform.

[0058] The card binding message is used to bind the target card management platform to the third-party payment platform and the target payment card. The target card management platform corresponds to the target payment card indicated in the card binding message.

[0059] In some embodiments, the card information includes a reserved mobile phone number. The third-party payment platform may also send the target mobile phone number to the payment transfer platform, enabling the payment transfer platform to send a verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number. The target mobile phone number is the reserved mobile phone number used by the user to input operation instructions. The platform may also send the user-input verification code information to the payment transfer platform, enabling the payment transfer platform to verify the verification code information based on the verification code corresponding to the target payment card.

[0060] In some embodiments, card information includes a reserved mobile phone number. The third-party payment platform may also send the target mobile phone number to the payment transfer platform, causing the payment transfer platform to forward the target mobile phone number to the target card management platform. The target card management platform then sends a verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number. The target mobile phone number is the reserved mobile phone number used by the user to input operation instructions. The platform may also send the user-input verification code information to the payment transfer platform, causing the payment transfer platform to forward the verification code information to the target card management platform. The target card management platform then verifies the verification code information based on the verification code corresponding to the target payment card.

[0061] In some embodiments, the payment card information request message also includes a mobile phone number. The third-party payment platform may also send the user-input verification code to the payment transfer platform; wherein, the verification code corresponding to the target payment card is sent by the payment transfer platform to the user terminal corresponding to the mobile phone number in the payment card information request message, and the payment transfer platform verifies the verification code input information based on the verification code corresponding to the target payment card. Alternatively, the verification code corresponding to the target payment card is sent by the target card management platform to the user terminal corresponding to the mobile phone number in the payment card information request message, and the target card management platform verifies the verification code input information based on the verification code corresponding to the target payment card.

[0062] In some embodiments, card information includes a registered mobile phone number. A third-party payment platform can group and display information about multiple payment cards matching the user's identity information to the user based on the registered mobile phone number.

[0063] In some embodiments, at least one of the payment card information response message and the card information interaction message includes primary information and secondary information, wherein the secondary information is a sub-information of the primary information. The card information interaction message is used by the card management platform to transmit card information of the payment card that matches the user's identity information to the payment transfer platform. The primary information includes a card information list label. The secondary information includes a payment card token and a masked payment card number. The secondary information also includes one or more of the following: payment card serial number, payment card type, reserved mobile phone number token, masked reserved mobile phone number, payment card product type, payment card status, and payment card face pattern information.

[0064] In some embodiments, the card information returned by at least one card management platform includes the payment card number. The payment card information response message is generated based on the payment card token and the masked payment card number. The payment card token and masked payment card number are generated by the payment switching platform through tokenization processing of the payment card number returned by at least one card management platform.

[0065] In some embodiments, the binding relationship between the third-party payment platform and the target payment card in a third-party payment platform includes the binding relationship between the third-party payment platform and the payment card token of the target payment card.

[0066] In some embodiments, the third-party payment platform may also verify the user identity based on at least one of user identity information, payment knowledge elements, holding elements, and biometric elements to achieve the user identity authorization.

[0067] It should be noted that the payment card binding method applied to the third-party payment platform corresponds to the payment card binding method applied to the payment transfer platform described above. All implementation methods in the embodiments of the payment card binding method applied to the payment transfer platform described above are applicable to the embodiments of the payment card binding method applied to the third-party payment platform and can achieve the same technical effect.

[0068] To facilitate understanding, the following example illustrates the information interaction between platforms such as the third-party payment platform, payment transfer platform, and card management platform in the above embodiments. Figure 6 This is a schematic diagram illustrating an example of information interaction between various platforms in the payment card binding process provided in this application embodiment, such as... Figure 6 As shown, the third-party payment platform 11 can authorize user identity through interaction with the third-party trusted identity authentication source 14, or the third-party payment platform 11 can interact with the card management platform 13 through the payment transfer platform 12 to authorize user identity based on the information of the already activated payment cards. The third-party payment platform 11 can interact with the card management platform 13 through the payment transfer platform 12 to obtain card information of multiple payment cards matching the user's identity information from the card management platform 13. Card information may include, but is not limited to, payment card number, payment card token, masked payment card number, payment card serial number, payment card type, reserved mobile phone number token, masked reserved mobile phone number, payment card product type, payment card status, and payment card face pattern information. After the third-party payment platform 11 determines the target payment card based on the user's input, it can interact with the card management platform 13 through the payment transfer platform 12 to trigger an SMS verification code. After the SMS verification code is successfully verified, the interaction between the third-party payment platform 11, the payment transfer platform 12, and the card management platform 13 completes a one-time binding of multiple payment cards.

[0069] This application also provides a payment card binding device for use in a payment transfer platform. Figure 7 This is a schematic diagram of the structure of a payment card binding device provided in an embodiment of this application, as shown below. Figure 7 As shown, the payment card binding device 500 may include a receiving module 501 and a sending module 502.

[0070] The receiving module 501 and the sending module 502 are used to forward the payment card information request message of the third-party payment platform to at least one card management platform after the user identity authorization is completed on the third-party payment platform. The payment card information request message includes user identity information. The sending module 502 is also used to send a payment card information response message to a third-party payment platform. The payment card information response message is generated based on the card information of multiple payment cards that match the user's identity information fed back by at least one card management platform. The payment card information response message is used to instruct the third-party payment platform to display the relevant information of the multiple payment cards that match the user's identity information to the user. The receiving module 501 and the sending module 502 are also used to forward the card binding message generated by the third-party payment platform to the target card management platform when the verification code corresponding to the target payment card indicated by the user's selection input is successfully verified. The card binding message is used to bind the third-party payment platform and the target payment card to the target card management platform, and the target card management platform corresponds to the target payment card indicated by the card binding message.

[0071] In the above embodiments, forwarding the payment card information request message to the card management platform includes receiving the payment card information request message from the third-party payment platform first, and then sending the payment card information request message to the card management platform by the sending module 502. Similarly, forwarding the card binding message generated by the third-party payment platform for binding the target payment card to the target card management platform in the above embodiments includes receiving the card binding message from the third-party payment platform first, and then sending the card binding message to the card management platform by the sending module 502.

[0072] In some embodiments, the card information includes a registered mobile phone number. The payment card binding device 500 may also include a verification code sending module and a verification module.

[0073] The receiving module 501 can also be used to receive the target mobile phone number sent by the third-party payment platform. The target mobile phone number is the reserved mobile phone number for which the user inputs operation instructions.

[0074] The verification code sending module is used to send the verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number.

[0075] The receiving module 501 is used to receive verification code input information sent by the third-party payment platform.

[0076] The verification module can be used to verify the verification code input information based on the verification code corresponding to the target payment card.

[0077] In some embodiments, the card information includes a registered mobile phone number.

[0078] The receiving module 501 and the sending module 502 can also be used to forward the target mobile phone number sent by the third-party payment platform to the target card management platform, so that the target card management platform can send the verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number. The target mobile phone number is the reserved mobile phone number for the user to input operation instructions.

[0079] The receiving module 501 and the sending module 502 can also be used to forward the verification code input information sent by the third-party payment platform to the target card management platform, so that the target card management platform can verify the verification code input information according to the verification code corresponding to the target payment card.

[0080] In some embodiments, the payment card information request message also includes a mobile phone number. The payment card binding device 500 also includes a verification code sending module and a verification module.

[0081] The verification code sending module can be used to send the verification code corresponding to the target payment card to the user terminal corresponding to the mobile phone number in the payment card information request message.

[0082] The receiving module 501 can also be used to receive verification code input information sent by a third-party payment platform.

[0083] The verification module can be used to verify the verification code input information based on the verification code corresponding to the target payment card.

[0084] In some embodiments, the payment card information request message also includes a mobile phone number. The receiving module 501 and the sending module 502 can also be used to forward the verification code input information sent by the third-party payment platform to the target card management platform, so that the target card management platform verifies the verification code input information according to the verification code corresponding to the target payment card. The verification code corresponding to the target payment card is sent by the target card management platform to the user terminal corresponding to the mobile phone number in the payment card information request message.

[0085] In some embodiments, card information includes a reserved mobile phone number, and the relevant information of multiple payment cards in the payment card information response message is displayed by the third-party payment platform in groups according to the reserved mobile phone number.

[0086] In some embodiments, at least one of the payment card information response message and the card information interaction message includes primary information and secondary information, where secondary information is a sub-information of primary information. The card information interaction message is used by the card management platform to transmit card information of the payment card matching the user's identity information to the payment switching platform. Primary information includes a card information list label. Secondary information includes a payment card token, a masked payment card number, and may also include one or more of the following: payment card serial number, payment card type, registered mobile phone number token, masked registered mobile phone number, payment card product type, payment card status, and payment card face pattern information.

[0087] In some embodiments, the card information returned by at least one card management platform includes a payment card number. The payment card binding device 500 may further include a tokenization processing module and a message generation module. The tokenization processing module can be used to tokenize the payment card number returned by at least one card management platform to obtain a payment card token and a masked payment card number. The message generation module can be used to generate a payment card information response message based on the payment card token and the masked payment card number.

[0088] In some embodiments, the payment card binding device 500 may further include an information synchronization module. The information synchronization module can be used to synchronize the binding relationship between the third-party payment platform and the target payment card based on the card binding message. In the third-party payment platform, the binding relationship between the third-party payment platform and the target payment card includes the binding relationship between the third-party payment platform and the payment card token of the target payment card.

[0089] In some embodiments, user identity authorization is achieved by a third-party payment platform through verification based on at least one of user identity information, payment knowledge elements, holding elements, and biometric elements.

[0090] It should be noted that the payment card binding device 500 is a device corresponding to the payment transfer method applied to the payment transfer platform described above. All implementation methods in the above method embodiments are applicable to the embodiments of this device and can achieve the same technical effect.

[0091] This application also provides a payment card binding device for use on a third-party payment platform. Figure 8 This is a schematic diagram of the structure of a payment card binding device provided in another embodiment of this application, as shown below. Figure 8 As shown, the payment card binding device 600 may include a sending module 601, a receiving module 602, and a display module 603.

[0092] The sending module 601 can be used to send a payment card information request message to the payment switching platform after the user identity authorization is completed, so that the payment switching platform forwards the payment card information request message to at least one card management platform. The payment card information request message includes user identity information.

[0093] The receiving module 602 can be used to receive payment card information response messages sent by the payment transfer platform. The payment card information response messages are generated based on the card information of multiple payment cards that match the user's identity information fed back by at least one card management platform.

[0094] The display module 603 can be used to respond to messages based on payment card information and display relevant information of multiple payment cards that match the user's identity information to the user.

[0095] The sending module 601 can also be used to send a card binding message generated by binding the target payment card to the payment transfer platform when the verification code corresponding to the target payment card indicated by the user's selection input is verified. This allows the payment transfer platform to forward the card binding message to the target card management platform. The card binding message is used to bind the third-party payment platform and the target payment card to the target card management platform, and the target card management platform corresponds to the target payment card indicated by the card binding message.

[0096] In some embodiments, the card information includes a reserved mobile phone number. The sending module 601 can also be used to: send the target mobile phone number to the payment transfer platform, so that the payment transfer platform sends a verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number, wherein the target mobile phone number is the reserved mobile phone number used by the user to input the operation instruction; and send the verification code input information entered by the user to the payment transfer platform, so that the payment transfer platform verifies the verification code input information based on the verification code corresponding to the target payment card.

[0097] In some embodiments, the card information includes a reserved mobile phone number. The sending module 601 can also be used to: send the target mobile phone number to the payment transfer platform, so that the payment transfer platform forwards the target mobile phone number to the target card management platform, and the target card management platform sends a verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number, wherein the target mobile phone number is the reserved mobile phone number used by the user to input operation instructions; and send the user-input verification code information to the payment transfer platform, so that the payment transfer platform forwards the verification code information to the target card management platform, and the target card management platform verifies the verification code information based on the verification code corresponding to the target payment card.

[0098] In some embodiments, the payment card information request message further includes a mobile phone number. The sending module 601 can be used to send the user-inputted verification code to the payment transfer platform. Specifically, the verification code corresponding to the target payment card is sent by the payment transfer platform to the user terminal corresponding to the mobile phone number in the payment card information request message, and the payment transfer platform verifies the verification code input information based on the verification code corresponding to the target payment card. In some embodiments, the payment card information request message also includes a mobile phone number. The verification code corresponding to the target payment card is sent by the target card management platform to the user terminal corresponding to the mobile phone number in the payment card information request message, and the target card management platform verifies the verification code input information based on the verification code corresponding to the target payment card.

[0099] In some embodiments, the card information includes a registered mobile phone number. The display module 603 can be used to: group and display information about multiple payment cards matching the user's identity information to the user according to the registered mobile phone number.

[0100] In some embodiments, at least one of the payment card information response message and the card information interaction message includes primary information and secondary information, where secondary information is a sub-information of primary information. The card information interaction message is used by the card management platform to transmit card information of the payment card matching the user's identity information to the payment switching platform. Primary information includes a card information list label. Secondary information includes a payment card token, a masked payment card number, and may also include one or more of the following: payment card serial number, payment card type, registered mobile phone number token, masked registered mobile phone number, payment card product type, payment card status, and payment card face pattern information.

[0101] In some embodiments, the card information fed back by at least one card management platform includes the payment card number; the payment card information response message is generated based on the payment card token and the masked payment card number, which is obtained by the payment switching platform through tokenization processing of the payment card number fed back by at least one card management platform.

[0102] In some embodiments, the binding relationship between the third-party payment platform and the target payment card in a third-party payment platform includes the binding relationship between the third-party payment platform and the payment card token of the target payment card.

[0103] In some embodiments, the payment card binding device 600 may further include a user authorization module. The user authorization module can be used to verify user identity based on at least one of user identity information, payment knowledge elements, holding elements, and biometric elements to achieve user identity authorization.

[0104] It should be noted that the payment card binding device 600 is the same device as the payment card binding method applied to the third-party payment platform described above. All implementation methods in the above method embodiments are applicable to the embodiments of this device and can achieve the same technical effect.

[0105] This application also provides an electronic device. Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, as shown below. Figure 9 As shown, the electronic device 700 includes a memory 701, a processor 702, and a computer program stored in the memory 701 and executable on the processor 702.

[0106] In some examples, the processor 702 described above may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0107] Memory 701 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform operations described with reference to the payment card binding method applied to a payment switching platform or the payment card binding method applied to a third-party payment platform according to embodiments of this application.

[0108] The processor 702 runs a computer program corresponding to the executable program code stored in the memory 701 to implement the payment card binding method applied to the payment transfer platform or the payment card binding method applied to the third-party payment platform in the above embodiments.

[0109] In some examples, the electronic device 700 may also include a communication interface 703 and a bus 704. For example, Figure 9 As shown, the memory 701, processor 702, and communication interface 703 are connected through bus 704 and complete communication with each other.

[0110] The communication interface 703 is mainly used to enable communication between various modules, devices, units, and / or equipment in the embodiments of this application. Input devices and / or output devices can also be connected through the communication interface 703.

[0111] Bus 704 includes hardware, software, or both, that couples components of electronic device 700 together. For example, and not as a limitation, bus 704 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 704 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0112] This application also provides a payment card binding system, which includes a third-party payment platform and a payment transfer platform.

[0113] A third-party payment platform may send a payment card information request message to a payment transfer platform after completing user identity authorization. The payment card information request message includes user identity information. The payment switching platform can be used to forward payment card information request messages from the third-party payment platform to at least one card management platform; The payment transfer platform is also used to send a payment card information response message to the third-party payment platform. The payment card information response message is generated based on the card information of multiple payment cards that match the user's identity information fed back by the at least one card management platform. The third-party payment platform is also used to respond to the payment card information and display relevant information of multiple payment cards that match the user's identity information to the user; The third-party payment platform is also used to send a card binding message generated by binding the target payment card to the payment transfer platform when the verification code corresponding to the target payment card selected and entered by the user is successfully verified. The payment transfer platform can also be used to forward the card binding message generated by the third-party payment platform binding the target payment card to the target card management platform. The card binding message is used to enable the target card management platform to bind the third-party payment platform and the target payment card. The target card management platform corresponds to the target payment card indicated by the card binding message.

[0114] In some embodiments, the payment card binding system may also include a card management platform.

[0115] The specific details of the payment card binding methods executed by the aforementioned third-party payment platform, payment transfer platform, and card management platform can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0116] This application also provides a computer-readable storage medium storing computer program instructions. When executed by a processor, these computer program instructions can implement the payment card binding method applied to a payment transfer platform or a payment card binding method applied to a third-party payment platform as described above, achieving the same technical effect. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.

[0117] This application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it can implement the payment card binding method applied to the payment transfer platform or the payment card binding method applied to the third-party payment platform in the above embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0118] It should be clarified that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For the device embodiments, equipment embodiments, system embodiments, computer-readable storage medium embodiments, and computer program product embodiments, the relevant parts can be referred to the description section of the method embodiments. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application. Furthermore, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

[0119] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in 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, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0120] Those skilled in the art will understand that the above embodiments are exemplary and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, specification, and claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to identify names and not to indicate any particular order. No reference numerals in the claims should be construed as limiting the scope of protection. The functionality of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A payment card binding method, characterized by, The method is applied to a payment switching platform, and the method comprises the following steps: After a third-party payment platform completes authorization of a user identity, forwarding a payment card information request message of the third-party payment platform to at least one card management platform, wherein the payment card information request message comprises user identity information; sending a payment card information response message to the third-party payment platform, wherein the payment card information response message is generated according to card information of multiple payment cards that are matched with the user identity information and that are fed back by the at least one card management platform, and the payment card information response message is used to instruct the third-party payment platform to display relevant information of the multiple payment cards that are matched with the user identity information to a user; in a case where verification of a verification code corresponding to a target payment card indicated by a selection input of the user is passed, forwarding a card binding message generated by the third-party payment platform in binding of the target payment card to a target card management platform, wherein the card binding message is used to make the target card management platform bind the third-party payment platform and the target payment card, and the target card management platform corresponds to the target payment card indicated by the card binding message.

2. The method of claim 1, wherein, The card information comprises a reserved mobile phone number. The method further comprises the following steps: receiving a target mobile phone number sent by the third-party payment platform, wherein the target mobile phone number is a reserved mobile phone number indicated by a user input operation; downloading a verification code corresponding to the target payment card to a user terminal corresponding to the target mobile phone number; receiving verification code input information sent by the third-party payment platform, and verifying the verification code input information according to the verification code corresponding to the target payment card.

3. The method of claim 1, wherein, The card information comprises a reserved mobile phone number. The method further comprises the following steps: forwarding a target mobile phone number sent by the third-party payment platform to the target card management platform, so as to make the target card management platform download a verification code corresponding to the target payment card to a user terminal corresponding to the target mobile phone number, wherein the target mobile phone number is a reserved mobile phone number indicated by a user input operation; forwarding verification code input information sent by the third-party payment platform to the target card management platform, so as to make the target card management platform verify the verification code input information according to the verification code corresponding to the target payment card.

4. The method of claim 1, wherein, The payment card information request message further comprises a mobile phone number. The method further comprises the following steps: downloading a verification code corresponding to the target payment card to a user terminal corresponding to the mobile phone number in the payment card information request message; receiving verification code input information sent by the third-party payment platform, and verifying the verification code input information according to the verification code corresponding to the target payment card. Alternatively, forwarding verification code input information sent by the third-party payment platform to the target card management platform, so as to make the target card management platform verify the verification code input information according to a verification code corresponding to the target payment card, wherein the verification code corresponding to the target payment card is downloaded by the target card management platform to a user terminal corresponding to the mobile phone number in the payment card information request message.

5. The method of claim 1, wherein, The card information comprises a reserved mobile phone number, and relevant information of the multiple payment cards in the payment card information response message is displayed in groups according to the reserved mobile phone number by the third-party payment platform.

6. The method of claim 1, wherein, The at least one of the payment card information response message and the card information interaction message includes first information and second information, the second information is sub-information of the first information, and the card information interaction message is used for the card management platform to transmit card information of a payment card matched with the user identity information to the payment switching platform. The first information includes a card information list label. The second information includes one or more of a payment card Token, a masked payment card number, a payment card serial number, a payment card type, a reserved mobile phone number Token, a masked reserved mobile phone number, a payment card product type, a payment card state, and payment card face pattern information.

7. The method of claim 1, wherein, The card information fed back by the at least one card management platform includes a payment card number. The method further includes: Tokenizing the payment card number fed back by the at least one card management platform to obtain a payment card Token and a masked payment card number; Based on the payment card Token and the masked payment card number, the payment card information response message is generated.

8. The method of claim 1, wherein, Further including: According to the card binding message, the binding relationship between the third-party payment platform and the target payment card is synchronized. In the third-party payment platform, the binding relationship between the third-party payment platform and the target payment card includes a binding relationship between the third-party payment platform and a payment card Token of the target payment card.

9. The method of claim 1, wherein, The user identity authorization is verified by the third-party payment platform based on at least one of user identity information, payment knowledge elements, possession elements, and biological feature elements.

10. A payment card binding method, characterized by, Applied to a third-party payment platform, the method includes: After completing the user identity authorization, a payment card information request message is sent to a payment switching platform, so that the payment switching platform forwards the payment card information request message to at least one card management platform, and the payment card information request message includes user identity information; A payment card information response message sent by the payment switching platform is received, and the payment card information response message is generated according to card information of multiple payment cards matched with the user identity information fed back by the at least one card management platform; According to the payment card information response message, related information of multiple payment cards matched with the user identity information is displayed to the user; In a case where verification of a verification code corresponding to a target payment card indicated by a selection input of the user is passed, a card binding message generated by binding the target payment card is sent to the payment switching platform, so that the payment switching platform forwards the card binding message to a target card management platform, and the card binding message is used for the target card management platform to bind the third-party payment platform and the target payment card corresponding to the target payment card indicated by the card binding message.

11. The method of claim 10, wherein, The card information includes a reserved mobile phone number. The method further includes: A target mobile phone number is sent to the payment switching platform, so that the payment switching platform issues a verification code corresponding to the target payment card to a user terminal corresponding to the target mobile phone number, and the target mobile phone number is a reserved mobile phone number indicated by a user input operation. The payment switching platform is sent user input verification code input information, so that the payment switching platform verifies the verification code input information according to the target payment card corresponding verification code.

12. The method of claim 10, wherein, The card information includes a reserved mobile phone number; The method further comprises: The target mobile phone number is sent to the payment switching platform, so that the payment switching platform forwards the target mobile phone number to the target card management platform, and the target card management platform issues the verification code corresponding to the target payment card to the user terminal corresponding to the target mobile phone number, and the target mobile phone number is a reserved mobile phone number indicated by user input operation; The payment switching platform is sent user input verification code input information, so that the payment switching platform forwards the verification code input information to the target card management platform, and the target card management platform verifies the verification code input information according to the verification code corresponding to the target payment card.

13. The method of claim 10, wherein, The payment card information request message further includes a mobile phone number; The method further comprises: User input verification code input information is sent to the payment switching platform; The verification code corresponding to the target payment card is issued by the payment switching platform to the user terminal corresponding to the mobile phone number in the payment card information request message, and the verification code input information is verified by the payment switching platform according to the verification code corresponding to the target payment card; Or, The verification code corresponding to the target payment card is issued by the target card management platform to the user terminal corresponding to the mobile phone number in the payment card information request message, and the verification code input information is verified by the target card management platform according to the verification code corresponding to the target payment card.

14. The method of claim 10, wherein, The card information includes a reserved mobile phone number; The method further comprises: According to the reserved mobile phone number, the user is displayed the related information of the plurality of payment cards matched with the user identity information.

15. The method of claim 10, wherein, At least one of the payment card information response message and the card information interaction message includes first information and second information, the second information is the sub information of the first information, and the card information interaction message is used for the card management platform to transmit the card information of the payment card matched with the user identity information to the payment switching platform. The first information includes a card information list label; The second information includes a payment card Token, a masked payment card number, and one or more of a payment card serial number, a payment card type, a reserved mobile phone number Token, a masked reserved mobile phone number, a payment card product type, a payment card state, and payment card face pattern information.

16. The method of claim 10, wherein, The card information fed back by the at least one card management platform includes a payment card number; The payment card information response message is generated based on the payment card Token and the masked payment card number, and the payment card Token and the masked payment card number are obtained by marking the payment card number fed back by the at least one card management platform.

17. The method of claim 10, wherein, In the third-party payment platform, the binding relationship between the third-party payment platform and the target payment card includes a binding relationship between the third-party payment platform and a payment card Token of the target payment card.

18. The method of claim 10, wherein, Also comprising: The user identity authorization is realized based on verification of at least one of user identity information, payment knowledge elements, possession elements, and biological characteristic elements.

19. A payment card binding apparatus, characterized by, Applied to a payment switching platform, the device comprises a receiving module and a sending module; The receiving module and the sending module are configured to, after the third-party payment platform completes user identity authorization, forward a payment card information request message of the third-party payment platform to at least one card management platform, the payment card information request message comprising user identity information; The sending module is further configured to send a payment card information response message to the third-party payment platform, the payment card information response message being generated according to card information of multiple payment cards that match the user identity information and that are fed back by the at least one card management platform, the payment card information response message being used to instruct the third-party payment platform to display relevant information of the multiple payment cards that match the user identity information to the user; The receiving module and the sending module are further configured to, in a case where verification of a verification code corresponding to a target payment card indicated by a selection input of the user is passed, forward a card binding message generated by the third-party payment platform in binding the target payment card to a target card management platform, the card binding message being used to make the target card management platform bind the third-party payment platform and the target payment card, the target card management platform corresponding to the target payment card indicated by the card binding message.

20. A payment card binding apparatus, characterized by, Applied to a third-party payment platform, the device comprises: A sending module configured to, after completing user identity authorization, send a payment card information request message to a payment switching platform, so that the payment switching platform forwards the payment card information request message to at least one card management platform, the payment card information request message comprising user identity information; A receiving module configured to receive a payment card information response message sent by the payment switching platform, the payment card information response message being generated according to card information of multiple payment cards that match the user identity information and that are fed back by the at least one card management platform; A display module configured to display relevant information of the multiple payment cards that match the user identity information to the user according to the payment card information response message; The sending module is further configured to, in a case where verification of a verification code corresponding to a target payment card indicated by a selection input of the user is passed, send a card binding message generated by binding the target payment card to the payment switching platform, so that the payment switching platform forwards the card binding message to a target card management platform, the card binding message being used to make the target card management platform bind the third-party payment platform and the target payment card, the target card management platform corresponding to the target payment card indicated by the card binding message.

21. A payment card binding device, comprising: Comprising: A processor and a memory storing computer program instructions; The processor, when executing the computer program instructions, implements the payment card binding method according to any one of claims 1 to 18.

22. A payment card binding system, characterized by, Comprising: The third-party payment platform is configured to send a payment card information request message to the payment switching platform after completing the user identity authorization, wherein the payment card information request message comprises user identity information. The payment switching platform is configured to forward the payment card information request message of the third-party payment platform to at least one card management platform. The payment switching platform is further configured to send a payment card information response message to the third-party payment platform, wherein the payment card information response message is generated according to the card information of multiple payment cards that match the user identity information and are fed back by the at least one card management platform. The third-party payment platform is further configured to display the relevant information of the multiple payment cards that match the user identity information to the user according to the payment card information response message. The third-party payment platform is further configured to send a binding target payment card message generated by binding the target payment card to the payment switching platform in the case that the verification code corresponding to the target payment card indicated by the selection input of the user is verified successfully. The payment switching platform is further configured to forward the binding target payment card message generated by the third-party payment platform to a target card management platform, wherein the binding target payment card message is used to make the target card management platform bind the third-party payment platform and the target payment card, and the target card management platform corresponds to the target payment card indicated by the binding target payment card message.

23. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the payment card binding method in any one of claims 1 to 18.

24. A computer program product, characterised in that, The computer program is executed by the processor to implement the payment card binding method in any one of claims 1 to 18.

Images