Case Study: How Rampa Cut Cross-Border Transfers from Hours to 30 Seconds in 180+ Countries
How Rampa used Para's embedded wallets to grow from cross-border transfers to everyday money, with sub 30-second transfers in 180+ countries.
Rampa is a money app for people sending euros from Europe to Latin America. Para powers the wallets behind it.
Most remittance products treat the transfer as the whole product. Money leaves one country, arrives in another, and whatever happens in between is the customer's problem. The sender gets a confirmation screen. The recipient gets a cash pickup. Nobody gets a relationship.
Rampa started somewhere else. The team looked at the same corridor everyone else looks at, Europe into LATAM, and noticed that the money sitting in the gap is the largest untapped asset most senders have. It sits idle because no one built a product that lets it do anything else.
So Rampa built one. The app combines instant stablecoin transfers with optional yield, fast local off-ramps in the destination market, and short financial literacy lessons. Users can hold a balance, earn on it, and cash out when the rate works in their favor rather than when a wire clears. For many of their users, it functions less like a transfer service and more like a first real financial account.
None of that works if the wallet gets in the way.
The Constraint: Building on Crypto Rails
Rampa's target user is not a crypto user. The team's requirements were specific. They needed stablecoin rails for speed and cost, non-custodial architecture to hold up under their regulatory posture across Europe and LATAM, and an onboarding flow a first-time user could finish on a phone in under four minutes.
They also needed to ship. Building wallet infrastructure and a yield integration in-house would have meant a year of work before the first euro moved.
“We’re a small team building for families, not for crypto users, building MPC key management ourselves would have meant months of security work before a single euro moved. What made us choose Para was the support. From day one, the team has been there for us, and whenever something came up, they solved it quickly and to the point.” – Juan Manuel Gallego, Co-Founder
The Stack
Rampa runs on Solana, chosen for the combination of settlement speed and fee economics a remittance product actually needs. When the median transfer is a few hundred euros, per-transaction cost matters. Solana's throughput also means a user in Madrid sees confirmation in seconds, which is the promise the app makes on its homepage.
On top of that, Rampa assembled three pieces rather than building any of them.
Para for wallets. A user signs up with an email and a wallet exists. Para uses Distributed MPC, so a private key never exists in full at any point, which is what lets Rampa tell users plainly that Rampa never holds their money. Para does not hold it either. Rampa is able to ship mobile experiences on iOS and Android using the React Native SDK.
RebelFi for earning. RebelFi gives Rampa access to yield vaults on Solana across protocols like Kamino and Jupiter. For its users, Rampa chose Jupiter Lend as the lowest-risk option. On top of that, Rampa designed Earn to be as simple as possible: a couple of taps to put money to work, and the same to take it out. The idea is that when someone loads money to send home, they save a percentage of it, and the recipient sets aside a share of what they receive too. Rampa encourages both through in-app messages and the Learn tab. This is the piece that changes what the product is. A transfer service moves money and takes a cut. Rampa gives the sender a reason to leave money in the app between transfers, and gives the recipient a reason to hold rather than cash out immediately into a local currency that may be moving against them.
Local payment rails for off-ramping. A balance that cannot be spent is a balance the user will eventually flee. Rampa solves the exit inside the app. The recipient cashes out through the instant payment systems they already use, like Bre-B in Colombia, with Koywe handling the local payout behind the scenes. A recipient moves from stablecoins to money in their own account in seconds, through a system they already trust, without Rampa needing to issue a card or ask anyone to learn a new way to get paid.
Read as a whole, this is not a remittance app with crypto bolted on. It is a consumer financial account where the crypto is entirely load-bearing and entirely invisible. The user does an email signup, a two-minute KYC, and a bank transfer. Everything after that is infrastructure she will never need to think about.
"We started with the wallet, because everything else depends on it. Then we added licensed partners for KYC, on-ramp and local payouts, and only then Earn. Yield only matters once people trust that their money can come in and go out easily.” Juan Manuel Gallego, Co-Founder
Education
Many Rampa users never had access to dollar savings or yield back home. So the app also explains how to use them.
The "Learn" tab has short lessons in Spanish on how stablecoins work, why saving in dollars helps when the local currency loses value, and how to get more out of a stablecoin balance instead of cashing out right away. The in-app messages that encourage users to save part of each transfer build on these lessons.
Results Since Launch
Android in April 2026, iOS in July 2026
- 150+ families actively using Rampa every month
- 180+ countries supported
- ~30s transfer time compared to hours
- Nearly 1 in 3 active families use Earn
- 1,500+ downloads, including on Solana Seeker
"Para let us skip building key management, wallet recovery and security from scratch. We estimate that saved us close to a year of engineering time, plus a security audit we couldn't have paid for, which for a team our size makes the difference between launching and not launching.” Juan Manuel Gallego, Co-Founder

Remittances are one of the clearest cases for stablecoins and one of the least forgiving places to deploy them. The users have the least tolerance for friction, the least appetite for jargon, and the most at stake when a transfer goes wrong.
Building something similar? → getpara.com