| CPC G06Q 20/204 (2013.01) [G06Q 20/023 (2013.01); G06Q 20/027 (2013.01); G06Q 20/10 (2013.01); G06Q 20/102 (2013.01); G06Q 20/105 (2013.01); G06Q 20/108 (2013.01); G06Q 20/202 (2013.01); G06Q 20/322 (2013.01); G06Q 20/3221 (2013.01); G06Q 20/325 (2013.01); G06Q 20/34 (2013.01); G06Q 20/341 (2013.01); G06Q 20/36 (2013.01); G06Q 20/385 (2013.01); G06Q 20/387 (2013.01); G06Q 20/40 (2013.01); G06Q 20/401 (2013.01); G06Q 20/4012 (2013.01); G06Q 20/4016 (2013.01); G06Q 20/405 (2013.01); G06Q 40/02 (2013.01); G06Q 10/107 (2013.01); G06Q 2220/00 (2013.01)] | 9 Claims |

|
1. A method comprising:
generating a shadow payment card account in response to a token set-up request;
mapping the generated shadow payment card account to a deposit account number;
generating a token for the shadow payment card account;
storing the token in a cloud;
mapping the token to the deposit account number, the deposit account number corresponding to a deposit account at a financial institution;
remotely accessing the token in the cloud to access the deposit account via ACH (automated clearing house) transactions by presenting the token as part of a transaction request at payment card account acceptance points, wherein the remote access is via a payment/wallet app in a device of a holder of the deposit account;
presenting the token at a payment card account acceptance point;
determining, by a gateway computer, the presentation of the token at the payment card account acceptance point is via remote access of the cloud to which the token was stored, the remote access via the payment/wallet app in the device of the holder of the deposit account;
routing the transaction request to an entity for execution of the ACH transaction;
executing the ACH transaction including one of:
pushing funds from the deposit account of the deposit account holder to a second account, or
holding the funds from the deposit account of the deposit account holder for clearing to the second account.
|