Systems and methods for transferring resource access
Systems and methods for transferring resource access from a sender to a recipient are disclosed that can allow a sender to specify an amount of a resource to provide access to (e.g., an amount of money or an amount of access rights), while still providing security for the sender's sensitive credential information (e.g., PAN and/or PIN). These systems and methods can allow a sender to transfer resource access from any location and at any time of the day. In the case of money transfers, the recipient can quickly and directly obtain the money from any ATM location associated with any bank and at any time of the day, even without a bank account.
1. A method comprising:
obtaining, by a server computer, a token corresponding to an account identifier and a recipient code associated with a sender code, the account identifier and the sender code associated with a sender, and the token and the recipient code capable of being used at only at a specific terminal;
sending, by the server computer, the token and the recipient code to a recipient using a recipient identifier;
receiving, by the server computer, a request to access a resource, the request including the token and the recipient code, from the specific terminal;
translating, by the server computer, the token into the account identifier and the recipient code into the sender code; and
processing, by the server computer, the request using the account identifier and the sender code.
2. The method of claim 1 , further comprising:
after processing the request, invalidating the token and the recipient code.
3. The method of claim 2 , further comprising:
after invalidating the token and the recipient code, receiving another request to access the resource, the another request including the token and the recipient code; and
declining the another request.
4. The method of claim 1 , wherein the recipient code is generated after being selected by the sender.
5. The method of claim 1 , wherein the recipient identifier is associated with a mobile device of the recipient.
6. The method of claim 5 , further comprising:
provisioning the mobile device of the recipient with the token.
7. The method of claim 1 , wherein the request is a second request, and the server computer receives a first request which specifies at least one condition under which the second request must be received.
8. The method of claim 7 , wherein the at least one condition comprises at least one of a maximum duration of time between receiving the first request and receiving the second request, and a location associated with the second request.
9. The method of claim 8 , further comprising:
receiving a third request to access a second portion of the resource, the third request including the token and the recipient code;
translating, by the server computer, the token into the account identifier and the recipient code into the sender code; and
processing, by the server computer, the third request using the account identifier and the sender code.
10. The method of claim 1 , wherein the specific terminal is a specific ATM.
11. The method of claim 1 , wherein at least one of the sender code and the recipient code is a PIN number.
12. A server computer comprising:
a processor; and
a memory element comprising code, executable by the processor, for implementing a method comprising:
obtaining a token corresponding to an account identifier and a recipient code associated with a sender code, the account identifier and the sender code associated with a sender, and the token and the recipient code capable of being used at only at a specific terminal;
sending the token and the recipient code to a recipient using a recipient identifier;
receiving a request to access a resource, the request including the token and the recipient code, from the specific terminal;
translating the token into the account identifier and the recipient code into the sender code; and
processing the request using the account identifier and the sender code.
13. The server computer of claim 12 , the method further comprising:
after processing the request, invalidating the token and the recipient code.
14. The server computer of claim 13 , the method further comprising:
after invalidating the token and the recipient code, receiving another request to access the resource, the another request including the token and the recipient code; and
declining the another request.
15. The server computer of claim 12 , wherein the recipient code is generated after being selected by the sender.
16. The server computer of claim 12 , wherein the recipient identifier is associated with a mobile device of the recipient.
17. The server computer of claim 16 , the method further comprising:
provisioning the mobile device of the recipient with the token.
18. The server computer of claim 12 , wherein the request is a second request, and wherein the method further comprises:
receiving a first request, wherein the first request specifies at least one condition under which the second request must be received.
19. A system comprising:
a server computer comprising
a processor, and
a memory element comprising code, executable by the processor, for implementing a method comprising
obtaining a token corresponding to an account identifier and a recipient code associated with a sender code, the account identifier and the sender code associated with a sender, and the token and the recipient code capable of being used at only at a specific terminal,
sending the token and the recipient code to a recipient using a recipient identifier,
receiving a request to access a resource, the request including the token and the recipient code, from the specific terminal,
translating the token into the account identifier and the recipient code into the sender code, and
processing the request using the account identifier and the sender code; and
the specific terminal in communication with the server computer.
20. The system of claim 19 , wherein the specific terminal is an ATM.