> 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-507-servisleri.md).

# VUK 507 Servisleri

### Genel Bakış

VUK 507 servisleri, fiziksel POS cihazları üzerinden gerçekleştirilen standart satış, iade, iptal ve gün sonu işlemlerini kapsar.

Bu yapı, e-fatura süreçlerinden bağımsız olarak çalışır ve klasik POS ödeme akışını temel alır.

### Kapsam

Bu bölümde aşağıdaki işlemler ele alınmaktadır:

* Satış (Payment)
* İade (Refund)
* İptal (Void)
* İşlem Sorgulama (Query)
* İade Edilebilir Satış Bilgisi
* Kısmi Ödeme (Partial Payment)
* Gün Sonu (End of Day)

### Authentication

Tüm servis çağrılarında OAuth2 tabanlı kimlik doğrulama kullanılmaktadır.

> Authorization: Bearer {access\_token}\
> Content-Type: application/json

{% hint style="warning" %}
Not: Access token, Login İşlemleri adımında alınır ve tüm servislerde zorunludur.
{% endhint %}

### Genel Ödeme Akışı

```mermaid
sequenceDiagram
    autonumber
    participant CashRegister as Satış Uygulaması
    participant Iyzico as iyzico Terminal API
    participant GMU as GMU Cihazı
    participant Bank as Banka / Acquirer

    CashRegister->>Iyzico: POST /v2/terminal-host/gmu/payment
    Note right of CashRegister: Authorization Bearer access_token
    Iyzico->>GMU: Satış isteğini iletir
    GMU->>Bank: Ödeme provizyonu başlatılır
    Bank-->>GMU: İşlem sonucu
    GMU-->>Iyzico: Ödeme sonucu ve işlem detayları
    Iyzico-->>CashRegister: Sale response döner

    alt İşlem başarılı
        Note over CashRegister,Iyzico: paymentId, authCode, hostReference döner
    else İşlem başarısız
        Note over CashRegister,Iyzico: status failure, errorCode, errorMessage döner
    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-507-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.