Payments and payouts policy
Last updated: March 20, 2026
This policy explains how Fluencity handles contract funding, approval-based payout eligibility, country routing, payout readiness, disputes, and payment-provider limitations.
Policy status
Active and enforced.
These policies govern how Fluencity operates. They may be updated as the platform evolves. Material changes will be communicated through the platform or by email.
Section 01
Contract funding
Fluencity uses a contract-based payment flow. 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 prevented.
Section 02
Approval-based payout release
Creator payouts are not released automatically at contract creation. Payout release requires the contract to be approved or completed and the funding state to be eligible.
Queued payout releases are created first, then processed through the payout workflow. A creator must have a default payout account in ready status before release can proceed.
Section 03
Country routing and payout availability
Payout availability is country-specific and controlled by the country support matrix in the platform.
Self-serve payout onboarding is available for supported Stripe Connect countries. Unsupported or waitlisted countries cannot start payout onboarding until a supported corridor is activated.
Nigeria is currently waitlisted for payouts until a supported non-Stripe payout corridor is implemented and tested.
Section 04
Disputes and reversals
Disputes and chargeback-related events may change payment-order state, affect ledger balances, and delay or reverse creator payout availability.
Dispute handling and ledger updates are built into the platform, but operational review and provider outcomes may affect final resolution.
Section 05
Creator payout readiness
Creators are responsible for completing payout setup, selecting a supported payout country, and maintaining any required provider onboarding information.
Fluencity may block or delay payout processing when the payout account is not ready, the provider is unsupported for that country, or the contract or payment state is no longer eligible.