> ## Documentation Index
> Fetch the complete documentation index at: https://andcze.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment providers

> Supported providers, channels, and payment-method configuration.

Each shop configures its own payment methods (`POST /payment-methods`). A list of providers with minimum amounts and currencies is available publicly through `GET /payment-methods/providers`.

## Supported providers

| Provider               | Adapter name (`name`)                                              |
| ---------------------- | ------------------------------------------------------------------ |
| Stripe                 | `stripe`                                                           |
| PayPal Business (REST) | `paypalRest`                                                       |
| imoje                  | `imojeTransfer`                                                    |
| ZEN                    | `zen`                                                              |
| Paymentic              | `paymentic`                                                        |
| Przelewy24             | `przelewy24`                                                       |
| CashBill               | `cashbillTransfer`                                                 |
| PayByLink              | `paybylinkTransfer`                                                |
| HotPay                 | `hotpayTransfer`, `hotpayPSC`, `hotpayDB`, `hotpayPR`, `hotpaySMS` |
| SimPay                 | `simpayOnline`                                                     |

The table lists adapters this application version can create and safely confirm. Buyer-facing channels depend on the adapter, method configuration, and services enabled in the merchant's provider agreement; do not infer them from the provider brand alone.

<Warning>
  Do not configure `paypal`, `dotpayTransfer`, `dpayTransfer`, `psc`, `icehost`, `host2play`, or `skillhost`.
  They are historical or incomplete integrations hidden by the API because they cannot
  safely verify payment and automatically fulfil an order. Dotpay was consolidated into
  Przelewy24 and is no longer offered for new configurations. `microSMS` is not currently
  implemented. Use `paypalRest` for PayPal.
</Warning>

## Choosing a provider

The public `GET /payment-methods/providers` response is the source of truth for adapters configurable in this application version. It is not a price list or a promise that a particular merchant channel will be activated.

<Warning>
  ItemShop does not publish provider rates because they change and are often negotiated per merchant. Before launch, confirm in your agreement: enabled channels and currencies, percentage and minimum fees, payout schedule, reserves/chargebacks, webhook requirements, and sandbox access. Test every method from checkout through a signed webhook to plugin delivery.
</Warning>

## Configuring a method

Each provider requires its own set of keys in the `config` field. Example for imoje:

```bash theme={null}
curl -X POST https://api.itemshop.dev/api/v2/payment-methods/<shopId> \
  -H "X-API-Key: <shop-key-with-payment-methods:manage>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "imojeTransfer",
    "displayName": "imoje",
    "shopId": "<shopId>",
    "config": {
      "MERCHANT_ID": "...",
      "SERVICE_ID": "...",
      "SERVICE_KEY": "...",
      "AUTH_TOKEN": "...",
      "SANDBOXMODE": true
    },
    "fees": { "percentage": 1.9, "minimumFee": 0.3 }
  }'
```

The required `config` keys for a given provider are returned by `GET /payment-methods/providers/{provider}/config`.

The example `fees` values are only a shop accounting configuration; they are not imoje pricing or a recommended rate.

## Fees and channels

You can set a global method fee and per-channel overrides (`channelFees`). The fee is deducted from the gross amount during payment processing. See [VAT and fees](/en/guides/vat-and-fees).