v1.1.0
Acquiring
Changed
3-D Secure, AVS and Pre-authorization endpoints — descriptions and examples
Five acquiring endpoints now show their summary and full description straight from the OpenAPI specification, together with every named request and response example. Pick a scenario from the example dropdown to see the exact payload for that case.
POST
/v1/3d/enrollment/{init}
Check 3-D Secure enrollment for a card
First step of the 3DS flow — verifies the card is enrolled in a 3-D Secure programme. No financial transaction occurs.
POST
/v1/3d/authenticate/{init}
Authenticate a cardholder via 3-D Secure (v2)
Starts the authentication; the response says whether to proceed frictionless or redirect the cardholder to the issuer's ACS.
POST
/v1/3d/result/{version}/{init}
Submit the 3-D Secure challenge result
Completes a challenged authentication with the ACS result and returns the eci, cavv and directory_transaction_id for the acquiring call.
POST
/v1/avs/{init}
Address Verification Service check
Verifies the billing address and postal code with the issuer as a zero-amount authorization — no funds blocked, no transaction created.
POST
/v1/pre-authorization/{init}
Reserve funds on a card (pre-authorization)
Blocks an amount without capturing it; settle with capture or release with reversal. Approved on response codes 00, 10 (partial) and 85.
Read them on the 3-D Secure and Acquiring reference pages.
What changed
- 3-D Secure —
POST /v1/3d/enrollment/{init},POST /v1/3d/authenticate/{init}andPOST /v1/3d/result/{version}/{init}now walk through the enrollment check, the frictionless-or-challenge decision and the challenge result, including how an init session token replaces the card and merchant fields. - Address verification —
POST /v1/avs/{init}explains the zero-amount authorization behind the check: amount and currency are still required for routing, but no funds are blocked and no transaction is created. - Pre-authorization —
POST /v1/pre-authorization/{init}documents the hold, the capture / reversal follow-ups and the approved response codes (00,10partial approval,85). - Each endpoint carries the specification's named request and response examples — pick a scenario from the dropdown above the JSON to see the exact payload.