Skip to main content
POST
Decline a 3D Secure challenge

Authorizations

​
X-API-Key
string
header
required

User API key authentication. Create a key under Settings → API keys in the Slash dashboard (https://app.slash.com/global-settings/api-keys) and send the x-legal-entity header naming the legal entity to act on with every request. Keys scoped to a legal entity are rejected with 403 user_api_key_required.

Headers

​
x-legal-entity
string
required

The legal entity to act on. Required on every request except GET /v2/legal-entities, which lists the ids a user API key can send here: those of every legal entity its user has access to.

Pattern: ^le_[a-zA-Z0-9]+$

Path Parameters

​
challengeId
string
required

3D Secure challenge id with the three_ds_challenge_ prefix.

Response

The declined 3D Secure challenge.

A request to confirm a card purchase with 3D Secure. It must be approved or declined before expiresAt, about five minutes after it is requested; a challenge left unanswered is declined.

​
id
string
required

3D Secure challenge id with the three_ds_challenge_ prefix.

Example:

"three_ds_challenge_2rj4l7hmrrrcv"

​
cardId
string
required

The card the purchase was made with, with the c_ prefix.

Example:

"c_2rj4l7hmrrrcv"

​
status
enum<string>
required

pending until it is decided. approved and declined record the decision. expired means it was not decided in time and the purchase was declined. failed means the decision could not be reported and the purchase was declined.

Available options:
pending,
approved,
declined,
expired,
failed
​
merchant
object
required
​
amount
Money · object
required

A signed monetary amount expressed in minor units.

​
expiresAt
string<date-time>
required

The deadline to approve or decline the challenge.