Currencies & payouts

Each group checkout runs in one currency — the currency on your signed cart. Merchants can set a preferred payout currency in Business settings to control when Plurel Pay withholds an FX fee. This preference does not change the settlement transfer currency.

Copy this page as a setup prompt for your coding assistant.

Important limitations

Read before choosing preferred payout currency

Transfer currency is always checkout currency. Settlement transfers through our payments partner Stripe are created in the session currency (the cart's currency). Preferred payout currency only tells Plurel Pay when to apply the FX fee — it does not convert the transfer into your preferred currency.
Plurel Pay's fee is on the settlement transfer, not bank payout. When checkout ≠ preferred, Plurel Pay withholds an FX fee from your gross merchant transfer in checkout currency. Converting from your payout balance to your bank account is handled separately by our payments partner Stripe when you withdraw.
Our payments partner Stripe may charge additional payout fees. Cross-border or multi-currency bank payouts can incur separate fees (for example cross-border fees on some routes). Plurel Pay's FX fee covers the settlement transfer step; check your payouts dashboard for payout-line fees.
Amounts use the smallest currency unit. All Plurel Pay amounts are integers in the smallest unit (cents for USD/EUR, whole yen for JPY). FX fee math rounds per component in that unit — not always "cents."
Sandbox skips settlement transfers. Test-mode settlements set transfer_id to none and sandbox_payout_skipped: true. FX fields still appear on group.funded when your preference would trigger a fee in live mode.

Checkout currency

Set currency on every cart you sign (lowercase ISO 4217, e.g. usd, eur). All share payments for that session use the same currency. Amounts are always integers in the smallest unit (cents for USD/EUR, whole yen for JPY). See Cart signing for canonical fields.

Cart excerpt

{
  "total": 12000,
  "currency": "eur",
  "items": [ … ]
}

One currency per group

A single Plurel Pay session cannot mix currencies. If your catalog sells in multiple countries, pass the appropriate currency when you build each cart on your server.

Payout currency modes

Mode	Behavior
Checkout currency (default)	No Plurel Pay FX fee. Settlement transfer is created in the session currency. Best when checkouts already match how you hold or withdraw funds with our payments partner Stripe.
Preferred payout currency	You pick a target currency (e.g. USD). When checkout uses a different currency, Plurel Pay withholds an FX fee from your gross merchant transfer before the settlement transfer. The transfer itself still posts in checkout currency.

Configure under Settings → Business → Payout currency. Owners and admins can change this anytime; it applies to the next funded group.

FX fee when currencies differ

If you choose a preferred payout currency and a checkout runs in another currency, Plurel Pay withholds an FX fee from your gross merchant transfer. It applies only when checkout ≠ preferred payout currency. Business settings shows the current rate before you save.

Supported preferred currencies

When using preferred mode, choose one of:

ISO codes

usd, eur, gbp, cad, aud, chf, jpy, nzd, sek, nok, dkk, sgd, hkd

Webhooks

group.funded includes FX fields when a fee would apply (live or sandbox). Use them for accounting and reconciliation. In sandbox, transfer_id is none and sandbox_payout_skipped: true is set because settlement transfers are not created in sandbox.

group.funded (with FX)

{
  "session_id": "j57…",
  "group_id": "j57…",
  "transfer_id": "tr_…",
  "total": 12000,
  "merchant_fee": …,
  "order_ref": "ORD-1042",
  "checkout_currency": "eur",
  "payout_currency_preference": "usd",
  "fx_fee_cents": …,
  "merchant_transfer_gross_cents": …,
  "merchant_transfer_cents": …,
  "fx_fee_stripe_bps": …,
  "fx_fee_plurel_bps": …
}

Read fx_fee_plurel_bps. When checkout matches your preference (or you use checkout-currency mode), those fields are omitted. See Webhooks.