US2018336553A1PendingUtilityA1

Facilitating a fund transfer between user accounts

Assignee: APPLE INCPriority: May 16, 2017Filed: May 16, 2018Published: Nov 22, 2018
Est. expiryMay 16, 2037(~10.8 yrs left)· nominal 20-yr term from priority
G06Q 20/10G06Q 20/3227G06Q 20/3226G06Q 20/3821G06Q 20/385G06Q 20/3829G06Q 20/367G06Q 20/102G06Q 20/4016G06Q 40/02G06Q 40/04
55
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Systems, methods, and computer-readable media for facilitating a fund transfer between user accounts are provided.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method for facilitating a transfer of funds between a first fund account of a credential issuer subsystem and a second fund account of the credential issuer subsystem using a first end-user host electronic device and a second end-user host electronic device and an administration entity subsystem, wherein the first fund account is linked to a first send token and a first receive token at the credential issuer subsystem, wherein the second fund account is linked to a second send token and a second receive token at the credential issuer subsystem, wherein the first end-user host electronic device is associated with a first social token at the administration entity subsystem, and wherein the second end-user host electronic device is associated with a second social token at the administration entity subsystem, the method comprising:
 when a first user transaction credential associated with the first fund account is requested for use on the first end-user host electronic device:
 linking, by the administration entity subsystem, the first receive token to the first social token; and 
 facilitating, by the administration entity subsystem, the provisioning of the first send token on to the first end-user host electronic device; 
   when a second user transaction credential associated with the second fund account is requested for use on the second end-user host electronic device:
 linking, by the administration entity subsystem, the second receive token to the second social token; and 
 facilitating, by the administration entity subsystem, the provisioning of the second send token on to the second end-user host electronic device; and 
   when the transfer of funds is requested:
 receiving, by the administration entity subsystem, from the first end-user host electronic device, device transfer funds request data that comprises:
 device payment credential data comprising the first send token; and 
 the second social token; 
 
 identifying, by the administration entity subsystem, the second receive token as linked to the second social token of the received device transfer funds request data; and 
 communicating, by the administration entity subsystem, to the credential issuer subsystem, administration entity transfer funds request data that comprises:
 the identified second receive token; and 
 the first send token of the received device transfer funds request data. 
 
   
     
     
         2 . The method of  claim 1 , further comprising registering, by the administration entity subsystem, the second end-user host electronic device, wherein the registering comprises storing, by the administration entity subsystem, the second social token against a registration identifier of the second end-user host electronic device. 
     
     
         3 . The method of  claim 2 , wherein the linking the second receive token to the second social token comprises:
 after the registering, receiving, by the administration entity subsystem, from the credential issuer subsystem, the second receive token; and   storing, by the administration entity subsystem, the received second receive token against the second social token and against the registration identifier.   
     
     
         4 . The method of  claim 1 , wherein the linking the second receive token to the second social token comprises:
 receiving, by the administration entity subsystem, from the credential issuer subsystem, the second receive token; and   storing, by the administration entity subsystem, the received second receive token against the second social token.   
     
     
         5 . The method of  claim 1 , wherein, after the communicating, the administration entity subsystem does not comprise any link between the first send token and the second social token. 
     
     
         6 . The method of  claim 1 , wherein, after the communicating, the administration entity subsystem does not comprise any link between the first send token and the second receive token. 
     
     
         7 . The method of  claim 1 , wherein, after the communicating, the administration entity subsystem does not comprise any link between the first end-user host electronic device and the second end-user host electronic device. 
     
     
         8 . The method of  claim 1 , wherein neither one of the first end-user host electronic device and the second end-user host electronic device is operative to receive or store or send any one of the first receive token and the second receive token. 
     
     
         9 . The method of  claim 1 , wherein:
 the administration entity subsystem comprises a device protection server and a credential protection server;   the method further comprises registering the second end-user host electronic device with the administration entity subsystem;   the registering comprises storing, by the device protection server, the second social token against a registration identifier of the second end-user host electronic device; and   the linking the second receive token to the second social token comprises, after the registering, storing, by the credential protection server, the second receive token against the registration identifier.   
     
     
         10 . The method of  claim 9 , wherein:
 the receiving the device transfer funds request data comprises receiving, by the device protection server, from the first end-user host electronic device, the device transfer funds request data; and   the identifying the second receive token as linked to the second social token of the received device transfer funds request data comprises:
 identifying, by the device protection server, the registration identifier as stored against the second social token of the received device transfer funds request data; 
 communicating, by the device protection server, to the credential protection server, updated device transfer funds request data that comprises the identified registration identifier; and 
 identifying, by the credential protection server, the second receive token as stored against the identified registration identifier of the updated device transfer funds request data. 
   
     
     
         11 . The method of  claim 1 , wherein:
 a third fund account is linked to a third send token and a third receive token at the credential issuer subsystem;   when a third user transaction credential associated with the third fund account is requested for use on the second end-user host electronic device, the method further comprises:
 linking, by the administration entity subsystem, the third receive token to the second social token; and 
 facilitating, by the administration entity subsystem, the provisioning of the third send token on to the second end-user host electronic device; and 
   when the transfer of funds is requested:
 the identifying comprises identifying, by the administration entity subsystem, each one of the second receive token and the third receive token as linked to the second social token of the received device transfer funds request data; 
 the method further comprises, after the identifying but before the communicating, defining, by the administration entity subsystem, the administration entity transfer funds request data to comprise the identified second receive token but not the identified third receive token; and 
 the communicating comprises communicating, by the administration entity subsystem, to the credential issuer subsystem, the defined administration entity transfer funds request data. 
   
     
     
         12 . The method of  claim 11 , wherein the defining comprises determining, by the administration entity subsystem, using a pre-defined rule, to select the identified second receive token but not the identified third receive token for inclusion in the definition of the administration entity transfer funds request data. 
     
     
         13 . The method of  claim 11 , wherein:
 the linking the first receive token to the first social token comprises linking, by the administration entity subsystem, the first receive token to the first social token and to a first credential identifier;   the linking the second receive token to the second social token comprises linking, by the administration entity subsystem, the second receive token to the second social token and to a second credential identifier;   the linking the third receive token to the second social token comprises linking, by the administration entity subsystem, the third receive token to the second social token and to a third credential identifier; and   the defining comprises determining, by the administration entity subsystem, to select the identified second receive token but not the identified third receive token for inclusion in the definition of the administration entity transfer funds request data by:
 sending, by the administration entity subsystem, to the second end-user host electronic device, a request for selection of one of a first option defined by the second credential identifier or a second option defined by the third credential identifier; and 
 in response to the sending, receiving, by the administration entity subsystem, from the second end-user host electronic device, a response indicating a selection of the first option. 
   
     
     
         14 . The method of  claim 1 , wherein, after the receiving but prior to the identifying, the method further comprises:
 determining, by the administration entity subsystem, that the second social token of the received device transfer funds request data is not currently linked to any receive token; and   in response to the determining, sending, by the administration entity subsystem, to the second end-user host electronic device, a prompt for the second end-user host electronic device to request use of the second user transaction credential on the second end-user host electronic device.   
     
     
         15 . The method of  claim 14 , wherein, when the second user transaction credential is requested for use on the second end-user host electronic device, the method further comprises, prior to the linking the second receive token to the second social token and prior to the facilitating the provisioning of the second send token on to the second end-user host electronic device, the method further comprises instructing, by the administration entity subsystem, the credential issuer subsystem to create the second fund account as a new stored-value account. 
     
     
         16 . The method of  claim 1 , wherein the receiving the device transfer funds request data comprises receiving, by the administration entity subsystem, from the first end-user host electronic device, the device transfer funds request data as a portion of a messaging communication generated by an instant messaging application running on the first end-user host electronic device. 
     
     
         17 . A method for facilitating a transfer of funds between a first fund account of a credential issuer subsystem and a second fund account of the credential issuer subsystem using a first end-user host electronic device and a second end-user host electronic device and an administration entity subsystem, the method comprising:
 when a first user transaction credential associated with the first fund account is requested for use on the first end-user host electronic device:
 linking, by the credential issuer subsystem, a first receive token and a first send token to a first account token that is uniquely associated with the first fund account; 
 communicating, by the credential issuer subsystem, to the administration entity subsystem, the first receive token; and 
 provisioning, by the credential issuer subsystem, on to the first end-user host electronic device, the first send token; 
   when a second user transaction credential associated with the second fund account is requested for use on the second end-user host electronic device:
 linking, by the credential issuer subsystem, a second receive token and a second send token to a second account token that is uniquely associated with the second fund account; 
 communicating, by the credential issuer subsystem, to the administration entity subsystem, the second receive token; and 
 provisioning, by the credential issuer subsystem, on to the second end-user host electronic device, the second send token; and 
   when the transfer of funds is requested:
 receiving, by the credential issuer subsystem, from the administration entity subsystem, an administration entity transfer funds request that comprises:
 device payment credential data comprising the first send token; 
 a fund amount; and 
 the second receive token; 
 
 validating, by the credential issuer subsystem, the first send token of the device payment credential data of the administration entity transfer funds request; and 
 in response to the validating, communicating, by the credential issuer subsystem, the fund amount of funds, from the first fund account as linked to the validated first send token, to the second fund account as linked to the second receive token of the administration entity transfer funds request. 
   
     
     
         18 . A method for facilitating a transfer of funds between a first fund account of a credential issuer subsystem and a second fund account of the credential issuer subsystem using a first end-user host electronic device and a second end-user host electronic device and an administration entity subsystem, wherein the first fund account is linked to a first send token and a first receive token at the credential issuer subsystem, wherein the second fund account is linked to a second send token and a second receive token at the credential issuer subsystem, wherein the first end-user host electronic device is associated with a first social token at the administration entity subsystem, wherein the second end-user host electronic device is associated with a second social token at the administration entity subsystem, wherein the first end-user host electronic device comprises a first user identifier and the first send token, and wherein the second end-user host electronic device comprises a second user identifier and the second send token, the method comprising:
 receiving, by the administration entity subsystem, from the first end-user host electronic device, a device transfer funds request that comprises:
 device payment credential data comprising the first send token; 
 a fund amount; 
 the second social token; and 
 a mandate key that comprises a hash of the first user identifier and of the second social token; 
 
 determining, by the administration entity subsystem, a mandate identifier that comprises a hash of the mandate key and of the first user identifier and of the second user identifier; and 
 calculating, by the administration entity subsystem, a fraud risk of the device transfer funds request using the determined mandate identifier. 
 
     
     
         19 . The method of  claim 18 , further comprising, storing, by the administration entity subsystem, the determined mandate identifier against fraud request data for the device transfer funds request, wherein the fraud request data comprises at least one of:
 the fund amount;   the time at which the determining occurred; or   a location of the first end-user host electronic device during the receiving.   
     
     
         20 . The method of  claim 18 , further comprising:
 after the calculating, identifying, by the administration entity subsystem, the second receive token using the second social token of the device transfer funds request;   sending, by the administration entity subsystem, to the credential issuer subsystem, an administration entity transfer funds request that comprises:
 the device payment credential data comprising the first send token; 
 the fund amount; and 
 the second receive token; and 
   in response to the sending, receiving, by the administration entity subsystem, from the credential issuer subsystem, a status of the administration entity transfer funds request.   
     
     
         21 . The method of  claim 20 , further comprising, storing, by the administration entity subsystem, the determined mandate identifier against fraud request data for the device transfer funds request, wherein the fraud request data comprises the received status of the administration entity transfer funds request. 
     
     
         22 . The method of  claim 20 , further comprising:
 accessing, by the administration entity subsystem, a unique transfer identifier for the device transfer funds request;   generating, by the administration entity subsystem, a send transaction identifier that comprises a hash of the unique transfer identifier and a send transaction salt; and   storing, by the administration entity subsystem, the generated send transaction identifier against send transaction data for the device transfer funds request, wherein the send transaction data comprises at least one of:   the fund amount;   the time at which the determining occurred;   a location of the first end-user host electronic device during the receiving;   the calculated fraud risk;   the received status of the administration entity transfer funds request; or   the first user identifier.   
     
     
         23 . The method of  claim 20 , further comprising:
 accessing, by the administration entity subsystem, a unique transfer identifier for the device transfer funds request;   generating, by the administration entity subsystem, a receive transaction identifier that comprises a hash of the unique transfer identifier and a receive transaction salt; and   storing, by the administration entity subsystem, the generated receive transaction identifier against receive transaction data for the device transfer funds request, wherein the receive transaction data comprises at least one of:   the fund amount;   the time at which the determining occurred;   the calculated fraud risk;   the received status of the administration entity transfer funds request;   the second user identifier; or   the second social token.   
     
     
         24 . The method of  claim 23 , further comprising:
 generating, by the administration entity subsystem, a send transaction identifier that comprises a hash of the unique transfer identifier and a send transaction salt; and   storing, by the administration entity subsystem, the generated send transaction identifier against send transaction data for the device transfer funds request, wherein the send transaction data comprises at least one of:   the fund amount;   the time at which the determining occurred;   a location of the first end-user host electronic device during the receiving;   the calculated fraud risk;   the received status of the administration entity transfer funds request; or   the first user identifier.   
     
     
         25 . The method of  claim 24 , wherein the send transaction salt is different than the receive transaction salt. 
     
     
         26 . A method for facilitating a transfer of funds between a first fund account of a first credential issuing subsystem and a second fund account of a second credential issuing subsystem using a first electronic device and a second electronic device and an administration entity (“AE”) subsystem, wherein the first fund account is linked to a first send token and a first receive token at the first credential issuing subsystem, wherein the second fund account is linked to a second send token and a second receive token at the second credential issuing subsystem, wherein the first electronic device is associated with a first social token, and wherein the second electronic device is associated with a second social token, the method comprising:
 when the provisioning of a first device credential associated with the first fund account is requested on the first electronic device, using the AE subsystem to:
 store, at the AE subsystem, the first receive token against the first social token; and 
 provision first device credential data comprising the first send token on the first electronic device; 
 
 when the provisioning of a second device credential associated with the second fund account is requested on the second electronic device, using the AE subsystem to:
 store, at the AE subsystem, the second receive token against the second social token; and 
 provision second device credential data comprising the second send token on the second electronic device; and 
 
 when the transfer of funds is initiated by the first electronic device, using the AE subsystem to:
 receive, at the AE subsystem from the first electronic device, device transfer funds request data that comprises:
 device payment credential data comprising the first send token; and 
 the second social token; 
 
 identify, at the AE subsystem, the second receive token using the second social token of the device transfer funds request data; and 
 communicate, from the AE subsystem to the first credential issuing subsystem, AE transfer funds request data that comprises:
 the identified second receive token; and 
 the received device payment credential data comprising the first send token.

Join the waitlist — get patent alerts

Track US2018336553A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.