Project Payments Preview Terms
Rules for using the private preview and its no-money simulator.
1. Status and scope
These Preview Terms describe the planned Project Payments pilot. They are not a live-payment offer, do not authorize VibeNest to collect buyer funds, and do not enable a project to accept real payments. Binding Project Payments terms will require a separately recorded acceptance after provider and legal review. Use of the underlying VibeNest account and hosting platform remains governed by the main VibeNest Terms of Service.
2. Roles
- VibeNest provides tools for a coding agent to work on one approved project and test payment behaviour in a no-money simulator.
- The project owner (creator) operates the project and is responsible for its product, pricing, descriptions, fulfilment, technical support, and buyer-facing legal pages.
- Paddle is the intended Merchant of Record for a future Paddle Auto mode, using a separate seller account belonging to the creator. That role is subject to Partner approval, onboarding, and Paddle’s agreements.
- The buyer, once live payments are available, purchases under the seller and Merchant-of-Record terms identified at checkout. A simulator user is not a buyer and makes no purchase.
3. Pilot access and authority
Pilot access is invite-only. A project owner may issue a time-limited, single-use grant to a supported coding agent for one project and one integration job. The grant is intended only for inspection, manifest preparation, simulator configuration, verification, and explicitly permitted deployment work. It never authorizes live catalog changes, refunds, payouts, bank-account access, or handling real buyer data.
The owner must review the agent’s proposal, code changes, migrations, prices, entitlement rules, and legal templates. AI output may be incomplete or incorrect; the project owner remains responsible for approving what is merged or deployed.
4. Simulator rules
Simulator sellers, customers, transactions, subscriptions, refunds, and revenue are synthetic. They have no monetary value, create no debt or payout right, and must not contain real card details, identity documents, bank details, or production secrets. Attempts to bypass environment isolation or represent simulator results as real sales may result in immediate pilot suspension.
5. Creator responsibilities
- Provide accurate product, price, recurrence, cancellation, and fulfilment information.
- Use only code, content, and products the creator has the right to sell.
- Publish and maintain project-specific buyer Terms, Privacy, and Refund pages before any future live launch.
- Comply with the Project Payments Acceptable Use Policy and applicable law.
- Protect access codes and revoke a session immediately if it is disclosed or no longer needed.
6. Before live payments
A successful simulator run or production-code deployment does not activate checkout. Live enablement will require Partner access, a separate approved seller account, KYC/KYB where required, provider-approved products and domains, final legal documents, and a fresh explicit action by the project owner. Production code deployed during this phase keeps Project Payments disabled.
7. Fees
The simulator is free and moves no money. The intended Paddle Auto economics are described in the draft Fee Schedule. The planned 1% VibeNest fee and its collection mechanism are not effective until confirmed in final commercial terms and accepted by the creator.
8. Suspension, changes, and availability
VibeNest may limit or revoke preview access to protect projects, investigate abuse, enforce scope, or comply with a provider request or law. Preview features may change or be withdrawn and carry no uptime or compatibility commitment. Material live terms will be versioned and presented for separate acceptance; this draft will not silently become a live authorization.
9. Relationship to other documents
The main VibeNest Terms govern the account, hosting, credits, and hardware. These Preview Terms cover only the Project Payments integration layer. A future live seller must also provide its own buyer-facing terms, and Paddle’s terms govern the Merchant-of-Record transaction. If documents address different subjects, each applies only within its stated boundary.