privy (Kibble provisions it) or byo (you bring your own). Both types accept only USDC on Base.
Wallet types
privy — recommended
Kibble provisions an embedded wallet tied to your merchant email. No crypto wallet app required. The same address is reused every time you create a charge or invoice with the same email.
byo — bring your own
You provide an existing USDC wallet address on Base. Must be a valid EVM address starting with
0x. Use this if you already manage your own wallet (e.g. Coinbase Wallet, MetaMask, a smart contract treasury).Privy wallets
When you chooseprivy, Kibble looks up your email in Privy’s system:
- If you already have a Privy account with a wallet, Kibble reuses that wallet address.
- If you have a Privy account but no wallet yet, Kibble creates one for you.
- If you have no Privy account, Kibble creates both the account and the wallet.
BYO wallets
When you choosebyo, you provide your own USDC wallet address on Base. The address must:
- Start with
0x - Be a valid EVM address (checksummed or lowercase)
- Be an address you control on the Base network (chain ID
8453)
Accepted token
Regardless of wallet type, Kibble only accepts USDC on Base.| Property | Value |
|---|---|
| Token | USDC |
| Network | Base |
| Chain ID | 8453 |
| Contract address | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
Which type should you choose?
| privy | byo | |
|---|---|---|
| Requires a crypto wallet app | No | Yes |
| Requires a seed phrase | No | Yes |
| Address reused across charges | Yes (same email) | Depends on your wallet |
| Works for a team / treasury | No (email-scoped) | Yes |
| Good for quick setup | Yes | No |
| Good for on-chain accounting | No | Yes |
privy if you are setting up quickly and do not already have a crypto wallet. Choose byo if you manage a treasury wallet, want funds going directly into a multisig, or need on-chain accounting across multiple tools.