In March 2010, PayPal announced an iPhone Send Money update with a feature designed to be memorable: bring two phones together to begin a transfer between accounts. The old “bump to send” headline refers to this specific release, not a suggestion that the same gesture remains part of the current app.
What version 2.0 introduced
PayPal’s March 16, 2010 announcement describes Bump transfers alongside splitting a check and collecting money from a group. The common theme was turning a familiar real-world situation into a phone workflow: settling a meal, repaying someone or coordinating a shared contribution.
The gesture was the interface, not the whole transaction
A friendly physical action can make a digital process easier to understand. It does not remove the need to identify the recipient, review the amount and understand the terms. Those details matter regardless of whether the interaction begins with a tap, a code or two phones moving together.
Historical demonstrations often focus on the memorable moment because it is easy to show. When evaluating a present payment tool, pay equal attention to confirmation screens, transaction records and what happens if something goes wrong.
Keep historical features separate from current choices
The release is useful evidence of PayPal’s mobile design at the time. Its interface, fees, availability and supported account functions should not be assumed to describe today’s service. Use the provider’s current app and help information when deciding how to complete a real payment.
This article provides product history, not instructions to transfer money or a recommendation about a financial transaction. The design lesson is broader: convenience works best when it makes a task understandable while leaving the important details visible. A distinctive gesture is memorable; a clear record is what makes the interaction reviewable afterward.
