WO2020219590A1

WO2020219590A1 - Payment system accepting any cryptocurrency or virtual currency that performs transaction between purchaser and merchant

Info

Publication number: WO2020219590A1
Application number: PCT/US2020/029383
Authority: WO
Inventors: Nazanin UDDIN
Original assignee: Payalt Corp.
Priority date: 2019-04-22
Filing date: 2020-04-22
Publication date: 2020-10-29

Abstract

A payment provides a user the ability to pay a vendor with any cryptocurrency of their choosing. The user is provided with several payment options. Each of the payment options includes a type of digital asset, such as a cryptocurrency or virtual currency. Once fund confirmation is received by the payment system, the payment system processes payment with the merchant and the merchant receives funds in the requested amount and currency (for example, US dollars) from the payment system. In this fashion, the user has the ability to pay with any cryptocurrency of their choosing via the payment system, and the merchant is paid the requested amount in its preferred currency. The merchant is not involved with the digital asset and does not know how or in what currency the user paid.

Description

PAYMENT SYSTEM ACCEPTING ANY CRYPTOCURRENCY OR VIRTUAL CURRENCY THAT PERFORMS TRANSACTION BETWEEN PURCHASER AND

MERCHANT

CROSS-REFERENCE TO RELATED APPLICATION [0001] The present Application claims priority to U.S. Application No. 62/837,189 filed April 22, 2019, which is incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

[0002] The present disclosure generally relates to payment systems, and more particularly to payment systems accepting cryptocurrency or virtual currency.

BACKGROUND

[0003] Digital assets, also known as virtual currency, are commonly used as an alternative form of fiat. Such digital assets are typically referred to as cryptocurrency. One such cryptocurrency available is bitcoin; however, many other types of cryptocurrencies are available. Bitcoin and other types of cryptocurrencies operate as a medium of exchange between two parties. However, even the most popular types of virtual currencies are not accepted by most merchants. Even if accepted, it may be limited to select merchants where the conventional payment system has a predetermined relationship between the intermediary and/or the merchant. This is very limiting as only select merchants are available and limited number of virtual currencies are available.

SUMMARY

[0004] Embodiments of the present disclosure may provide a payment method comprising: detecting a payment form that is presented to a user, wherein the payment form has a payment amount in a first currency; presenting a plurality of payment options to the user, wherein each of the payment options may include a currency type, at least one of which is a virtual or cryptocurrency, and wherein the currency type is different from the first currency; receiving a selected payment option of the plurality of payment options from the user; generating a virtual card after fund confirmation is received in accordance with the selected payment option; and processing payment using the virtual card through the payment form without involvement of the user and without payment specifying the currency type that is different from the first currency associated with the payment form. The payment form may be presented on a web browser of the user. The fund confirmation step may include accessing a virtual wallet of a user; and transferring funds from the wallet of the user to a second wallet, wherein the user does not have access to the second wallet. The payment transferred may be determined using an exchange rate between the first currency and the currency type of the selected payment option and the payment amount. The fund confirmation step may further comprise prompting a user to provide a wallet access identifier to a third-party provider; and receiving a non-fraudulent transaction confirmation from blockchain through the third-party provider. The user may never be presented with information associated with the virtual card. The steps may be performed via a web browser extension application, accessing a browser through an application virtualization product, and/or via a mobile application running on a mobile device of the user.

[0005] Embodiments of the present disclosure may provide a payment system comprising: a storage system; a payment processor that is configured to access information stored in the storage system, wherein the processor is configured to: (a) detect that a user is presented with a payment form, wherein the payment form has a payment amount in a first currency, (b) querying the user to determine which of a plurality of payment options the user selects, wherein at least one of the plurality of payment options is cryptocurrency or virtual currency, (c) cashing out after fund confirmation is received in accordance with the payment option selected by the user, and (d) processing payment on behalf of the user; and a local bus that is configured to provide communication between the storage system and the payment processor. Cashing out may comprise generating a virtual card, and the payment processor may include a virtual card controller that is configured to generate the virtual card to process payment. Cashing out may comprise one or more of the following: ACH transfer, EFT transfer, debit card, charge card, bank deposit and physical checks, and the payment processor may include a money transfer controller. The payment processor also may include a scraping and auto filling controller that is configured to detect that the user is presented with the payment form and to process the payment on behalf of the user by auto-populating a form with virtual card information or other payment information. The storage system may include user information, transaction information, wallet account information, deposit information, and optionally, virtual card information. The payment processor also may include a user management controller; and a wallet access interface.

[0006] Other embodiments of the present disclosure may provide a payment method using a payment processor in communication with a storage system, the payment method comprising: detecting that a user is presented with a payment form, wherein the payment form has a payment amount in a first currency; querying the user to determine which of a plurality of payment options the user selects, wherein at least one of the plurality of payment options is cryptocurrency or virtual currency; cashing out after fund confirmation is received in accordance with the payment option selected by the user; and processing payment on behalf of the user, wherein the payment processor communicates with the storage system over a local bus and a network. Cashing out may comprise generating a virtual card using a virtual card controller within the payment processor that is configured to generate the virtual card to process payment. Cashing out also may comprise one or more of the following: ACH transfer, EFT transfer, debit card, charge card, bank deposit and physical checks using a money transfer controller within the payment processor. The detecting and processing steps may be performed using a scraping and auto filling controller within the payment processor.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] For a more complete understanding of this disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0008] FIG. 1 depicts a payment method according to an embodiment of the present disclosure;

[0009] FIG. 2 depicts a browser extension according to an embodiment of the present disclosure;

[0010] FIG. 3 depicts options that may be provided in a browser extension in an embodiment of the present disclosure;

[0011] FIG. 4 depicts a browser extension in a taskbar according to an embodiment of the present disclosure;

[0012] FIG. 5 depicts a payment method in a browser extension according to an embodiment of the present disclosure;

[0013] FIG. 6 depicts crypto payment options in a browser extension according to an embodiment of the present disclosure;

[0014] FIG. 7 depicts a payment button for a crypto payment option according to an embodiment of the present disclosure;

[0015] FIG. 8 depicts a payment processing screen in a browser extension according to an embodiment of the present disclosure;

[0016] FIG. 9 depicts a website browser associated with the payment system according to an embodiment of the present disclosure;

[0017] FIG. 10 depicts browsing within a website browser associated with the payment system according to an embodiment of the present disclosure; [0018] FIG. 11 depicts the payment button within a website browser associated with the payment system according to an embodiment of the present disclosure;

[0019] FIG. 12 depicts crypto payment options in a browser associated with the payment system according to an embodiment of the present disclosure;

[0020] FIG. 13 depicts a payment button for a crypto payment option according to an embodiment of the present disclosure;

[0021] FIG. 14 depicts a payment processing screen in a browser associated with the payment system according to an embodiment of the present disclosure;

[0022] FIG. 15 depicts a mobile app associated with a payment system via a mobile phone browser according to an embodiment of the present disclosure;

[0023] FIG. 16 depicts a webpage for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure;

[0024] FIG. 17 depicts a checkout screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure;

[0025] FIG. 18 depicts a delivery method screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure;

[0026] FIG. 19 depicts a payment method screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure;

[0027] FIG. 20 depicts a cryptocurrency or virtual currency selection screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure;

[0028] FIG. 21 depicts a payment screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure; [0029] FIG. 22 depicts a payment processing screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure;

[0030] FIG. 23 depicts another payment method according to an embodiment of the present disclosure;

[0031] FIG. 24 depicts another step in an in-person payment system according to an embodiment of the present disclosure;

[0032] FIG. 25 depicts another step in an in-person payment system according to an embodiment of the present disclosure;

[0033] FIG. 26 depicts another step in an in-person payment system according to an embodiment of the present disclosure;

[0034] FIG. 27 depicts a completion step in an in-person payment system according to an embodiment of the present disclosure;

[0035] FIG. 28 depicts a payment system according to an embodiment of the present disclosure; and

[0036] FIG. 29 depicts a user flow diagram according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

[0037] A payment system according to embodiments of the present disclosure may provide a user with the ability to pay a vendor/merchant with any cryptocurrency or virtual currency of their choosing. The merchant/vendor may present a payment amount in a first currency to the user. The user may be provided with one or more payment options. Each of the payment options may include a type of digital asset, such as a cryptocurrency or other virtual currency, that may be different from the first currency. The user may select a payment option, and in an embodiment of the present disclosure, a virtual card may be generated after fund confirmation is received in accordance with the selected payment option, and the virtual card may be used to auto-populate the payment form and process payment. Regardless whether a virtual card is used or other banking products such as EFT, ACH or check, once fund confirmation is received by the payment system, the payment system according to embodiments of the present disclosure may process payment with the vendor/merchant, and the vendor/merchant may receive funds in the amount and currency (for example, US dollars) originally requested from the payment system. In this fashion, the user has the ability to pay with any cryptocurrency or virtual currency of their choosing via the payment system, and the vendor/merchant may be paid the requested amount in its preferred currency. The merchant is not involved with the digital asset and need not know how or in what currency the user made payment.

[0038] FIG. 1 depicts payment method 100 according to an embodiment of the present disclosure. At step 101, a payment system may detect a payment form presented to a user. The payment form may include a payment amount in a first currency. At step 102, a plurality of payment options may be presented to the user. At step 103, the user may select one of the plurality of payment options. [0039] At step 104, a determination may be made whether the user’s wallet is accessible via an application programming interface (API) (for example, Coinbase). If it is determined that the user’s wallet is accessible via API, then the method may proceed to step 105. At step 105, the user’s wallet may be accessed via API, and funds may be transferred from user’s wallet based on cryptocurrency or virtual currency type and exchange rate.

[0040] If it is determined that the user’s wallet is not accessible via API, then the method may proceed to step 106. At step 106, the user may be prompted to provide a wallet identification (ID) to a third-party point-of-sale (POS) provider (such as Aliant) to obtain confirmation that a transaction is not fraudulent. This third-party POS provider may be used for processing cryptocurrency or virtual currency transactions, providing a way for users to use any external wallet and wait for the third-party POS provider to return a complete status on a transfer. This confirmation may involve waiting over thirty minutes until the third-party provider receives three confirmations from the blockchain regarding the funds. However, it should be appreciated that the wait time may be longer or shorter without departing from the present disclosure. It also may be appreciated that more or fewer than three confirmations may be required in embodiments of the present disclosure. The user may receive a communication, such as an email, once his/her virtual card is ready for use.

[0041] Once confirmation from the blockchain is received through the third-party POS provider that the transaction is not fraudulent in step 107, then the method may proceed to step 108. At step 108, a virtual card may be generated, such as through PEX as described in more detail herein, and the payment form may be auto populated. Next, at step 109, the transaction may be completed using the virtual card without user involvement. The virtual card also may be referred to as a charge card in embodiments of the present disclosure. It should be appreciated that users may be provided with the option to convert their funds into a virtual charge card that may be instantly issued and provided to the client via text, email or displayed on the screen. The user can use the card directly at any merchant’s website in some embodiments of the present disclosure. While embodiments of the present disclosure describe use of virtual or charge cards, other methods of cashing out may be used without departing from the present disclosure. Methods may include, but are not limited to, sending funds via electronic fund transfer/automated clearinghouse (EFT/ACH), issuance of physical checks, and/or issuance of physical charge cards.

[0042] FIGS. 2-8 illustrate operation via a browser extension that performs payment method 100 of FIG. 1. More specifically, FIG. 2 depicts a browser extension according to an embodiment of the present disclosure. While the browser extension is depicted in the right-hand corner of the browser in FIG. 2, it should be appreciated that the browser extension may be positioned elsewhere on the browser, such as may be dictated by the browser being used, without departing from the present disclosure. FIG. 3 depicts options that may be provided in a browser extension in an embodiment of the present disclosure. FIG. 4 depicts a browser extension in a taskbar according to an embodiment of the present disclosure. FIG. 5 depicts a payment method in a browser extension according to an embodiment of the present disclosure. As depicted in FIG. 5, the extension may insert a payment method button within a web page. FIG. 6 depicts crypto payment options in a browser extension according to an embodiment of the present disclosure. At checkout on a retail website, a system according to embodiments of the present disclosure may insert crypto payment options directly into the browser where payment on the retail website may be completed. In FIG. 7, a payment button may be provided once a crypto payment option has been selected in FIG. 6. FIG. 8 depicts a payment processing screen in a browser extension according to an embodiment of the present disclosure. As depicted in FIG. 8, the browser may display a payment processing screen to reflect payment is being processed on the blockchain.

[0043] FIGS. 9-14 illustrate operation via a browser operating within a browser that performs method 100 of FIG. 1. More specifically, FIG. 9 depicts a website browser associated with the payment system according to an embodiment of the present disclosure. In this embodiment, no browser extension may be used, and accordingly, the payment system may not have control of the browser. The user may access the Internet through the website associated with the payment system. FIG. 10 depicts browsing within a website browser associated with the payment system according to an embodiment of the present disclosure. FIG. 11 depicts the payment button within a website browser associated with the payment system according to an embodiment of the present disclosure. When the user is ready to complete a purchase on a retail website, the browser associated with the payment system may insert the payment button within the website. FIG. 12 depicts crypto payment options in a browser associated with the payment system according to an embodiment of the present disclosure. At checkout on a retail website, a system according to embodiments of the present disclosure may insert crypto payment options directly into the browser where payment on the retail website may be completed. In FIG. 13, a payment button may be provided once a crypto payment option has been selected in FIG. 12. FIG. 14 depicts a payment processing screen in a browser associated with the payment system according to an embodiment of the present disclosure. As depicted in FIG. 14, the browser may display a payment processing screen to reflect payment is being processed on the blockchain.

[0044] FIGS. 15-22 illustrate operation via a mobile application that performs method 100 of FIG. 1. More specifically, FIG. 15 depicts a mobile app associated with a payment system via a mobile phone browser according to an embodiment of the present disclosure. This may permit shopping online or in-person using the payment system according to embodiments of the present disclosure. FIG. 16 depicts a webpage for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure. FIG. 17 depicts a checkout screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure. FIG. 18 depicts a delivery method screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure. FIG. 19 depicts a payment method screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure. FIG. 20 depicts a cryptocurrency or virtual currency selection screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure. FIG. 21 depicts a payment screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure. Once the user selects“pay now” or makes another similar selection, payment may be made using the selected cryptocurrency or virtual currency. FIG. 22 depicts a payment processing screen for a retail store within the mobile app associated with a payment system according to an embodiment of the present disclosure.

[0045] While a file may be downloaded or a mobile app may be used to access the payment system according to embodiments of the present disclosure, it should be appreciated that downloading a browser extension may be downloaded, an application may be downloaded, a mobile app may be used, and/or a link that directly accesses the payment system without downloading anything may be used without departing from the present disclosure.

[0046] FIG. 23 depicts payment method 200 according to an embodiment of the present disclosure. At step 201, a payment system may prompt a user via mobile device to enter an amount of currency needed for an in-store purchase. At step 202, a plurality of payment options may be presented to the user. At step 203, the user selects one of the payment options. At step 204, a determination may be made whether the user’s wallet is accessible via API (for example, Coinbase). If it is determined that the user’s wallet is accessible via API, then the method proceeds to step 205. At step 205, the user’s wallet may be accessed via API, and funds may be transferred from user’s wallet based on currency type and exchange rate.

[0047] If it is determined that the user’s wallet is not accessible via API, then the method proceeds to step 206. At step 206, the user may be prompted to provide a wallet ID to a third- party provider (such as Aliant). Once confirmation is received in step 207, then the method proceeds to step 208. At step 208, funds may be transferred to a user account so that the user can initiate the mobile payment. In one embodiment, step 208 involves generating a virtual card. However, mobile payment may be initiated through methods other than generation of a virtual card without departing from the present disclosure.

[0048] FIGS. 24-27 depict steps for use of a payment system via a mobile application that performs method 200 of FIG. 23. FIG. 24 depicts another step in an in-person payment system where a user may enter the purchase amount and select a payment method. FIG. 25 depicts another step in an in-person payment system where a user may select where funds should be sent. FIG. 26 depicts another step in an in-person payment system where the payment system may process the payment, identify when cryptocurrency or virtual currency is received at a designated wallet, assess risk, and then transfer funds to a user. FIG. 27 depicts a completion step in an in-person payment system where a user may be notified once transfer is complete.

[0049] FIG. 28 depicts payment system 300 according to an embodiment of the present disclosure. Payment system 300 is a structure that may perform method 100 or method 200. Payment system 300 may include processor 301, storage system 302, network interface 303, and local bus 305. Processor 301 may include user management controller 310, scraping and auto filling controller 311 configured to detect when the user is being presented with a purchase option and to process the payment on behalf of the user by auto-populating a form with virtual card information, virtual card controller 312 that is configured to generate a virtual card to process payment, and wallet access interface 313. Scraping and auto filling controller 311, which also may be referred to as a shopping cart scraper, may detect when a user is on a checkout page and then may scrape the page to identify the transaction amount. The shopping cart scraper may query the user as to whether the transaction amount is correct, giving the user an option to change the amount if needed. This amount is what is used in the transaction process of FIG. 29; it may get stored in a database to be used as the transaction amount to be converted to cryptocurrency or other virtual currency, as described in detail herein. While FIG. 28 depicts virtual card controller 312, it should be appreciated that other cash-out options may be substituted for virtual card controller 312 in embodiments of the present disclosure. For example, virtual card controller 312 may be substituted with a money transfer controller allowing for ACH, EFT and checks to be used. There also may be embodiments of the present disclosure where scraping and auto filling controller 311 in FIG. 28 may be substituted with a currency conversion controller, such as in embodiments where instant cards may be issued. Storage system 302 may include user information 320 (which may include, but is not limited to, first name, last name, email address, phone number, date of birth, confirmation of age, and billing address), transaction information 321, wallet account information 322, and virtual card information 323. In one embodiment, processor 301 and storage system 302 may be distributed and communicate over a network.

[0050] FIG. 29 depicts a user flow diagram according to an embodiment of the present disclosure. The payment system (referenced as Pay Alt) may be accessed through a login on a website that may control logins, confirm registrations, and enable viewing of transaction history as reflected in box 401. In an embodiment of the present disclosure, the at least one database associated with the website may be stored on the same server as the website; however, there may be embodiments of the present disclosure where different servers may be used to host the at least one database and the website. As noted in box 401, a user may sign up to use the payment system. The sign-up process may prompt the user to provide one or more items of personal information including, but not limited to, first name, last name, email address, birthdate, phone number, and/or whether the user is over 18 years of age. The user may then be provided with a one-time password (OTP) on his/her mobile device so that he/she may verify the account and be able to auto-login to the account.

[0051] Returning to box 401, upon logging in, the user may access his/her profile details and transactions. Profile details or account information may include, but are not limited to, first name, last name, date of birth, email address, phone number, username, password, and/or billing information. A user may view his/her profile information, including whether his/her account is active or inactive. Similarly, an admin may view a grid or display of all users, including their email addresses, phone numbers, and/or whether their accounts are active. An admin may be presented with options to change the password for the user by sending a password reset link to the user’s email address and/or phone number which he/she can follow to reset his/her password. Options also may be provided for an admin to change a phone number associated with a user.

[0052] Transactions may include, but are not limited to, completed, pending, and failed or user cancelled transactions as reflected in admin box 402. Completed transactions may include transactions where Coinbase/ Aliant payment has been completed and/or virtual card creation has been completed. Pending transactions may include transactions that have been created but payment is pending. Failed/cancelled transactions may be transactions that have failed or have been cancelled by the user. For each transaction, information may be provided including, but not limited to, date and time of transaction, platform where purchase was made, transaction ID, and amount. There may be a transactions grid wherein a user may select one or more transactions to display details of those transactions. This information may be accessible by the admin of the payment system as depicted in admin box 402. The admin also may add or edit users in embodiments of the present disclosure. In embodiments of the present disclosure, admin box 402 may provide an admin with settings for one or more platforms associated with the payment system, including, but not limited to, Coinbase (including API key and secret key), Aliant Pay, PEX Card, Twilio and/or Transaction sandbox (enable/disable).

[0053] Within his/her account, a user may select an option (i.e., ShopNow) that may redirect the user to a link that may include an embedded executable file associated with the payment system so that the user may shop and pay using cryptocurrency or other virtual currency. The user may begin to shop, such as through accessing a browser through an application virtualization product, such as Cameyo. Cameyo is a Google cloud server that may run an instance of Windows 10 with an executable installed. Cameyo may serve the ElectronJS application from a browser using a clientless remote desktop gateway, such as Apache Guacamole, in an embodiment of the present disclosure. ElectronJS is an open-source framework that may allow for development of desktop graphical user interface (GUI) applications using web technologies. ElectronJS may be used to build applications using a webview so that user interaction may be enabled, thereby allowing users to input different things into their browsers to aid in the shopping experience in embodiments of the present disclosure. In an embodiment of the present disclosure, the website used to log into the payment system may the same at least one database as ElectronJS; however, there may be other embodiments of the present disclosure where different databases may be used. Using Cameyo, an application may be opened that is unique to each user, not requiring the user to download the application to his/her mobile device. It also may allow for the application to only need to work in one environment, making debugging easier and/or faster, as the application only needs to work in a single environment. As depicted in FIG. 29, upon selecting“shop now” (or another similar selection), a shopping portal may be opened in Cameyo from which the shopping process may be initiated. The application virtualization product may direct the user to a landing page, such as a Google landing page, where the user may engage in a login process, where the user may be prompted for the same username and password registered with the payment system.

[0054] The user may then access an e-commerce or e-shopping site, select items for purchase, and at the time of checkout, the user may be directed to a checkout page (403) where cart scraping may occur, such as through a cart scraper plugin. The scraped amount may be presented, and the user may be prompted with a pay button. Upon selection of the pay button, a confirmation popup (404) may be displayed to the user so that the user can elect to convert the scraped amount to a particular form of cryptocurrency or virtual currency (i.e., select coin type). The amount of coin (cryptocurrency or virtual currency) that will be charged may be displayed to the user once a cryptocurrency or virtual currency type has been selected. An additional fee may be charged for use of the payment system in embodiments of the present disclosure. A third- party provider, such as Coinbase, may be accessed and an exchange rate may be provided (405). If the user has not already synced his/her third-party provider account with his/her payment system account, the user may be prompted with an authentication popup so that the user may specify the amount that he/she allows the payment system to withdraw for the transaction. As described herein, the third-party provider may be used to process cryptocurrency or other virtual currency from the user to the payment system in embodiments of the present disclosure. Users may access the third-party provider and sync their respective accounts with the payment system, granting permission for the payment system to process payments on their behalf. If the user is logged in with the third-party provider, the transaction process may be simpler and may bypass blockchain confirmation of funds, as the user may already have the cryptocurrency/virtual currency funds in his/her third-party account that has already been through the blockchain. As further described herein, a user may pre-load a virtual card or make a one-time purchase at checkout on an e-commerce website in embodiments of the present disclosure.

[0055] An account sync may then occur with the third-party provider (406). This sync may be with one or more servers and databases associated with the third-party provider. If the user has not synced with the third-party provider before, an authentication step may occur. Once syncing has occurred, the payment process may occur (407). After syncing, the user’s Coinbase access token and refresh token may be saved in one or more databases mapped to the user’s ID so that the amount that the user wants to add to a crypto credit card may be charged from the user’s Coinbase account. Coinbase may create a new transaction using one or more API calls. The transaction may initially be identified as pending and stored in one or more databases in an embodiment of the present disclosure. If the payment fails, the transaction may be canceled, and an error message may be displayed.

[0056] If payment is successful, a virtual card creation provider, such as PEX, may be called via API with an amount of the checkout for creating a virtual card (408). Post card details (i.e., card ID) may be provided in response from PEX and posted to webhooks through a URL and/or in a card creation request call in an embodiment of the present disclosure. Data from PEX may then be encrypted and stored on the backend of the payment system in one or more databases, and virtual card details may be accessed through the one or more databases and fed into the automation process so that an order may be placed (409). As described in detail herein, when the status of a payment through a third-party provider, such as Coinbase, or a third-party POS provider, such as Aliant, is complete, a PEX webhook may be called to create a virtual card or fund an existing virtual card based on information, including but not limited to, the user’s account and the card that may be associated with the user’s account, if one is already attached to the user’s account. The virtual card creation provider, such as PEX, may provide the payment system with card details so that the card details may be auto-filled, such as using a machine learning autofiller in an embodiment of the present disclosure. The user also may have access as a backup to the card details where he/she may enter the card details manually if needed. Once filled, the transaction amount may be deducted from the user’s virtual card, and the virtual card creation provider may track the funds for a card so that transactions may be managed. For the example, the virtual card creation provider may manage updates to card balances, and each transaction, whether failed, pending, or completed, may be displayed to a user in his/her respective web portal.

[0057] In one embodiment of the present disclosure, the user may be prompted with a preloaded credit card popup (410). If the user already has created a preloaded crypto credit card, he/she may be prompted to add fund details or simply load card info. If the user does not have a preloaded card, the user may be prompted to add fund details. The user may select from a menu of one or more forms of cryptocurrency or virtual currency. The user may then be directed to the same confirmation popup described above with respect to conversion of the scraped amount, and the process may proceed in a similar manner from that step.

[0058] Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the disclosure as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present disclosure. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Claims

1. A payment method comprising:

detecting a payment form that is presented to a user, wherein the payment form has a payment amount in a first currency;

presenting a plurality of payment options to the user, wherein each of the payment options includes a currency type, at least one of which is a cryptocurrency or a virtual currency, and wherein the currency type is different from the first currency;

receiving a selected payment option of the plurality of payment options from the user; generating a virtual card after fund confirmation is received in accordance with the selected payment option; and

processing payment using the virtual card through the payment form without involvement of the user and without payment specifying the currency type that is different from the first currency associated with the payment form.

2. The method of claim 1, wherein the payment form is presented on a web browser of the user.

3. The method of claim 1, the fund confirmation step comprising:

accessing a virtual wallet of a user; and

transferring funds from the wallet of the user to a second wallet, wherein the user does not have access to the second wallet.

4. The method of claim 3, wherein the payment transferred is determined using an exchange rate between the first currency and the currency type of the selected payment option and the payment amount.

5. The method of claim 1, the fund confirmation step further comprising: prompting a user to provide a wallet access identifier to a third-party provider; and receiving a non-fraudulent transaction confirmation from blockchain through the third- party provider.

6. The method of claim 1, wherein the user is never presented with information associated with the virtual card.

7. The method of claim 1, wherein the steps are performed via a web browser extension application.

8. The method of claim 1, wherein the steps are performed via a mobile application running on a mobile device of the user.

9. A payment system comprising:

a storage system;

a payment processor that is configured to access information stored in the storage system, wherein the processor is configured to: (a) detect that a user is presented with a payment form, wherein the payment form has a payment amount in a first currency, (b) querying the user to determine which of a plurality of payment options the user selects, wherein at least one of the plurality of payment options is cryptocurrency or virtual currency, (c) cashing out after fund confirmation is received in accordance with the payment option selected by the user, and (d) processing payment on behalf of the user; and

a local bus that is configured to provide communication between the storage system and the payment processor.

10. The payment system of claim 9, wherein cashing out comprises generating a virtual card.

11 The payment system of claim 10, the payment processor further comprising: a virtual card controller that is configured to generate the virtual card to process payment.

12. The payment system of claim 9, wherein cashing out comprises one or more of the following: ACH transfer, EFT transfer, debit card, charge card, and check.

13. The payment system of claim 12, the payment processor further comprising: a money transfer controller.

14. The payment system of claim 9, the payment processor further comprising:

a scraping and auto filling controller that is configured to detect that the user is presented with the payment form and to process the payment on behalf of the user by auto-populating a form with virtual card information.

15. The payment system of claim 9, the storage system comprising:

user information, transaction information, wallet account information, deposit information, and optionally, virtual card information.

16. The payment system of claim 9, the payment processor further comprising:

a user management controller; and

a wallet access interface.

17. A payment method using a payment processor in communication with a storage system, the payment method comprising:

detecting that a user is presented with a payment form, wherein the payment form has a payment amount in a first currency;

querying the user to determine which of a plurality of payment options the user selects, wherein at least one of the plurality of payment options is cryptocurrency or virtual currency; cashing out after fund confirmation is received in accordance with the payment option selected by the user; and processing payment on behalf of the user,

wherein the payment processor communicates with the storage system over a local bus and a network.

18. The payment method of claim 17, wherein cashing out comprises generating a virtual card using a virtual card controller within the payment processor that is configured to generate the virtual card to process payment.

19. The payment method of claim 17, wherein cashing out comprises one or more of the following: ACH transfer, EFT transfer, and check using a money transfer controller within the payment processor.

20. The payment system of claim 9, wherein the detecting and processing steps are performed using a scraping and auto filling controller within the payment processor.