← Readback blog
Scope · June 2026

Why we don’t touch the charter payment

It’s tempting. The flight is the big number — six figures on a good charter — and we sit right at the moment of acceptance. Taking a percentage of that would look great on a deck. We don’t move the charter payment, and we don’t plan to.

Card rails on a charter are a tell

Watch how a company handles the money and you learn what it really is. Running a $40,000 charter across card rails means eating roughly 3% in fees — over a thousand dollars a flight — which nobody does on purpose. When a stack quietly routes the flight payment through cards, that’s not a feature; it’s a margin leak it’s hoping you don’t notice.

Acceptance, not settlement

Our accept page records that the client said yes — the timestamp, the terms, the signature. The operator then collects exactly how they always have: wire, ACH, their existing merchant relationship. We capture the decision; we don’t become a payments company to do it.

If we ever add payments, it’s ACH or wire — never cards for the flight.

Scope is a strategy

Aviation is a hydra: fuel, FBOs, scheduling, maintenance, customs, crew. Try to own all of it and you ship none of it well. Endlessness is the incumbent’s problem. Depth on one workflow — quote to compliant send — is ours. Saying no to the shiny adjacent thing is how a small team beats a funded one.

Readback — charter quoting with the compliance gate built in

Forward a charter request; get a compliant, formula-annotated quote — but only if the assigned crew is legal.