Order Statuses
Boostigo exposes a small, stable set of statuses. Provider-specific states are never exposed.
| Status | Meaning | Final? | Your action |
|---|---|---|---|
pending |
Order created, execution not started yet | no | wait |
processing |
Recharge is being processed | no | wait |
success |
Diamonds delivered | yes | mark fulfilled |
failed |
Permanently failed — amount refunded to your API key | yes | inform customer / retry with a new request_id |
cancelled |
Cancelled — amount refunded | yes | inform customer |
delayed |
Temporarily delayed; processing continues | no | wait — a final webhook will follow |
#Lifecycle
pending→processing→success
processing→delayed→success / failed
- A new recharge is returned as
processing(the API accepted it and debited your key). - Orders normally finish in seconds;
delayedis used when a provider is slow or a manual check is needed on Boostigo's side. - Refunds for
failed/cancelledare automatic and appear in your Transactions asrefund_credit.
#Failed orders carry an error object
"status": "failed",
"error": { "code": "RECHARGE_FAILED", "message": "Recharge could not be completed." }
The message is intentionally generic — provider details stay inside Boostigo.