Digital products
The seller sets the listing price. NexoRush deducts the applicable marketplace fee from seller earnings, based on whether the product is exclusive or non-exclusive.
Transparent by design
A marketplace built around clear terms and controlled payment release
NexoRush brings digital products and freelance services into one platform. We make money through clearly disclosed marketplace fees while giving buyers and sellers a structured record of every transaction.
Payment protection
Release follows project status
Transparent totals
Fees and estimated tax shown before pay
Structured resolution
Revisions, evidence and disputes
The business model
We earn when the marketplace creates value
Sellers provide the products and professional services. Buyers pay for access or agreed work. NexoRush provides discovery, checkout, transaction records, communication, delivery controls, reviews and support.
Freelance services
The agreed service price belongs to the seller, subject to refunds, reversals and mandatory law. The buyer pays a separate NexoRush service fee shown before checkout.
Freelance payment flow
From agreement to seller payout
Each stage creates a traceable project record, so decisions are based on the agreed scope and activity inside NexoRush.
Agree the scope
The buyer selects a service package or accepts a custom offer with a defined price, delivery time and revisions.
Pay securely
Checkout itemises the agreed price, the NexoRush fee and applicable tax before payment confirmation.
Work in one place
Requirements, messages, versions and delivery evidence stay attached to the project record.
Review delivery
The buyer can approve the work, request an included revision or open a dispute when something is materially wrong.
Release earnings
Eligible seller earnings move to payout after completion and the applicable review or dispute controls.
Payment protection, explained accurately
For freelance projects, payment is processed through Stripe Checkout and seller earnings are not released merely because an offer was accepted. Release follows the project workflow, including delivery, approval, review windows and dispute controls.
Why we do not simply call this “escrow”NexoRush is not presenting itself as a bank, trust account or independently licensed escrow provider. “Payment protection” and “controlled release” describe the product workflow more precisely. Stripe processes the payment and maintains platform and connected-account balances; the legal treatment depends on the payment setup and applicable law.
This overview explains the platform experience and is not financial or legal advice. Contractual rights are governed by the applicable NexoRush terms and mandatory law.
Buyer protection
Defined scope and price before payment, recorded requirements, delivery review, included revisions and a dispute path.
Seller protection
A paid project record, versioned delivery evidence, documented client requirements and a controlled completion process.
Refunds and disputes
Eligible full or partial refunds follow the refund process. A dispute pauses the normal project and payout flow while evidence is reviewed.
Current marketplace fees
Simple, visible and connected to checkout
These rates are loaded from the current marketplace settings. The transaction summary shown before payment or publication is authoritative for that transaction.
Exclusive digital product
Deducted from the seller's product earnings.
Non-exclusive digital product
Deducted from the seller's product earnings.
Freelance buyer fee
Added to the agreed service price and itemised separately.
VAT or other indirect tax is separate from the marketplace fee. Where enabled, Stripe Automatic Tax calculates the applicable amount from checkout information such as customer location, transaction type and tax status. The final total is shown before payment.
What the fees support
Secure checkout infrastructure
Marketplace discovery
Private project communication
Delivery and revision records
Reviews and trust signals
Support and dispute handling
Documents that govern a transaction
This page is a plain-language overview. For the full rules, read the policies accepted in the relevant flow.