Galliun does not issue on-chain refunds. Funds go directly to the API provider's wallet in each exact_split payment. Refunds are the provider's responsibility.
Refund recommendations (not refunds)
When payment succeeds but endpoint execution fails with a refund-recommended outcome, the API creates a refundRecommendations row — an operational signal for the provider, not an automatic refund.
| Status | Meaning |
|---|---|
recommended |
Provider should consider refunding the payer |
provider_notified |
Provider was notified |
provider_refunded |
Provider confirmed they refunded off-platform |
provider_declined |
Provider declined to refund |
closed |
Recommendation closed |
Providers track recommendations in the dashboard. Platform admins review them at /refund-recommendations in the admin panel.
API response
{
"error": "execution_failed_after_payment",
"message": "The endpoint failed after payment. A refund may be recommended to the provider.",
"refundRecommendationId": "...",
"refundRecommendationStatus": "recommended"
}
There is no finance worker and no Galliun-signed refund transaction.
Default refund policy
Per-endpoint refundPolicy (default | strict | custom):
Recommend refund by default:
- Network error
- Timeout
- Galliun proxy/internal error
- Upstream 502, 503, 504
Do not recommend by default:
- Billable 4xx (400, 401, 403, 404, 409, 422)
- 429 (unless configured)
- 500 (unless configured)
Strict mode: all non-2xx → refund_recommended.
Because funds went directly to the provider wallet, any refund must be sent from the provider's own wallet.
Receipts
Paid responses include refundManagedBy: "api_provider" on receipts. See Receipts.
Disputes
Users or the platform can open disputes for operational review. Dispute records do not obligate Galliun to return on-chain funds.