Guide
Refunds and Disputes
No broad public developer refund initiation API was verified. Access follows entitlement/license state. Verified current refund/dispute visibility and mutation boundaries.
SoundSync
Current support table
Only these refund/dispute surfaces are documented.
| Capability | Status | Evidence or boundary |
|---|---|---|
| Developer refund initiation | Not public | No verified POST developer refund route exists |
| Developer refund visibility | Available | GET /api/developer/revenue/refunds-disputes and detail route expose owned payment issue reporting |
| Owner visibility | Available | GET /api/owner/refunds-disputes and detail route are owner/admin only |
| Partner external refund/revoke | Controlled | POST /api/partner/v1/orders/:externalOrderId/refund requires partner scope and idempotent partner API flow |
| Stripe refund/dispute processing | Webhook/service | Stripe refund and dispute events drive ledger/order/entitlement effects when provider events arrive |
| Public /docs/api/refunds | Not published | Only publish an API refund page after a verified public developer refund endpoint exists |
Financial mutation rule
Do not describe refund amount, currency, settlement effects, tax effects, entitlement effects, or partner reversals as client-authoritative. Refund side effects are provider/webhook/service-owned.