Refunds
Authentication and scopes
Section titled “Authentication and scopes”Required API-client scopes: refunds:read for list/get and refunds:write for create/update.
How Refunds Work
Section titled “How Refunds Work”Refund behavior depends on the DSP. Some providers use a manual support workflow; others support direct API submission and automated status updates.
- First records the refund request and submits it using the best supported workflow.
- DoorDash and Uber Direct use their supported integrations. Grubhub is submitted through the DaaS API. Other DSPs may use support email.
- DoorDash, Uber Direct, and Grubhub can return automated provider status updates. Grubhub decisions arrive by refund webhook rather than email.
- Grubhub webhook decisions include DSP delivery ID, acceptance, reason/description, and approved delivery-fee, tip, and contents-value amounts when supplied.
internal_status manages First’s internal workflow state. It is distinct from status, which represents the provider decision and can only be changed by the DSP/integration.
Provider capability summary
Section titled “Provider capability summary”- DoorDash: automatic submission and provider updates; no First approval/rejection email.
- Uber Direct: automatic submission and provider updates; no First approval/rejection email.
- Grubhub: DaaS API submission and webhook decision; no approval/rejection email.
- Other DSPs: behavior varies and may remain manual/email based.