Secured, Unified, Multifunctional, Digital Currency Store with Machine-Readable Card and/or Mobile App

Abstract

A prepaid electronic funds transferring system, components, and method is provided for users that do not have checking or savings accounts. A user has a digital currency store such as, for example, in a non-checking non-savings prepaid account associated with a secure unified prepaid banking card and/or smartphone app. Interest may be provided by an issuer on funds in the digital currency store. Debit and credit transactions may be processed. NFC and UWB geo-locating can be used to find lost cards and/or the mobile device on which the app is loaded. Electronic transactions may be received and performed without requiring a recipient to download an app. Secure semiconductors may facilitate wireless and non-wireless communications with ATMs and POS machines. QR codes may identify accounts, constitute private/public encryption keys, or other relevant info. A cold storage or hot storage system may be implemented for the digital currency store.

Claims

1. A prepaid electronic funds transferring method for a user with a smartphone that does not have a checking account or a savings account to use with an automated teller machine (ATM) and a point-of-sale machine (POS) comprising the steps of: a) providing a secure unified prepaid banking card to the user; b) linking, by a prepaid banking server, a non-checking non-savings prepaid digital currency store to the card; c) funding, by the prepaid banking server, the prepaid digital currency store with an amount; d) providing, by the prepaid banking server, interest on the amount in the prepaid digital currency store; e) processing, by the prepaid banking sever, a debit request from the ATM or the POS if the debit request is equal to or less than the amount in the prepaid digital currency store; f) processing, by the prepaid banking server, a deposit request for a deposit received at the ATM; g) receiving, by the prepaid banking server, an electronic transfer to the prepaid digital currency store; h) depositing, by the prepaid banking server in the prepaid digital currency store, the electronic transfer without requiring the user to download a prepaid banking server app to the user's smartphone; i) geo-locating, by the prepaid banking server, the card by near field communications (NFC) or ultra-wideband (UWB) if the card is lost by the user; j) securing, the prepaid banking card, with a first security chip to enable secure non-wireless transactions between the card and the ATM and the POS; and k) securing, the prepaid banking card, with a second security chip to enable secure wireless transactions between the card and the ATM and the POS.

2. The prepaid electronic funds transferring method of claim 1 further comprising the step of processing, by the prepaid banking sever, a credit request from the POS if the credit request is equal to or less than the amount in the prepaid digital currency store.

3. The prepaid electronic funds transferring method of claim 1 further comprising the step of providing a first quick reference (QR) code on the card to identify the prepaid digital currency store.

4. The prepaid electronic funds transferring method of claim 1 further comprising the step of providing a first quick reference (QR) code on the card to identify a public encryption key for the prepaid digital currency store.

5. The prepaid electronic funds transferring method of claim 2 further comprising the step of awarding, by the prepaid banking server, rewards for the credit request if the credit request is equal to or less than the amount in the prepaid digital currency store.

6. The prepaid electronic funds transferring method of claim 5 further comprising the step of providing a second quick reference (QR) code on the card to identify a private encryption key for the prepaid digital currency store.

7. The prepaid electronic funds transferring method of claim 6 wherein the public encryption key and the private encryption key are used in blockchain ledgers on a plurality of blockchain devices.

8. A secure unified banking card for use in transactions in a prepaid electronic funds transferring system that includes an automated teller machines (ATM) and point-of-sale machine (POS), said card comprising: a) a metal or plastic laminate; b) geo-locating means for geo-locating the laminated card if lost, the geo-locating means embedded within the laminate; c) secure wireless communication means to secure wireless communications with the ATM and the POS to facilitate deposits, withdrawals, credit charges, and transfers for a non-checking non-savings prepaid digital currency store associated with the card, said secure wireless communication means embedded within the laminate; d) security chip means to enable secure non-wireless communications when the card is physically inserted into the ATM or the POS to facilitate the deposits, the withdrawals, the credit charges, and the transfers for the prepaid digital currency store associated with the card, said security chip means embedded within the laminate; e) a machine-readable magnetic strip on the laminate to identify the prepaid digital currency store; f) a first machine-readable quick reference (QR) code printed on the laminate that is a public encryption key for the prepaid digital currency store; and g) a second machine-readable quick reference (QR) code printed on the laminate that is a private encryption key for the prepaid digital currency store, wherein said card is able to be used to at the ATM as a debit card and at a POS as a credit card, and wherein the prepaid digital currency store bears interest, and further wherein the transactions are only funded when sufficient funds are available in the prepaid digital currency store.

9. The secure unified banking card of claim 8 wherein the geo-locating means includes either at least one near field communications (NFC) semiconductor or at least one ultra-wideband (UWB) semiconductor.

10. The secure unified banking card of claim 8 wherein the geo-locating means includes at least one near field communications (NFC) semiconductor and at least one ultra-wideband (UWB) semiconductor.

11. The secure unified banking card of claim 8 wherein the card includes means for providing cold storage of currency corresponding to the prepaid digital currency store.

12. A prepaid electronic funds transferring system for use with an automated teller machine (ATM), an automated clearing house (ACH), and a point of sale machine (POS), by a user having (a) a smartphone with a smartphone camera and a smartphone processor, smartphone memory, at least one smartphone communication interface communicatively coupled to the smartphone processor and the smartphone memory, and (b) a secure unified banking card, said user capable of sending an encrypted outgoing transfer of funds and receiving an encrypted incoming transfer of funds to or from a third party, said user capable of receiving a gift card having gift card information to transfer gift card funds, said system comprising: a) a prepaid banking server having: i) at least one server processor, ii) at least one server communication interface communicatively coupled to the at least one server processor; iii) a server memory communicatively coupled to the at least one server communication interface, said server memory storing server computer-readable instructions that, when executed by the at least one server processor, cause the prepaid banking server to: (1) create, by the at least one server processor, a non-checking non-savings prepaid user account; (2) store, by the at least one server processor in the server memory, the prepaid user account; (3) process, by the at least one server communication interface, funding instructions to fund the prepaid user account with an initial currency amount; (4) store, by the at least one server processor in said server memory, the initial currency amount for the prepaid user account; (5) calculate daily, by the at least one server processor in said server memory, interest for the prepaid user account and apply the interest to the prepaid user account; (6) process, by the at least one server processor in real time, encrypted deposit instructions, received by the at least one server communication interface from the ATM network, to increase the prepaid user account by a deposit amount; (7) receive, by the at least one server processor in real time from the at least one server communication interface, an encrypted debit request from the ACH to decrease the prepaid user account by a debit amount; (a) decrypt, by the at least one server processor in real time, the debit request; (b) calculate, by the at least one server processor in real time, whether the debit amount exceeds available funds in the prepaid user account; (c) fund, by the at least one server processor in real time, the debit request if the available funds is at least equal to the debit amount; (d) reject, by the at least one server processor in real time, the debit request if the available funds does not exceed the debit amount; (8) receive, by the at least one server processor in real time from the at least one server communication interface, an encrypted credit request to decrease the prepaid user account by a credit amount; (a) decrypt, by the at least one server processor in real time, the credit request; (b) calculate, by the at least one server processor in real time, whether the credit amount exceeds available funds in the prepaid user account; (c) fund, by the at least one server processor in real time, the credit request if the available funds is at least equal to the debit amount; (d) reject, by the at least one server processor in real time, the credit request if the available funds does not exceed the credit amount; (9) process, by the at least one server processor in real time, encrypted transfer instructions, received by the at least one server communication interface from a prepaid banking app, to increase the prepaid user account based on the accepted transfer funds; (10) transmit, by the at least one server processor in real time through the at least one server communication interface over the Internet to the at least one smartphone communication interface in response to a download request from the smartphone, the prepaid banking app; (11) award, by the at least one server processor to the prepaid user account, at least one reward based on the debit requests and the credit requests that were funded; (12) process, by the at least one server processor, the encrypted incoming transfer and the encrypted outgoing transfer, received from the prepaid banking app, in order to increase or decrease the prepaid user account; (13) store, by the at least one server processor in real time in the prepaid user account in said server memory, updated amounts for accepted transactions based on the deposit amount, the debit amount, the credit amount, and for the encrypted incoming transfers, the encrypted outgoing transfer, and the gift card information; (14) process, by the at least one server processor, a balance request received from the prepaid banking app and transmit an account balance to the prepaid banking app in response to the balance request; (15) process, by the at least one server processor, the gift card information received from the prepaid banking app in order to increase the prepaid user account in accordance with the gift card; b) the secure unified banking card including: i) a geo-locating means to locate the card if lost, said geo-locating means embedded in the card; ii) machine-readable means to enable the ATM and the POS to read account identifying means on the card corresponding to the prepaid user account and the prepaid banking server; iii) security means to secure the card against fraud; iv) wireless communication means to enable wireless communication with the ATM and POS; v) user-identifying indicia printed on the card; c) the prepaid banking app residing in the smartphone memory after having been downloaded in response to the download request, said prepaid banking app including digital wallet means, said smartphone memory storing smartphone computer-readable instructions that, when executed by the at least one smartphone processor, cause the smartphone to: i) receive, by the smartphone processor from the at least one smartphone communication interface over the Internet, the encrypted incoming transfer from the third party; ii) accept or reject, by the smartphone processor, the incoming encrypted transfer from the third party; iii) transmit, to the prepaid banking server over the Internet through the smartphone communication interface, the encrypted incoming transfer if accepted by the user; iv) send, by the smartphone processor over the Internet through the smartphone communication interface to the prepaid banking server, the encrypted outgoing transfer for the third party; v) transmit, to the banking server over the Internet through the smartphone communication interface, the account balance request; vi) receive, from the banking server over the Internet through the smartphone communication interface, the account balance in response to the account balance request; vii) scan, by the smartphone processor utilizing the smartphone camera, the gift card in order to identify the gift card information; and viii) transmit, by the smartphone processor over the Internet to the prepaid banking server, the gift card information in order to increase the prepaid user account in accordance with the gift card.

13. The prepaid electronic funds transferring system of claim 12 wherein the account identifying means includes at least one quick reference (QR) code printed on the card to identify the prepaid user account and the banking server.

14. The prepaid electronic funds transferring system of claim 13 wherein said at least one quick reference (QR) code is an encryption key.

15. The prepaid electronic funds transferring system of claim 14 said encryption key is a public key.

16. The prepaid electronic funds transferring system of claim 14 said encryption key is a private key.

17. The prepaid electronic funds transferring system of claim 12 wherein the account identifying means includes a public encryption key quick reference (QR) code printed on a first side of the card and a private encryption key QR code printed on a second side of the card.

18. The prepaid electronic funds transferring system of claim 12 wherein the card contains encrypted non-volatile memory.

19. The prepaid electronic funds transferring system of claim 12 wherein the card constitutes cold storage of currency.

20. The prepaid electronic funds transferring system of claim 12 wherein the card constitutes a link to a hot storage of currency.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] FIG. 1 depicts an example front side of a prepaid banking card for a secured, unified, multifunctional digital currency store in accordance with one or more aspects of the disclosure.

[0031] FIG. 1 depicts a sample back side of prepaid banking card for a secured, unified, multifunctional digital currency store in accordance with one or more aspects of the disclosure.

[0032] FIG. 3 is a functional diagram illustrating the interconnection and interaction of various components in a prepaid electronic funds transferring system in accordance with one or more aspects of the disclosure.

[0033] FIG. 4 depicts an exemplary prepaid banking server with hardware and memory components in accordance with one or more aspects of the disclosure.

[0034] FIG. 5 depicts an exemplary wireless portable electronic device with a prepaid banking app in which the device has various hardware and memory components in accordance with one or more aspects of the disclosure.

[0035] FIG. 6 illustrates the geo-locating functionality to locate lost prepaid banking cards by use of ultra-wideband (UWB) and/or near field communication (NFC) technology in accordance with one or more aspects of the disclosure.

[0036] FIG. 7 shows various potential high-level interconnected components of a prepaid electronic funds transferring system in accordance with one or more aspects of the disclosure.

[0037] FIG. 8 is a sample process flow diagram for implementing one or more aspects of the disclosure to provide a secured, unified, multifunctional digital currency store for use with physical prepaid cards and/or mobile smart devices.

[0038] FIG. 9 is a sample process flow diagram illustrating a sample transaction process for implementation a prepaid digital currency store in blockchain device(s)/ledgers in the context of one or more aspects of this disclosure.

DETAILED DESCRIPTION

[0039] In the following description of the various embodiments to accomplish the foregoing, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration, various embodiments in which the disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made.

[0040] FIGS. 1 and 2 illustrate a potential front side and back side of prepaid banking card(s) 100 in accordance with one or more aspects of the disclosure. Anything noted as being on the front side of the card could additionally and/or alternatively be provided on the back side of the card, and/or visa versa.

[0041] The card 100 may constitute a plastic laminate or metallic laminate. Alternatively, the card 100 could be constructed or constituted in accordance with any other known method of providing debit or credit cards or structure for such cards. The card 100 may include indicia 102 that identifies the issuer of the card or the holding source or manager for the digital currency store.

[0042] Various forms of machine-readable mechanisms that perform various machine functionality may be provided on or embedded in the card 100. For example, the card 100 may include a magnetic strip 104 for identifying the non-checking non-savings prepaid digital currency store 340 or other prepaid account associated with the card and/or the issuer 102. Encrypted non-volatile memory 106 may also be provided to store digital currency information, account information, blockchain information, currency store information, wallet information, or the like. The memory 106 may be used in conjunction with other components and systems to provide cold storage of currency as described in more detail infra.

[0043] One or more secure wireless NFC and/or UWB geo-locating semiconductors 108 may be used to enable NFC and/or UWB devices to triangulate or otherwise detect and locate the card 100 if it is lost or stolen. One or more secure wireless communication transaction semiconductors 110 can be used to facilitate wireless transactions and communications between the card 100 and ATMs 316 and/or POS machines 328. One or more scannable QR codes 112 (and 202 as in FIG. 2) can be provided to identify prepaid accounts, account issuers, and/or private and/or public encryption keys for the prepaid banking account. In one arrangement, a first QR code (e.g., 112) might be for a public encryption key and a second QR code (e.g., 202) might be for a private encryption key. For security reasons, the first 112 and second 202 QR codes may be on different sides of card 100 such that if the front side of the card (e.g., public key) is presented to a merchant or third party to facilitate a transaction, the back side of the card with the private key will not be revealed.

[0044] One or more security chips 114 may also be provided to secure non-wireless communications between the card 100 and ATMs 316 and/or POS machines 328 such as, for example, when the card 100 is physically inserted into an ATM or POS reader.

[0045] If desired, the owner name 116 of the prepaid banking account may be printed on the card 100. The prepaid banking account number or corresponding card number 118 may also be printed on the card 100. Or, for security or privacy reasons, the owner name 116 and account information 118 may be omitted from the card. Owner lost card and/or contact information 200 may also be identified on the card 100 if desired.

[0046] FIG. 3 is a functional diagram illustrating the interconnection and interaction of various components in a prepaid electronic funds transferring system in accordance with one or more aspects of the disclosure.

[0047] The prepaid electronic funds transferring system may include prepaid banking card 100, which is linked to the prepaid digital currency store 340 and/or other non-checking non-savings account. The prepaid electronic funds transferring system may also include a smartphone or like mobile device 300 with corresponding digital wallet 304 or processing functionality.

[0048] The mobile device 300 may include volatile and/or non-volatile memory 302 to store a digital wallet 304 (or implement digital wallet functionality) and a prepaid banking app 305. The wallet 304 may be a separate module in memory or may be included as part of the prepaid banking app 305. Private and/or public encryption keys 306 may be generated and/or stored electronically in memory 302 using standard cryptography. Preferably, prepaid banking server 400 will generate both a private and public encryption key and will communicate the keys with the prepaid banking app 305 over the Internet 314 during setup of the non-checking non-savings prepaid account. QR codes 307 may also be generated by the server 400 and used by the app 305 on the mobile device 300. The QR codes 307 may identify an issuing entity, a prepaid banking account, a number corresponding to the prepaid banking account, a public encryption key, and/or a private encryption key. The QR codes 307 (or 112 and 202 as printed on the card) may be used to implement cold storage for the prepaid digital currency store on the card 100 and/or be linked to implement hot storage for the prepaid digital currency store.

[0049] In simple terms, cold storage in the context of this disclosure refers to keeping a user's digital currency store completely offline. Cold storage, also known as a cold storage wallet, is the opposite of a hot wallet where a digital currency store is kept online. Keeping a digital currency store online increases a user's risk for the asset to be stolen when kept online using a custodial service. Accordingly, cold storage may be beneficial. By keeping the digital currency store in cold storage, attack threat vectors may be diminished.

[0050] Funds may be added to the non-checking non-savings digital currency store 340 in cold storage by, for example, scanning a QR code or copying an address and sending the funds to the digital currency store. Funds may be similarly sent by importing a private key for a digital wallet that is online. Any wallet that supports importing private keys will work.

[0051] The non-checking non-savings prepaid digital currency store 340 may be implemented in various ways on the mobile device 300 and/or unified card 100. For example, it may be stored and handled in digital wallet 304 in memory 302 on mobile device 300 and/or in encrypted non-volatile memory 106 on card 100. Or it may reside in a prepaid banking app 305 in memory 302. It can be secured and/or accessed with encryption keys 306, QR codes 112, 202, 307. Security chip(s) 114 may also be used to store or otherwise secure the digital currency store 340. Alternatively, the non-checking non-savings prepaid digital currency store 340 may be implemented partially and/or entirely on prepaid banking server 400.

[0052] Hardware on the mobile device 300 may include one or more processor(s) 308 which can access the memory 302 and execute computer-executable instructions in memory corresponding to the functions or modules of the digital wallet 304, prepaid banking app 305, encryption key(s) 306, and/or QR codes 307. The processors 308 can communicate directly with memory 302 via a bus or the like through communication interface(s) 310. The processors can also access near-field communications (NFC) and/or ultra-wideband (UWB) hardware 311 in the mobile device 300 to facilitate communications with ATMs 316 and POS machines 328, and can also be used to geo-locate the card 100 or the mobile device 300 if lost via NFC and/or UWB triangulation, networking, or the like. The mobile device 300 may also include a camera or scanner 312 to scan gift cards or QR codes to facilitate transfers, debits, deposits, or credit transactions.

[0053] The mobile device 300 may interact wirelessly with card 100 such as, for example, by Bluetooth, Wi-Fi, UWB, and/or NFC through NFC/UWB hardware 311 or communication interface(s) 310, and corresponding secure wireless communication transaction semiconductors 110. Smartphone 300 may also interact wirelessly with card 100 by scanning one or more QR codes 112, 202 on card 100 via a camera or scanner 312.

[0054] Similarly, smartphone 300 and/or unified card 100 may interact wirelessly with ATM 316 such as, for example, by Bluetooth, Wi-Fi, UWB, and/or NFC through NFC/UWB hardware 311 or communication interface(s) 310, and/or secure wireless communication transaction semiconductors 110. Smartphone 300 may also interact wirelessly with ATM 316 by scanning one or more QR codes 112, 202 displayed on the ATM screen 316 via a camera or scanner 312. Conversely, the ATM 316 can scan or read QR code(s) 307 on the mobile device 300 or codes 112, 202 on card 100.

[0055] Relatedly, smartphone 300 and/or unified card 100 may interact wirelessly with a POS machine 328 to, for example, make purchases from a merchant. Wireless communication may be accomplished by Bluetooth, Wi-Fi, UWB, and/or NFC through NFC/UWB hardware 311 or communication interface(s) 310, and/or secure wireless communication transaction semiconductors 110. POS machine 328 may also be able to scan or read QR code(s) 307 on the mobile device 300 or codes 112, 202 on card 100. Secure non-wireless communication between card 100 and POS machine 328 can be facilitated by security chip(s) 114 that secure transactions when the card 100 is inserted physically into a POS machine 328.

[0056] Preferably, mobile device 300 is connected either via cellular service and/or Wi-Fi to Internet 314. And, mobile device 300, ATM 316, blockchain device(s)/ledger(s) 338, prepaid banking servers 400, merchant POS machine(s) 328, may all communicate directly with one another or through Internet 314.

[0057] As used herein, blockchain in the context of blockchain device(s)/ledger(s) 338, at a high level, can be considered to be a type of database. The blockchain collects information together in groups, also known as blocks, that hold sets of information regarding the digital currency store. Blocks have certain storage capacities and, when filled, are chained onto the previously filled block, forming a chain of data known as the “blockchain.” All new information that follows that freshly added block is compiled into a newly formed block that will then also be added to the chain once filled. The blockchain, structures its data (e.g., prepaid digital currency store and/or information corresponding to the same) into blocks that are chained together. This makes it so that all blockchains are databases but not all databases are blockchains. This system also inherently makes an irreversible timeline of data for the prepaid digital currency store when implemented in a decentralized nature. When a block is filled it is set in stone and becomes a part of this timeline. Each block in the chain is given an exact timestamp when it is added to the chain.

[0058] A sample transaction process for implementation of blockchain device(s)/ledgers 338 in the context of this disclosure is shown in FIG. 9. In step 900, a new transaction for the prepaid digital currency store is entered. In step 902, the transaction is then transmitted to a network of peer-to-peer computers geographically distributed. In step 904, the network of computers (collectively 338) solves equations to confirm the validity of the transaction. Once confirmed to be legitimate transactions for the prepaid digital currency store, they are clustered together into blocks in step 906. These blocks are then chained together in step 908 in a ledger to create a long history of all transactions corresponding to the digital currency store and is permanent. The transaction for the prepaid digital currency store is then completed in step 910.

[0059] FIG. 4 depicts an exemplary prepaid banking server 400 with hardware 418 and memory components 402 in accordance with one or more aspects of the disclosure. Various server modules 403-416 for implementing functionality on the server 400, communicating with mobile device 300, handling transactions related to card 100, interacting with users and user devices 300, communicating with blockchain devices 338, and/or handling transactions and communicating with POS machines 328, may be stored in one or more sectors of integrated and/or accessible non-volatile memory, memories, data stores, databases or the like.

[0060] As an example, prepaid banking server 400 may utilize user authentication and/or hardware validation module(s) 403 in order to authorize mobile devices 300 to access the server 400 and/or to proceed with transactions on validated and/or registered devices 300. Prepaid digital currency transaction(s) received directly from mobile app 305 or indirectly via use of unified card 100 from may be stored in memory 402 and/or processed in module 404. Network communication module(s) 406 may facilitate direct communications between banking server 400 and mobile device 300 via network communication interface(s) 424, or indirectly with card 100. User information, hardware information, encryption keys, session information, digital currency store prepaid account information, ATM information, POS information, reward information, interest information, etc. may be communicated via module(s) 406 and interface(s) 424.

[0061] Public and private encryption keys received from, generated by, and/or distributed by the prepaid banking server 400 can be stored in module 408 and used to enable establishment and securing of communications between servers 400, ATMs 316, POS machines 328, mobile devices 300, and/or unified card 100.

[0062] One or more modules 410 may be used to provide detection, location determination, and/or facilitate communication with mobile devices 300 or unified card 100 via NFC/UWB hardware interfaces in ATMs or the like. Such detection of NFC/UWB devices may occur if and/or when the device 300 and/or card 100 comes within NFC/UWB of various devices 600, 602, 604, 606 which can then be communicated to server 400 and the location information for the device 300 or card 100 can be shared with a user, directly or indirectly, to locate a lost card.

[0063] Input/output (I/O) and/or wireless communication module(s) 412 in memory 402 may be used to accept inputs via optical scanner 426, touchscreen display 428, keypad 432, and/or voice recognition microphone 436 or the like. Messages may be communicated via display 428 or speaker 434 and/or wirelessly to devices such as, for example, smartphone 300.

[0064] FIG. 5 depicts an exemplary wireless portable electronic device 300 with a prepaid banking app in which the device has various hardware 522 and memory 501 components in accordance with one or more aspects of the disclosure.

[0065] User authentication module(s) 502 can be used by the device 300 in communication with ATMs 316 and banking servers 400 in order to authenticate the user in order to establish a session and/or recognize a device 300 corresponding to a user who has a non-checking non-savings prepaid digital currency store or like account. Prepaid banking app module(s) 304, 504 executed on processor(s) 528, can be used to facilitate execution of digital currency store transactions as well as to provide haptic feedback via haptic feedback module(s) 520 and haptic feedback mechanism(s) 526 if desired for such transactions. Similarly, processor(s) 528 may execute instructions to perform the functionality of any of the module(s) stored in memory 501. One type of preferable haptic feedback would be if the card 100 is out of wireless communication with device 300. This would prevent loss of the card if, for example, it was left at a location and the user walked away.

[0066] Transaction processing/storage module(s) 506 on device 300 can be used to set up a prepaid transaction, store a previously set up prepaid transaction, and/or locally handle a prepaid transaction at an ATM 316 or POS machine 328. Wireless/network communication module(s) 508 and/or NFC/UWB functionality module(s) 512 can provide wireless local communication between the device 300, ATM 316, POS machine 328, and/or banking server 400 via network communication interface(s) 530 or the like.

[0067] Local public/private key encryption module(s) 510 may store key(s) received from banking server(s) 400 and/or generate keys that are communicated to server(s) 400 and thereafter distributed to ATMs 316 and/or POS machines 328. Either way, the public and private encryption keys stored in module(s) 510 can be used to establish and facilitate secure communications with device 300 via interfaces 524 and/or 530, and communication module(s) 508, 514.

[0068] As noted above, the non-checking non-savings prepaid digital currency store 340 may be implemented in various ways on the mobile device 300 and/or unified card 100 such as, for example, in digital currency store module 518, digital wallet module 516, and/or in prepaid banking app module 504 in memory 302.

[0069] Input to device 300 and/or output displays to provide information to the user may be accomplished through a touchscreen or non-touchscreen display 532, an optical scanner 534 such as for facial recognition or barcode or QR code scanning, a fingerprint scanner 536, and/or user interface/keypad 538. A speaker 540 may be included in device 300 to provide audible information and/or feedback to the user. If desired, the haptic feedback conveyed herein may provided audibly. A voice-recognition microphone 542 may also be included in 300 to enable voice commands or dictation in order to obviate, in whole or in part, manual key entries or manual interactions with the device.

[0070] FIG. 6 illustrates the geo-locating functionality to locate lost prepaid banking cards by use of UWB and/or NFC technology or networking in accordance with one or more aspects of the disclosure.

[0071] As noted previously, unified card 100 is preferably enabled with secure wireless communication semiconductor(s) 108 that are able to communicate by NFC and/or UWB with geographically distributed NFC/UWB enabled devices 600, 602, 604, 606. This communication allows triangulation or other location detection of the unified card 100 when within wireless range of one or more devices 600, 602, 604, 606. The location information may be provided to mobile device 300 directly via Wi-Fi, Bluetooth, NFC, and/or UWB, and/or provided indirectly to banking server 400 via Internet 314, which can then relay the location information and potentially directions 608 for the lost card 100 to mobile device 300 via the Internet 314.

[0072] FIG. 7 shows various potential components of a prepaid electronic funds transferring system 700 in accordance with one or more aspects of the disclosure. In short, the non-checking non-savings prepaid digital currency store 340 of this disclosure may be implemented in a banking app on a smartphone 708 or in the form of a prepaid banking card 710. The prepaid currency store may be accessed, credited, debited, transferred, and/or other transactions may be performed by various interconnected devices such as ATMs 702, POS machines 704, automated clearing houses 706, prepaid banking server 712, and/or 714.

[0073] FIG. 8 is a sample process flow diagram for implementing one or more aspects of the disclosure to provide a method that can be used based on interactions with the smartphone and automated teller machine(s) (ATMs) and/or a point-of-sale machine(s) (POS).

[0074] In step 800, an institution or holding facility can provide a secure unified prepaid banking card 100 to the user. A prepaid banking server 400 can link a non-checking non-savings prepaid account to the card 100 in step 802, fund the prepaid account with an initial or other amount in step 804, provide interest on some or all funds held in the prepaid account in step 806, process debit requests in step 808 and/or credit requests in step 820 from ATMs 316 or POS machines 328 if the debit/credit request is equal to or less than the amount in the prepaid account, and process deposit requests in step 810 for deposits received at an ATM 316 or other means.

[0075] The prepaid banking server 400 can receive electronic transfers to the prepaid account in step 812 and can deposit in the prepaid account the electronic transfers preferably without requiring the user to download a prepaid banking server app or other app to the user's smartphone in step 814. Wireless communication between the card 100, smartphone 300, ATMs 316, and/or POS machines 328 can be accomplished via Bluetooth, Wi-Fi, UWB, NFC, or the like in secure wireless transaction semiconductor(s) 110. Geo-locating of the card, if lost, can similarly be accomplished by wireless means in step 816 by secure wireless NFC/UWB geo-locating semiconductor(s) 108. Communications between the card and/or smartphone and either ATMs or POS machines can be secured with one or more security chip(s) 114 to secure both wireless and/or non-wireless communications in step 818. Rewards for credit purchases may be processed in step 822.

[0076] One or more quick reference (QR) codes 112, 202, 307 may be used to identify the prepaid banking account and/or associated public encryption key(s) and/or private encryption key(s) in step 824. The keys may be used in order to facilitate blockchain transaction implementation 338 in step 826.

[0077] Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.