> ## Documentation Index > Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt > Use this file to discover all available pages before exploring further. # Payments > How money moves in Soundcheck — connect and verify a bank account, onboard crew for payouts, send gig payments, and track history. Soundcheck moves money for live events: organizations pay the crew who work their shows, and members get paid into their own account. This page is the map of how it all fits together — connecting a bank account, verifying it, onboarding crew for payouts, sending gig payments, and following the trail afterward. Payment features are enabled per organization and per plan. If you don't see the pages described here, payouts aren't turned on for your organization yet — ask your account owner or [contact support](mailto:support@soundcheck.live). ## The big picture ```mermaid theme={null} flowchart LR A["Org connects & verifies
a bank account"] --> B["Crew onboard for payouts
(Stripe Connect / bank)"] B --> C["Admin sends payouts
from a gig"] C --> D["Payment history
updates for org & member"] ``` Two setups happen once, then payouts are routine: * **The organization** connects a bank account and verifies it. That verified account is the funding source for ACH (direct-deposit) payouts. * **Each member who gets paid** onboards their own payout destination — a Stripe Connect account, a bank account for direct deposit, or both. ## Connect and verify an organization bank account An owner or admin adds the organization's bank account under the org **Bank Accounts** card (in organization settings). You enter the account and routing number; Soundcheck stores them encrypted and only ever shows a masked number (for example `••••1234`) afterward. ### Micro-deposit verification A newly added account starts as **Pending** and must be verified before it can move money: Enter the account and routing numbers and save. The account shows a **Pending** status. Two small deposits (each a few cents) arrive in the bank account within a couple of business days. Come back to the Bank Accounts card, click **Validate Micro Deposit**, and enter the two amounts. While this is in progress the badge reads **Verifying micro-deposits**. When the amounts match, the status flips to **Verified** and the account can fund payouts. A **verification badge** on each bank account shows exactly where it stands — Pending, Verifying, Verified, or Removed — so there's never a guess about whether an account is ready. Only a **Verified** account can fund direct-deposit payouts. A pending or unverified account is blocked — Soundcheck will ask you to verify it or pick another account before it will send. A removed account can't be used at all. ## Onboard members for payouts Before a member can be paid, they set up where the money goes. This happens from **their own profile** — admins never edit a member's payout destination. * **Stripe Connect** — the member opens the Stripe Connect card on their profile, clicks **Connect**, and completes Stripe's hosted onboarding (identity, tax details, bank account). Their status shows as Setup Incomplete until Stripe marks the account active. Payouts to that member are held until the account is active. * **Bank account (direct deposit)** — a member can also add and verify their own bank account (same micro-deposit flow as above) to receive ACH direct deposits. See [Your profile → payouts](/features/user-guide/profile#payments) for the member-side walkthrough. ## Send gig payouts Payouts are sent from the gig that generated them. In short: build the team with performance fees, wait for members to accept, then review and send eligible payouts and pick the funding method. ACH-funded payouts from a verified bank account cost the organization nothing; card-funded payouts carry the platform fee. Reviewing payable members, choosing who to pay, selecting a funding method, and tracking settlement. ## Follow the money: payment history Every payout is recorded on both sides: * **Organization view** — the org **Payments** page aggregates every payment request members have submitted and every payout the organization has sent, with date, recipient, amount, funding method, and the originating gig. Each row links back to the gig for context. This page requires an owner/admin role and the payments feature enabled for your organization. * **Member view** — a member sees their own earnings on their [profile](/features/user-guide/profile#payments): completed payouts, anything still pending, and total earnings. Connect [QuickBooks](/integrations/quickbooks) to have these payouts and your gig income reconcile into your accounting automatically. ## Subscriptions are separate The card that pays for your Soundcheck **subscription** is handled through Stripe billing and is entirely separate from the bank accounts and Stripe Connect setup used to pay your crew. Changing one never affects the other. See [Plans & billing](/subscriptions/plans). ## Related Configure fees and send payouts from a single gig. Member payout onboarding and earnings history. Sync payouts and income to your accounting. Subscription billing — separate from member payouts.