All posts
Compass Labs

Everyone wants to be a one-stop shop

The best one stop shops in finance weren't built by one company. They were assembled.

  • Fintech
  • Embedded Finance
  • Build vs Buy
  • Infrastructure
  • Non-custodial
Everyone wants to be a one-stop shop

Your users see one app. Underneath, a wallet or custody provider secures the keys, a card partner handles spend and a banking partner moves the fiat. The brand on top owns the relationship.

Most of the fintechs, wallets and neobanks we talk to want to be that app: payments, cards, savings, credit and investing in one place. It's the right ambition. People don't want five apps for their money.

The question isn't whether to partner. It's which layers you still insist on building yourself.

Why now

The largest names in finance are already building this way, one layer at a time.

In November, Morgan Stanley said it had tokenized US equities and Treasuries through DTCC's new tokenization service (Morgan Stanley on X; The Block). Even a bank of that size plugged into shared infrastructure for a new layer.

The same week, Visa opened six capability hubs in Singapore, with dedicated hubs for agentic commerce, for stablecoins and programmable payments, and for wallets (Visa, via Singapore EDB).

Stablecoins, tokenized assets and AI agents are each becoming a layer of their own, with their own specialists. No single product team stays expert in all of them at once.

Building every layer yourself is the slow way there

Look at what a full financial stack actually involves.

Wallets and custody. Card issuing. Fiat rails. Customer onboarding and compliance. And more and more, onchain products: stablecoin yield, lending, tokenized assets, trading.

Each of those layers is its own discipline. Take just one. Adding a single onchain venue means:

  • Reading its contracts and building deposit, withdrawal and accounting logic around them
  • Monitoring its rates, liquidity and risk settings as they change
  • Handling its upgrades, migrations and incidents on someone else's schedule
  • Testing every new flow against your own signing and custody setup

Now multiply that by every venue you want to offer. Then multiply again by every product: earn, lending, tokenized assets, trading.

That is the integration tax, and you pay it on every layer you build yourself. Engineering time goes into plumbing instead of the product your users see. Every new feature waits behind the last one.

The stack gets built in partnerships

The one-stop shops that work look like one product on the outside. On the inside, they are a set of specialists, each chosen for one job.

The business on top keeps the part that matters most: the customer, the brand and the economics. Everything underneath is a partner, and a partner can be added or replaced with far less rework than rebuilding the layer yourself.

Where Compass fits

Compass is the onchain product layer: one API to add stablecoin yield, loans and tokenized assets to a product that already exists.

Just as important is what we are not.

  • We don't hold funds or keys. Compass is non-custodial. We return an unsigned transaction or typed data, and the signing setup you or your custody partner already runs approves it.
  • We don't issue cards or move fiat. Those stay with the partners who specialize in them.
  • We don't choose products for your users. Each business picks the products that fit its licences and its customers.

That is what lets Compass sit next to the wallet, custody and card partners you already have, instead of replacing them.

Your app stays in front. You can embed your own fees. On supported flows, you can sponsor gas so users don't need a separate token to pay network fees.

Onchain products carry smart contract and market risk, loans can be liquidated, and rates are variable. That is why the controls you choose matter as much as the products you add.

What to ask before you build it all yourself

  1. Is this layer the reason users choose us or something they just expect to work?
  2. How many integrations does it really mean, and who maintains them when they change?
  3. Who holds the keys and who signs at each step? Does a new partner change that?
  4. Can a partner plug into the wallet or custody setup we already run?
  5. Do we keep our brand, our pricing and the customer relationship?
  6. When we add the next product, is it a new integration or the same one?

If a layer isn't the reason users choose you, it is probably a partnership.

One app on the outside

People will keep moving their financial lives into fewer apps. The businesses that win will look like a one-stop shop and be built like a network of specialists.

Own the customer. Partner for the rest.

If you're mapping which onchain products to add, and who should provide them, we'd like to talk. See what you can build or read the docs.

Build the same on Compass.

Yield, lending, trading & RWAs that plug into your app or platform. Non-custodial, monetized, live in days.