topup_authentication_required: The card needs 3-D Secure, which the preview does not support
The end user entered a card in the top-up page's card form (POST /pay/topup/{token}), and the card asks for bank authentication (3-D Secure). The preview does not support it: the core asks Stripe to refuse an authorization that needs it rather than leave it waiting. Nothing was charged. 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 use a card that does not ask for bank authentication.
- Developers: create a new top-up session;
GET /owner/v1/topups/{id}showsstate: "failed"andfailureCode: "topup_authentication_required". - 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_authentication_required",
"message": "this card needs bank authentication (3-D Secure), which is not supported in the preview; nothing was charged",
"param": null,
"doc_url": "…/developers/topup.md#topup-authentication-required",
"fix": "this card needs bank authentication (3-D Secure), which is not supported in the preview; nothing was charged"
}
}
Any other decline answers topup_declined. See all error codes.