# Payment types


The `payment_type` parameter is sent when creating a payment and returned in API responses, callbacks, and status requests. The value indicates the **channel** or **operation type** in the 1Payment system.

Below are allowed literals used in integration (per the product reference). **Do not translate** machine codes in requests and responses — send them as in the table.

## `payment_type` values

| Value | Description |
| --- | --- |
| `card` | Bank card. |
| `refund` | Payment refund. |
| `sbp` | Fast Payment System (SBP). |
| `link` | Link-based payment acceptance. |
| `erip` | Unified Settlement and Information Space (ERIP). |
| `sberpay` | SberPay. |
| `p2p` | P2P payment. |

## Payment acceptance in this documentation

Payment initiation is documented for **`card`**, **`sbp`**, **`link`**, **`erip`**, and **`sberpay`** — see the corresponding groups in the sidebar ("Card payments", "Link payments", etc.).

When creating a payment, send `payment_type` enabled on your project.

## `refund` and `p2p`

**`refund`** is a **refund** operation type; it appears in responses and notifications for refunds, not in primary payment. See "Payment refunds" for [cards](./card/refund.md), [SBP](./sbp/refund.md), [link](./link/refund.md), [ERIP](./erip/refund.md), and [SberPay](./sberpay/refund.md).

**`p2p`** is a P2P payment in the system reference. P2P acceptance methods are **not** documented in the current API portal; if the channel is enabled, confirm the current contract with your 1Payment manager.

## Related sections

- [API request format](./init-request.md)
- [Transaction statuses](./transaction-statuses.md)