Payment configuration

Cross-tenant list of connected accounts with requirement issues or paused payouts — for support & monitoring. Read/monitoring view: the operator never edits a tenant's payment configuration, only sees where money gets stuck. The platform's own payment parameters are edited at the bottom.

2 accounts with issues · 2 payouts paused

Tenant	OrgNode	Country	Provider account	Status	disabled_reason	Detail	Payouts
Svenska Bouleförbundet	Nordvik BK	SE	acct_1P…NBK	restricted	requirements.past_due	Missing ID document · due 2026-07-20	⏸ paused
FFPJP (FR)	Boule Béziers	FR	acct_1P…BEZ	restricted	requirements.currently_due	account_tokens incomplete	⏸ paused
Norges Forbund	Bergen BK	NO	acct_1P…BER	onboarding	pending_verification	Awaiting provider	—
Svenska Bouleförbundet	Sjöstad PK	SE	acct_1P…SJO	active	—	Active · payouts OK	—

Provenance: the status is projected from the central idempotent webhook receiver (account.updated routed on provider_account_id) + the worker tick (payment_requirements_tick). Payment configuration has no webhook receiver or requirements table of its own — it reads the projected status.

State — no issues

✓

No accounts with requirement issues or paused payouts.

All connected accounts across tenants are active.

Platform payment parameters (sys)

Global payment configuration

Payment provider * Account model Club customer payments: the club is the connected-account merchant Platform fee (%)Application fee on the club's customer payments Fixed fee per transaction (öre) Payout schedule Currency (default) Statement descriptorShown on the cardholder's statement (max 22 characters) Webhook signing secret Require Stripe onboarding before club treasury is enabled Pause payouts automatically on requirements.past_due Allow Swish (SE) as a payment method Allow cards (Visa/Mastercard)

Platform parameters apply to all tenants. A tenant's own configuration (the club's connected account) is never edited from here — it lives in the tenant's own admin.