---
title: How buyers pay
description: The ways buyers pay on Insy — card, BLIK and P24 through Stripe, crypto through CoinGate — the two supported currencies, and the Stripe account a paid product needs.
---

Insy handles the payment: the buyer pays on a hosted checkout, and once it succeeds Insy grants
access and sends their files. Two rails sit behind that checkout — cards, and crypto.

## Cards, BLIK and P24 (Stripe)

Card payments run through **Stripe**. Depending on what your connected Stripe account supports,
buyers can pay with:

- **Cards** — Visa, Mastercard and the rest. Always available.
- **BLIK** and **Przelewy24 (P24)** — the two methods most Polish buyers reach for.

Stripe may also offer wallet options like Link or Klarna where your account has them enabled. You
don't pick the list by hand — checkout shows whichever methods your Stripe account can process, with
card always present as the fallback.

## Crypto (CoinGate)

Crypto payments run through **CoinGate** and work differently from cards. Insy holds the funds and
pays you out **net**, which is why crypto earnings settle on their own schedule rather than landing
in your Stripe balance. See [Payouts](/payouts) for how that money reaches you.

> **A crypto payment is never anonymous**
>
> Crypto checkout always needs the buyer's **email address** (or a linked Telegram account). CoinGate
> doesn't hand a buyer's identity back after they pay, so without an email up front there'd be no way
> to know who the purchase belongs to — and Insy refuses the checkout rather than take an untraceable
> payment. Pay-what-you-want and buying several units at once are handled on the card rail.

A digital product's own checkout is card-based. Crypto is offered on community and subscription
access — see [Communities & Telegram](/communities).

## Currencies

Insy operates in two currencies only:

- **PLN** — Polish złoty
- **USD** — US dollar

No euro, pound sterling or anything else. Product prices themselves are entered in złoty (see
[Choosing a price model](/selling/pricing)).

## What you need before publishing a paid product

> **A paid product needs a fully set-up Stripe account**
>
> To publish a product with any paid option, you must connect a **Stripe account that is fully
> onboarded and able to take charges**. Connecting the account isn't enough on its own — Stripe has to
> have finished verifying you and switched charges on. Until then the product won't publish and buyers
> can't see it.

The one exception is a product where **every** option is free: that can publish with no Stripe
account. Note that a pay-what-you-want option counts as paid even if its minimum is 0 — because a
buyer *can* pay — so it still needs Stripe.

> **Connect Stripe early**
>
> Stripe's verification can take time. If you plan to sell anything paid, finish Stripe onboarding
> before launch so publishing isn't the step that holds you up.

<CardGroup cols={2}>
  <Card title="Coupons, refunds and limits" href="/selling/coupons-refunds" icon="ticket">
    Discount codes, your refund policy, and controlling how much sells and when.
  </Card>
  <Card title="Payouts" href="/payouts" icon="wallet">
    How your card and crypto earnings actually reach you.
  </Card>
</CardGroup>
