Venue Payment Terms

Draft — pending attorney review. This copy is provided for transparency and is not yet in effect. A Texas-barred attorney must review and sign off before it governs any account. Items flagged [ATTORNEY REVIEW] are open questions for that review.

Operator: Blender Holdings LLC ("DJGO," "we," "us") Applies to: Venues and the operators who instruct DJ payouts through DJGO Version: 2026-06-23 (draft) · Effective date: TBD

These Venue Payment Terms supplement the Terms of Service and explain how payouts and platform fees work. They use the same money-handling posture as the rest of the platform: payments are processed by Stripe, and DJGO never holds or custodies your funds.

1. How a payout works

1. Your Entertainment Director enters the DJ lineup; gigs complete automatically when the night ends. 2. The ED submits a weekly payout batch of completed, unpaid gigs. 3. Where your venue requires it, the Owner approves the batch (approval is on by default). 4. On approval, DJGO instructs Stripe to charge the venue's connected payment source and transfer each DJ's fee to their Stripe Connected Account, deducting the DJGO platform fee.

Funds move venue source → Stripe → DJ. DJGO instructs the transfers and collects its fee; it does not receive, hold, store, or custody the money outside Stripe.

2. Funding source

Each venue connects a payment source through Stripe — typically a bank account (ACH) connected via Stripe's bank-linking, which is the default. Card funding may be available as an exception. You authorize DJGO to instruct Stripe to debit the connected source for approved payout batches plus the disclosed platform fee.

3. Platform fee

DJGO charges a platform fee per payout, shown in the app before you approve a batch:

• Bank (ACH) transfers: the greater of 1% of the payout or $10 per batch.
• Card: 5% of the payout.
• No payout, no fee.

The venue bears the platform fee. Stripe's own processing fees are separate and governed by your Stripe agreement. `[ATTORNEY REVIEW]` Confirm fee disclosure language is adequate and consistent with the Stripe platform agreement.

4. Timing and settlement

Payout batches are typically run weekly. Bank (ACH) debits take a few business days to clear; a DJ's transfer is released once the funding clears. Card-funded payouts settle on Stripe's card timeline. Because settlement depends on Stripe and the banks, exact timing is not guaranteed.

5. Authorization and idempotency

Submitting and approving a batch authorizes the corresponding Stripe instructions. Every payment operation carries an idempotency key, so a retry or a duplicate submission will not pay anyone twice.

6. Refunds, disputes, and returned debits

• Returned ACH debit / failed funding: if the venue's funding debit fails or is returned, the related DJ transfers may be held or reversed through Stripe, and the venue remains responsible for paying its DJs.
• Disputes about a gig or amount: the venue and the DJ resolve these directly; DJGO can produce the gig audit log to help. DJGO does not have unilateral authority to change an agreed amount.
• Chargebacks and reserves: handled through Stripe under your Stripe agreement.

`[ATTORNEY REVIEW]` Confirm allocation of risk for returned debits and chargebacks, and that nothing here implies DJGO advances or guarantees funds.

7. Taxes

Stripe Connect Tax Reporting issues 1099 forms to qualifying DJs. The venue is responsible for the accuracy of the gig and fee data underlying each payout and for its own business taxes.

8. What DJGO will not do

DJGO will not hold a drawable or stored balance for any venue, will not act as an escrow or wallet, and will not move money outside Stripe's regulated infrastructure. Prefunding a balance for later withdrawal is not supported. These limits are deliberate and define how the platform may be used.

9. Contact

• Payments support: support@djgo.app
• Legal notices: legal@djgo.app