pending status and its current step must be redirect. Attempting to fetch auth session data for an action in any other state (e.g. already successful, failed, or on a different step) will return a 400 error. This endpoint is typically called by the checkout front-end to hydrate the authentication page before redirecting the user.curl --location '/intent-action-auth-session/01J3K8VXZP4MNQR6TW9BCDEFGH' \
--header 'Authorization: Bearer <token>'{
"message": "Intent action auth session retrieved successfully",
"status": "success",
"data": {
"id": "01J3K8VXZP4MNQR6TW9BCDEFGH",
"amount": 150000,
"charged_amount": 152250,
"applicable_fee": 2250,
"session_action": {
"type": "redirect",
"url": "https://3ds.provider.io/challenge?token=eyJhbGciOiJSUzI1NiJ9...",
"context": {
"is_3ds": true,
"acs_transaction_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}
},
"return_url": "https://checkout.example.com/payment/complete?ref=ord_abc123",
"return_url_type": "redirect"
}
}