FIELD OF DISCLOSURE

Generally, the present disclosure relates to the sharing of access and usage of digital assets and/or accounts. Specifically, the present disclosure pertains to method and system of providing or sharing access to digital asset and accounts, whether financial or non-financially related.

BACKGROUND

Conventional digital transactions facilitate electronic payment, such as money transfers, payment asset charges, e-commerce transactions and any other types of transactions. However, in multiple circumstances, payees may be unbanked people (e.g., children that need money to buy something) or may have no payment asset (e.g., lost asset). Payment fund transfers may be expensive, time-consuming, heavily regulated, and cumbersome for financial institutions. Thus, there is need for an improved approach.

In some instances, a person may need to delegate his or her right or obligation associated with an asset and/or account, to another person for any reason. The delegation of the rights or obligations may in certain instances be impossible without a physical transmission of such asset and/or account or credentials for access to the asset and/or account. However, such persons may be in different places. Thus, there is need for an improved approach.

BRIEF OVERVIEW

This brief overview is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This brief overview is not intended to identify key features or essential features of the claimed subject matter. Nor is this brief overview intended to be used to limit the claimed subject matter's scope.

Methods, systems, and a computer-readable medium for providing or sharing access to an asset are disclosed. A first request for sharing the asset from a consuming party may be received. The asset may be verified as a registered asset. The first request may be sent for approval by a provisioning party. The first request may comprise details about a transaction for which sharing the asset has been requested and a specification of the asset requested for sharing. Approval may be provided with restriction parameters. In turn, a first digital token may be generated. A second request for the transaction may be received from the consuming party. Transaction details may be verified not to violate the restriction parameters associated with the first digital token. A second digital token associated with the asset from an asset custodian may be received. A request to perform the transaction may be sent to the asset custodian for processing. A confirmation of a processed transaction from the asset custodian may then be received.

Embodiments of the present disclosure may provide methods, systems, and computer-readable media, that may comprise computer-readable instructions, which when executed, perform at least some of the following stages:

Receiving a first request for sharing an asset from a consuming party,

Wherein receiving the first request for sharing asset from the consuming party comprises at least one of the following: the consuming party scanning a barcode and the consuming party using NFC to generate the request;

Verifying the asset has been registered,

Wherein verifying the asset has been registered comprises verifying a provisioning party has configured the asset to be shared by providing asset access information,

Wherein providing asset access information comprises providing at least one of the following: an account number of the asset, a routing number of an asset custodian, legal name of an asset owner, the asset custodian, a mailing address of the asset owner, a billing address of the asset owner, zip code of the asset owner; a Card Verification Value (CVV), a digital wallet address, an access code for the digital wallet, Personal Identification Number (PIN), an API key for accessing the asset, a multi-factor code, Device ID, a username, and a password;

Sending a provisioning party, the first request for approval,

Wherein sending the provisioning party the first request for approval comprises sending the following: details about a transaction for which sharing the asset has been requested and a specification of the asset requested for sharing,

Wherein the details about the transaction for which sharing the asset has been requested comprise at least one of the following: amount of funds to cover the transaction, a merchant that the transaction is with, the time of the transaction, and the geolocation of the transaction;

Receiving an approval for the first request from the provisioning party,

Wherein receiving the approval for the first request from the provisioning party comprises receiving restriction parameters,

Wherein the restriction parameters comprise at least one of the following: the amount of funds approved for sharing, the merchant approved for the transaction, the asset approved for sharing, the time during which sharing is approved, and the geolocation where sharing is approved;

Generating a first digital token to be shared with the consuming party,

Wherein generating the first digital token to be shared with the consuming party comprises generating the first digital token based on the restriction parameters,

Wherein the first digital token corresponds to the approval for sharing and is used by the consuming user to specify the asset designated for sharing;

Notifying the consuming party of the approval for the first request,

Wherein notifying the consuming party of the approval for the first request further comprises providing the first digital token to the consuming party;

Receiving a second request for the transaction from the consuming party,

Wherein receiving the second request for the transaction from the consuming party further comprises receiving the first digital token and the details about the transaction;

Verifying the details about the transaction do not violate the restriction parameters associated with the first digital token,

Wherein verifying the details about the transaction do not violate the restriction parameters associated with the first digital token comprises comparing the details about the transaction to the restriction parameters and verifying that the details about the transaction do not exceed or violate the restriction parameters;

Receiving a second digital token associated with the asset from an asset custodian,

Wherein receiving the second digital token associated with the asset from the asset custodian comprises sending the asset access information to the asset custodian and receiving the second digital token associated with the asset,

Wherein receiving the second digital token associated with the asset from the asset custodian further comprises receiving the second digital token for specifying the asset to the asset custodian in order to process transactions with the asset designated for sharing;

Sending a third request for the transaction to the asset custodian for processing,

Wherein sending the third request for the transaction to the asset custodian for processing comprises sending the second digital token and the details about the transaction to the asset custodian;

Receiving a confirmation of a processed transaction from the asset custodian;

Notifying a merchant of the processed transaction,

Wherein notifying the merchant of the processed transaction comprises sending the merchant at least one of the following: an Android/iOS/Windows/Linux system notification, a text message, an MMS, an email, an application notification, and a phone call;

Notifying the consuming party of the processed transaction,

Wherein notifying the consuming party of the processed transaction comprises sending the consuming party at least one of the following: the Android/iOS/Windows/Linux system notification, the text message, the MMS, the email, the application notification, and the phone call; and

Notifying the provisioning party of the processed transaction,

Wherein notifying the provisioning party of the processed transaction comprises sending the provisioning party at least one of the following: the Android/iOS/Windows/Linux system notification, the text message, the MMS, the email, the application notification, and the phone call.

Both the foregoing brief overview and the following detailed description provide examples and are explanatory only. Accordingly, the foregoing brief overview and the following detailed description should not be considered to be restrictive. Further, features or variations may be provided in addition to those set forth herein. For example, embodiments may be directed to various feature combinations and sub-combinations described in the detailed description.

