Escrow process for app acquisitions
AppsVerified supports an Escrow.com workflow for eligible app and SaaS sale orders. The process gives buyers and sellers a shared transaction status, clear transfer actions, and an inspection step without replacing due diligence.
Escrow structures payment. It does not replace diligence.
Escrow can help sequence agreement, funding, transfer, inspection, and release. Buyers still need to inspect proof artifacts, confirm ownership, verify revenue, and understand platform transfer requirements before closing.
Supported escrow flow
The current workflow follows the transaction states exposed by the AppsVerified Escrow.com integration.
Order and transaction setup
After a buyer has an order for a listing, the buyer can initiate an Escrow.com transaction when escrow credentials are configured for the marketplace environment.
Both parties agree
The buyer and seller review and agree to the Escrow.com transaction terms before the transaction moves to payment.
Buyer funds escrow
The buyer funds the Escrow.com transaction. AppsVerified tracks the status so both parties can see when payment has been secured.
Seller transfers assets
Once payment is secured, the seller marks the software assets as transferred through the escrow workflow.
Buyer inspects and accepts
The buyer confirms receipt, reviews the transferred assets during the configured inspection period, and accepts or rejects the transfer through the escrow workflow.
Status stays visible
Deal pages can refresh escrow status and show available actions such as agreeing, marking transfer, confirming receipt, accepting, or rejecting.
What AppsVerified can track
- Escrow.com transaction creation for app and SaaS sale orders
- Buyer and seller party assignment using their account email addresses
- A three-day inspection period for generated app sale transactions
- Status mapping for agreement, payment, transfer, receipt, rejection, and completion
- Deal-page actions for the current buyer or seller role
Important limits
- Escrow availability depends on the marketplace environment being configured with valid Escrow.com credentials.
- Escrow status does not verify revenue, code quality, transfer eligibility, taxes, contracts, or legal ownership by itself.
- Escrow.com terms, fees, compliance review, payment methods, disputes, and release decisions are governed by Escrow.com and the transaction terms.
- Buyers and sellers should keep their own records and use professional advice for legal, tax, accounting, and transfer questions.
Frequently asked questions
Does AppsVerified hold buyer funds directly?
No. The supported workflow creates and tracks an Escrow.com transaction. Funds are handled through Escrow.com according to its terms and the transaction details.
When can a seller transfer the app or SaaS assets?
The deal workflow indicates that the seller can transfer after Escrow.com reports payment as secured for the transaction.
Does escrow guarantee a successful acquisition?
No. Escrow helps structure payment, transfer, inspection, and release steps, but buyers still need to verify the business, assets, ownership, revenue, and transfer requirements.
What happens if escrow is not configured?
The escrow API returns an escrow_not_configured response, and the transaction cannot be created through AppsVerified until valid Escrow.com credentials are configured.