Open it from your own system
An embedded sign-in opens the wallet for a person who is already signed in to your product. They do not meet a second login.
Embedded wallet
A wallet inside your own app.
Embedded means the wallet opens where your customers already are. They sign in where they already sign in, the balance appears inside your product, and nothing sends them to another brand to handle their own money.
The wallet is live in production inside connected applications on web and mobile.
A wallet screen showing a balance, this month's movement and three actions.
What embedded means here
Inside your product, under your sign-in.
The word gets used for several different arrangements, so here is the one this page describes.
Your customers reach the wallet from inside your own application. There is no second app to download and no separate account to create, because the wallet is opened for a person who is already your user. Your name and your colours sit around it, and the DigiWise lockup stays in the wallet header.
What that buys you is the thing most payment arrangements give away: the moment money moves, your customer is still in your product. A top up does not end at somebody else's confirmation screen. A refund does not disappear towards a card for several days. A payment between two of your users does not route out through a bank and back.
Embedded describes where the wallet runs. It does not mean a drop-in component you paste into a page, and this page will not pretend otherwise. What we provide is documented below.
Connecting it
Three ways in, and most products use all three.
These are the connections that exist today. Nothing here needs you to rebuild your own sign-in or hold a balance of your own.
Let your system ask for a payment
Your app asks for an amount and your customer approves it in the wallet. Your system never handles the balance itself.
Take the records out
Every movement can be exported for any period, straight into a spreadsheet, so your finance team reconciles against the same record the balances are built from.
On your side the only thing to store is the wallet ID, held against your own user. Every later call names the wallet by that ID.
What your customers get
Four movements, one screen.
A wallet does four things. Embedding it means all four happen without your customer leaving.
- Top Up. Money loaded from a card on the payment provider's own secure page. Card details never reach us.
- Payment. Approved in the wallet, and divisible between several parties as it is made.
- Transfer. Wallet to wallet with a reference. Instant, and not reversible, with a one-time code first.
- Withdraw. To a bank account, or as cash at an ATM with a PIN sent by SMS, after a person reviews it.
Wallets sit in tiers under your name: your ecosystem wallet at the top, merchant and business wallets for each business trading inside your product, and personal wallets for the people using it. Two-factor authentication applies to every wallet holder, on login and before a transfer.
A note on the word
Embedded finance, without the crypto.
Most search results for embedded wallets describe wallets that hold digital assets. This is not one of those.
A DigiWise wallet holds ordinary money in ordinary currency, one currency per wallet, running today in ZAR, GBP, EUR and AED. There is no chain, no key for your customer to lose and no asset whose value moves overnight. The balance is what was loaded, minus what was spent, recorded twice.
Questions
What people ask about embedding.
What is an embedded wallet?
A wallet that opens from inside a business's own application rather than as a separate app. In a DigiWise wallet your customers sign in where they already sign in, and the balance, the payment screen and the withdrawal all happen inside your product.
Do our customers need another app or another login?
No. The wallet opens from inside your own application, and your customers sign in where they already sign in.
Does this hold cryptocurrency?
No. A wallet holds ordinary money in one currency, set when the wallet is opened. Wallets run today in ZAR, GBP, EUR and AED.
What do we have to build?
Enough to open the wallet from your own system, ask for a payment when you need one, and store the wallet ID against your user. We scope the integration with you first and set up a test-mode connected application before anything is live.
Put it inside what you already have.
Tell us what your product does and where money enters it. We will scope the wallet layer with you.