How Fluencity protects both sides of every partnership.

Every paid partnership on Fluencity uses approval-based payouts. Brands fund the contract up front, work happens, the brand reviews the deliverable, and the payout is only released to the creator after the brand approves the work.

Until the brand approves, funds stay locked inside the platform. Neither side has to take the other on trust alone — the workflow itself is the protection.

When a brand and a creator agree on a partnership, the brand funds the contract value through Stripe. Once funding is confirmed, the deal moves into the in-progress state and the creator can start work.

Funding gives the creator the confidence that the budget is real, and gives the brand the assurance that the payout will only release when work is approved. Stripe processing fees are separate from the platform fee.

Each contract has one or more deliverables, with the content type, platform, quantity, due date, and usage rights agreed up front. Creators submit deliverables directly inside Fluencity — files, links, and notes are attached to the contract.

Submitting a deliverable moves it into the brand's review queue. The creator can see exactly when the brand has viewed and acted on the submission.

When a deliverable is submitted, the brand has three options: approve it, request a revision, or open a dispute. Approving the deliverable marks the payout as eligible for release. Requesting a revision sends the work back to the creator with notes attached to the record.

Revisions stay inside the same deliverable so both sides have full context and history. There is no “is the brand going to ghost me?” — the status is visible at all times.

Once the brand approves the deliverable, Fluencity marks the creator payout as eligible for release. The amount eligible equals the agreed contract value minus the 5% platform fee, subject to payout-account readiness, country support, and any risk or dispute review.

Payouts are processed through the creator's connected payout account. Timing depends on the creator's bank and country corridor. Once approval is recorded, the payout becomes eligible for release and is queued for processing.

If a deliverable cannot be resolved through the revision flow, either side can open a dispute. Fluencity reviews the contract, the submitted work, and the communication record before deciding the outcome.

Refunds and dispute resolutions follow the Refund Policy. Possible outcomes include releasing payout, returning funds to the brand, or splitting the payout. Every decision is recorded inside the contract.

Stripe Connect payouts are live across 32 countries today. Creators in the broader Stripe Connect footprint can still sign up and build a profile while we activate more corridors.

Nigeria: creators can sign up, build a profile, and be discovered. Payouts stay on the waitlist until a non-Stripe payout corridor is live for Nigerian creators.

If your country isn't supported for payouts yet, your profile is still visible to brands. You'll be able to take payouts as soon as the corridor activates.

Fluencity charges a 5% platform fee on creator payouts. The fee is deducted from the approved creator compensation when the payout is released — not when the brand funds the contract.

Brand and creator accounts are free. Brand Plus and Creator Pro are optional subscriptions for advanced workflows.

Messaging on Fluencity opens after an application, invite, contract, or collaboration exists — so spam is reduced from day one. Every message, submission, and approval is linked to the contract so both sides have the same record.

If a dispute is opened, this record is the primary source for resolution. That's why we keep communication and deliverable history inside the partnership rather than in scattered DMs.