> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/direct-api-integration/direct-api-integration-for-cards/handling-3ds.md). # Handling 3DS After submitting a charge, if you receive a response with "status\_code": "waiting\_for\_shopper\_action" , you may follow these steps to handle the 3DS challenge: * Include a challenge page with the challenge\_jwt and the challenge\_md. * Automatically submit this form to the challenge\_url endpoint, * The customer completes the challenge page. The payment request is then submitted for authentication.
Example 3DS challenge inside an iframe: ```javascript .... .... ``` #### Type: Redirection After submitting a charge, if you receive a response with "status\_code":"waiting\_for\_shopper\_action" and "type": "redirection", you may follow these steps to handle the 3DS challenge for redirection type: * Extract the url from the shopper\_action.redirection object. * Redirect the customer to this URL using the specified method (GET). * The customer completes the 3DS challenge on the redirected page. * After completion, the customer is redirected back to your return URL with the result. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coda.co/codapay/direct-api-integration/direct-api-integration-for-cards/handling-3ds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.