What the grant allows
The wallet keeps working normally. Enablement does not lock it or make Dakota a signer on the customer’s own payments.
Before you enable a wallet
The wallet must be an EVM wallet of the customer the cards are for, with exactly one customer policy that no other wallet uses. To set one up:- Register the customer’s key with
POST /signers. - Create a signer group with that key in
member_keys, withPOST /signer-groups. - Create a policy for this wallet only with
POST /policies, withsigner_group_idset to that group. - Create the wallet with
POST /wallets, passingname,customer_id,family: "evm",signer_groups(the group from step 2), andpolicies(the policy from step 3).
customer_id cannot be enabled: the call returns 400. A card draws on its own customer’s wallet only, so creating a card on another customer’s wallet returns 404 not-found.
Enable a wallet
1. Have the customer sign the intent. The intent contains three fields, plus the optional spend option described in Choose the spend option, so you can build it straight away:signer_group_id (its members, or its governing group’s), at that group’s governance quorum: one signature by default, unless the group sets its own governance_threshold, or your team has governance enforcement on and the governing group has 3 or more members (then two). Each signature must come from a different key. Do not include a settlement destination: Dakota supplies it, and an intent that contains settlement_destination is refused with 400.
2. Submit it with POST /wallets/{wallet_id}/card_enablement:
state: "active", and you can issue cards against the wallet straight away. It can instead have state: "attaching" while Dakota finishes activating the enablement, so handle both.
3. Receive wallet.card_enablement.completed. It is sent once, when the enablement becomes active, whichever state the response had. Keep its payload as your acceptance record. It holds what the customer signed: the intent hash, the signatures, and the signing key, which is empty for a passkey endorsement. It also holds the settlement destination Dakota pinned alongside, which is not part of what the customer signed. When the intent named no spend option, spend_asset and spend_network_id are unsigned too: they hold the default Dakota recorded. GET /wallets/{wallet_id}/card_enablement returns the current state.
Choose the spend option
A wallet’s cards spend one asset on one network, the wallet’s spend option. You choose it when you enable the wallet. It is optional: a request that names none enables the wallet on the default, RD on Base.GET /cards/spend_options lists the options your account can choose, and the default:
default is null when the default is not one of your options. In that case every enablement must name an option. Use the strings exactly as the list returns them. In sandbox the networks are the testnets, such as base-sepolia and ethereum-sepolia, so read the list rather than assuming a value.
To choose one, add spend_asset and spend_network_id to the intent, and to the request’s intent, with the same values:
- Send both fields or neither. The customer signs them as sent, so a field you leave out is not signed.
- Leave a field out rather than sending an empty string or
null: either is refused with400. - The option is fixed once the wallet is enabled. To spend another asset or network, enable a different wallet. Repeating the request with the same option returns the existing enablement, and a different option is refused with
409 card-spend-option-conflict. - Only that asset on that network counts toward the wallet’s card balance. A deposit of anything else does not fund cards.
- The option appears as
spend_assetandspend_network_idon the enablement, the wallet’scardbalance, every card on the wallet, and the card and enablement events.
card-spend-option-not-allowed and card-spend-option-required, errors holds one entry per allowed option, with the option as an ASSET:network string in message, not as the pair GET /cards/spend_options returns:
message at the first colon to get spend_asset and spend_network_id.
States
When enablement is refused
Most refusals come before Dakota records anything: the400 for a malformed request or a wallet with no customer, the 404, the 422, and the 403. A 409 card-enablement-precondition or a rejected endorsement comes later, and removes an attaching enablement only if that same request created it, with the same idempotency_key and intent. A 503 can leave the wallet attaching, and so can an earlier attempt under another idempotency_key. Nothing moves an attaching enablement on by itself, and wallet.card_enablement.completed is sent only once a call activates it: if GET reports attaching, retry as Retrying a failed attempt describes. A 422 comes before a 403.
Retrying a failed attempt
Replaying the call on anactive enablement returns 200 and changes nothing, whatever the customer’s Cards capability. Otherwise, how you retry depends on what went wrong:

