Card reserved.
Funds in escrow. The custodian holds your deposit until each leg's wheels-up event. The audit chain stamps every release with a SHA-256 leaf hash you can verify against the public chain head.
Reservation summary
SAMPLE · NAME PERSONALIZED ON ISSUE
- Card serial
- OW-CARD-2026-XXXXX
- Tier
- RANGE
- Deposit held
- $235,000
- Hours guaranteed
- 25 hours
- Escrow custodian
- TBD · LOI in progress
- Posture
- DOT-compliant third-party escrow at a regulated trust. Funds released per-leg at wheels-up.
Three steps. We email at each one.
Verification, funding, and card-active confirmation arrive on separate emails so the audit chain stays legible. None of these steps require action from you; we move the card forward and stamp a leaf hash on each transition.
- 01 KYC document review.
One to three business days. Stripe Identity sends the verdict direct; we forward it on the same channel as your reservation receipt. Verdicts queue at the regulator threshold of $235k.
- 02 Escrow funding confirmation.
The custodian acknowledges the wire from Stripe ACH or your bank. The named-trust account record arrives on the same email with the trust-account suffix and the audit-chain leaf hash.
- 03 Card-active email · first-leg booking link.
Funding clears, card flips to active, and you receive the first-leg booking link. From there you book in the principal app; each leg debits from card balance at wheels-up.
Two reads. Both worth it.
Return home if you want a refresher on the rate card and the comparable-by-segment teardown. Read the field note if you want the balance-sheet argument behind the escrow posture in plain prose.
DESIGN PREVIEW · PRODUCTION CONFIRMATIONS LAND HERE WHEN ADR-0036 COUNTERSIGNS