Login and wallets
Your Commerce key connects your app to DYLI. It does not create wallets for your customers.
There are three parts:
- API key: lets your backend call DYLI. Keep it on your server.
- Login: tells your app who the customer is.
- Wallet: holds that customer's items and USDC, and signs actions on Base.
Customers do not need DYLI Pro or a separate DYLI sign-in. Only the developer needs Pro for a Commerce key.
Pick the setup that fits
| Your app today | What to do | Can you do it yourself? |
|---|---|---|
| You have login and Base wallets | Keep both. Connect your login and wallet to the API. | Yes |
| You have login but no wallets | Add your own Privy app, or another Base wallet provider, behind your login. | Yes |
| You are starting fresh | Use your own Privy app for login and embedded wallets. | Yes |
| You want DYLI to manage the provider | Request managed setup. DYLI creates or configures the provider app. | This needs DYLI activation |
Privy is optional. It is a service that can create a wallet inside your app when a customer signs in. Customers do not need to download a wallet extension.
Already have Base wallets?
Use them. You do not need a new Privy app or DYLI-managed login.
- Choose Keep your existing login and Use existing Base wallets at API key setup.
- Connect the example's client and server adapters, or use your own backend.
- Register each customer's wallet once. The customer signs a message. This does not make a payment.
Your backend must check the customer's login and wallet ownership. An API key alone does not prove who owns a wallet.
Have login but no wallets?
Keep your login. Create a Privy app you own and connect it to your existing login using Privy's JWT setup.
At DYLI registration, choose Keep your existing login and Add your own wallet provider. Add Privy's wallet SDK to your app and connect the client and server adapters. Register each wallet once.
Privy's JWT login currently needs their Scale plan. Check the provider requirements when choosing this path.
This takes integration work in your app, but does not need DYLI to create a Privy app for you. Keep your customer IDs the same.
Starting fresh?
Create a Privy app you own for both login and embedded wallets. Choose Use Privy for login and wallets at DYLI registration.
Follow the quickstart to add your app ID, server secret and domain to the example. You can do this without waiting for DYLI.
Prefer DYLI-managed setup?
Use Commerce setup to request managed login or managed wallets with your existing login.
DYLI needs to activate this option. Creating a Commerce key alone does not activate it. Your app still needs to connect the wallet SDK. Managed setup details.
Where do pulls and buybacks go?
Items go to the customer's DYLI Collection linked to their Base wallet and your customer ID. DYLI tracks their pulls, holdings and orders. You can show them in your app through the API.
Buybacks pay USDC to that customer's wallet. If you show a separate store credit balance, your app needs to track it.
Use one wallet per customer. The same wallet cannot be linked to two customer IDs in one Commerce app.
Who pays gas?
Gas is the small network fee for a transaction.
With DYLI-managed wallets, DYLI pays gas for pack openings, sell-backs, marketplace actions, trades, gifts, USDC withdrawals and shipping. Customers do not need to add ETH. The example handles this for them.
Customers still pay for their packs, purchases and shipping. Sponsorship covers the network fee.
With your own wallets, your developer can set up gas sponsorship, or customers can pay gas with Base ETH.
Production uses Base, chain ID 8453. A separately supplied test lab can use Base Sepolia, 84532.