WO2022166208A1 - 支付卡迁移方法、装置、电子设备、服务器和介质 - Google Patents

支付卡迁移方法、装置、电子设备、服务器和介质 Download PDF

Info

Publication number
WO2022166208A1
WO2022166208A1 PCT/CN2021/118145 CN2021118145W WO2022166208A1 WO 2022166208 A1 WO2022166208 A1 WO 2022166208A1 CN 2021118145 W CN2021118145 W CN 2021118145W WO 2022166208 A1 WO2022166208 A1 WO 2022166208A1
Authority
WO
WIPO (PCT)
Prior art keywords
electronic device
payment card
target
identifier
bound
Prior art date
Application number
PCT/CN2021/118145
Other languages
English (en)
French (fr)
Inventor
刘刚
彭程
孙权
邹震中
张爱龙
詹成初
才华
Original Assignee
中国银联股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国银联股份有限公司 filed Critical 中国银联股份有限公司
Priority to JP2022564657A priority Critical patent/JP2023523053A/ja
Priority to US17/920,596 priority patent/US11875336B2/en
Publication of WO2022166208A1 publication Critical patent/WO2022166208A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/355—Personalisation of cards for use
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3229—Use of the SIM of a M-device as secure element
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G06Q20/3263—Payment applications installed on the mobile devices characterised by activation or deactivation of payment capabilities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3278—RFID or NFC payments by means of M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/409—Device specific authentication in transaction processing
    • G06Q20/4097—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners

Definitions

  • the present application relates to the field of computer technology, and in particular, to a payment card migration method, apparatus, electronic device, server and medium.
  • the electronic device Before a user makes an online payment using an electronic device, the electronic device needs to be bound with a payment card, for example, the electronic device is bound with a bank card through a wallet application installed on the electronic device. After binding, you can use the bound payment card for online payment.
  • a payment card for example, the electronic device is bound with a bank card through a wallet application installed on the electronic device. After binding, you can use the bound payment card for online payment.
  • a user wants to migrate a payment card bound with one electronic device to another electronic device, the user needs to unbind one electronic device from the payment card first, and then bind the payment card with another electronic device. Each time a payment card is bound, the user is required to perform unbinding and binding operations.
  • the user needs to perform multiple operations to realize the migration of the payment card, which leads to a cumbersome operation for the user to perform the migration of the payment card.
  • the embodiments of the present application provide a payment card migration method, device, electronic device, server, and medium, which can solve the technical problem that a user performs a relatively cumbersome payment card migration operation.
  • an embodiment of the present application provides a method for migrating a payment card, which is applied to a first electronic device, and the method includes:
  • the target device identifier is sent to the server, so that the server migrates the payment card bound to the second electronic device to the first electronic device, and the second electronic device It is an electronic device corresponding to the target device identifier in at least one of the target electronic devices.
  • an embodiment of the present application provides a payment card migration method, which is applied to a server, and the method includes:
  • the target device identification is the device identification selected by the user in at least one device identification, and the at least one device identification is the target electronic device that has logged in the account. identification;
  • an embodiment of the present application provides a payment card migration device, which is applied to a first electronic device, and the device includes:
  • a first receiving module configured to receive a payment card migration operation after the first electronic device logs in to an account
  • a first display module configured to display at least one device identifier in response to the payment card migration operation, where the at least one device identifier is the identifier of the target electronic device that has logged in the account;
  • a second receiving module configured to receive a first selection operation on the target device identifier in the at least one device identifier
  • a first sending module configured to send the target device identifier to a server in response to the first selection operation, so that the server migrates the payment card bound to the second electronic device to the first electronic device , the second electronic device is an electronic device corresponding to the target device identifier in at least one of the target electronic devices.
  • an embodiment of the present application provides a payment card migration device, which is applied to a server, and the device includes:
  • the third receiving module is configured to receive a target device identifier sent by the first electronic device after logging in to the account, where the target device identifier is a device identifier selected by the user from at least one device identifier, and the at least one device identifier is a device identifier that has been logged in to the account.
  • the identification of the target electronic device of the account is a device identifier selected by the user from at least one device identifier, and the at least one device identifier is a device identifier that has been logged in to the account.
  • the migration module is configured to migrate the payment card bound to the second electronic device to the first electronic device according to the target device identifier, where the second electronic device is at least one of the target electronic devices and the The target device identifies the corresponding electronic device.
  • an embodiment of the present application provides an electronic device, the device includes: a processor and a memory storing computer program instructions, the processor implements the payment card provided in the first aspect when the processor executes the computer program instructions The steps of the migration method.
  • an embodiment of the present application provides a server, the server includes: a processor and a memory storing computer program instructions, the processor implements the payment card migration provided in the second aspect when the processor executes the computer program instructions steps of the method.
  • an embodiment of the present application provides a computer storage medium, where computer program instructions are stored on the computer storage medium, and when the computer program instructions are executed by a processor, the payment card migration method provided in the first aspect or the first method is implemented.
  • the second aspect provides the steps of the payment card migration method.
  • the device identifier of the target electronic device that has logged into the account is displayed ;
  • the target device identification is sent to the server, So that the server migrates the payment card bound to the second electronic device to the first electronic device.
  • FIG. 1 is a schematic diagram of an embodiment of a system for implementing a payment card migration method provided by the present application.
  • FIG. 2 is a schematic flowchart of an embodiment of a payment card migration method provided by the present application.
  • FIG. 3 is a schematic flowchart of another embodiment of the payment card migration method provided by the present application.
  • 4 to 8 are schematic diagrams of scene interfaces of the payment card migration method provided by the present application.
  • FIG. 9 is a schematic flowchart of the payment card migration method provided by the first aspect of the present application.
  • FIG. 10 is a schematic flowchart of the payment card migration method provided by the second aspect of the present application.
  • FIG. 11 is a schematic structural diagram of an embodiment of the payment card migration device provided by the third aspect of the present application.
  • FIG. 12 is a schematic structural diagram of an embodiment of the payment card migration device provided by the fourth aspect of the present application.
  • FIG. 13 shows a schematic structural diagram of an embodiment of a payment card migration device provided by the present application.
  • the payment card bound on one electronic device needs to be migrated to another electronic device.
  • the card-changing solution includes the following steps:
  • the payment card bound on one electronic device can be migrated to another electronic device by using the above-mentioned solution for changing the card and binding the card.
  • the above steps 3-5 need to be repeated. In this way, the user needs to perform multiple operations to realize the migration of the payment card, so that the user's operation of migrating the payment card is cumbersome.
  • the present application provides a method for migrating a payment card.
  • the following first describes a system for implementing the method for migrating a payment card.
  • FIG. 1 is a schematic diagram of an embodiment of a system for implementing a payment card migration method provided by the present application.
  • the system for implementing the payment card migration method includes a first electronic device 102 (such as a new electronic device), a server 104, a second electronic device 106 (such as an old electronic device), and a trusted service management ( Trusted Service Manager, TSM) system 108.
  • a first electronic device 102 such as a new electronic device
  • server 104 such as a server 104
  • a second electronic device 106 such as an old electronic device
  • TSM trusted service management
  • the first electronic device 102 displays at least one device identifier after logging into the account and receiving a payment card (such as a bank card, shopping card, membership card, etc.) migration operation, and the device identifier is an electronic device that has logged into the above account. ID for the user to select from at least one device ID.
  • the first electronic device 102 receives the first selection operation on the target device identification in the at least one device identification, the first electronic device 102 sends the target device identification to the server 104 to notify the server 104 that the second electronic device corresponding to the target device identification needs to be selected.
  • the bound payment card is migrated to the first electronic device 102 .
  • the server 104 When the server 104 receives the target device identification, it migrates the payment card bound to the second electronic device 106 corresponding to the target device identification to the first electronic device 102 . Specifically, the server 104 sends a card binding request to the TSM system 108 to migrate the payment card bound to the second electronic device 106 to the first electronic device 102 through the TSM system 108 .
  • FIG. 2 is a schematic flowchart of an embodiment of a payment card migration method provided by the present application. As shown in Figure 2, the payment card migration method includes:
  • the first electronic device receives a payment card migration operation after the first electronic device logs in to the account.
  • a payment application (such as a wallet application) may be installed on the first electronic device, and after the payment application on the first electronic device logs in to the account, payment may be displayed on the interface of the payment application Card migration controls.
  • the first electronic device receives a user's touch operation on the payment card migration control.
  • the user's touch operation on the payment card migration control may be a click operation, a long-press operation, or a double-click operation.
  • the payment card migration operation is not limited to the touch operation on the payment card migration control, but may also be a voice input operation, and the payment card migration operation is not limited herein.
  • the payment card migration method further includes: S204, the first electronic device displays at least one device identifier in response to the payment card migration operation, and the at least one device identifier is the identifier of the target electronic device that has logged in the account.
  • the first electronic device may send a request to the server to request to obtain the identifier of the target electronic device that has logged in the above account.
  • the first electronic device receives at least one device identifier sent by the server, the at least one device identifier is displayed for the user to select from the at least one device identifier the payment card needs to be migrated to the second electronic device on the first electronic device.
  • the device identifier may be the model of the target electronic device that has logged in the above account, or the device identifier may be a user-defined name of the target electronic device that has logged in the above account.
  • the target electronic device may be an electronic device that has logged in an account and is bound with a payment card.
  • the displayed at least one device identifier is the identifier of the electronic device bound with the payment card, and the electronic device not bound with the bank card is not displayed, thereby facilitating the user to select the identifier of the electronic device to be migrated.
  • the payment card migration method further includes: S206, the first electronic device receives a first selection operation of the target device identifier in the at least one device identifier.
  • the first electronic device can receive the user's touch operation on the target device identification in the at least one device identification. At this time, the user selects the target device identification, which is equivalent to the user selecting the second electronic device corresponding to the target device identification to pay the card. migrate.
  • the payment card migration method further includes: S208, the first electronic device sends the target device identification to the server in response to the first selection operation; S210, after the server receives the target device identification, the server migrates the payment card bound to the second electronic device to On the first electronic device, the second electronic device is an electronic device corresponding to the target device identifier in at least one target electronic device.
  • the server may send the card binding request to the TSM system.
  • the TSM system After receiving the card binding request, the TSM system unbinds the second electronic device from the bound payment card, and binds the unbound payment card with the first electronic device.
  • the card binding request may include a payment card code (such as mpan-id) bound to the security environment identifier (Security environment identifier, SEID) of the second electronic device.
  • the card binding application channel type ( applyChannelType) is "04 channel”.
  • the card issuing bank system can verify at least one of the following: CVN2 (credit card does not verify this item), validity period, dynamic password (One-Time Password, OTP), password (debit card does not verify this item) .
  • CVN2 credit card does not verify this item
  • OTP Dynamic password
  • password debit card does not verify this item
  • the payment cards bound by the second electronic device can be migrated to the first electronic device in batches, and the user does not need to perform unbinding and binding operations on the payment cards bound to the second electronic device one by one. Simplifies the migration of payment cards for users.
  • the payment card migration method may further include:
  • the first electronic device displays a verification code input interface
  • the server sends the first verification code to the second electronic device corresponding to the target device identification according to the target device identification in the case of receiving the target device identification;
  • the first electronic device receives an input operation of inputting the second verification code on the verification code input interface
  • the first electronic device sends the second verification code to the server in response to the input operation.
  • S210 may specifically include: when the server verifies that the second verification code is consistent with the first verification code, and indicates that the user holding the second electronic device is a legitimate user, the server binds the second electronic device to The predetermined payment card is migrated to the first electronic device.
  • the server sends the first verification code to the second electronic device. If the first electronic device and the second electronic device belong to the same user or belong to two users with an associated relationship, Then the user of the first electronic device can obtain the first verification code received by the second electronic device, and input the first verification code into the verification code input interface of the first electronic device. In this way, the verification code can be used to verify whether the user who performs the card migration operation is a legitimate user, thereby ensuring the security of the payment card during the migration process.
  • the user only needs to input the verification code once, and does not need to input the verification code every time a payment card is bound. Moreover, the user does not need to input information such as the validity period of the payment card and the card confirmation code, which can further simplify the operation of migrating the payment card.
  • the server sends the first verification code to the second electronic device corresponding to the target device identifier according to the target device identifier, which may include:
  • the server In the case of logging in the above account on the payment application of the second electronic device, the server sends the first verification code to the payment application of the login account.
  • the payment application of the second electronic device can receive the first verification code sent by the server through the network under the condition of logging in to the above account and connecting to the network.
  • the second electronic device can receive the first verification code sent by the server through the wireless network.
  • the payment application of the first electronic device can also log in to the account when the payment application of the first electronic device logs in the account to perform payment card migration.
  • the second electronic device can receive the first verification code sent by the server. In this way, there is no need for the user to perform additional operations, and it is convenient for the user to migrate the payment card.
  • the server sends the first verification code to the second electronic device corresponding to the target device identifier according to the target device identifier, which may include:
  • SIM Subscriber Identity Module
  • the server may send a short message including the first verification code to the communication number corresponding to the SIM card, or the server may send voice information including the first verification code to the communication number corresponding to the SIM card.
  • the payment card migration method may further include:
  • the first electronic device displays at least one payment card identifier, and the payment card identifier is the identifier of the payment card bound to the second electronic device;
  • the first electronic device receives a second selection operation for the target payment card identifier in the at least one payment card identifier
  • the first electronic device sends the target payment card identifier to the server in response to the second selection operation;
  • the server migrates the target payment card bound to the second electronic device to the first electronic device, where the target payment card is the payment card corresponding to the target payment card identifier.
  • the first electronic device may display the at least one payment card identification, or the first electronic device may receive the server identification In the case of the sent information indicating that the second verification code is consistent with the first verification code, the first electronic device displays at least one payment card identifier.
  • the identifier of the payment card bound to the second electronic device may be displayed on the first electronic device, so that the user can choose to transfer the payment card to the second electronic device.
  • Which payment card bound to the second electronic device is to be migrated the user can choose to migrate all or some of the bank cards bound to the second electronic device according to requirements. In this way, the user can choose the migrated payment card independently, which satisfies the user's usage needs.
  • the payment card identifier may be the payment card number, the card opening time, and the name of the card opening company.
  • the identifiers of multiple electronic devices are the same. For example, if the identifier of the electronic device is the model of the electronic device, then the identifiers of two electronic devices with the same model are the same. In this case, it is difficult for the user to compare the prices of electronic devices with the same identification, resulting in that the selected target device identification is not the identification of the electronic device to be migrated.
  • payment card migration methods can also include:
  • At least one device identifier can be displayed, and the payment card information bound to each target electronic device can be displayed; and the device identifier can also be displayed when a touch input on a device identifier is received.
  • the payment card information bound to the corresponding target electronic device can be displayed, and the payment card information bound to each target electronic device can be displayed; and the device identifier can also be displayed when a touch input on a device identifier is received. The payment card information bound to the corresponding target electronic device.
  • the information of the payment card may include at least one of the following: the name of the card issuing company of the payment card (for example, a certain bank), the identification of the card issuing company of the payment card, and the card opening time.
  • the user by displaying the information of the payment card bound to the target electronic device, it is convenient for the user to distinguish each electronic device, so as to facilitate the user to select the target device identification from at least one device identification, and the selected target device identification is the user The identity of the electronic device to be migrated.
  • the payment card migration method may further include:
  • the user identification (User Identification, UID) corresponding to the account
  • at least one device information is obtained from the pre-stored information, and the device information includes at least one of the following hardware information of the electronic device bound to the payment card through the account.
  • migrating the payment card bound to the second electronic device to the first electronic device may include:
  • the payment card bound to the second electronic device is migrated to the first electronic device according to the target device identifier.
  • the payment card migration method of any one of the embodiments provided in this application can be applied to a scenario of replacing an electronic device, and the payment card bound to the old electronic device is migrated to the new electronic device. It can also be applied to a scenario where an electronic device is formatted. After formatting, the formatted electronic device is not bound with any payment card. By using the payment card migration method in any of the above embodiments, the electronic device before formatting can be transferred. The device-bound payment card is migrated to the formatted electronic device.
  • the "one-click migration" control is displayed on the interface of the wallet application.
  • the interface shown in FIG. 5 is displayed, and at least one device identifier is displayed on the interface shown in FIG. 5 , the at least one device Identifies the model of each electronic device that has logged into the account.
  • the new electronic device When the new electronic device receives the user's first selection operation on the target device identification in the at least one device identification, the new electronic device displays the verification code input interface as shown in FIG. 6, and sends the target device identification to the server, so that the server sends the first verification code to the old electronic device according to the target device identification.
  • the user can input the second verification code on the verification code input interface shown in FIG. 6 based on the first verification code received by the old electronic device.
  • the new electronic device sends the second verification code to the server, so that the server verifies whether the first verification code and the second verification code are consistent, and displays the following on the new electronic device.
  • the interface shown in FIG. 7 includes the card binding progress.
  • the server verifies that the first verification code and the second verification code are consistent, the payment card bound to the old electronic device is migrated to the new electronic device, and if the migration is successful, a feedback of successful migration is sent to the new electronic device information.
  • a migration success interface as shown in FIG. 8 is displayed.
  • FIG. 9 is a schematic flowchart of the payment card migration method provided by the first aspect of the present application.
  • the payment card migration method provided in the first aspect is applied to the first electronic device. As shown in FIG. 9 , the payment card migration method includes:
  • S308 in response to the first selection operation, send the target device identifier to the server, so that the server migrates the payment card bound to the second electronic device to the first electronic device, where the second electronic device is at least one target electronic device with The target device identifies the corresponding electronic device.
  • the payment cards bound by the second electronic device can be migrated to the first electronic device in batches, and the user does not need to perform unbinding and binding operations on the payment cards bound to the second electronic device one by one. , which simplifies the migration of payment cards for users.
  • the target device identifier is used to cause the server to send the first verification code to the second electronic device.
  • the payment card migration method may further include:
  • the second verification code is sent to the server, so that the server transfers the payment card bound to the second electronic device to the first electronic device under the condition that the second verification code is consistent with the first verification code .
  • the server sends the first verification code to the second electronic device. If the first electronic device and the second electronic device belong to the same user or belong to two users with an associated relationship, Then the user of the first electronic device can obtain the first verification code received by the second electronic device, and input the first verification code into the verification code input interface of the first electronic device. In this way, the verification code can be used to verify whether the user who performs the card migration operation is a legitimate user, thereby ensuring the security of the payment card during the migration process.
  • the user only needs to input the verification code once, and does not need to input the verification code every time a payment card is bound. Moreover, the user does not need to input information such as the validity period of the payment card and the card confirmation code, which can further simplify the operation of the payment card migration.
  • the payment card migration method may further include:
  • the target payment card identifier is sent to the server, where the target payment card identifier is used to instruct to migrate the target payment card bound to the second electronic device to the first electronic device, and the target payment card is the target payment card identifier the corresponding payment card.
  • the identifier of the payment card bound to the second electronic device may be displayed on the first electronic device, so that the user can choose to transfer the payment card to the second electronic device.
  • Which payment card bound to the second electronic device is to be migrated the user can choose to migrate all or some of the bank cards bound to the second electronic device according to requirements. In this way, the user can independently select the migrated payment card, which satisfies the user's usage needs.
  • the payment card migration method may further include:
  • the user by displaying the information of the payment card bound to the target electronic device, it is convenient for the user to distinguish each electronic device, so as to facilitate the user to select the target device identification from at least one device identification, and the selected target device identification is the user The identity of the electronic device to be migrated.
  • the target electronic device may be an electronic device that has logged into an account and is bound with a payment card.
  • FIG. 10 is a schematic flowchart of the payment card migration method provided by the second aspect of the present application.
  • the payment card migration method provided in the first aspect is applied to the server.
  • the payment card migration method includes:
  • the target device identification is the device identification selected by the user in at least one device identification, and the at least one device identification is the identification of the target electronic device that has logged in the account;
  • the payment cards bound by the second electronic device can be migrated to the first electronic device in batches, and the user does not need to perform unbinding and binding operations on the payment cards bound to the second electronic device one by one. , which simplifies the migration of payment cards for users.
  • S404 may include:
  • the second verification code is a verification code input by the user on the verification code input interface of the first electronic device based on the first verification code
  • the payment card bound to the second electronic device is migrated to the first electronic device.
  • the server sends the first verification code to the second electronic device. If the first electronic device and the second electronic device belong to the same user or belong to two users with an associated relationship, Then the user of the first electronic device can obtain the first verification code received by the second electronic device, and input the first verification code into the verification code input interface of the first electronic device. In this way, the verification code can be used to verify whether the user who performs the card migration operation is a legitimate user, thereby ensuring the security of the payment card during the migration process.
  • the user only needs to input the verification code once, and does not need to input the verification code every time a payment card is bound. Moreover, the user does not need to input information such as the validity period of the payment card and the card confirmation code, which can further simplify the operation of migrating the payment card.
  • sending the first verification code to the second electronic device according to the target device identifier may include:
  • the first verification code is sent to the payment application for logging in the account.
  • sending the first verification code to the second electronic device according to the target device identifier may include:
  • the first verification code is sent to the communication number corresponding to the SIM card.
  • migrating the payment card bound to the second electronic device to the first electronic device may include:
  • the card binding request is sent to the TSM system, so that the TSM system unbinds the second electronic device from the bound payment card, and binds the unbound payment card with the first electronic device.
  • the payment card migration method before migrating the payment card bound to the second electronic device to the first electronic device, the payment card migration method may further include:
  • the target payment card identifier sent by the first electronic device is received, where the target payment card identifier is the payment card identifier selected by the user from at least one payment card identifier, and the at least one payment card identifier is the identifier of the payment card bound to the second electronic device.
  • Migrating the payment card bound to the second electronic device to the first electronic device may include:
  • the target payment card bound to the second electronic device is migrated to the first electronic device, and the target payment card is the payment card corresponding to the target payment card identifier.
  • the method before migrating the payment card bound to the second electronic device to the first electronic device according to the target device identifier, the method further includes:
  • the device information includes at least one of the following hardware information of the electronic device bound to the payment card through the account;
  • Migrating the payment card bound to the second electronic device to the first electronic device according to the target device identifier including:
  • the payment card bound to the second electronic device is migrated to the first electronic device according to the target device identifier.
  • FIG. 11 is a schematic structural diagram of an embodiment of the payment card migration device provided by the third aspect of the present application.
  • the payment card migration device 500 includes:
  • the first receiving module 502 is configured to receive the payment card migration operation after the first electronic device logs in to the account;
  • the first display module 504 is configured to display at least one device identifier in response to the payment card migration operation, and the at least one device identifier is the identifier of the target electronic device that has logged into the account;
  • a second receiving module 506, configured to receive a first selection operation on the target device identifier in the at least one device identifier
  • the first sending module 508 is configured to send the target device identifier to the server in response to the first selection operation, so that the server migrates the payment card bound to the second electronic device to the first electronic device, and the second electronic device is at least An electronic device corresponding to the target device identifier in a target electronic device.
  • the payment cards bound by the second electronic device can be migrated to the first electronic device in batches, and the user does not need to perform unbinding and binding operations on the payment cards bound to the second electronic device one by one. , which simplifies the migration of payment cards for users.
  • the target device identifier is used to enable the server to send the first verification code to the second electronic device
  • the payment card migration apparatus 500 may further include:
  • the second display module is used to display the verification code input interface
  • a fourth receiving module configured to receive an input operation of inputting the second verification code on the verification code input interface
  • the second sending module is configured to send the second verification code to the server in response to the input operation, so that the server can bind the payment card bound to the second electronic device under the condition that the second verification code is consistent with the first verification code. Migrate to the first electronic device.
  • the server sends the first verification code to the second electronic device. If the first electronic device and the second electronic device belong to the same user or belong to two users with an associated relationship, Then the user of the first electronic device can obtain the first verification code received by the second electronic device, and input the first verification code into the verification code input interface of the first electronic device. In this way, the verification code can be used to verify whether the user who performs the card migration operation is a legitimate user, thereby ensuring the security of the payment card during the migration process.
  • the user only needs to input the verification code once, and does not need to input the verification code every time a payment card is bound. Moreover, the user does not need to input information such as the validity period of the payment card and the card confirmation code, which can further simplify the operation of migrating the payment card.
  • the payment card migration apparatus 500 may further include:
  • a third display module configured to display at least one payment card identifier, where the payment card identifier is the identifier of the payment card bound to the second electronic device;
  • a fifth receiving module configured to receive a second selection operation on the target payment card identifier in the at least one payment card identifier
  • the third sending module is configured to send the target payment card identifier to the server in response to the second selection operation, where the target payment card identifier is used to instruct the transfer of the target payment card bound to the second electronic device to the first electronic device, and the target payment card
  • the payment card is the payment card corresponding to the target payment card identifier.
  • the identifier of the payment card bound to the second electronic device may be displayed on the first electronic device, so that the user can choose to transfer the payment card to the second electronic device.
  • Which payment card bound to the second electronic device is to be migrated the user can choose to migrate all or some of the bank cards bound to the second electronic device according to requirements. In this way, the user can independently select the migrated payment card, which satisfies the user's usage needs.
  • the payment card migration apparatus 500 may further include:
  • the fourth display module is used to display the information of the payment card bound with the target electronic device.
  • the user by displaying the information of the payment card bound to the target electronic device, it is convenient for the user to distinguish each electronic device, so as to facilitate the user to select the target device identification from at least one device identification, and the selected target device identification is the user The identity of the electronic device to be migrated.
  • the target electronic device is an electronic device that has logged into an account and is bound with a payment card.
  • FIG. 12 is a schematic structural diagram of an embodiment of the payment card migration device provided by the fourth aspect of the present application.
  • the payment card migration device 600 includes:
  • the third receiving module 602 is configured to receive a target device identifier sent by the first electronic device after logging in to the account, where the target device identifier is a device identifier selected by the user from at least one device identifier, and at least one device identifier is the target electronic device that has logged into the account. the identification of the equipment;
  • the migration module 604 is configured to migrate the payment card bound to the second electronic device to the first electronic device according to the target device identification, where the second electronic device is an electronic device corresponding to the target device identification in at least one target electronic device.
  • the payment cards bound by the second electronic device can be migrated to the first electronic device in batches, and the user does not need to perform unbinding and binding operations on the payment cards bound to the second electronic device one by one. , which simplifies the migration of payment cards for users.
  • the migration module 604 may include:
  • a first sending unit configured to send the first verification code to the second electronic device according to the target device identifier
  • the first receiving unit is used for receiving the second verification code sent by the first electronic device, and the second verification code is the verification code input by the user on the verification code input interface of the first electronic device based on the first verification code;
  • the migration unit is configured to migrate the payment card bound with the second electronic device to the first electronic device when the second verification code is consistent with the first verification code.
  • the server sends the first verification code to the second electronic device. If the first electronic device and the second electronic device belong to the same user or belong to two users with an associated relationship, Then the user of the first electronic device can obtain the first verification code received by the second electronic device, and input the first verification code into the verification code input interface of the first electronic device. In this way, the verification code can be used to verify whether the user who performs the card migration operation is a legitimate user, thereby ensuring the security of the payment card during the migration process.
  • the user only needs to input the verification code once, and does not need to input the verification code every time a payment card is bound. Moreover, the user does not need to input information such as the validity period of the payment card and the card confirmation code, which can further simplify the operation of migrating the payment card.
  • the first sending unit may be specifically used for:
  • the first verification code is sent to the payment application for logging in the account.
  • the first sending unit may be specifically used for:
  • the first verification code is sent to the communication number corresponding to the SIM card.
  • the migration unit may be specifically used for:
  • the card binding request is sent to the trusted service management TSM system, so that the TSM system unbinds the second electronic device from the bound payment card, and binds the unbound payment card with the first electronic device.
  • the payment card migration device 600 may further include:
  • the sixth receiving module is used to receive the target payment card identifier sent by the first electronic device, the target payment card identifier is the payment card identifier selected by the user in at least one payment card identifier, and the at least one payment card identifier is bound to the second electronic device payment card logo.
  • the migration module 604 can be specifically used for:
  • the target payment card bound to the second electronic device is migrated to the first electronic device, and the target payment card is the payment card corresponding to the target payment card identifier.
  • the payment card migration device 600 may further include:
  • the obtaining module is configured to obtain at least one piece of device information from the pre-stored information according to the user identity certificate corresponding to the account, where the device information includes at least one of the following hardware information of the electronic device bound with the payment card through the account.
  • the migration module 604 can be specifically used for:
  • the payment card bound to the second electronic device is migrated to the first electronic device according to the target device identifier.
  • a fifth aspect of the present application provides an electronic device, the electronic device includes: a processor and a memory storing computer program instructions, the processor implements the steps of the payment card migration method provided in the first aspect when the processor executes the computer program instructions.
  • a sixth aspect of the present application provides a server.
  • the server includes: a processor and a memory storing computer program instructions.
  • the processor implements the steps of the payment card migration method provided in the second aspect when the processor executes the computer program instructions.
  • FIG. 13 shows a schematic structural diagram of an embodiment of a payment card migration device provided by the present application.
  • the payment card migration device may be the electronic device provided in the fifth aspect of the present application or the server provided in the sixth aspect of the present application.
  • the payment card migration device may include a processor 701 and a memory 702 storing computer program instructions.
  • processor 701 may include a central processing unit (CPU), or a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • Memory 702 may include mass storage for data or instructions.
  • memory 702 may include a Hard Disk Drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a Universal Serial Bus (USB) drive or two or more A combination of more than one of the above.
  • Storage 702 may include removable or non-removable (or fixed) media, as appropriate.
  • Storage 702 may be internal or external to the integrated gateway disaster recovery device, where appropriate.
  • memory 702 is non-volatile solid state memory.
  • Memory may include read only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical/tangible memory storage devices.
  • ROM read only memory
  • RAM random access memory
  • magnetic disk storage media devices e.g., magnetic disks
  • optical storage media devices e.g., magnetic disks
  • flash memory devices e.g., electrical, optical or other physical/tangible memory storage devices.
  • a memory includes one or more tangible (non-transitory) computer-readable storage media (eg, memory devices) encoded with software including computer-executable instructions, and when the software is executed (eg, by a or multiple processors), it is operable to perform the operations described with reference to a method according to the first or second aspect of the present disclosure.
  • the processor 701 reads and executes the computer program instructions stored in the memory 702 to implement the steps of any of the payment card migration methods in the foregoing embodiments.
  • the payment card migration device may also include a communication interface 703 and a bus 710 .
  • the processor 701 , the memory 702 , and the communication interface 703 are connected through the bus 710 and complete the mutual communication.
  • the communication interface 703 is mainly used to implement communication between modules, apparatuses, units and/or devices in the embodiments of the present application.
  • bus 710 includes hardware, software, or both, coupling the components of the online data flow metering device to each other.
  • bus 710 may include Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), HyperTransport (HT) interconnect, Industry Standard Architecture (ISA) ) bus, Infiniband Interconnect, Low Pin Count (LPC) bus, Memory Bus, Microchannel Architecture (MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus or other suitable bus or a combination of two or more of the above.
  • Bus 710 may include one or more buses, where appropriate. Although embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.
  • the embodiment of the present application may provide a computer storage medium for implementation.
  • Computer program instructions are stored on the computer storage medium; when the computer program instructions are executed by the processor, any one of the payment card migration methods in the foregoing embodiments is implemented.
  • Examples of computer-readable storage media shown include non-transitory computer-readable storage media, such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc. .
  • the functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof.
  • it When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (ASIC), suitable firmware, a plug-in, a function card, or the like.
  • ASIC application specific integrated circuit
  • elements of the present application are programs or code segments used to perform the required tasks.
  • the program or code segments may be stored in a machine-readable medium or transmitted over a transmission medium or communication link by a data signal carried in a carrier wave.
  • a "machine-readable medium” may include any medium that can store or transmit information.
  • Machine-readable media may include non-transitory computer-readable storage media, such as including electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, machine
  • the readable medium may also include a radio frequency (RF) link, among others.
  • the code segments may be downloaded via a computer network such as the Internet, an intranet, or the like.
  • processors may be, but are not limited to, general purpose processors, special purpose processors, application specific processors, or field programmable logic circuits. It will also be understood that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can also be implemented by special purpose hardware for performing the specified functions or actions, or by special purpose hardware and/or A combination of computer instructions is implemented.

Abstract

一种支付卡迁移方法、装置、电子设备、服务器和介质，支付卡迁移方法包括：在第一电子设备登录账号之后，接收支付卡迁移操作（S202）；响应于支付卡迁移操作，显示至少一个设备标识（S204），至少一个设备标识为登录过账号的目标电子设备的标识；接收对至少一个设备标识中的目标设备标识的第一选中操作（S206）；响应于第一选中操作，将目标设备标识发送至服务器（S208），以使服务器将第二电子设备绑定的支付卡迁移至第一电子设备上（S210），第二电子设备为至少一个目标电子设备中与目标设备标识对应的电子设备。利用所述方法能够简化用户对支付卡的迁移操作。

Description

支付卡迁移方法、装置、电子设备、服务器和介质
相关申请的交叉引用
本申请要求享有于2021年02月05日提交的名称为“支付卡迁移方法、装置、电子设备、服务器和介质”的中国专利申请202110170123.X的优先权，该申请的全部内容通过引用并入本文中。
技术领域
本申请涉及计算机技术领域，特别是涉及一种支付卡迁移方法、装置、电子设备、服务器和介质。
背景技术
随着计算机技术的发展，网上支付变得越来越普遍。在用户利用电子设备进行网上支付之前，需要将电子设备与支付卡进行绑定，比如，通过电子设备上安装的钱包应用程序将电子设备与银行卡进行绑定。在绑定完之后，可以使用绑定的支付卡进行网上支付。
如果用户想要将一个电子设备绑定的支付卡迁移至另一个电子设备上，则用户需要先将一个电子设备与支付卡解绑，然后，将该支付卡与另一个电子设备绑定。每绑定一个支付卡，均需要用户进行解绑和绑定的操作。
因此，用户需要进行多次操作才能实现支付卡的迁移，导致用户进行支付卡的迁移操作比较繁琐。
发明内容
本申请实施例提供一种支付卡迁移方法、装置、电子设备、服务器和介质，能够解决用户进行支付卡的迁移操作比较繁琐的技术问题。
第一方面，本申请实施例提供一种支付卡迁移方法，应用于第一电子 设备，所述方法包括：
在所述第一电子设备登录账号之后，接收支付卡迁移操作；
响应于所述支付卡迁移操作，显示至少一个设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
接收对所述至少一个设备标识中的目标设备标识的第一选中操作；
响应于所述第一选中操作，将所述目标设备标识发送至服务器，以使所述服务器将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
第二方面，本申请实施例提供了一种支付卡迁移方法，应用于服务器，所述方法包括：
接收第一电子设备在登录账号之后发送的目标设备标识，所述目标设备标识为用户在至少一个设备标识中选择的设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
第三方面，本申请实施例提供了一种支付卡迁移装置，应用于第一电子设备，所述装置包括：
第一接收模块，用于在所述第一电子设备登录账号之后，接收支付卡迁移操作；
第一显示模块，用于响应于所述支付卡迁移操作，显示至少一个设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
第二接收模块，用于接收对所述至少一个设备标识中的目标设备标识的第一选中操作；
第一发送模块，用于响应于所述第一选中操作，将所述目标设备标识发送至服务器，以使所述服务器将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
第四方面，本申请实施例提供了支付卡迁移装置，应用于服务器，所述装置包括：
第三接收模块，用于接收第一电子设备在登录账号之后发送的目标设备标识，所述目标设备标识为用户在至少一个设备标识中选择的设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
迁移模块，用于根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
第五方面，本申请实施例提供了一种电子设备，所述设备包括：处理器以及存储有计算机程序指令的存储器，所述处理器执行所述计算机程序指令时实现第一方面提供的支付卡迁移方法的步骤。
第六方面，本申请实施例提供了一种服务器，所述服务器包括：处理器以及存储有计算机程序指令的存储器，所述处理器执行所述计算机程序指令时实现第二方面提供的支付卡迁移方法的步骤。
第七方面，本申请实施例提供了一种计算机存储介质，所述计算机存储介质上存储有计算机程序指令，所述计算机程序指令被处理器执行时实现第一方面提供的支付卡迁移方法或者第二方面提供的支付卡迁移方法的步骤。
根据本申请实施例的支付卡迁移方法、装置、电子设备、服务器和介质，在第一电子设备登录账号之后接收到支付卡迁移操作的情况下，显示登录过该账号的目标电子设备的设备标识；在接收到对其中的目标设备标识的第一选中操作的情况下，说明用户想要将目标设备标识对应的第二电子设备绑定的支付卡进行迁移，则将目标设备标识发送至服务器，以使服务器将第二电子设备所绑定的支付卡迁移至第一电子设备上。由此，实现了支付卡迁移。由于可以将第二电子设备绑定的支付卡批量迁移至第一电子设备上，不需要用户逐个对第二电子设备绑定的支付卡分别进行解绑操作和绑定操作，简化了用户对支付卡的迁移操作。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请提供的用于实现支付卡迁移方法的系统的一实施例的示意图。
图2是本申请提供的支付卡迁移方法的一实施例的流程示意图。
图3是本申请提供的支付卡迁移方法的另一实施例的流程示意图。
图4至图8是本申请提供的支付卡迁移方法的场景界面示意图。
图9是本申请第一方面提供的支付卡迁移方法的流程示意图。
图10是本申请第二方面提供的支付卡迁移方法的流程示意图。
图11是本申请第三方面提供的支付卡迁移装置的一实施例的结构示意图。
图12是本申请第四方面提供的支付卡迁移装置的一实施例的结构示意图。
图13示出了本申请提供的支付卡迁移设备的一实施例的结构示意图。
具体实施方式
下面将详细描述本申请的各个方面的特征和示例性实施例，为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及具体实施例，对本申请进行进一步详细描述。应理解，此处所描述的具体实施例仅意在解释本申请，而不是限定本申请。对于本领域技术人员来说，本申请可以在不需要这些具体细节中的一些细节的情况下实施。下面对实施例的描述仅仅是为了通过示出本申请的示例来提供对本申请更好的理解。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而 使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
在一些场景下需要将一个电子设备上绑定的支付卡迁移至另一个电子设备上。比如，在更换电子设备的场景下，需要将旧的电子设备上绑定的支付卡迁移至新的电子设备上。在相关技术中提供了一种换机绑卡方案，换机绑卡方案包括如下步骤：
1)用户需事先将第一电子设备与其绑定的支付卡进行解绑；
2)用户打开第二电子设备并激活，在第二电子设备上登录账号；
3)用户打开第二电子设备的钱包应用程序，点击添加卡片，然后扫描或添加卡片，选择要添加到钱包应用程序的卡片类型；
4)用户手动输入卡片详细信息，用户选择输入支付卡的卡号以及短信验证码，另外，支付卡为贷记卡时，还需要用户手动输入有效期和CVN2(Card Verification Number 2，安全码)进行验证；
5)验证通过后完成换机绑卡操作。
利用上述的换机绑卡方案可以将一个电子设备上绑定的支付卡迁移至另一个电子设备上。但是，当用户需要绑定多个支付卡时，需要重复上述步骤3-5。如此，用户需要进行多次操作才能实现支付卡的迁移，导致用户进行支付卡的迁移操作比较繁琐。
针对上述技术问题，本申请提供一种支付卡迁移方法，下面首先说明用于实现支付卡迁移方法的系统。
图1是本申请提供的用于实现支付卡迁移方法的系统的一实施例的示意图。如图1所示，用于实现支付卡迁移方法的系统包括第一电子设备102(比如新的电子设备)、服务器104、第二电子设备106(比如旧的电子设备)以及可信服务管理(Trusted Service Manager，TSM)系统108。
第一电子设备102在登录账号之后，并接收到支付卡(比如银行卡、购物卡、会员卡等)迁移操作的情况下，显示至少一个设备标识，该设备 标识为登录过上述账号的电子设备的标识，以供用户在至少一个设备标识中进行选择。第一电子设备102接收到对至少一个设备标识中的目标设备标识的第一选中操作的情况下，将目标设备标识发送至服务器104，以通知服务器104需要将目标设备标识对应的第二电子设备106绑定的支付卡迁移到第一电子设备102上。
服务器104接收到目标设备标识的情况下，将目标设备标识对应的第二电子设备106绑定的支付卡迁移至第一电子设备102上。具体地，服务器104向TSM系统108发送绑卡请求，以通过TSM系统108将第二电子设备106绑定的支付卡迁移至第一电子设备102上。
由此，实现了支付卡迁移。由于可以将第二电子设备106绑定的支付卡批量迁移至第一电子设备102上，不需要用户逐个对第二电子设备106绑定的支付卡分别进行解绑操作和绑定操作，简化了用户对支付卡的迁移操作。
基于上述系统，下面说明本申请提供的支付卡迁移方法。图2是本申请提供的支付卡迁移方法的一个实施例的流程示意图。如图2所示，支付卡迁移方法包括：
S202，第一电子设备在第一电子设备登录账号之后，接收支付卡迁移操作。
在S202中，作为一些示例，第一电子设备上可以安装有支付应用程序(比如钱包应用程序)，在第一电子设备上的支付应用程序登录账号之后，可以在支付应用程序的界面上显示支付卡迁移控件。第一电子设备接收用户对支付卡迁移控件的触控操作。用户对支付卡迁移控件的触控操作可以为点击操作、长按操作或者双击操作等。
另外，支付卡迁移操作并不限于对支付卡迁移控件的触控操作，还可以是语音输入操作，在此对支付卡迁移操作并不做限定。
支付卡迁移方法还包括：S204，第一电子设备响应于支付卡迁移操作，显示至少一个设备标识，至少一个设备标识为登录过账号的目标电子设备的标识。
在S204中，作为一些示例，第一电子设备可以向服务器发送请求， 以请求获取登录过上述账号的目标电子设备的标识。在第一电子设备接收到服务器发送的至少一个设备标识的情况下，显示至少一个设备标识，以供用户在至少一个设备标识中选择支付卡需要迁移至第一电子设备上的第二电子设备。
在本申请的实施例中，设备标识可以为登录过上述账号的目标电子设备的型号，或者，设备标识可以为用户对登录过上述账号的目标电子设备的自定义名称。
目标电子设备可以为登录过账号且绑定有支付卡的电子设备。这样，显示的至少一个设备标识为绑定有支付卡的电子设备的标识，而没有绑定有银行卡的电子设备不进行显示，从而方便用户选择出想要迁移的电子设备的标识。
支付卡迁移方法还包括：S206，第一电子设备接收对至少一个设备标识中的目标设备标识的第一选中操作。
在S206中，第一电子设备可以接收用户对至少一个设备标识中的目标设备标识的触控操作，此时用户选中目标设备标识，相当于用户选中目标设备标识对应的第二电子设备进行支付卡迁移。
支付卡迁移方法还包括：S208，第一电子设备响应于第一选中操作，将目标设备标识发送至服务器；S210，服务器接收到目标设备标识之后，将第二电子设备绑定的支付卡迁移至第一电子设备上，第二电子设备为至少一个目标电子设备中与目标设备标识对应的电子设备。
在S210中，服务器可以将绑卡请求发送至TSM系统。TSM系统接收到绑卡请求之后，将第二电子设备与绑定的支付卡进行解绑，并将已解绑的支付卡与第一电子设备绑定。
具体地，绑卡请求中可以包括第二电子设备的安全环境标识(Security environment identifier，SEID)绑定的支付卡编码(比如mpan-id)，此时，绑卡请求的绑卡申请渠道类型(applyChannelType)为“04渠道”。在TSM系统接收到绑卡请求之后，根据绑卡请求中的支付卡编码查找对应的字段(span)，根据查找到的字段执行绑卡流程。在执行绑卡流程的过程中，TSM系统向发卡行发送认证请求，以使发卡行进行校验。其中， 发卡行系统可以对以下的至少一项进行校验：CVN2(信用卡不校验此项)、有效期、动态口令(One-Time Password，OTP)、密码(借记卡不校验此项)。在发卡行校验完成之后，将第二电子设备绑定的支付卡映射关系置为连接(linked)状态，并应答给TSM系统。
通过本申请实施例，可以将第二电子设备绑定的支付卡批量迁移至第一电子设备上，不需要用户逐个对第二电子设备绑定的支付卡分别进行解绑操作和绑定操作，简化了用户进行支付卡的迁移操作。
在相关技术中，为了安全考虑，每将一个支付卡与电子设备绑定时，需要用户手动输入短信验证码，另外，当支付卡为贷记卡时，还需要用户手动输入有效期和卡确认码(Card Vеrification Number，CVN)。如此，在保证安全的情况下，绑定银行卡变得更加复杂，绑卡操作过于繁琐。
为了解决在保证安全的情况下绑卡操作过于繁琐的技术问题，在本申请的一个或多个实施例中，如图3所示，在S206之后，支付卡迁移方法还可以包括：
S212，第一电子设备显示验证码输入界面；
S214，服务器在接收到目标设备标识的情况下，根据目标设备标识向目标设备标识对应的第二电子设备发送第一验证码；
S216，第一电子设备接收在验证码输入界面上输入第二验证码的输入操作；
S218，第一电子设备响应于输入操作，将第二验证码发送至服务器。
在本申请实施例中，S210具体可以包括：服务器在验证第二验证码与第一验证码一致的情况下，说明持有第二电子设备的用户为合法用户，则服务器将第二电子设备绑定的支付卡迁移至第一电子设备上。
在本申请实施例中，在进行支付卡迁移之前，服务器向第二电子设备发送第一验证码，如果第一电子设备和第二电子设备属于同一用户或者分别属于具有关联关系的两个用户，那么第一电子设备的用户能够获取到第二电子设备接收到的第一验证码，并且将第一验证码输入至第一电子设备的验证码输入界面上。如此，可以通过验证码来验证进行卡迁移操作的用户是否为合法用户，从而保证支付卡在迁移过程中的安全性。
另外，如果需要将第二电子设备绑定的多个支付卡迁移至第一电子设备上，用户输入一次验证码即可，不需要每绑定一个支付卡就输入一次验证码。而且，用户不需要输入支付卡的有效期和卡确认码等信息，可以进一步地简化支付卡迁移的操作。
在本申请的一个或多个实施例中，服务器根据目标设备标识向目标设备标识对应的第二电子设备发送第一验证码，可以包括：
在第二电子设备的支付应用程序上登录上述账号的情况下，服务器向登录账号的支付应用程序发送第一验证码。
具体地，如果服务器向登录上述账号的支付应用程序发送第一验证码，那么第二电子设备的支付应用程序在登录上述账号且连接网络的情况下，可以通过网络接收服务器发送的第一验证码。比如，第二电子设备在连接无线网络(比如，Wi-Fi，英文全称为Wireless-Fidelity，中文名为无线保真)的情况下，可以通过无线网络接收服务器发送的第一验证码。
如此，利用同一账号可以在多个电子设备上同时登录的特性，使得第一电子设备的支付应用程序在登录账号进行支付卡迁移过程中，第二电子设备的支付应用程序也可以登录该账号，使得第二电子设备能够接收到服务器发送的第一验证码。如此，不需要用户进行额外的操作，方便用户进行支付卡的迁移。
在本申请的一个或多个实施例中，服务器根据目标设备标识向目标设备标识对应的第二电子设备发送第一验证码，可以包括：
在第二电子设备上安装客户识别模块(Subscriber Identity Module，SIM)卡，且SIM卡对应的通信号码为与账号绑定的预定通信号码的情况下，服务器向SIM卡对应的通信号码发送第一验证码。
作为一些示例，服务器可以向SIM卡对应的通信号码发送包括第一验证码的短信，或者，服务器可以向SIM卡对应的通信号码发送包括第一验证码的语音信息。
在本申请的一个或多个实施例中，第一电子设备在响应于第一选中操作之后，支付卡迁移方法还可以包括：
第一电子设备显示至少一个支付卡标识，支付卡标识为第二电子设备 绑定的支付卡的标识；
第一电子设备接收对至少一个支付卡标识中的目标支付卡标识的第二选中操作；
第一电子设备响应于第二选中操作，将目标支付卡标识发送至服务器；
服务器接收到目标支付卡标识之后，将第二电子设备绑定的目标支付卡迁移至第一电子设备上，目标支付卡为目标支付卡标识对应的支付卡。
作为一些示例，可以在第一电子设备接收对至少一个设备标识中的目标设备标识的第一选中操作之后，第一电子设备显示至少一个支付卡标识，或者，可以在第一电子设备接收到服务器发送的表征第二验证码与第一验证码一致的信息的情况下，第一电子设备显示至少一个支付卡标识。
在本申请实施例中，在用户选择对第二电子设备绑定的支付卡进行迁移之后，在第一电子设备上可以显示第二电子设备绑定的支付卡的标识，以供用户选择需要将第二电子设备绑定的哪个支付卡进行迁移。其中，用户可以根据需求选择将第二电子设备绑定的所有银行卡或者部分银行卡进行迁移。如此，用户可以自主选择迁移的支付卡，满足了用户的使用需求。
在本申请实施例中，支付卡标识可以为支付卡卡号、开卡时间、开卡公司名称。
在一些情况下，有可能出现多个电子设备的标识相同，比如，如果电子设备的标识为电子设备的型号，那么两个型号相同的电子设备的标识相同。在此情况下用户比价困难区分标识相同的电子设备，导致选择的目标设备标识并非是想要迁移的电子设备的标识。
在用户选择目标设备标识之前，为了方便用户区分各个电子设备，在本申请的一个或多个实施例中，响应于支付卡迁移操作之后，且接收对至少一个设备标识中的目标设备标识的第一选中操作之前，支付卡迁移方法还可以包括：
显示与目标电子设备绑定的支付卡的信息。
作为一些示例，可以在显示至少一个设备标识的同时，显示与各个目标电子设备绑定的支付卡的信息；还可以在接收到对某个设备标识的触控输入的情况下，显示该设备标识对应的目标电子设备绑定的支付卡信息。
在本申请实施例中，支付卡的信息可以包括以下至少一项：支付卡的开卡公司名称(比如某某银行)、支付卡的开卡公司标识、开卡时间。
在本申请实施例中，通过显示与目标电子设备绑定的支付卡的信息，方便用户区分各个电子设备，从而便于用户在至少一个设备标识中选择目标设备标识，且选择的目标设备标识是用户想要迁移的电子设备的标识。
在本申请的一个或多个实施例中，在服务器根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上之前，支付卡迁移方法还可以包括：
根据账号对应的用户身份证明(User Identification，UID)，在预先存储的信息中获取至少一个设备信息，设备信息包括以下至少一项通过账号绑定过支付卡的电子设备的硬件信息。
根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上，可以包括：
在第二电子设备的信息与至少一个设备信息中的任意一个设备信息匹配的情况下，根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上。
如此，可以进一步地验证第二电子设备是否通过上述账号绑定过支付卡。
本申请提供的任意一项实施例的支付卡迁移方法可以应用于更换电子设备的场景中，将旧的电子设备绑定的支付卡迁移至新的电子设备上。还可以应用于电子设备进行格式化的场景，在格式化之后，格式化后的电子设备没有绑定任何支付卡，利用上述任意一项实施例的支付卡迁移方法，可以将格式化之前的电子设备绑定的支付卡迁移至格式化后的电子设备上。
下面以更换电子设备为例，通过图4至图8的示意图来说明本申请提供的实施例的支付卡迁移方法。
如图4所示，在新电子设备的钱包应用程序登录账号之后，在钱包应用程序的界面上显示“一键迁移”控件。在新电子设备接收到用户对“一键迁移”控件的触控输入的情况下，显示如图5所示的界面，在图5所示的界面上显示至少一个设备标识，所述至少一个设备标识为登录过所述账号的各个电子设备的型号。
新电子设备在接收到用户对至少一个设备标识中的目标设备标识的第一选中操作的情况下，新电子设备显示如图6所示的验证码输入界面，并且将所述目标设备标识发送至服务器，以使所述服务器根据目标设备标识向旧电子设备发送第一验证码。
用户可以基于旧电子设备接收到的第一验证码，在如图6所示的验证码输入界面输入第二验证码。
新电子设备在接收到用户输入的第二验证码的情况下，将第二验证码发送至服务器，以使服务器验证第一验证码和第二验证码是否一致，并且在新电子设备上显示如图7所示的界面，该界面包括绑卡进度。
在服务器验证第一验证码和第二验证码一致的情况下，将旧电子设备绑定的支付卡迁移至新电子设备上，并在迁移成功的情况下，向新电子设备发送迁移成功的反馈信息。
新电子设备接收到迁移成功的反馈信息的情况下，显示如图8所示的迁移成功界面。
基于上述的支付卡迁移方法，下面分别说明本申请第一方面提供的支付卡迁移方法以及本申请第二方面提供的支付卡迁移方法。
图9是本申请第一方面提供的支付卡迁移方法的流程示意图。第一方面提供的支付卡迁移方法应用于第一电子设备，如图9所示，支付卡迁移方法包括：
S302，在第一电子设备登录账号之后，接收支付卡迁移操作；
S304，响应于支付卡迁移操作，显示至少一个设备标识，至少一个设备标识为登录过账号的目标电子设备的标识；
S306，接收对至少一个设备标识中的目标设备标识的第一选中操作；
S308，响应于第一选中操作，将目标设备标识发送至服务器，以使服 务器将第二电子设备绑定的支付卡迁移至第一电子设备上，第二电子设备为至少一个目标电子设备中与目标设备标识对应的电子设备。
在本申请实施例中，可以将第二电子设备绑定的支付卡批量迁移至第一电子设备上，不需要用户逐个对第二电子设备绑定的支付卡分别进行解绑操作和绑定操作，简化了用户进行支付卡的迁移操作。
在本申请的一个或多个实施例中，目标设备标识用于使服务器向第二电子设备发送第一验证码，在S306之后，支付卡迁移方法还可以包括：
显示验证码输入界面；
接收在验证码输入界面上输入第二验证码的输入操作；
响应于输入操作，将第二验证码发送至服务器，以使服务器在验证第二验证码与第一验证码一致的情况下，将第二电子设备绑定的支付卡迁移至第一电子设备上。
在本申请实施例中，在进行支付卡迁移之前，服务器向第二电子设备发送第一验证码，如果第一电子设备和第二电子设备属于同一用户或者分别属于具有关联关系的两个用户，那么第一电子设备的用户能够获取到第二电子设备接收到的第一验证码，并且将第一验证码输入至第一电子设备的验证码输入界面上。如此，可以通过验证码来验证进行卡迁移操作的用户是否为合法用户，从而保证支付卡在迁移过程中的安全性。
另外，如果需要将第二电子设备绑定的多个支付卡迁移至第一电子设备上，用户输入一次验证码即可，不需要每绑定一个支付卡就输入一次验证码。而且，用户不需要输入支付卡的有效期和卡确认码等信息，可以进一步地简化支付卡迁移的操作。
在本申请的一个或多个实施例中，在响应于第一选中操作之后，支付卡迁移方法还可以包括：
显示至少一个支付卡标识，支付卡标识为第二电子设备绑定的支付卡的标识；
接收对至少一个支付卡标识中的目标支付卡标识的第二选中操作；
响应于第二选中操作，将目标支付卡标识发送至服务器，目标支付卡标识用于指示将第二电子设备绑定的目标支付卡迁移至第一电子设备上， 目标支付卡为目标支付卡标识对应的支付卡。
在本申请实施例中，在用户选择对第二电子设备绑定的支付卡进行迁移之后，在第一电子设备上可以显示第二电子设备绑定的支付卡的标识，以供用户选择需要将第二电子设备绑定的哪个支付卡进行迁移。其中，用户可以根据需求选择将第二电子设备绑定的所有银行卡或者部分银行卡进行迁移。如此，用户可以自主选择迁移的支付卡，满足了用户的使用需求。
在本申请的一个或多个实施例中，响应于支付卡迁移操作之后，且S306之前，支付卡迁移方法还可以包括：
显示与目标电子设备绑定的支付卡的信息。
在本申请实施例中，通过显示与目标电子设备绑定的支付卡的信息，方便用户区分各个电子设备，从而便于用户在至少一个设备标识中选择目标设备标识，且选择的目标设备标识是用户想要迁移的电子设备的标识。
在本申请的一个或多个实施例中，目标电子设备可以为登录过账号且绑定有支付卡的电子设备。
图10是本申请第二方面提供的支付卡迁移方法的流程示意图。第一方面提供的支付卡迁移方法应用于服务器，如图10所示，支付卡迁移方法包括：
S402，接收第一电子设备在登录账号之后发送的目标设备标识，目标设备标识为用户在至少一个设备标识中选择的设备标识，至少一个设备标识为登录过该账号的目标电子设备的标识；
S404，根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上，第二电子设备为至少一个目标电子设备中与目标设备标识对应的电子设备。
在本申请实施例中，可以将第二电子设备绑定的支付卡批量迁移至第一电子设备上，不需要用户逐个对第二电子设备绑定的支付卡分别进行解绑操作和绑定操作，简化了用户对支付卡的迁移操作。
在本申请的一个或多个实施例中，S404可以包括：
根据目标设备标识向第二电子设备发送第一验证码；
接收第一电子设备发送的第二验证码，第二验证码为用户基于第一验证码在第一电子设备的验证码输入界面上输入的验证码；
在第二验证码与第一验证码一致的情况下，将第二电子设备绑定的支付卡迁移至第一电子设备上。
在本申请实施例中，在进行支付卡迁移之前，服务器向第二电子设备发送第一验证码，如果第一电子设备和第二电子设备属于同一用户或者分别属于具有关联关系的两个用户，那么第一电子设备的用户能够获取到第二电子设备接收到的第一验证码，并且将第一验证码输入至第一电子设备的验证码输入界面上。如此，可以通过验证码来验证进行卡迁移操作的用户是否为合法用户，从而保证支付卡在迁移过程中的安全性。
另外，如果需要将第二电子设备绑定的多个支付卡迁移至第一电子设备上，用户输入一次验证码即可，不需要每绑定一个支付卡就输入一次验证码。而且，用户不需要输入支付卡的有效期和卡确认码等信息，可以进一步地简化支付卡迁移的操作。
在本申请的一个或多个实施例中，根据目标设备标识向第二电子设备发送第一验证码，可以包括：
在第二电子设备的支付应用程序上登录账号的情况下，向登录账号的支付应用程序发送第一验证码。
在本申请的一个或多个实施例中，根据目标设备标识向第二电子设备发送第一验证码，可以包括：
在第二电子设备上安装SIM卡，且SIM卡对应的通信号码为与账号绑定的预定通信号码的情况下，向SIM卡对应的通信号码发送第一验证码。
在本申请的一个或多个实施例中，将第二电子设备绑定的支付卡迁移至第一电子设备上，可以包括：
将绑卡请求发送至TSM系统，以使TSM系统将第二电子设备与绑定的支付卡进行解绑，并将已解绑的支付卡与第一电子设备绑定。
在本申请的一个或多个实施例中，将第二电子设备绑定的支付卡迁移至第一电子设备上之前，支付卡迁移方法还可以包括：
接收第一电子设备发送的目标支付卡标识，目标支付卡标识为用户在至少一个支付卡标识中选中的支付卡标识，至少一个支付卡标识为第二电子设备绑定的支付卡的标识。
将第二电子设备绑定的支付卡迁移至第一电子设备上，可以包括：
根据目标支付卡标识，将第二电子设备绑定的目标支付卡迁移至第一电子设备上，目标支付卡为目标支付卡标识对应的支付卡。
在本申请的一个或多个实施例中，根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上之前，方法还包括：
根据账号对应的用户身份证明，在预先存储的信息中获取至少一个设备信息，设备信息包括以下至少一项通过账号绑定过支付卡的电子设备的硬件信息；
根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上，包括：
在第二电子设备的信息与至少一个设备信息中的任意一个设备信息匹配的情况下，根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上。
与本申请第一方面提供的支付卡迁移方法对应地，本申请第三方面提供一种支付卡迁移装置。图11是本申请第三方面提供的支付卡迁移装置的一实施例的结构示意图。如图11所示，支付卡迁移装置500包括：
第一接收模块502，用于在第一电子设备登录账号之后，接收支付卡迁移操作；
第一显示模块504，用于响应于支付卡迁移操作，显示至少一个设备标识，至少一个设备标识为登录过账号的目标电子设备的标识；
第二接收模块506，用于接收对至少一个设备标识中的目标设备标识的第一选中操作；
第一发送模块508，用于响应于第一选中操作，将目标设备标识发送至服务器，以使服务器将第二电子设备绑定的支付卡迁移至第一电子设备上，第二电子设备为至少一个目标电子设备中与目标设备标识对应的电子设备。
在本申请实施例中，可以将第二电子设备绑定的支付卡批量迁移至第一电子设备上，不需要用户逐个对第二电子设备绑定的支付卡分别进行解绑操作和绑定操作，简化了用户对支付卡的迁移操作。
在本申请的一个或多个实施例中，目标设备标识用于使服务器向第二电子设备发送第一验证码，支付卡迁移装置500还可以包括：
第二显示模块，用于显示验证码输入界面；
第四接收模块，用于接收在验证码输入界面上输入第二验证码的输入操作；
第二发送模块，用于响应于输入操作，将第二验证码发送至服务器，以使服务器在验证第二验证码与第一验证码一致的情况下，将第二电子设备绑定的支付卡迁移至第一电子设备上。
在本申请实施例中，在进行支付卡迁移之前，服务器向第二电子设备发送第一验证码，如果第一电子设备和第二电子设备属于同一用户或者分别属于具有关联关系的两个用户，那么第一电子设备的用户能够获取到第二电子设备接收到的第一验证码，并且将第一验证码输入至第一电子设备的验证码输入界面上。如此，可以通过验证码来验证进行卡迁移操作的用户是否为合法用户，从而保证支付卡在迁移过程中的安全性。
另外，如果需要将第二电子设备绑定的多个支付卡迁移至第一电子设备上，用户输入一次验证码即可，不需要每绑定一个支付卡就输入一次验证码。而且，用户不需要输入支付卡的有效期和卡确认码等信息，可以进一步地简化支付卡迁移的操作。
在本申请的一个或多个实施例中，支付卡迁移装置500还可以包括：
第三显示模块，用于显示至少一个支付卡标识，支付卡标识为第二电子设备绑定的支付卡的标识；
第五接收模块，用于接收对至少一个支付卡标识中的目标支付卡标识的第二选中操作；
第三发送模块，用于响应于第二选中操作，将目标支付卡标识发送至服务器，目标支付卡标识用于指示将第二电子设备绑定的目标支付卡迁移至第一电子设备上，目标支付卡为目标支付卡标识对应的支付卡。
在本申请实施例中，在用户选择对第二电子设备绑定的支付卡进行迁移之后，在第一电子设备上可以显示第二电子设备绑定的支付卡的标识，以供用户选择需要将第二电子设备绑定的哪个支付卡进行迁移。其中，用户可以根据需求选择将第二电子设备绑定的所有银行卡或者部分银行卡进行迁移。如此，用户可以自主选择迁移的支付卡，满足了用户的使用需求。
在本申请的一个或多个实施例中，支付卡迁移装置500还可以包括：
第四显示模块，用于显示与目标电子设备绑定的支付卡的信息。
在本申请实施例中，通过显示与目标电子设备绑定的支付卡的信息，方便用户区分各个电子设备，从而便于用户在至少一个设备标识中选择目标设备标识，且选择的目标设备标识是用户想要迁移的电子设备的标识。
在本申请的一个或多个实施例中，目标电子设备为登录过账号且绑定有支付卡的电子设备。
与本申请第二方面提供的支付卡迁移方法对应地，本申请第四方面提供一种支付卡迁移装置。图12是本申请第四方面提供的支付卡迁移装置的一个实施例的结构示意图。如图12所示，支付卡迁移装置600包括：
第三接收模块602，用于接收第一电子设备在登录账号之后发送的目标设备标识，目标设备标识为用户在至少一个设备标识中选择的设备标识，至少一个设备标识为登录过账号的目标电子设备的标识；
迁移模块604，用于根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上，第二电子设备为至少一个目标电子设备中与目标设备标识对应的电子设备。
在本申请实施例中，可以将第二电子设备绑定的支付卡批量迁移至第一电子设备上，不需要用户逐个对第二电子设备绑定的支付卡分别进行解绑操作和绑定操作，简化了用户进行支付卡的迁移操作。
在本申请的一个或多个实施例中，迁移模块604可以包括：
第一发送单元，用于根据目标设备标识向第二电子设备发送第一验证码；
第一接收单元，用于接收第一电子设备发送的第二验证码，第二验证 码为用户基于第一验证码在第一电子设备的验证码输入界面上输入的验证码；
迁移单元，用于在第二验证码与第一验证码一致的情况下，将第二电子设备绑定的支付卡迁移至第一电子设备上。
在本申请实施例中，在进行支付卡迁移之前，服务器向第二电子设备发送第一验证码，如果第一电子设备和第二电子设备属于同一用户或者分别属于具有关联关系的两个用户，那么第一电子设备的用户能够获取到第二电子设备接收到的第一验证码，并且将第一验证码输入至第一电子设备的验证码输入界面上。如此，可以通过验证码来验证进行卡迁移操作的用户是否为合法用户，从而保证支付卡在迁移过程中的安全性。
另外，如果需要将第二电子设备绑定的多个支付卡迁移至第一电子设备上，用户输入一次验证码即可，不需要每绑定一个支付卡就输入一次验证码。而且，用户不需要输入支付卡的有效期和卡确认码等信息，可以进一步地简化支付卡迁移的操作。
在本申请的一个或多个实施例中，第一发送单元具体可以用于：
在第二电子设备的支付应用程序上登录账号的情况下，向登录账号的支付应用程序发送第一验证码。
在本申请的一个或多个实施例中，第一发送单元具体可以用于：
在第二电子设备上安装SIM卡，且SIM卡对应的通信号码为与账号绑定的预定通信号码的情况下，向SIM卡对应的通信号码发送第一验证码。
在本申请的一个或多个实施例中，迁移单元具体可以用于：
将绑卡请求发送至可信服务管理TSM系统，以使TSM系统将第二电子设备与绑定的支付卡进行解绑，并将已解绑的支付卡与第一电子设备绑定。
在本申请的一个或多个实施例中，支付卡迁移装置600还可以包括：
第六接收模块，用于接收第一电子设备发送的目标支付卡标识，目标支付卡标识为用户在至少一个支付卡标识中选中的支付卡标识，至少一个支付卡标识为第二电子设备绑定的支付卡的标识。
迁移模块604具体可以用于：
根据目标支付卡标识，将第二电子设备绑定的目标支付卡迁移至第一电子设备上，目标支付卡为目标支付卡标识对应的支付卡。
在本申请的一个或多个实施例中，支付卡迁移装置600还可以包括：
获取模块，用于根据账号对应的用户身份证明，在预先存储的信息中获取至少一个设备信息，设备信息包括以下至少一项通过账号绑定过支付卡的电子设备的硬件信息。
迁移模块604具体可以用于：
在第二电子设备的信息与至少一个设备信息中的任意一个设备信息匹配的情况下，根据目标设备标识，将第二电子设备绑定的支付卡迁移至第一电子设备上。
本申请第五方面提供一种电子设备，电子设备包括：处理器以及存储有计算机程序指令的存储器，处理器执行计算机程序指令时实现第一方面提供的支付卡迁移方法的步骤。
本申请第六方面提供一种服务器，服务器包括：处理器以及存储有计算机程序指令的存储器，处理器执行计算机程序指令时实现第二方面提供的支付卡迁移方法的步骤。
图13示出了本申请提供的支付卡迁移设备的一实施例的结构示意图。支付卡迁移设备可以为本申请第五方面提供的电子设备或者本申请第六方面提供的服务器。
支付卡迁移设备可以包括处理器701以及存储有计算机程序指令的存储器702。
具体地，上述处理器701可以包括中央处理器(CPU)，或者特定集成电路(Application Specific Integrated Circuit，ASIC)，或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器702可以包括用于数据或指令的大容量存储器。举例来说而非限制，存储器702可包括硬盘驱动器(Hard Disk Drive，HDD)、软盘驱动器、闪存、光盘、磁光盘、磁带或通用串行总线(Universal Serial Bus，USB)驱动器或者两个或更多个以上这些的组合。在合适的情况下，存储 器702可包括可移除或不可移除(或固定)的介质。在合适的情况下，存储器702可在综合网关容灾设备的内部或外部。在特定实施例中，存储器702是非易失性固态存储器。
存储器可包括只读存储器(ROM)，随机存取存储器(RAM)，磁盘存储介质设备，光存储介质设备，闪存设备，电气、光学或其他物理/有形的存储器存储设备。因此，通常，存储器包括一个或多个编码有包括计算机可执行指令的软件的有形(非暂态)计算机可读存储介质(例如，存储器设备)，并且当该软件被执行(例如，由一个或多个处理器)时，其可操作来执行参考根据本公开第一方面或第二方面的方法所描述的操作。
处理器701通过读取并执行存储器702中存储的计算机程序指令，以实现上述实施例中的任意一种支付卡迁移方法的步骤。
在一些示例中，支付卡迁移设备还可包括通信接口703和总线710。其中，如图13所示，处理器701、存储器702、通信接口703通过总线710连接并完成相互间的通信。
通信接口703，主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。
总线710包括硬件、软件或两者，将在线数据流量计费设备的部件彼此耦接在一起。举例来说而非限制，总线710可包括加速图形端口(AGP)或其他图形总线、增强工业标准架构(EISA)总线、前端总线(FSB)、超传输(HT)互连、工业标准架构(ISA)总线、无限带宽互连、低引脚数(LPC)总线、存储器总线、微信道架构(MCA)总线、外围组件互连(PCI)总线、PCI-Express(PCI-X)总线、串行高级技术附件(SATA)总线、视频电子标准协会局部(VLB)总线或其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下，总线710可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线，但本申请考虑任何合适的总线或互连。
另外，结合上述实施例中的支付卡迁移方法，本申请实施例可提供一种计算机存储介质来实现。该计算机存储介质上存储有计算机程序指令；该计算机程序指令被处理器执行时实现上述实施例中的任意一种支付卡迁 移方法。所示的计算机可读存储介质的示例包括非暂态计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
需要明确的是，本申请并不局限于上文所描述并在图中示出的特定配置和处理。为了简明起见，这里省略了对已知方法的详细描述。在上述实施例中，描述和示出了若干具体的步骤作为示例。但是，本申请的方法过程并不限于所描述和示出的具体步骤，本领域的技术人员可以在领会本申请的精神后，作出各种改变、修改和添加，或者改变步骤之间的顺序。
以上所述的结构框图中所示的功能块可以实现为硬件、软件、固件或者它们的组合。当以硬件方式实现时，其可以例如是电子电路、专用集成电路(ASIC)、适当的固件、插件、功能卡等等。当以软件方式实现时，本申请的元素是被用于执行所需任务的程序或者代码段。程序或者代码段可以存储在机器可读介质中，或者通过载波中携带的数据信号在传输介质或者通信链路上传送。“机器可读介质”可以包括能够存储或传输信息的任何介质。机器可读介质可以包括非暂态计算机可读存储介质，比如包括电子电路、半导体存储器设备、ROM、闪存、可擦除ROM(EROM)、软盘、CD-ROM、光盘、硬盘、光纤介质，机器可读介质还可以包括射频(RF)链路，等等。代码段可以经由诸如因特网、内联网等的计算机网络被下载。
还需要说明的是，本申请中提及的示例性实施例，基于一系列的步骤或者装置描述一些方法或系统。但是，本申请不局限于上述步骤的顺序，也就是说，可以按照实施例中提及的顺序执行步骤，也可以不同于实施例中的顺序，或者若干步骤同时执行。
上面参考根据本申请的实施例的方法、装置(系统)和计算机程序产品的流程图和/或框图描述了本申请的各方面。应当理解，流程图和/或框图中的每个方框以及流程图和/或框图中各方框的组合可以由计算机程序指令实现。这些计算机程序指令可被提供给通用计算机、专用计算机、或其它可编程数据处理装置的处理器，以产生一种机器，使得经由计算机或其它可编程数据处理装置的处理器执行的这些指令使能对流程图和/或框图的 一个或多个方框中指定的功能/动作的实现。这种处理器可以是但不限于是通用处理器、专用处理器、特殊应用处理器或者现场可编程逻辑电路。还可理解，框图和/或流程图中的每个方框以及框图和/或流程图中的方框的组合，也可以由执行指定的功能或动作的专用硬件来实现，或可由专用硬件和计算机指令的组合来实现。
以上所述，仅为本申请的具体实施方式，所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、模块和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。应理解，本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。

Claims (17)

  1. 一种支付卡迁移方法，应用于第一电子设备，所述方法包括：
    在所述第一电子设备登录账号之后，接收支付卡迁移操作；
    响应于所述支付卡迁移操作，显示至少一个设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
    接收对所述至少一个设备标识中的目标设备标识的第一选中操作；
    响应于所述第一选中操作，将所述目标设备标识发送至服务器，以使所述服务器将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
  2. 根据权利要求1所述的方法，其中，所述目标设备标识用于使所述服务器向所述第二电子设备发送第一验证码；
    所述接收对所述至少一个设备标识中的目标设备标识的第一选中操作之后，所述方法还包括：
    显示验证码输入界面；
    接收在所述验证码输入界面上输入第二验证码的输入操作；
    响应于所述输入操作，将所述第二验证码发送至所述服务器，以使所述服务器在验证所述第二验证码与所述第一验证码一致的情况下，将所述第二电子设备绑定的支付卡迁移至所述第一电子设备上。
  3. 根据权利要求1所述的方法，其中，在响应于所述第一选中操作之后，所述方法还包括：
    显示至少一个支付卡标识，所述支付卡标识为所述第二电子设备绑定的支付卡的标识；
    接收对所述至少一个支付卡标识中的目标支付卡标识的第二选中操作；
    响应于所述第二选中操作，将所述目标支付卡标识发送至所述服务器，所述目标支付卡标识用于指示将所述第二电子设备绑定的目标支付卡迁移至所述第一电子设备上，所述目标支付卡为所述目标支付卡标识对应的支付卡。
  4. 根据权利要求1所述的方法，其中，所述响应于所述支付卡迁移操作之后，且所述接收对所述至少一个设备标识中的目标设备标识的第一选中操作之前，所述方法还包括：
    显示与所述目标电子设备绑定的支付卡的信息。
  5. 根据权利要求1至4中任意一项所述的方法，其中，所述目标电子设备为登录过所述账号且绑定有支付卡的电子设备。
  6. 一种支付卡迁移方法，应用于服务器，所述方法包括：
    接收第一电子设备在登录账号之后发送的目标设备标识，所述目标设备标识为用户在至少一个设备标识中选择的设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
    根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
  7. 根据权利要求6所述的方法，其中，所述根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上，包括：
    根据所述目标设备标识向所述第二电子设备发送第一验证码；
    接收所述第一电子设备发送的第二验证码，所述第二验证码为用户基于所述第一验证码在所述第一电子设备的验证码输入界面上输入的验证码；
    在所述第二验证码与所述第一验证码一致的情况下，将所述第二电子设备绑定的支付卡迁移至所述第一电子设备上。
  8. 根据权利要求7所述的方法，其中，所述根据所述目标设备标识向第二电子设备发送第一验证码，包括：
    在所述第二电子设备的支付应用程序上登录所述账号的情况下，向登录所述账号的所述支付应用程序发送所述第一验证码。
  9. 根据权利要求7所述的方法，其中，所述根据所述目标设备标识向第二电子设备发送第一验证码，包括：
    在所述第二电子设备上安装客户识别模块SIM卡，且所述SIM卡对应的通信号码为与所述账号绑定的预定通信号码的情况下，向所述SIM卡 对应的通信号码发送所述第一验证码。
  10. 根据权利要求7所述的方法，其中，所述将所述第二电子设备绑定的支付卡迁移至所述第一电子设备上，包括：
    将绑卡请求发送至可信服务管理TSM系统，以使所述TSM系统将所述第二电子设备与绑定的支付卡进行解绑，并将已解绑的支付卡与所述第一电子设备绑定。
  11. 根据权利要求7所述的方法，其中，所述将所述第二电子设备绑定的支付卡迁移至所述第一电子设备上之前，所述方法还包括：
    接收所述第一电子设备发送的目标支付卡标识，所述目标支付卡标识为用户在至少一个支付卡标识中选中的支付卡标识，所述至少一个支付卡标识为所述第二电子设备绑定的支付卡的标识；
    所述将第二电子设备绑定的支付卡迁移至所述第一电子设备上，包括：
    根据所述目标支付卡标识，将所述第二电子设备绑定的目标支付卡迁移至所述第一电子设备上，所述目标支付卡为所述目标支付卡标识对应的支付卡。
  12. 根据权利要求6至11中任意一项所述的方法，其中，所述根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上之前，所述方法还包括：
    根据所述账号对应的用户身份证明，在预先存储的信息中获取至少一个设备信息，所述设备信息包括以下至少一项通过所述账号绑定过支付卡的电子设备的硬件信息；
    所述根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上，包括：
    在所述第二电子设备的信息与所述至少一个设备信息中的任意一个设备信息匹配的情况下，根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上。
  13. 一种支付卡迁移装置，应用于第一电子设备，所述装置包括：
    第一接收模块，用于在所述第一电子设备登录账号之后，接收支付卡 迁移操作；
    第一显示模块，用于响应于所述支付卡迁移操作，显示至少一个设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
    第二接收模块，用于接收对所述至少一个设备标识中的目标设备标识的第一选中操作；
    第一发送模块，用于响应于所述第一选中操作，将所述目标设备标识发送至服务器，以使所述服务器将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
  14. 一种支付卡迁移装置，应用于服务器，所述装置包括：
    第三接收模块，用于接收第一电子设备在登录账号之后发送的目标设备标识，所述目标设备标识为用户在至少一个设备标识中选择的设备标识，所述至少一个设备标识为登录过所述账号的目标电子设备的标识；
    迁移模块，用于根据所述目标设备标识，将第二电子设备绑定的支付卡迁移至所述第一电子设备上，所述第二电子设备为至少一个所述目标电子设备中与所述目标设备标识对应的电子设备。
  15. 一种电子设备，包括：处理器以及存储有计算机程序指令的存储器；
    所述处理器执行所述计算机程序指令时实现如权利要求1-5任意一项所述的支付卡迁移方法的步骤。
  16. 一种服务器，包括：处理器以及存储有计算机程序指令的存储器；
    所述处理器执行所述计算机程序指令时实现如权利要求6-12任意一项所述的支付卡迁移方法的步骤。
  17. 一种计算机存储介质，所述计算机存储介质上存储有计算机程序指令，所述计算机程序指令被处理器执行时实现如权利要求1-12任意一项所述的支付卡迁移方法的步骤。
PCT/CN2021/118145 2021-02-05 2021-09-14 支付卡迁移方法、装置、电子设备、服务器和介质 WO2022166208A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022564657A JP2023523053A (ja) 2021-02-05 2021-09-14 支払カードの移行方法、装置、電子機器、サーバ及び媒体
US17/920,596 US11875336B2 (en) 2021-02-05 2021-09-14 Method and apparatus for migrating payment card, electronic device, server and medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110170123.X 2021-02-05
CN202110170123.XA CN112801655B (zh) 2021-02-05 2021-02-05 支付卡迁移方法、装置、电子设备、服务器和介质

Publications (1)

Publication Number Publication Date
WO2022166208A1 true WO2022166208A1 (zh) 2022-08-11

Family

ID=75814761

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/118145 WO2022166208A1 (zh) 2021-02-05 2021-09-14 支付卡迁移方法、装置、电子设备、服务器和介质

Country Status (5)

Country Link
US (1) US11875336B2 (zh)
JP (1) JP2023523053A (zh)
CN (1) CN112801655B (zh)
TW (1) TWI814142B (zh)
WO (1) WO2022166208A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112801655B (zh) 2021-02-05 2024-02-23 中国银联股份有限公司 支付卡迁移方法、装置、电子设备、服务器和介质
CN115049387A (zh) * 2021-03-09 2022-09-13 北京同邦卓益科技有限公司 支付卡片绑定方法、装置、电子设备及存储介质
CN113807843B (zh) * 2021-09-06 2023-10-20 中国银联股份有限公司 绑卡方法、用户终端、服务器、系统及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109544135A (zh) * 2018-10-25 2019-03-29 北京三快在线科技有限公司 银行卡绑定方法、装置、存储介质和移动终端
CN111311251A (zh) * 2020-05-09 2020-06-19 支付宝(杭州)信息技术有限公司 绑定处理方法、装置及设备
CN112118227A (zh) * 2017-11-29 2020-12-22 华为技术有限公司 绑卡方法及终端
US10902405B1 (en) * 2016-05-11 2021-01-26 Wells Fargo Bank, N.A. Transient mobile wallets
CN112801655A (zh) * 2021-02-05 2021-05-14 中国银联股份有限公司 支付卡迁移方法、装置、电子设备、服务器和介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004287594A (ja) 2003-03-19 2004-10-14 Sony Corp 決済システムおよび方法、携帯情報端末および情報処理方法、情報管理装置および方法、並びにプログラム
CN103746792B (zh) 2013-12-31 2017-11-07 郑盈盈 一种第三方应用账号与手机号码绑定、解除和更新方法
CN104618415B (zh) * 2014-03-13 2018-06-19 腾讯科技（深圳）有限公司 信用账户创建方法、装置及系统
US11017373B2 (en) 2017-01-25 2021-05-25 Huawei Technologies Co., Ltd. Bank card adding method, and apparatus
CN112258178B (zh) 2018-01-23 2024-01-26 创新先进技术有限公司 支付卡的绑定方法、信任评估方法、装置和电子设备
CN110545526A (zh) 2018-05-28 2019-12-06 王正伟 移动通信控制方法
CN110288332A (zh) * 2019-06-28 2019-09-27 北京三快在线科技有限公司 银行卡绑定的系统、方法、装置、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10902405B1 (en) * 2016-05-11 2021-01-26 Wells Fargo Bank, N.A. Transient mobile wallets
CN112118227A (zh) * 2017-11-29 2020-12-22 华为技术有限公司 绑卡方法及终端
CN109544135A (zh) * 2018-10-25 2019-03-29 北京三快在线科技有限公司 银行卡绑定方法、装置、存储介质和移动终端
CN111311251A (zh) * 2020-05-09 2020-06-19 支付宝(杭州)信息技术有限公司 绑定处理方法、装置及设备
CN112801655A (zh) * 2021-02-05 2021-05-14 中国银联股份有限公司 支付卡迁移方法、装置、电子设备、服务器和介质

Also Published As

Publication number Publication date
TW202232405A (zh) 2022-08-16
JP2023523053A (ja) 2023-06-01
CN112801655A (zh) 2021-05-14
US20230153789A1 (en) 2023-05-18
CN112801655B (zh) 2024-02-23
US11875336B2 (en) 2024-01-16
TWI814142B (zh) 2023-09-01

Similar Documents

Publication Publication Date Title
WO2022166208A1 (zh) 支付卡迁移方法、装置、电子设备、服务器和介质
US11531976B2 (en) Systems and methods for facilitating card present transactions
AU2018202542B2 (en) Automated account provisioning
US8346672B1 (en) System and method for secure transaction process via mobile device
CN104145297B (zh) 轮辐式个人识别号码验证
US20170116596A1 (en) Mobile Communication Device with Proximity Based Communication Circuitry
EP3652694A1 (en) Systems and methods for using a transaction identifier to protect sensitive credentials
JP7454052B2 (ja) データ処理方法、装置、デバイス及び媒体
US11023880B2 (en) Online mobile payment system and method using authentication codes
WO2022247842A1 (zh) 一种认证服务器、卡认证系统、免密认证方法和系统
US9836618B2 (en) System and method of authentication of a first party respective of a second party aided by a third party
US11257063B2 (en) Telephone call purchase with payment using mobile payment device
US11645643B2 (en) System for harnessing a connected network to securely verify a transaction
CN114463012A (zh) 认证方法、支付方法、装置及设备
CN105577742A (zh) 一种数据转移方法及移动终端
CN103457730B (zh) 安全性信息交互装置及方法和用于安全性信息交互的ic卡
CN106982202B (zh) 安全性信息交互方法及装置
KR101419260B1 (ko) 와이브로 통신 기능이 구비된 차량단말을 이용한 금융거래 서비스 제공방법 및 시스템
CN115511609A (zh) 业务办理方法及装置
CN117974133A (zh) 数字货币交易方法和终端
TW201837766A (zh) 利用國際行動設備識別碼及國際行動用戶識別碼進行認證的網路會員認證方法

Legal Events

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

Ref document number: 21924205

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022564657

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21924205

Country of ref document: EP

Kind code of ref document: A1