> 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/checkoutform/cf-implementation.md).

# CF Implementation

<figure><img src="https://3756320043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBnccQ14a3b6OedaJJFT4%2Fuploads%2FjMOvjpzAnCaI9crerlbO%2FCheckoutForm_EN.png?alt=media&amp;token=ae00f877-e095-4a95-9511-0c9199162cc5" alt=""><figcaption></figcaption></figure>

CF(Checkoutform) technically consists of 2(two) basic steps as like [PWI](/en/payment-methods/paywithiyzico.md);

* [CF-Initalize](/en/payment-methods/checkoutform/cf-implementation/cf-initialize.md)
* [CF-Retrieve](/en/payment-methods/checkoutform/cf-implementation/cf-retrieve.md)

**CF-Initialize** is where we start the payment process.\
While **CF-Retrieve** step is retrieving payment result, simply.

### Implementation Steps

1. [Usage](#usage)
2. [CF - Initialize](/en/payment-methods/checkoutform/cf-implementation/cf-initialize.md)
3. Redirection
4. [CF - Retrieve](/en/payment-methods/checkoutform/cf-implementation/cf-retrieve.md)
5. [Webhook](/en/advanced/webhook.md)

### Top View

* [ ] Usage; decision making of payment form which is available in pop-up, responsive, iframe or redirection forms.
* [ ] CF-Initialize; first `POST` request of managing two-step CF transactions.
* [ ] Redirection; Following up consumers' payment, iyzico triggers correlated IPN(Instant Payment Notification) to given callbackUrl.
* [ ] CF-Retrieve; engage step to officialize transaction between Acquirer and Issuer.
* [ ] Webhook; real-time notification of relevant payment.

### UML Diagram

<figure><img src="https://3756320043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBnccQ14a3b6OedaJJFT4%2Fuploads%2FhIPjQF7sduW2cTcceP63%2Fcf.png?alt=media&amp;token=df7f8fa7-b78f-4db7-9e5a-703ab252c5ae" alt=""><figcaption></figcaption></figure>

### Usage

CF(Checkoutform) offers multiple way of forms on the browsers;&#x20;

#### Responsive

```html
<div id="iyzipay-checkout-form" class="responsive"></div>
```

#### Pop-up

```html
<div id="iyzipay-checkout-form" class="popup"></div>
```

#### iFrame

* It requires to add `&iframe=true` postfix to `paymentPageUrl` parameter that returns after CF-Initialize request.

#### Redirection

* Most common method where direct routing of `paymentPageUrl` on the application.


---

# 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/checkoutform/cf-implementation.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.