One check, one answer: carry on, hold, or look closer.
Looks at the address you're paying and the account you're paying from. The payer is optional; leave it out and the answer says the payer was not checked. Preflight is a check, not a guarantee. We never sign or send for you.
Can this address receive the payment?
Can the sender afford it without getting stuck?
What did this payment look like when it landed?
Check up to ten destinations in one go.
After sending: did what landed match what we meant?
Also available Suite — One combined check before you spend. GET /v1/suite 1000 flat · not post-send
Includes Receive Card, Payer Ready, Receipt, and Batch — not Post-send.
For agents
Preflight Destination + optional payer, one answer. GET /v1/preflight · 1000 drops, one payment.
Suite Dest + optional payer/receipt/batch. GET /v1/suite · 1000 flat. Does not include post-send.
Receive Card Destination readiness. GET /v1/receive-card · 500 drops
Payer Ready Affordability vs reserves. GET /v1/payer-ready · 500 drops
Receipt Decode landed Payment — read/decode a landed payment, not a match to intent. GET /v1/receipt · 500 drops
Batch Up to 10 destinations. POST /v1/receive-card/batch · 500 drops
Post-send Confirm expected vs landed — confirm it matches what you meant. GET /v1/post-send · 500 drops · not in Suite
Post-send Carry on is confirm-match only — not destination spend-ok. Not in Suite — call separately.
XRPreflight checks; it does not move funds or promise a payment will succeed.
Your keys stay with you. We never ask for a seed, and we never sign.
Independent payment checks for XRPL — not a wallet, bank, or affiliate of Ripple.
x402 settlement Facilitator settles on-chain; XRPreflight is the resource server.
Discovery xrpl-ai.org · /.well-known/x402
Canonical API destinationpreflight.com · hub is xrpreflight.com.