topup_card_mode_absent: The credit card rail is not configured here
A top-up funds a credit card authorization-backed budget, so it needs the credit card rail. This deployment does not run it. Two places answer this code:
- Creating a top-up session (
POST /owner/v1/topups) on a deployment without the credit card mode or without the credit card configuration (Stripe TEST keys andCORE_CARD_PAYEES). Nothing is created. - The end user's Authorize click on the top-up page (
POST /pay/topup/{token}) when the credit card mode is no longer running on the deployment (for example, it was turned off after the session was created). The top-up is markedfailedwith this code, and nothing was charged.
On the multi-tenant hosted tier, live keys run Control Mode only, so a top-up created with a live key always answers this code. Use a test key.
What to do
- Operators: configure the credit card rail (Stripe TEST keys and
CORE_CARD_PAYEES) and allow the card mode, then restart. - Developers on the hosted tier: create top-ups with a test key.
- After a failed top-up, create a new top-up session.
- See the top-up guide.
On the wire
HTTP 409, error type state_error. POST /owner/v1/topups answers JSON:
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "topup_card_mode_absent",
"message": "the credit card rail is not configured on this deployment, so a top-up cannot run (fail closed)",
"param": null,
"doc_url": "…/developers/topup.md#topup-card-mode-absent",
"fix": "configure the credit card rail (Stripe TEST keys) on this deployment"
}
}
The top-up page answers a short HTML page naming the code, or the same JSON shape to a client that sends Accept: application/json (and not text/html). See all error codes.