> 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/tokenization/tokenization-integration/initialize-payment-with-session.md).

# Initialize Payment with Session

Based on the type of the last payment made using the obtained session information, the payment can be processed in two different ways as shown below.

* [Balance Payment](/en/payment-methods/tokenization/tokenization-integration/initialize-payment-with-session/balance-payment.md)
* [Card Payment](/en/payment-methods/tokenization/tokenization-integration/initialize-payment-with-session/card-payment.md)

<table><thead><tr><th width="186.734375">Payment Types in Response</th><th>Parameter</th><th width="256.44921875">Description</th><th>Payment Type in Requestu</th></tr></thead><tbody><tr><td>When the last payment is made with the balance, paymentType returns “FUND”.</td><td>FUND</td><td>Means Payment with Balance.</td><td>In this case, paymentType “FUND” should be sent in the next payment request.</td></tr><tr><td>When the last payment is made by Card, paymentType returns as “CARD_PAYMENT”.</td><td>NON3D</td><td>Non-3DS Payment Method</td><td>For 2D Processing, it must be sent as “NON3D”.</td></tr><tr><td>When the last payment is made by Card, paymentType returns as “CARD_PAYMENT”.</td><td>3DS</td><td>3DS Payment Method</td><td>3DS For a 3DS transaction, “3DS” must be sent. Debit cards must be sent as 3DS.</td></tr></tbody></table>


---

# 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/tokenization/tokenization-integration/initialize-payment-with-session.md?ask=<question>&goal=<user_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.