MONEY TRANSFER USING CANONICAL URL
Described is a technology for executing financial transactions, e.g., payment transfers, by enabling a sender to trigger a money transfer by specifying a payment proxy having a particular syntax, the syntax including a monetary indicator preceding one or more alphanumeric characters. The payment proxy having the syntax indicates an intent of the sender to transfer money to a recipient associated with that payment proxy. The payment proxy can be used to transfer money within the context of a landing page. For example, a landing page in the form of a webpage can be generated to enable a recipient (e.g., “Alex”) to receive money. The webpage can have a canonical URL that includes a payment proxy of the recipient (e.g., www. . . . com/$alex). The canonical URL can direct any sender (e.g., “Bob”), who wishes to send money to the recipient, to the webpage to initiate a money transfer to the recipient.
1 . A method of transferring money to one or more recipients from one or more senders, the method executed by a payment service system associated with a payment service, comprising:
receiving, by a payment service system, a request to generate a web page based on a uniform resource locator (URL) input into a browser application executing at a client device of a first sender of the one or more senders, wherein the web page is associated with a money transfer service implemented by the payment service system, the web page configured to collect money on behalf of a recipient;
determining, by the payment service system, a user account of the recipient based on the URL, wherein the URL has been personalized by the payment service system to include information associated with the user account of the recipient;
causing, by a payment service system, the web page to be displayed on the browser application at the client device, the web page including a first user interface configured to prompt the first sender to input a monetary amount to be transferred to the recipient;
receiving, by the payment service system via the web page, the monetary amount input into the web page by the first sender;
2 . based on the monetary amount received and the user account of the recipient determined based on the URL, initiating a transfer of money from a financial account associated with the first sender to a financial account associated with the recipient. The method of claim 1 , further comprising:
determining an identity of a user accessing the web page based on a logged-in status associated with the browsing application, the logged-in status established based on login credentials associated with the user;
designating the user as the first sender;
identifying a user account of the first sender based on the determined identity of the user; and
determining the financial account associated with the first sender based on a stored association between the user account of the first sender and the financial account associated with the first sender, the stored association established in a registration of the user account of the first sender with the payment service system.
3 . The method of claim 1 , further comprising:
causing a second user interface of the web page to be displayed on the browser application at the client device, the second user interface configured to prompt the first sender to input a unique identifier associated with the first sender, the unique identifier including any of an email address or a phone number;
receiving the unique identifier from the client device;
identifying a user account of the first sender based on the unique identifier; and
determining the financial account associated with the first sender by accessing a database associated with the payment service system, the database storing association data specifying an association between the user account and the financial account associated with the first sender.
4 . The method of claim 1 , further comprising:
causing a second user interface of the web page to be displayed on the browser application at the client device, the second user interface configured to prompt the first sender to input financial account information for the financial account associated with the first sender.
5 . The method of claim 1 , further comprising:
receiving, by a payment service system, a second request to generate the web page based on the URL input into a second browser application executing at a second client device of a second sender;
causing, by a payment service system, the web page to be displayed on the second browser application at the second client device;
receiving, by the payment service system via the web page, a second monetary amount input into the web page by the second sender;
identifying, by the payment service system, a second financial account associated with the second sender; and
aggregating, by the payment service system, the monetary amount from the sender with the second monetary amount from the second sender to generate an aggregated amount; and
causing, by the payment service system, the aggregated amount to be transferred to the financial account associated with the recipient.
6 . A method comprising:
receiving a request to generate a web page based on a uniform resource locator (URL) entered by a sender into a browsing application executing on a sender device of the sender;
identifying, based on the URL, a recipient user account associated with a money transfer service, the money transfer service implemented by a payment service system;
causing the web page to be displayed at the browsing application executing on the sender device, the web page including an entry field configured to receive a payment amount to be transferred to a recipient at the recipient user account via the money transfer service;
receiving the payment amount from the sender via the sender device; and
based on the payment amount received and the recipient user account identified, initiating a transfer of the payment amount to a recipient financial account associated with the recipient.
7 . The method of claim 6 , further comprising:
determining an identity of a user accessing the web page based on login credentials associated with the browsing application;
designating the user as the sender;
identifying a user account of the sender based on the determined identity of the user; and
determining a sender financial account based on a stored association between the user account of the sender and the sender financial account, the stored association established in a registration of the user account with the payment service system, wherein the payment amount is transferred from the sender financial account to the recipient financial account.
8 . The method of claim 6 , wherein the web page further includes a financial information field configured to prompt the sender to input financial account information for a sender financial account associated with the sender.
9 . The method of claim 6 , wherein said initiating the transfer of the payment amount comprises:
generating a confirmation message that includes a confirmation link to confirm the transfer of the payment amount;
transmitting the confirmation message to the sender for viewing at the sender device;
receiving an indication of user engagement with the confirmation link to confirm the transfer of the payment amount indicated in the confirmation message; and
causing the payment amount to be transferred from a sender financial account to the recipient financial account.
10 . The method of claim 9 , wherein the confirmation link is configured to prompt the sender to input sender financial account information identifying the sender financial account.
11 . The method of claim 6 , further comprising:
receiving a unique identifier associated with the sender; and
accessing a database to identify a sender financial account based on a stored association between the unique identifier and the sender financial account in the database.
12 . The method of claim 11 , wherein the unique identifier is any of an email address, a phone number, or a payment proxy.
13 . The method of claim 11 , wherein the unique identifier is any of an IP address, a device ID, an application ID, or a biometric identifier.
14 . The method of claim 6 , further comprising:
receiving a unique identifier associated with the sender;
sending a confirmation message to a mobile device associated with the unique identifier, wherein the mobile device is preregistered with the computer system, wherein the confirmation message includes a confirmation link to enable the sender to confirm the transfer of the payment amount; and
receiving, by the computer system, a confirmation from the mobile device via the confirmation link, wherein the payment amount is transferred in response to the confirmation.
15 . The method of claim 14 , wherein the mobile device is the sender device accessing the web page or a different sender device.
16 . The method of claim 6 , further comprising:
receiving a plurality of payment amounts inputted at the web page by a plurality of senders as a plurality of payments to the recipient, wherein the plurality of senders access the web page through a plurality of applications installed on a plurality of sender devices of the plurality of senders;
identifying a plurality of unique identifiers associated with the plurality of senders;
identifying a plurality of financial accounts associated with the identified plurality of unique identifiers; and
aggregating the plurality of payment amounts inputted by the plurality of senders into an aggregated payment amount; and
causing the aggregated payment amount to be transferred to the recipient financial account associated with the recipient.
17 . The method of claim 16 , wherein the plurality of unique identifiers include any of an email address, a phone number, a payment proxy, an IP address, a device ID, an application ID, or a biometric identifier.
18 . A payment service system comprising:
a processor;
a communications module; and
a non-transitory computer-readable storage medium containing a set of instructions including:
instructions for receiving a request to generate a web page based on a uniform resource locator (URL) entered into a browsing application at a sender device of a sender, the URL including information associated with a recipient of a payment amount in a money transfer, the URL generated by the payment service system to collect payments on behalf of the recipient;
instructions for determining, based on the URL, a recipient account and a monetary value;
instructions for causing the web page to be displayed at the sender device, the webpage displaying the monetary value and identity information associated with the recipient account;
instructions for, receiving, based on the web page, a user account associated with a user accessing the web page and designating the user as the sender of the payment amount to the recipient; and
instructions for receiving an indication of confirmation of the money transfer to the recipient;
instructions for causing, based on the user account and the confirmation, the payment amount to be transferred from a sender financial account to a recipient financial account associated with the recipient.
19 . The payment service system of claim 18 , the set of instructions further including:
instructions for sending a financial account request for viewing at the sender device, the financial account request configured to prompt the sender to input sender financial account information identifying the sender financial account.
20 . The payment service system of claim 18 , wherein the instructions further comprise:
instructions for identifying the recipient financial account by accessing a database associated with the payment service system, the identifying based on a stored association between the web page and the recipient financial account stored in the database, the stored association established in a registration of the web page by the recipient with the payment service system.
21 . The payment service system of claim 18 , wherein the instructions further comprise:
instructions for sending a confirmation message, via the communications module, to a mobile device of the sender, wherein the mobile device is preregistered with the payment service system, wherein the confirmation message includes a confirmation link to enable the sender to confirm a transfer of the payment amount; and
instructions for receiving the indication of the confirmation of the money transfer from the mobile device via the confirmation link, wherein the payment amount is transferred in response to the confirmation.
22 . The payment service system of claim 21 , wherein the mobile device is the sender device accessing the web page or a different sender device.
23 . A non-transitory computer readable medium storing a program causing a computer to execute a process of transferring money, comprising:
receiving, from a user device, a request to generate a web page based on a personalized uniform resource locator (URL), the personalized URL including information associated with a recipient of money;
determining, based on the personalized URL, a recipient account and a monetary value;
causing the web page to be displayed at the user device, the webpage displaying the monetary value and identity information associated with the recipient account;
based on the web page, receiving a user account associated with a user accessing the web page and designating the user as a sender of money to the recipient;
receiving, via the web page, a confirmation from the sender of a money transfer to the recipient based on an entry by the sender at the web page; and
based on receipt of the user account and the confirmation, initiating a transfer of the monetary value to a recipient financial account associated with the recipient account.
24 . The non-transitory computer readable medium of claim 23 , wherein the process of transferring money further comprises:
determining a sender financial account associated with the sender based on a stored association between the user account and the sender financial account; and
causing the monetary value to be transferred from the sender financial account to the recipient financial account.
25 . The non-transitory computer readable medium of claim 23 , wherein the process further comprises:
causing a second user interface of the web page to be displayed at the client device, the second user interface configured to prompt the user to input financial account information for a sender financial account; and
causing the monetary value to be transferred from the sender financial account to the recipient financial account.