View as Markdown

llms.txt

The API reference isn't available right now

This instance couldn't load its API specification. The reference returns as soon as the specification is readable again.

Back to the API reference

No such model

This instance publishes no model under that name. It may have been renamed, or no operation this installation serves uses it.

Back to the API reference

This reference may be out of date

This instance couldn't reach its API specification on the last attempt, so this page shows the copy fetched before that. Anything added or changed since then is missing here, and the reference updates itself as soon as the specification is readable again. Last fetched 2026-10-22 22:57 UTC.

API reference Models

ThreeDSAuthenticationType

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

How a 3-D Secure authentication reached its outcome. Recorded on `ThreeDSAuthenticationData` so a reader can tell a frictionless approval from one the cardholder had to complete, without re-deriving it from the transaction status and the challenge flags.

Values

Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
Frictionless The issuer authenticated the cardholder from the risk data alone; no challenge was presented.
Challenge The issuer required a cardholder challenge and the flow completed it (or the challenge was attempted and the issuer reported its result).
Attempt The directory server or the scheme stood in for an issuer that could not authenticate and produced attempts proof (wire status A). Liability may still shift under scheme rules.
RequestorInitiated A merchant-initiated (3RI) authentication with no cardholder present, run against a prior authentication.

Fields

Field Type Description

This model has no documented fields.

Reconnecting to the server

Could not reconnect

This session has ended

Attempt 1

Your work on this page is still here. Retrying keeps it; reloading starts the page again.

The server no longer holds this page's state, so it has to be loaded again.