Future.dev Payment Terms

These Payment Terms govern all payments made and received through the Future.dev platform operated by VPV Group, LLC, doing business as Future.dev ("Future.dev"). They are incorporated into the Client Platform Terms, Developer Platform Terms, and each Order Form. Capitalized terms not defined here have the meanings in those documents.

1. Payment Processing

1.1 Processor. All payments are processed by Future.dev's third-party payment processor (currently Stripe, Inc., via Stripe Connect) ("Processor"). By transacting, Clients and Developers agree to the Processor's applicable terms (including, for Developers, the Stripe Connected Account Agreement). Client funds are held and settled by the Processor, not by Future.dev.

1.2 Authorization. Clients authorize recurring charges per their Order Form and executed ACH Authorization (or other payment authorization). Future.dev or the Processor may retry failed payments per the ACH Authorization and applicable network rules.

2. Charges to Clients

2.1 Cadence. References in these Payment Terms to an "Order Form" include a Platform-accepted engagement offer per the Service Contract Terms. Clients are charged the Plan Fee (the engagement fee stated in the Order Form) on the cadence stated in the Order Form (e.g., every two weeks), in advance of each billing period, beginning on the Engagement Start Date.

2.2 Invoice disputes. A Client must dispute a charge in writing (hi@future.dev) within five (5) business days of the charge date; after that, the charge is deemed accepted and any objection waived, except as required by law or card-network/NACHA rules.

2.3 Failed payments. If a Client payment fails: (a) Future.dev will notify the Client and retry per the authorization; (b) the Developer may suspend Services after five (5) business days of continued failure; (c) the affected Developer payout pauses per Section 3.3; and (d) amounts remain due with interest at 1.5% per month or the lawful maximum, plus collection costs.

2.4 Default; no chargebacks. A Client is in default if it fails to pay any amount when due, fails to cure a declined or expired payment method within thirty (30) days, initiates a chargeback or ACH return that reverses a proper charge, or otherwise causes a negative or past-due balance. On default, Future.dev may — in addition to all other remedies — close or limit the Client's account (with the Client remaining liable for amounts accruing on open engagements), charge any payment method on file for amounts owed, set off amounts owed against other amounts held for or owed to the Client, make reports to credit-reporting agencies, and cooperate with law enforcement, to the extent permitted by law. The Terms of Service provide a dispute process (Section 5) as the Client's remedy for payment disagreements; to the extent permitted by law, Client agrees not to ask its bank, card issuer, or payment provider to charge back or reverse any properly authorized charge, and any such chargeback is a material breach that Future.dev may dispute, appeal, and pursue through collection. Future.dev does not guarantee that any Client will pay and may reverse or offset Developer credits attributable to a defaulted or charged-back Client payment.

3. Payouts to Developers

3.1 Split. For each cleared Client payment, the Processor is configured to route (a) the Platform Fee (the percentage stated on the Developer's signed Commercial Schedule, applied to Gross Client Payments net of processing fees and refunds) to Future.dev, and (b) the remaining Developer Earnings to the Developer.

3.2 Fixed payout schedule. Developer Earnings are released on a weekly payout cycle, with each billing period's earnings released seven (7) days after that billing period closes, provided the corresponding Client funds have cleared.

3.3 Pauses and adjustments. Payouts may be paused or adjusted, in whole or the affected part, where: the corresponding Client payment failed, is disputed, or is charged back; a dispute under Section 5 is open; fraud or a Terms violation is reasonably suspected; Future.dev requires additional information (such as tax forms, government-issued identification, or other proof of identity); there are reasonable grounds for insecurity regarding performance of obligations under the Terms of Service; a legal hold, investigation, or requirement of law applies; or circumstances outside Future.dev's reasonable control prevent processing. Paused amounts are released promptly when the condition resolves in the Developer's favor.

4. Refunds; Cancellations

4.1 Initial Term. Fees for the Initial Term are non-refundable and non-cancelable per the Order Form, except as this Section provides.

4.2 Refund matrix.

StageRule

Before the Term Start Date

Client may cancel via the Platform's "Manage Billing" function; full refund of any prepaid amounts less non-refundable setup fees stated on the Order Form.

In-period, Services being delivered

No refund; capacity is reserved.

Developer's uncured material breach / non-delivery (per Service Contract §2.3)

Refund of prepaid amounts attributable to undelivered capacity in the current period, funded from Developer Earnings (and clawed back from the Developer if already paid out).

Negotiated exit

Governed by a signed Termination & Release Agreement; any refund is voluntary consideration, not an obligation.

4.3 Chargebacks. Chargebacks and ACH returns attributable to Developer non-delivery or breach are borne by the Developer (offset against payouts or invoiced). Chargebacks attributable to Client fraud or friendly fraud are the Client's responsibility, and Future.dev may recover them plus reasonable processing costs. Future.dev may submit Platform records as chargeback evidence.

5. Payment Disputes Between Client and Developer

Before initiating arbitration under the Service Contract, the parties will use the Platform's dispute process: written notice through the Platform, ten (10) business days of good-faith exchange, and Future.dev's non-binding facilitation based on Platform records. Future.dev may hold disputed amounts at the Processor until resolution. Future.dev's facilitation is not arbitration, and Future.dev has no liability for dispute outcomes.

5.1 Orders affecting Future.dev or the payment flow. If a Client or Developer seeks an order from any court or arbitrator that would direct Future.dev or the Processor to take or refrain from any action with respect to funds in the payment flow, that party will (a) give Future.dev at least five (5) business days' prior notice of the hearing on the order; (b) include in any such order, as a precondition to any obligation affecting Future.dev, that Future.dev be paid in full all amounts to which it is otherwise entitled; and (c) include a provision that Future.dev be compensated for the reasonable value of any services the order obligates it to undertake.

6. Off-Platform Payments Prohibited

All payments for Platform-sourced engagements must run through the Platform during the Restricted Period (24 months), per the non-circumvention provisions of the Client and Developer Platform Terms. Off-platform payment is a material breach by both participants; Future.dev may recover the Platform Fees it would have earned, plus enforcement costs, and may suspend or terminate accounts.

7. Taxes; Reporting

Fees are exclusive of taxes. Clients are responsible for sales, use, VAT, and similar taxes; Developers are responsible for their own income and self-employment taxes. Developers will provide a valid Form W-9; the Processor or Future.dev will issue required information returns (e.g., Form 1099-K or 1099-NEC). Future.dev may withhold where required by law.

8. Currency; No Interest; Offset; Errors

All amounts are in US dollars, and the Platform operates in US dollars. No User will receive interest or other earnings on funds at any stage of the payment flow; any interest earned on funds in transit is assigned to Future.dev or the Processor as their arrangements provide. To the extent any amount is owed to Future.dev by a Client or Developer under the Terms of Service, Future.dev may obtain reimbursement by offsetting future payouts, setting off against amounts otherwise payable, charging accounts or payment methods on file, or invoicing, to the extent permitted by law. Future.dev may correct processing errors (over- or under-payments) by adjustment to subsequent charges or payouts with notice.

9. Changes

Future.dev may update these Payment Terms at any time by in-Platform notice (posting the updated version with a new version date and a conspicuous in-Platform notice), which all Users agree is reasonable and sufficient notice without email or other delivery. Changes are effective immediately on posting, except changes that materially reduce a User's rights or increase a User's obligations take effect no earlier than seven (7) days after notice. Updated Payment Terms apply to Platform payments and in-flight engagements from their effective date (continued use is acceptance), except that no update modifies the commercial values on signed Order Forms (other than price increases for future renewal terms on at least 30 days' written notice per Service Contract Terms §2.2), executed payment authorizations, or a Developer's signed Commercial Schedule, or amounts accrued before the effective date.

Contact: VPV Group, LLC · 2506 Bransford Ave, Ste 6, Nashville, TN 37204 · hi@future.dev