- Dakota has activated your account for Cards. This happens once, for your whole account.
- The customer has accepted the Cards terms. Each customer does this once, on a page Dakota hosts. You get the link from the API.
1. Get your account activated
There is no API for this step. Contact your Dakota representative. Dakota configures whether your account issues cards to business customers, individual customers, or both.- Sandbox: nothing is needed from you.
- Production: your company signs a cards program addendum and a marketing attestation.
unavailable. When Dakota activates it, Dakota rechecks every customer, and each one whose Cards capability changes gets a customer.capability_status.updated webhook.
2. Read the customer’s Cards capability
The customer completes Dakota’s normal onboarding first. The terms can only be accepted once their application is approved: that is when the terms link appears. In sandbox, approve the application yourself withPOST /sandbox/simulate/onboarding and type: kyb_approve: see Testing Cards.
requirements lists only what is still outstanding. Treat a requirement type you do not recognize as not satisfied.
Read the terms requirement’s key from the response rather than hard-coding it. Business customers accept the commercial terms (cards_tos), and individual customers may be asked for separate consumer terms (cards_consumer_tos).
3. Send the terms link
Send theurl to the customer by email or in your app. The customer reads and accepts the terms on Dakota’s page.
- Only the customer can accept. There is no API to accept on their behalf.
- Send the link exactly as you received it. Do not build or change it.
- Read the link right before you send it. It carries a token that expires. Dakota does not send a webhook when it reissues the link, so do not reuse a link from an earlier webhook.
- An empty
urlmeans the terms cannot be accepted online in this environment. Contact Dakota. Dakota can also record an acceptance the customer signed outside the hosted page.
4. Wait for the capability to become available
The capability moves fromaction_required to enabling, then to available. An individual customer can go straight to available. The webhook fires for every capability, so filter on capability: "cards":
403 cards-tos-not-accepted. Its resolution_url carries the same terms link.

