Booking and account changes can have lasting financial consequences. Client integrity needs server controls for ownership and repeated operations.
Evaluation approach
Viewing a booking differs from canceling or refunding it. Verify ownership, eligibility and duplicates on the server, including flows opened by notifications or deep links.
Application example
Opening a refund link is not authorization. Check the current session and booking relationship; use stronger approval when the payment destination changes.
Limits and considerations
Positive device integrity does not rule out account takeover. A different country or network during travel is not inherently suspicious.
Checks and decisions
- Verify object ownership
- Classify refunds separately
- Treat deep links as input
Account for travel conditions and provide safe support for urgent booking access.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.