> 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/urunler/fiziki-pos/terminal-api-entegrasyonu/vuk-509-servisleri.md).

# VUK 509 Servisleri

### Genel Bakış

VUK 509 servisleri, ödeme işlemlerinin mali mevzuata uyumlu veri yapıları ile yürütülmesini sağlar.

Bu modelde ödeme işlemleri gerçekleştirilirken, mali süreçlerde kullanılacak veri setleri de birlikte iletilir.

VUK 509 kapsamındaki servisler; satış, iade, iptal ve gün sonu işlemlerini kapsar.

### Servis Kapsamı

Bu bölümde aşağıdaki servisler yer almaktadır:

* Satış (Payment)
* İşlem Sorgulama 
* İade (Refund)
* İptal (Void)
* Gün Sonu (End of Day)

### Genel Akış

```mermaid
sequenceDiagram
    autonumber
    participant Client as Uygulama
    participant Iyzico as iyzico Terminal API
    participant Bank as Banka / Acquirer

    Client->>Iyzico: Login ve token alma
    Iyzico-->>Client: access_token

    Client->>Iyzico: Payment Request
    Note right of Client: Authorization Bearer access_token

    Iyzico->>Bank: Ödeme provizyonu
    Bank-->>Iyzico: İşlem sonucu

    Iyzico-->>Client: Response döner

    alt Başarılı
        Note over Client,Iyzico: paymentId, authCode, işlem detayları
    else Başarısız
        Note over Client,Iyzico: status failure, errorCode, errorMessage
    end
```


---

# 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/urunler/fiziki-pos/terminal-api-entegrasyonu/vuk-509-servisleri.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.