Payment Card Network and Self-Controlled Wallet / Payment Card for Blockchain Transactions

Abstract

The self-managed wallet and payment card includes an electronic component having a storage device, a processor, and a near field communication interface. When two programs are stored on the electronic component and provisioned, the electronic component stores one or more blockchain addresses and security keys. The two programs can include a payment application capable of interfacing with a point-of-sale terminal (e.g., following EMV specifications) and a cryptographic application capable of securely storing keys and returning signatures for blockchain transactions.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 234,481, filed August 18, 2021, the entire disclosure of which is incorporated herein by reference. [Background technology]

[0002] As digital currencies such as cryptocurrencies become more widely accepted by the general public, it will also be important to support payment transactions at merchants that are currently set up only with traditional payment cards and payments via banking networks. In addition, since most financial services are regulated with guidelines that include standards such as KYC (Know Your Customer), which involves verifying the identity of customers, their suitability, and the risks associated with fraud, corruption, money laundering, etc., it may be important to provide a path to KYC for cryptocurrency wallets. Summary of the Invention

[0003] A self-managed wallet and payment card for payment card networks and blockchain transactions is provided. Digital assets can be used in payment transactions over traditional payment card networks using the self-managed wallet and payment card described above.

[0004] The self-managed wallet and payment card includes an electronic component having a storage device, a processor, and a near field communication interface. Two programs are stored on the electronic component, and when provisioned, the electronic component stores one or more blockchain addresses and security keys. The two programs include a payment application capable of interfacing with a point of sale terminal (e.g., following EMV specifications) and a cryptographic application capable of securely storing keys and returning signatures for blockchain transactions.

[0005] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. [Brief description of the drawings]

[0006] [Figure 1] Figure 1A shows a representative diagram of a self-controlled wallet and payment card. Figure 1B shows an exemplary operating environment for a payment card network and a self-controlled wallet and payment card for blockchain transactions. [Figure 2A] 1 shows a process flow diagram for operations performed with a self-directed wallet and payment card; [Figure 2B] 1 shows a process flow diagram of operations performed with a self-controlled wallet and payment card; FIG shows a process flow diagram for topping-up a controlled wallet; [Figure 2C] 1 shows a process flow diagram of operations performed with a self-directed wallet and payment card; FIG shows a process flow diagram for a self-directed use case; [Diagram 3] FIG. 1 illustrates a schematic diagram of an exemplary self-controlled wallet and payment card. [Figure 4] FIG. 1 illustrates a schematic diagram of an exemplary computing device that supports a self-managed wallet and payment card. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] A self-managed wallet and payment card for payment card networks and blockchain transactions is provided. Digital assets can be used in payment transactions over traditional payment card networks using the self-managed wallet and payment card described above.

[0008] A self-managed wallet and payment card provides a chip card that can function as both a crypto card and a hardware wallet.

[0009] A chip card is a payment card that includes electronic components with secure storage and secure processing. Secure storage is used to store sensitive information such as cryptographic keys and security data. Storage can be considered as a secure storage where the storage is intended to be protected from unwanted access. Secure storage is usually a non-volatile memory that can include protection mechanisms. Encrypted binary large object (blob) keys, tamper-proof protection, and private key bus are some common protection mechanisms used to provide secure storage. Secure processing includes cryptographic processing. This includes generation, verification, and certification of cryptographic keys (e.g., public and private keys). A designated hardware processor or processing element (with or without hardware accelerators) can be used for secure processing. Most chip cards comply with the EMVCo standard.

[0010] A crypto-card is a payment card associated with a crypto-wallet. Funds associated with the payment card are managed via the crypto-wallet.

[0011] A crypto wallet refers to an application that allows for the secure storage and management of digital assets such as cryptocurrencies. Crypto wallets are provided by a crypto wallet provider and can typically hold multiple cryptocurrencies. Crypto wallets can be implemented in a variety of forms, including hot wallets and cold wallets.

[0012] A hot wallet refers to a crypto wallet that is connected to the internet, for example in the form of a mobile wallet on a phone. Since the information in a hot wallet is stored online, it is vulnerable to hacking.

[0013] A cold wallet refers to a crypto wallet that is not connected to the internet, such as a paper / physical wallet (i.e., they record information) or a hardware wallet. Information stored in a cold wallet is safe from online hacks, but can be lost or stolen if proper care is not taken.

[0014] A hardware wallet refers to a wallet where the security keys are stored in hardware. A typical hardware wallet can take the form of a dongle. Hardware wallets are suitable for self-managed / self-regulated wallets.

[0015] A self-managed / self-managed wallet is a wallet whose keys are owned and managed by the user / owner. Self-managed wallets can be hot (e.g., online) or cold (e.g., hardware).

[0016] A managed wallet is one where the keys are controlled by the wallet provider, rather than by the user / owner.

[0017] FIG. 1A shows a representative diagram of a self-managed wallet and payment card. With reference to FIG. 1A, a self-managed wallet and payment card 100 is provided, including an electronic component 101 having a storage device 102, a processor 103, and a near-field communication interface 104. The electronic component 101 of the self-managed wallet and payment card 100 can be embodied as described with respect to the computing device 300 of FIG. 3. The storage device 102 can be or include a secure storage device. The processor 103 can be or include a secure processing component (e.g., a processing element that includes a protection mechanism and / or includes a cryptographic accelerator). Once the two programs are stored and provisioned in the electronic component, the electronic component stores one or more blockchain addresses and security keys in the storage device 102.

[0018] The two programs include a payment application 105, such as a traditional payment application (e.g., following the EMV standard), and a crypto application 106 that can securely store keys (e.g., key 108) and return signatures for blockchain transactions. The self-managed wallet and payment card further stores at least one blockchain address (e.g., blockchain address 107) for a crypto card wallet account, which is a different address than for the digital assets managed by the crypto application (which provides the self-managed wallet on the payment card). The management of the keys that control this blockchain address for the crypto card wallet account (which is not an address managed by the crypto application which provides the self-managed wallet) is done with the crypto wallet provider.

[0019] A self-controlled wallet and payment card can be provisioned with a primary account number (PAN) 109. The PAN 109 can be associated with a controlled wallet such as that implemented by a crypto-card, which is described in more detail with respect to Figures 1B and 2A.

[0020] The described self-controlled wallet and payment card can provide a cost-effective hardware wallet for securely storing and easily accessing security keys (e.g., keys 108) that allow holders to verify cryptocurrency transactions and prove ownership / access to cryptocurrency. This hardware wallet functionality enables self-controlled wallet use cases.

[0021] FIG. 1B illustrates an exemplary operating environment for a self-controlled wallet and payment card for payment card networks and blockchain transactions. Referring to FIG. 1B, as described with respect to FIG. 1A, the self-controlled wallet and payment card 100 includes two programs (e.g., a payment application 105 and a crypto application 106) stored on an electronic component. During initial setup / configuration of the card 100, the crypto application 106 is configured with a blockchain address (e.g., stored as BCA-CW 107) of a managed wallet account managed by the crypto wallet provider 110. The crypto wallet provider 110 provides the managed wallet by controlling / managing the security keys of the account. As mentioned above, this blockchain address (BCA-CW 107) is a different address than the one for the digital assets managed by the crypto application 106 (and for the self-controlled wallet on the payment card). The blockchain address BCA-CW 107 can be used as a receiving address on the blockchain for managed wallet deposit scenarios (e.g., transfers from self-controlled wallet to managed wallet).

[0022] The crypto application 106 can be managed by a mobile application ("mobile app") 120, which also supports self-managed use cases. The mobile app 120 can be a standalone application or can be integrated as part of an issuer's (e.g., bank's) application or a wallet application (e.g., of a crypto wallet provider), as some examples. The mobile app 120 is stored in a memory unit and executed by a processor of a computing device, as described in more detail with respect to FIG.

[0023] The configuration of a self - managed wallet can be done by the user upon receiving the card. The card supports creating a wallet with a new key and creating a wallet by introducing an existing key. During the process of creating a self - managed wallet, the self - managed account is associated with the consumer who owns the cryptographic card account. The association can occur by linking the blockchain address for the assets of the managed wallet (e.g., BCA - CW107) to the blockchain address for the assets of the self - managed wallet (this can then be received by the associating entity as part of an activation request). This association can be stored by the associating entity. The associating entity can be, by way of example, an issuer (e.g., a bank), a wallet provider, or a self - managed platform / application provider. If the associating entity is an issuer, a processor, or a managed wallet provider that has access to the card's PAN, the association can, in some cases, include <PAN, blockchain address for the assets of the managed wallet, blockchain address for the assets of the self - managed wallet>. An exemplary initial setup process is shown in Figure 2A.

[0024] For example, the crypto application 106 can create a self-managed wallet by establishing a private key associated with a self-managed blockchain address in response to receiving a request to create a wallet from a mobile app. As described with respect to the example initial setup process of FIG. 2A, the request to create a wallet can include authentication information (e.g., a PIN or biometric). The crypto application 106 can verify the authentication information, create the wallet (e.g., generate a key and a self-managed blockchain address), and provide the activation request information (e.g., a blockchain address) to the mobile app. The wallet can initially be created in a non-valid state (e.g., an available but non-valid key) until the crypto application 106 receives a request from the mobile app to activate the wallet. In one operation, the crypto application 106 can check to ensure that the private key is in a valid state before using it to sign a transaction request. The request to activate the wallet can include an activation certificate, which can be generated by the managed wallet provider. The mobile app can map the blockchain address of the self-managed wallet to the blockchain address of the user's managed wallet.

[0025] Use cases for the card 100 can include loading a crypto card (e.g., loading a managed wallet associated with the crypto card using funds from a self-managed wallet). In a loading scenario, a consumer can initiate a loading use case and specify an amount to apply in the mobile app 120. The crypto application 106 can be used to add an amount of cryptocurrency value to a managed wallet associated with a blockchain address stored on the card 100 via communication with the mobile application over a near-field communication channel. For example, the mobile app 120 can request the consumer to authenticate themselves (e.g., via a PIN or biometric) and request the consumer to tap the card 100 to the mobile device 120 (setting up a near-field communication channel via the card interface 104, such that a near-field communication channel is established between the card 100 and a computing device running the mobile app 120). The consumer can perform the requested action, including tapping the card 100 on the mobile device 120. The crypto application 106 can sign and send the transaction signature back to the mobile app 120. For example, a calculation is performed to generate a signed transaction request using the self-managed wallet account's key and blockchain address (e.g., key, blockchain address 108) and the managed wallet account's blockchain address (blockchain address 107). The mobile app 120 initiates the blockchain transaction via some node 130 or sets the appropriate address location 140 via the blockchain network 150. An exemplary deposit process is shown in FIG. 2B.

[0026] For payments at a merchant (e.g., for payments based on digital / cryptocurrency), the card 100 can be used at a payment terminal (merchant's point of sale terminal (POS) 160) in a conventional manner. For example, in response to a payment request by a payment application 105 at the POS 160 (e.g., including PAN 109 of FIG. 1A), the POS 160 communicates an authorization request to the acquirer 170 to the issuer / processor 190 via the payment network 180. Because the PAN (e.g., PAN 109 of FIG. 1A) is associated with the crypto wallet provider, the issuer / processor 190 can identify the PAN in the authorization request as part of the crypto wallet provider 110 and communicate with the crypto wallet provider 110. The crypto wallet provider 110 can respond to the authorization request, with the authorization response being based on funds available in the wallet account.

[0027] The described self-managed wallet and payment card can provide a crypto card “associated” with a self-managed wallet. An entity (e.g., an issuer (e.g., a bank), a wallet provider, or a self-managed platform / application provider, etc.) can provide a relationship mapping between the crypto card wallet account (with associated KYC information) and the self-managed wallet in the self-managed wallet and payment card. By associating ownership of the self-managed wallet with the consumer who owns the crypto card, a KYC path is provided for the self-managed wallet. Although the self-managed application (crypto application 106) and the managed application (with crypto wallet provider 110 / payment application 105) are separate, their ownership can be associated. When the self-managed application is configured (either with the creation of a new wallet or the introduction of a key for an existing wallet), the crypto application 106 communicates the blockchain address of the self-managed wallet (e.g., stored as part of 108) to the appropriate entity (e.g., issuer, wallet provider, etc.). In some cases, the crypto application 106 can be configured to not have access to the self-managed keys (e.g., 108) unless the crypto application 106 informs an appropriate entity (e.g., crypto wallet provider, card issuer, or self-managed application provider) of the blockchain address (of the self-managed wallet) corresponding to the key and obtains an activation certificate from the entity. Additionally, by incorporating a traditional payment application 105 and PAN 109 associated with a crypto card / managed wallet, the card can provide both self-managed functionality (consumer owns the key) and managed functionality (consumer can use the card to make payments at retail merchants). Thus, it is possible to achieve KYC for a blockchain account / address and still hold the key.

[0028] Advantageously, the described self-controlled wallet and payment card does not require the multi-step process that a consumer with self-controlled funds must go through to spend the self-controlled funds at a retail merchant, which includes creating a controlled wallet account with a wallet provider that provides a crypto card, transferring funds to the controlled wallet account, and using the crypto card to spend at the merchant. Rather, the consumer can use the self-controlled wallet and payment card that includes both the self-controlled wallet hardware wallet and a traditional payment application with a PAN associated with the controlled wallet to spend with digital assets. A simple top-off process (e.g., as described with respect to FIG. 2B) can be performed to transfer digital assets from the self-controlled wallet to the controlled wallet as needed.

[0029] Figures 2A-2C show process flow diagrams for operations performed with a self-managed wallet and payment card. Figure 2A shows a process flow diagram for initially setting up a crypto application. Figure 2B shows a process flow diagram for depositing funds into a managed wallet. Figure 2C shows a process flow diagram for a self-managed use case.

[0030] 2A, the consumer 200 can begin configuring the crypto app 106 by selecting the appropriate options on the mobile app 120 (202). In some cases, the mobile app 120 may request more information from the consumer 200 about the network (Ethereum, blockchain, etc.) and a new / existing wallet (204). If there is an existing wallet, the mobile app 120 can capture a mnemonic word. In operation 206, the mobile app 120 asks the consumer 200 to enter a crypto app PIN and tap their card. The consumer 200 will continue the process by entering the PIN and tapping their card.

[0031] At operation 208, the mobile app 120 submits the PIN to the crypto app 106 and requests that the crypto app 106 create a wallet. For example, the mobile app 120 may send a request to "create a new wallet for the Ethereum network" or "create a Bitcoin wallet for an existing key."

[0032] At operation 210, the crypto app 106 verifies the PIN, creates the wallet / keys (prk.sc=self-managed private key, bca.sc=self-managed blockchain address) in an inactive state, and provides “activation request” information to the mobile app 120.

[0033] At operation 212, the mobile app 120 provides an activation request to the crypto wallet provider 110 that manages the managed wallet, requesting an "activation certificate."

[0034] In operation 214, the crypto wallet provider 110 verifies the request and provides a certificate. In one case, the certificate is a signature of bca.sc using prk.c (the private key of the managed wallet owned by the managed wallet provider). At this point, bca.c (bca.c=blockchain address of the managed wallet) and bca.sc are associated.

[0035] At operation 216, the mobile app 120 requests the crypto app 106 to activate the wallet by providing an "activation certificate." At operation 218, the crypto app 106 verifies the "activation certificate" and responds with the results. The verification can be done using a public key that the crypto app 106 possesses, derived from bca.c. The mobile app 120 can then notify the consumer of the activation at operation 220.

[0036] The following table shows the parameters for steps A (202), E (210), and H (216).

[0037] [Table 1]

[0038] 2B, the consumer 200 can initiate a deposit into a managed wallet managed by the crypto wallet provider 110 by selecting the appropriate option on the mobile app 120 (222). In some cases, the mobile app 120 may request more information about the digital assets such as for a deposit (224). In operation 226, the mobile app 120 asks the consumer 200 to enter a crypto app PIN and tap their card. The consumer 200 will continue the process by entering the PIN and tapping their card.

[0039] At operation 228, the mobile app 120 submits the PIN to the crypto app 106 and requests the crypto app 106 to provide a transaction signature that can be submitted to the blockchain 150.

[0040] At operation 230, the crypto app 106 verifies the PIN, formats the transaction, signs the transaction using prk.sc, and provides the transaction signature to the mobile app 120. The transaction signature may include the controlled blockchain address (bca.c) as the receiving / recipient address. Before signing the transaction with the private key, the crypto app 106 ensures that the private key is in an activated state.

[0041] In operation 232, the mobile app 120 sends the transaction to the blockchain network 150. An option for this operation is to go through node 130 as described with respect to FIG. 1B.

[0042] In operation 234, the blockchain 150 incorporates / executes the transaction.

[0043] In operation 236, as a result of the transaction, the managed wallet provider 110 may identify the transaction (beneficiary=bca.c) and update the balance associated with bca.c.

[0044] In operation 238, the mobile app 120 obtains the balance from the managed wallet provider 110 and updates its interface so that the consumer 200 can view the balance in both the self-managed and managed wallets via the mobile app 120.

[0045] 2C, the consumer 200 can initiate a self-governing use case by selecting (240) an appropriate self-governing use case (e.g., P2P) on the mobile app 120. In some cases, the mobile app may request (242) more information about the digital asset, blockchain address, etc. In operation 244, the mobile app 120 asks the consumer 200 to enter a crypto app PIN and tap the card. The consumer 200 will continue the process by entering the PIN and tapping the card.

[0046] At operation 246, the mobile app 120 submits the PIN to the crypto app 106 and requests the crypto app 106 to provide a transaction signature that can be submitted to the blockchain 150. At operation 248, the crypto app 106 verifies the PIN, formats the transaction, signs the transaction using prk.sc, and provides the transaction signature to the mobile app 120. Before signing the transaction using the private key, the crypto app 106 ensures that the private key is in an activated state. At operation 250, the mobile app 120 sends the transaction to the blockchain network 150 (e.g., via node 130). At operation 252, the mobile app 120 can notify the consumer 200 of the transaction.

[0047] 3 shows a schematic diagram of an exemplary self-managed wallet and payment card. Referring to FIG. 3, a computing device 300 may include a processor 310, a memory device 320, and a short-range communications interface 330 (short-range, broadband, or other common short-range communications protocol), coupled, for example, via a system bus 340.

[0048] The processor 310 may include one or more of any suitable processing devices ("processors"), such as a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a logic circuit, a state machine, etc.

[0049] The storage device 320 may include a first persistent (e.g., non-volatile) storage unit 350 that stores instructions 352 of a payment application (e.g., payment application 105), a first non-volatile storage unit 360 that stores payment credentials (e.g., including PAN) for a payment card profile 362, a second persistent (e.g., non-volatile) storage unit 370 that stores instructions 372 of a crypto application (e.g., crypto application 106), and a second non-volatile storage unit 380 that stores keys 382 and blockchain addresses 384.

[0050] A short-range communication interface 330 (short-range, wideband, or other common communication protocol) can be used to communicate with contactless readers and mobile devices (e.g., computing device 400 of FIG. 4). Exemplary protocols for the short-range communication interface 330 include BLUETOOTH and Zigbee.

[0051] In one case, the payment application instructions 352 and the crypto application instructions 372 can be implemented as part of a smart card computing environment, such as the Java Card Platform, in which the applets (of the two applications) are run (e.g., executed by the processor 310). In such a case, the first persistent storage unit 350 and the second persistent storage unit 370 are part of the secure storage unit of the computing device / card. In addition, at least the key 382 will be stored as part of the secure storage unit of the computing device / card. Although four separate storage units are described, it should be understood that these may be implemented as part of one or more of the same storage devices in separate areas / memory areas.

[0052] 4 shows a schematic diagram of an exemplary computing device supporting a self-managed wallet and payment card. With reference to FIG. 4, computing device 400 may include a processor 410, a storage device 420, a communication interface 430 including a short-range communication interface 432 (short-range, wideband, or other common short-range communication protocol) and a network interface 434, and a user input / output (I / O) interface 440, coupled, for example, via a system bus 450.

[0053] Computing device 400 may represent a computing device such as, but not limited to, a personal computer, a reader, a mobile device, a personal digital assistant, a wearable computer, a smartphone, a tablet, a laptop computer (notebook or netbook), a desktop computer, etc. Thus, more or fewer elements described with respect to computing device 400 may be incorporated to implement a particular computing device.

[0054] The processor 410 may include one or more processing elements, examples of which include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), a field programmable gate array (FPGA), a microprocessor, an application specific integrated circuit (ASIC), a logic circuit, and a state machine.

[0055] Storage 420 may include volatile and non-volatile memory, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Examples of storage 420 include random access memory, read-only memory, magnetic disks, optical disks, CDs, DVDs, flash memory, magnetic disk storage or other magnetic storage devices, or any other suitable storage medium. In no case is the storage medium (or any storage medium described herein) a transitory, propagating signal.

[0056] The processor 410 may transform or manipulate data according to instructions of software, including an operating system (OS) 460 and any applications 470 stored on the storage device 420. The OS 460 controls and coordinates the functioning of various components within the computing device 400, including allowing the applications 470 to interface with low-level interfaces such as networking interfaces. The application(s) 470 include the mobile app 120, which may be a standalone application or may be integrated into other applications in the computing device 400.

[0057] The communication interface 430 may include communications connections and devices that enable communication with other computing systems over one or more communications networks (not shown). The short-range communication interface 432 may include interfaces for short-range, wideband, and / or other wireless communication protocols that provide wireless connectivity within a local area of ​​interaction. Exemplary protocols for the short-range communication interface 330 include BLUETOOTH and Zigbee. The network interface 434 may include interfaces for accessing a local area network and / or the Internet.

[0058] User (I / O) interface 440 supports input devices, such as a mouse, trackpad, keyboard, touch devices for receiving touch gestures from a user, motion input devices for detecting non-touch gestures and other movements by the user, microphones for detecting voice, and / or other types of input devices and associated processing elements capable of receiving user input, and output devices, such as a display screen (e.g., for displaying a graphical user interface such as that displayed for mobile app 120), speakers, haptic devices for tactile feedback, and / or other types of output devices.

[0059] As described in the use case scenarios herein, a computing device 400 running a mobile app 120 communicates with the self-managed wallet and payment card 100 to provide an interface to facilitate initial setup and loading of the card. A communication channel between the computing device 400 and the self-managed wallet and payment card 100 is implemented by a communication interface 430, for example via a short-range / near-field communication interface 432 that facilitates short-range / near-field wireless communication between the card 100 and the computing device 400.

[0060] Although the subject matter has been described in language specific to structural features and / or operations, it is to be understood that the subject matter defined in the appended claims need not be limited to the specific features or operations described above. Rather, the specific features and operations described above are disclosed as example implementations of the claims, and other equivalent features and operations are intended to be within the scope of the claims.

Claims

1. A self-managed wallet and payment card, A storage device; A processor; a short-range communication interface for establishing a short-range communication channel; A payment application stored in the storage device; and a cryptographic application stored on the storage device; and A blockchain address of a crypto card wallet account stored in the storage device; a self-managed wallet security key stored in said storage device; the cryptographic application performs calculations to generate a signed transaction request using the security key stored in the storage device. A self-managed wallet and payment card.

2. 2. The self-controlled wallet and payment card of claim 1, further comprising a primary account number (PAN) stored in the storage device, the PAN being associated with the crypto card wallet account.

3. 3. The self-managed wallet and payment card of claim 2, wherein the payment application communicates a payment request to a payment terminal via the short-range communications channel, the payment request including the PAN.

4. 2. The self-managed wallet and payment card of claim 1, wherein the cryptographic application, in response to a request to create a wallet from a mobile application over the near field communications channel, creates the self-managed wallet by establishing a private key associated with a self-managed blockchain address, the private key being stored as part of the security key for the self-managed wallet stored in the storage device.

5. 5. The self-managed wallet and payment card of claim 4, wherein the cryptographic application comprises: receiving the request to create the wallet from the mobile application over the short range communications channel, the request to create the wallet including authentication information; verifying the authentication information; and creating said private key in a non-validated state; generating said self-managed blockchain address; providing the self-managed blockchain address to the mobile application via the short-range communications channel; receiving a request to activate the wallet from the mobile application via the near field communication channel, the request to activate the wallet including an activation certificate generated by a managed wallet provider associated with the blockchain address of the crypto card wallet account; Activating the wallet by setting the private key to a valid state; A self-managed wallet and payment card that:

6. 2. The self-managed wallet and payment card of claim 1 , wherein the crypto application performs the calculations and generates the signed transaction request in response to receiving a deposit request for a controlled wallet associated with the blockchain address of the crypto card wallet account from a mobile application over the near field communications channel.

7. 7. The self-managed wallet / payment card according to claim 6, The crypto application performs the calculations and generates the signed transaction request using the security key of the self-managed wallet, the signed transaction request indicating the blockchain address of the crypto-card wallet account as a receiving address.

8. 8. The self-managed wallet and payment card of claim 7, wherein the cryptographic application comprises: receiving a deposit request for the managed wallet associated with the blockchain address of the crypto card wallet account from the mobile application via the short range communications channel, the deposit request including authentication information; verifying the authentication information; and formatting a transaction request; signing the transaction request using the security key to generate the signed transaction request; providing the signed transaction request to the mobile application via the short-range communications channel; A self-managed wallet and payment card that:

9. 2. The self-managed wallet and payment card of claim 1, wherein the cryptographic application performs the calculations and generates the signed transaction request in response to receiving a self-managed wallet transaction request from a mobile application over the near field communications channel.

10. 10. The self-managed wallet and payment card of claim 9, wherein the cryptographic application comprises: receiving the self-managed wallet transaction request from the mobile application via the short-range communications channel, the self-managed wallet transaction request including authentication information and a receiving address; verifying the authentication information; and formatting a transaction request; signing the transaction request using the security key to generate the signed transaction request; providing the signed transaction request to the mobile application via the short-range communications channel; A self-managed wallet and payment card that:

11. 1. A method of operating a self-managed wallet and payment card, comprising: A storage device; A processor; a short-range communication interface for establishing a short-range communication channel; A payment application stored in the storage device; and a cryptographic application stored on the storage device; and A blockchain address of a crypto card wallet account stored in the storage device; said method comprising: creating, by the cryptographic application, a self-managed wallet by establishing, in response to a request to create a wallet from a mobile application over the short range communications channel, a private key associated with a self-managed blockchain address; storing the private key associated with the self-managed blockchain address of the self-managed wallet in the storage device; A method comprising:

12. 12. The method of claim 11, wherein creating the self-managed wallet comprises: receiving the request to create the wallet from the mobile application over the short range communications channel, the request to create the wallet including authentication information; verifying the authentication information; and creating said private key in a non-validated state; generating said self-managed blockchain address; providing the self-managed blockchain address to the mobile application via the short-range communications channel; receiving a request to activate the wallet from the mobile application via the near field communication channel, the request to activate the wallet including an activation certificate generated by a managed wallet provider associated with the blockchain address of the crypto card wallet account; Activating the wallet by setting the private key to a valid state; A method comprising:

13. 12. The method of claim 11, wherein the self-directed wallet and payment card further comprises a primary account number (PAN) stored in the storage device, the PAN being associated with the crypto card wallet account, the method comprising: and transmitting, by the payment application, a payment request to a payment terminal over the near field communication channel, the payment request including the PAN. method.

14. 12. The method of claim 11, performing a calculation and generating, by the cryptographic application, a signed transaction request using the private key associated with the self-managed blockchain address of the self-managed wallet stored in the storage device.

15. 15. The method of claim 14, receiving a deposit request for a managed wallet associated with the blockchain address of the crypto card wallet account from a mobile application via the near field communication channel; said performing said calculations and said generating said signed transaction request are performed in response to receiving said deposit request. method.

16. 16. The method of claim 15, wherein the signed transaction request indicates the blockchain address of the crypto card wallet account as a receiving address. method.

17. 16. The method of claim 15, wherein the deposit request includes authentication information, and in response to the deposit request, the method further comprises: verifying the authentication information; and formatting a transaction request; signing the transaction request using the private key to generate the signed transaction request; providing the signed transaction request to the mobile application via the short-range communications channel; A method comprising:

18. 15. The method of claim 14, wherein the performing of the calculations and the generating of the signed transaction request are performed in response to receiving a self-managed wallet transaction request from a mobile application via the short-range communications channel. method.

19. 20. The method of claim 18, wherein the self-managed wallet transaction request includes authentication information and a receiving address, and in response to the self-managed wallet transaction request, the method further comprises: verifying the authentication information; and formatting a transaction request; signing the transaction request using the private key to generate the signed transaction request; providing the signed transaction request to the mobile application via the short-range communications channel; A method comprising:

Images