Payments & Refunds Policy

• ClientFlux uses licensed payment providers (e.g., Stripe Connect, GCash/Maya providers, M-Pesa, or Mobile Money) connected per country and currency.
• The licensed provider holds and moves funds. ClientFlux.ai does not hold consumer funds or operate a stored-value wallet.
• Each transaction carries a permanent ClientFlux Transaction ID plus the external provider reference, and is associated with the Business ID, Consumer ID, Booking/Request ID, currency, and amount.

We distinguish marketplace-acquired customers from merchant-acquired customers and from SaaS subscription billing. Marketplace commissions require an explicit contractual basis and are not charged automatically.

• Payment methods depend on merchant country, provider eligibility, merchant onboarding status, supported currency, and provider capabilities.
• If no supported online provider is connected, existing booking flows work and only legitimate offline arrangements are shown.
• We never claim GCash, Maya, Mobile Money, M-Pesa, or Stripe Connect is live unless verified for that merchant and country.

• Partial refunds, multiple refunds, and full refunds are supported and tracked against the original payment amount and currency — never treated as a blanket full refund.
• Out-of-order events (e.g., a refund arriving before a payment) are handled idempotently so status is not corrupted.
• Dispute creation and resolution are recorded on the transaction record and reflected in the Business Hub and Admin dashboards.
• Refund eligibility for the underlying consumer transaction is governed by the business's own terms and applicable consumer-protection law.

Commissions (including sales-partner and any marketplace fee) are calculated only from verified events and actual eligible payments — never from simulated, test-mode, or duplicate transactions. Automatic revenue splitting is not enabled unless separately approved and supported by the connected provider.

ClientFlux Circle is non-monetary. It does not issue cash, cashback, transferable monetary points, or consumer-to-consumer transfers, and verified transactions may inform Circle only through a secure event interface that keeps Circle operable without ClientFlux Pay.

• Webhook signatures are verified; provider test-mode and live-mode events are isolated and tracked.
• Provider credentials are stored as server-side secrets and never exposed to the frontend.
• Provider-controlled fields (connection/verification status, external merchant IDs) are writable only through authorized server-side operations — not by self-service merchants.
• A signed event plus a connected-account match is not sufficient to attribute a transaction; the payment object must match an authorized ClientFlux test or booking record.

Premium plans (Starter, Growth, AI Business) and any free-trial entitlements are configurable. Trials are not charged without explicit consent; on expiry, the free ClientFlux CRM is retained and premium entitlements are disabled per policy. No data is deleted on trial expiry.

For payment, refund, or dispute questions contact billing@clientflux.ai.