Skip to main content
Cards is available in sandbox only while we finish development. Dakota enables Cards per account. The Cards endpoints are in the API reference, marked Sandbox only. Endpoints, fields, and flows can still change before release.
When a cardholder disputes a purchase, they tell you. You report it to Dakota with POST /card_dispute_reports. The call records the report and nothing more: it does not reach the card network. Dakota reviews the report and files the dispute with the network itself.
Networks set deadlines on disputes, so report them promptly. Reporting a dispute does not change the card or the transaction: it does not reverse the charge or credit the wallet. The response is the report, with state received when you named the transaction, or awaiting_transaction when you did not. It also has three fields Dakota fills in later, all null on a new report: dakota_filed_with_vendor_at (when Dakota filed the dispute), vendor_dispute_reference (the reference that filing produced), and rejection_reason (why the report was closed without a filing).
Not built yet: reading a report back, dispute webhooks, evidence upload, dispute outcomes, and credits to the wallet. Today, the create response is your only view of the report.