Skip to content
Creative Payments

Amounts, currencies and VAT

A payment keeps the price you set apart from what the buyer is charged. This page explains the fields that carry money: amount, charge, provider_charge and fee.

On this page

The price and the charge

  • amount and currency are the price you set, in EUR or USD, exactly as you sent it.
  • charge is what the buyer is charged:
    • charge.amount: the total the buyer pays, VAT included. It is what the provider charges.
    • charge.currency: EUR for a payment taken on the operator’s accounts. A payment made with your own provider keys is charged as priced, in its own currency.
    • charge.fx_rate and charge.fx_date: the ECB euro reference rate a USD price was converted at, and its day. For a EUR price the rate is "1" and the day is null.
    • charge.net_amount: the price before VAT, in charge.currency. Your fee and your payout are computed on it.
    • charge.vat_amount: the VAT. charge.amount is always net_amount plus vat_amount.
A price of 49.00 USD, charged in EURJSON
{
  "amount": "49.00",
  "currency": "USD",
  "charge": {
    "amount": "43.78",
    "currency": "EUR",
    "fx_rate": "1.1193",
    "fx_date": "2026-11-05",
    "net_amount": "43.78",
    "vat_amount": "0.00"
  },
  "fee": "1.03"
}

USD prices

On the operator’s accounts a USD price is converted to EUR at the latest ECB euro reference rate when the payment is created, rounded half up to the cent, and the buyer is charged in EUR. If no recent rate is available, creating the payment fails with 503 fx_unavailable and a Retry-After: nothing was created, so retry with the same Idempotency-Key. EUR prices are never affected.

The fee

Local-currency methods

BLIK (PLN), TWINT (CHF), Swish (SEK) and Vipps (NOK) charge the buyer in their own currency while the payment stays in EUR. Once the buyer has chosen one of them, provider_charge shows what is charged; otherwise it is null.

  • provider_charge.amount and currency: what the buyer pays, charge.amount times fx_rate, rounded half up. The buyer pays no margin on top.
  • fx_rate and fx_date: the ECB rate used and its day.
  • margin_bps and fx_fee: the margin in basis points and the FX fee you bear, in charge.currency. Your fee includes fx_fee once the buyer has chosen the method, so the fee of a payment can rise at that point.
49.00 EUR paid with SwishJSON
{
  "charge": {
    "amount": "49.00",
    "currency": "EUR"
  },
  "provider_charge": {
    "amount": "561.00",
    "currency": "SEK",
    "fx_rate": "11.449",
    "fx_date": "2026-11-05",
    "margin_bps": 150,
    "fx_fee": "0.74"
  },
  "fee": "1.87"
}

VAT

A payment gets an invoice only if invoicing is switched on for your account, and then VAT is added at checkout, after the buyer has given their country and billing details and before they pay. Until the buyer confirms, charge.amount equals net_amount and vat_amount is "0.00". A payment.paid event carries the final VAT.

vat_amount stays "0.00" for a BTCPay coin payment, a buyer outside the EU, a business buyer in another EU country with a valid VAT number, a payment that gets no invoice, and a test payment.

The USD example, sold to a buyer in GermanyJSON
{
  "amount": "49.00",
  "currency": "USD",
  "charge": {
    "amount": "52.10",
    "currency": "EUR",
    "fx_rate": "1.1193",
    "fx_date": "2026-11-05",
    "net_amount": "43.78",
    "vat_amount": "8.32"
  },
  "fee": "1.03"
}

Older payments and events

Some fields were added over time: charge, then net_amount and vat_amount, then provider_charge. An event body is never changed after it is written, and a stored idempotent response is replayed as it was for up to 24 hours. Treat these fields as optional if you may read older events or replays.