Sending an invoice is not the same as locking the money. A deposit invoice gets paid, the truck rolls, and then the files sit in limbo while someone argues about what “done” means. Or the opposite problem: the pilot delivers, the client stalls, and the balance becomes a collection project.
Drone payment protection is the layer that sits between those two failure modes. On supported jobs, it is an optional trust hold: the client’s funds are committed and held until the agreed work is delivered, then released. It is not a broker taking a cut of the job. It is not hardware escrow. It is not the same thing as tagging an invoice as a deposit.
This explainer covers the buyer and pilot problem the feature solves, how a hold-and-release flow differs from ordinary invoicing, what fees actually mean in this model, and how to talk about availability without overselling a rollout that can vary by account.
The problem a deposit alone does not solve
Most commercial drone work starts with money risk on both sides.
The pilot’s risk: fly first, get paid later — or never. First-time clients cancel after mobilization. AP “loses” the invoice. Scope expands verbally and the signed total does not. A signed quote with no committed funds is still a maybe with nicer stationery.
The client’s risk: pay a large deposit to someone they found online, then watch the job stall, the deliverables miss the quote, or the files never arrive in a usable form. Wire-first and Venmo-first arrangements leave them with little structure when delivery is disputed.
Ordinary invoicing and deposit flags help with when money is requested. They do not create a neutral hold until delivery matches the accepted quote. That is the gap payment protection closes on jobs where it is offered.
What payment protection is (and is not)
On Pilot Ledger, Payment Protection is documented as an optional escrow-like service. The client pays against a quote or invoice that uses the feature. Funds are held via Stripe and are not transferred to the pilot immediately. The pilot performs the work and delivers what the accepted quote specifies. Funds release when the client confirms satisfactory delivery, or automatically after a documented waiting period if no dispute is filed — or after a dispute is resolved in the pilot’s favor under the Payment Protection terms.
That is a trust workflow. It is not a marketplace brokerage. Pilot Ledger markets $0 commissions on the job amount: there is no broker cut that skims your quoted price because a middleman “found” the client. The pilot is still the service provider. The platform is facilitating hold and release, not buying the job and reselling it.
It is also not the same as:
- Deposit tracking — marking an invoice as a deposit (percent or flat) so the pay page collects only the upfront amount. Useful, and separate.
- Standard Stripe payout timing — processor settlement to your connected bank after a normal pay-now invoice.
- Hardware escrow — holding physical gear. Payment Protection is about client funds, not drones in a locker.
If you need the long form of the hold, release, dispute, and refund rules, they live in the Payment Protection Terms. This post is the product explanation for pilots and buyers who want the “why” before the legal text.
How a hold-and-release job typically flows
Think in three moves, not twenty toggles.
1. Commit. The client pays the invoice amount for a protected job. Under the published Payment Protection addendum, that payment includes a 2% Payment Protection fee charged to the client on top of the quoted project amount. Funds sit in hold. They are not sitting in the pilot’s operating account yet.
2. Deliver. The pilot flies and delivers exactly what the accepted quote lists — ortho, report, thermal packet, whatever was written. Vague “we’ll figure it out on site” scopes fight this model. The quote is the measuring stick for release and for any dispute review.
3. Release. The client confirms delivery in the client flow, or funds auto-release after 14 calendar days from delivery notification if no dispute is opened, or a dispute resolves toward the provider. The published process gives clients a window to dispute against the quote specs and gives the pilot a response window with evidence.
Payment Protection can apply to a deposit, a milestone, or a full project payment when the quote is configured that way. The hold-and-release idea is the same; only the amount held changes.
Fees without the mythology
Two fee stories get confused. Keep them separate.
Platform processing fees (Stripe). Cards and ACH still cost money to move. In Pilot Ledger’s public pricing framing, card processing is on the order of about 0.5% and ACH about 0.7% as platform processing fees — not invented “broker” percentages. Those are processor/platform rails, not a commission on finding work.
Payment Protection fee (client-side, when used). Per the Payment Protection Terms, the 2% Payment Protection fee is charged to the client, added at payment time, on top of the quoted amount. The documented pilot-facing pitch is that the pilot receives 100% of the quoted amount; the protection fee is not framed as a cut of the pilot’s price. Standard Stripe processing fees on the payout side still apply as they do elsewhere on the platform.
There is still no broker commission baked into “we introduced you, so we take 15–20% of every job.” That distinction matters when you explain the product to a GC or a facilities buyer who has been burned by marketplace take-rates.
Client accounts, delivery, and login myths
Client accounts exist on Pilot Ledger. For Payment Protection specifically, documentation ties the protected pay path and the confirm/dispute dashboard to a client account (sign-in or create when they choose protected pay).
That does not mean every file handoff requires a client login. Separately, Pilot Ledger’s delivery model has long included sharing deliverables without forcing the customer through a login wall for ordinary viewing — the point of a shareable link is that AP, the superintendent, and the owner can open the map without another password reset. Do not conflate “client account for protected payment and confirmation” with “nobody can see the ortho without an account.”
Write the quote so delivery criteria are objective. “GeoTIFF orthomosaic of Tract A at agreed GSD, PDF summary, share link within 72 hours of wheels-down” is dispute-friendly. “Make the site look good” is not.
Availability: optional on supported jobs
Payment Protection is optional. Pilots may decline it on a quote. Clients may pay without it. Neither side is required to use the service.
Rollout and visibility have varied. How-to documentation has noted that in some releases the feature is admin-gated or not the lead item on every customer pay page. Product-honest framing: optional Payment Protection on supported jobs — not a promise that every account sees the toggle on every invoice. If your workspace does not show it, check current Help / How-To guidance rather than promising a hold you cannot enable.
Use it where the trust gap is real: larger first-time deposits, multi-phase mapping, clients who will not wire ahead without a hold, pilots who will not mobilize without committed funds.
When ordinary invoicing is enough
Not every flight needs a hold. A repeat municipal client on Net 15 may only need a deposit flag and a Stripe pay link. A small inspection with a known local GC may not justify the extra confirmation step.
Use payment protection when amount, first-time relationship, or delivery complexity makes “pay now / deliver later” uncomfortable. Use standard invoicing when the relationship already carries the trust. Either way you still need a clear quote, a real pay path, and deliverables that match the paper. Protection does not fix a vague scope — it holds money against a specified one.
Soft next step
Pilot Ledger’s job-and-pay loop is quote, accept, invoice, collect, deliver. Payment Protection is one optional trust tool inside that loop — not a broker marketplace.
Evaluating plans and payment tooling? Start at Pilot Ledger pricing. Read Help / How-To for current Stripe Connect and deposit settings, and read the Payment Protection Terms before you enable the feature for a real client. Then decide job by job whether a hold until done is what the relationship needs.