System and method for facilitating electronic financial transactions during a communication session
A payment button on a device capable of making telephone calls, such as a mobile phone, allows a payer to electronically transfer money while in a phone call with a payee. The payment button also allows a payee to initiate an electronic payment transaction while in a phone call with a payer. The payment button may be a clickable or tappable virtual button presented on a display of the phone when being used to make or receive a call. The payer or the payee can simply enter a payment amount on the phone to complete an electronic payment transaction. A notification of payment is instantly transmitted to the phones being used for the phone call, so that the parties can safely and conveniently conclude a purchase and/or payment transaction during one phone call.
1. A method, comprising:
detecting, by a payment provider server comprising at least one processor, a first communication session between a first mobile device of a first user and a second mobile device of a second user;
in response to a determination that the first communication session is associated with a transaction between the first user and the second user, communicating, by the payment provider server, with the first mobile device to cause to be displayed, via a first application of the first mobile device, a first user interface element, wherein the first user interface element is associated with the payment provider server, and wherein the first application uses the first communication session;
responsive to detecting a selection of the first user interface element via the first application, determining, by the payment provider server, a first account associated with the first user and determining a second account associated with the second user, wherein the first account and the second account are associated with the payment provider server;
communicating, by the payment provider server, with the first mobile device to cause to be displayed, via the first application, a second user interface element that indicates the transaction between the first account and the second account; and
responsive to detecting a selection of the second user interface element, processing the transaction using the first account and the second account.
2. The method of claim 1 , further comprising:
responsive to said determining one or more of the first account and the second account, verifying, by the payment provider server, one or more of the first user or the second user via communicating with the first mobile device or the second mobile device, respectively.
3. The method of claim 1 , wherein the first communication session is conducted over internet protocol (IP).
4. The method of claim 1 , further comprising transmitting, by the payment provider server, a transaction completion notification to one or more of the first mobile device and the second mobile device.
5. The method of claim 1 , further comprising responsive to said detecting the selection of the first user interface element, communicating, by the payment provider server, with the first mobile device to prompt the first user, via the first application, to provide a payment amount for the transaction.
6. The method of claim 1 , further comprising responsive to said detecting the selection of the first user interface element, communicating, by the payment provider server, with the first mobile device to prompt the first user, via the first application, to provide a user identifier corresponding to the second user.
7. The method of claim 1 , wherein said determining the second account associated with the second user is based on a user identifier associated with the transaction.
8. The method of claim 1 , wherein the selection of the second user interface element indicates a request for processing of the transaction using the second account and the first account.
9. A payment provider server comprising:
a non-transitory memory storing instructions; and
a processor coupled with the non-transitory memory and configured to execute the instructions from the non-transitory memory to cause the payment provider server to:
detect a first communication session between a first user device of a first user and a second user device of a second user;
in response to a determination that the first communication session is associated with a transaction between the first user and the second user, communicate with the first user device to cause to display a first user interface element via a first application at the first user device, wherein the first user interface element is associated with the payment provider server that is operable to process the transaction, and wherein the first application uses the first communication session;
in response to a detection of a selection of the first user interface element, determine a first account and a second account at the payment provider server that are associated with the first user and the second user, respectively;
communicate with the first user device to display a second user interface element via the first application, wherein the second user interface element is associated with the transaction between the first account and the second account; and
in response to a detection of a selection of the second user interface element, process the transaction between the first account and the second account.
10. The payment provider server of claim 9 , wherein executing the instructions further causes the payment provider server to, in response to the determination of the one or more of the first account and the second account, verify one or more of the first user or the second user via communicating with the first user device or the second user device, respectively.
11. The payment provider server of claim 9 , wherein executing the instructions further causes the payment provider server to transmit a transaction completion notification to the first user device or the second user device.
12. The payment provider server of claim 9 , wherein executing the instructions further causes the payment provider server to, in response to the detection of the selection of the first user interface element, communicate with the first user device to prompt the first user, via the first application, to provide a payment amount for the transaction.
13. The payment provider server of claim 9 , wherein executing the instructions further causes the payment provider server to, in response to the detection of the selection of the first user interface element, communicate with the first user device to prompt the first user, via the first application, to provide a user identifier corresponding to the second user.
14. The payment provider server of claim 9 , wherein the selection of the second user interface element indicates a request for processing of the transaction using the second account and the first account.
15. A non-transitory machine-readable medium storing instructions that, when executed by a payment provider server that comprises one or more processors, cause the payment provider server to perform operations comprising:
detecting a first communication session between a first mobile device of a first user and a second mobile device of a second user;
in response to a determination that the first communication session is associated with a transaction between the first user and the second user, communicating with the first mobile device to cause the first mobile device to display a first user interface element via a first application at the first mobile device, wherein the first user interface element is associated with the payment provider server, and wherein the first application uses the first communication session;
in response to a detection of a selection of the first user interface element, determining a first account and a second account at the payment provider server that are associated with the first user and the second user, respectively;
communicating with the first mobile device to display a second user interface element via the first application, wherein the second user interface element is associated with the transaction between the first account and the second account; and
in response to a detection of a selection of the second user interface element, processing the transaction between the first account and the second account.
16. The non-transitory machine-readable medium of claim 15 , wherein the instructions, when executed by the payment provider server, further cause the payment provider server to perform operations comprising:
verifying, based on one or more of the first account and the second account, one or more of the first user or the second user via communicating with the first mobile device or the second mobile device, respectively.
17. The non-transitory machine-readable medium of claim 15 , wherein the instructions, when executed by the payment provider server, further cause the payment provider server to transmit a transaction completion notification to the first mobile device or the second mobile device.
18. The non-transitory machine-readable medium of claim 15 , wherein the instructions, when executed by the payment provider server, further cause the payment provider server to perform operations comprising: responsive to the detection of the selection of the first user interface element, communicating with the first mobile device to prompt the first user, via the first application, to provide a payment amount for the transaction.
19. The non-transitory machine-readable medium of claim 15 , wherein the instructions, when executed by the payment provider server, further cause the payment provider server to perform operations comprising: responsive to the detection of the selection of the first user interface element, communicating with the first mobile device to prompt the first user, via the first application, to provide a user identifier corresponding to the second user.
20. The non-transitory machine-readable medium of claim 15 , wherein the selection of the second user interface element indicates a request for processing of the transaction using the second account and the first account.