> For the complete documentation index, see [llms.txt](https://docs.iyzico.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iyzico.com/en/payment-methods/api/3ds.md).
# 3DS
With iyzico robust and reliable 3DS infrastructure, payment transactions can handle with confidence, focusing on growing your business rather than worrying about payment complexities.
This powerful feature allows businesses to seamlessly handle secure online payments while providing a smooth user experience.
The documentation covers the entire process of integrating and utilizing the iyzico handled 3DS operations. It includes detailed explanations of the flow, step-by-step instructions, and code examples in various programming languages to assist developers in implementing this feature effectively.
### Advantages
### 3DS Payment Flow
The 3DS payment process involves selecting a credit card, entering card details, opting for 3D Secure payment, continuing to the next step, entering OTP received via SMS, and finalizing the transaction.
### Which Products Can It be Used with?
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.iyzico.com/en/payment-methods/api/3ds.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
