Payments and payouts policy

Fluencity's current payment flow is contract-based. Brands fund contracts through Stripe Checkout, and the platform records the corresponding payment order and ledger state.

Payment coverage is tied to the contract and organization that created it. Duplicate funded coverage for the same contract is blocked in the runtime.

Creator payouts are not released automatically at contract creation. The current runtime only allows payout release once the contract is approved or completed and the funding state is eligible.

Queued payout releases are created first, then processed by admin workflow. A creator must have a default payout account in ready status before release can proceed.

Payout availability is country-specific and controlled by the live country support matrix in the platform.

The current self-serve payout flow is implemented only for supported Stripe Connect countries. Unsupported or waitlisted countries cannot start live payout onboarding in the current release.

Nigeria currently remains waitlisted for payouts in the live platform flow until a real non-Stripe payout corridor is implemented.

Disputes and chargeback-related events may change payment-order state, affect ledger balances, and delay or reverse creator payout availability.

The current runtime includes dispute handling and ledger updates, but operational review and provider outcomes still matter for final resolution.

Creators are responsible for completing payout setup, selecting a supported payout country, and maintaining any required provider onboarding information.

Fluencity may block or fail payout processing when the payout account is not ready, the provider is unsupported for that country, or the contract/payment state is no longer eligible.