CASE STUDIES · 2023

Scramble Pay

Multi-chain crypto checkout, pilot-ready for merchant integration, shipped in 2 months.

ScramblePay is a flexible online and Point-of-Sale payment system. Drops into online shops and handles on-site payments in restaurants, hotels, and bars, with a built-in DEX aggregator for paying in low-cap tokens.

“Communication, work, and scheduling: all perfect.” Tom Google
FUNDS 2023 Live
01 Overview

Overview

ScramblePay is a flexible online and Point-of-Sale payment system. Drops into online shops and handles on-site payments in restaurants, hotels, and bars, with a built-in DEX aggregator for paying in low-cap tokens.

02 What's the challenge?

What's the challenge?

Build an enterprise-grade crypto checkout other companies could embed. PoS and web, multi-chain, wallet-agnostic, and ship it pilot-ready in two months. No off-the-shelf product covered the full scope, and writing a swap engine from scratch would have burned both the runway and the timeline.

03 What call did we make?

Two months from kickoff to enterprise-ready, pilot-ready, handed over.

Time was the real constraint. The product had to be enterprise-grade, something other companies could embed in their checkout, and it had to land in two months. We bought speed where it was cheap (forked a proven DEX aggregator) and built where it mattered (a checkout clean enough for a third-party merchant to drop in). Two months in, we handed over a pilot-ready product.
04 What We Did

What We Did

Two months to ship an enterprise-grade crypto checkout other companies could integrate. We forked a battle-tested DEX aggregator for the swap layer and poured the budget into a clean, embeddable checkout, speed where it was cheap, depth where it mattered. PoS plus web, multi-chain, wallet-agnostic on desktop and mobile, merchant dashboard, third-party integration surface. The trade was dependence on the upstream aggregator’s roadmap.

05 Outcomes

Outcomes

Speed 2 months Concept to Pilot-Ready
Any DEX token Payment Coverage
06 Client Voice

Client Voice

Communication, work, and scheduling: all perfect.
Tom
07 What We Learned

What We Learned

Tight budgets force the right architectural bets upfront. Forking a battle-tested DEX aggregator and building a thin merchant layer on top reaches production faster than writing a swap engine. The client only cares about the checkout experience.

Tech Stack
Tags
Cross Chain SwapsEVM & Non-EVM supportDesktop & Mobile
FAQ

Questions about this project

What is Scramble Pay?

ScramblePay is a flexible online and Point-of-Sale payment system. Drops into online shops and handles on-site payments in restaurants, hotels, and bars, with a built-in DEX aggregator for paying in low-cap tokens.

What was the challenge in the Scramble Pay project?

Build an enterprise-grade crypto checkout other companies could embed. PoS and web, multi-chain, wallet-agnostic, and ship it pilot-ready in two months. No off-the-shelf product covered the full scope, and writing a swap engine from scratch would have burned both the runway and the timeline.

What did Wavect do for Scramble Pay?

Two months to ship an enterprise-grade crypto checkout other companies could integrate. We forked a battle-tested DEX aggregator for the swap layer and poured the budget into a clean, embeddable checkout, speed where it was cheap, depth where it mattered. PoS plus web, multi-chain, wallet-agnostic on desktop and mobile, merchant dashboard, third-party integration surface. The trade was dependence on the upstream aggregator’s roadmap.

What were the outcomes of the Scramble Pay project?
  • 2 months, Concept to Pilot-Ready
  • Any DEX token, Payment Coverage
How did Wavect work with Scramble Pay?

Engagement: Fullstack Build. Engagement size: Hourly rate. Year: 2023.

Which tech stack did Wavect use for Scramble Pay?

React, Typescript, NestJS, Google Cloud.

What did Wavect learn from the Scramble Pay project?

Tight budgets force the right architectural bets upfront. Forking a battle-tested DEX aggregator and building a thin merchant layer on top reaches production faster than writing a swap engine. The client only cares about the checkout experience.

Want outcomes like this?

Tell us what you're building. We'll tell you whether we're the right team for it.

 Get in touch