topup_funding_failed: The top-up did not complete
The end user clicked Authorize on the top-up page (POST /pay/topup/{token}), and funding the budget failed for a reason other than a card decline. Funding is three steps: open the credit card budget (which places the authorization hold), open the stream to the payee (which checks the payee's signed offer when the top-up carries one), and register the stream's session key. Any error in those steps answers this code; for example, the card processor could not be reached, or the stream open was refused.
Nothing was charged. If the budget had already been opened, it is closed again. The top-up is marked failed with this code and cannot be retried.
The multi-tenant hosted tier answers the same way: the front door checks the link's token and passes the request to the account's core.
What to do
- End users: ask the service for a new link and try again later.
- Developers: create a new top-up session;
GET /owner/v1/topups/{id}showsstate: "failed"andfailureCode: "topup_funding_failed". If it keeps failing, operators check the credit card rail's configuration and logs. - See the top-up guide.
On the wire
HTTP 402. A browser gets a short HTML page naming the code; a client that sends Accept: application/json (and not text/html) gets:
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "topup_funding_failed",
"message": "the authorization did not complete; nothing was charged",
"param": null,
"doc_url": "…/developers/topup.md#topup-funding-failed",
"fix": "the authorization did not complete; nothing was charged"
}
}
A declined card answers topup_declined. See all error codes.