Is there anything DEV3 Odolane does not do?

Good to know

• The deposit is a real second charge. It is taken as its own payment and refunded after check-in. There is no card pre-authorisation, so a customer sees two charges.
• A card refund that keeps failing falls back to wallet credit. Refunds are retried for about an hour; after that the amount is credited to the customer's wallet instead of the card.
• Stripe refunds have no idempotency key yet. A gateway timeout after Stripe accepted a refund can be retried, so retries need buyer review before you go live with real card payments. The key is a shared-core change that is not in this release.
• The staff app's live check is at API level. With a real server it was verified through the app's own API client and models in automated tests, not by hand on a device.
• Some concurrency paths are not covered on MySQL. The lock-order tests for creating a transfer against allocating a vehicle run on SQLite, and the MySQL race section does not cover them.
• A narrow refund window exists. A normal card refund takes the newest payment first, so a captured but not yet settled duplicate payment could absorb it.
• Payments, SMS and push are simulated by default. The simulated payment gateway works out of the box, so booking and paying need no keys. Stripe, Razorpay and PayPal drivers are included but were not run against real accounts.
• The apps were not tested on physical devices. They build as debug Android packages and run on the iOS simulator.
• Use MySQL or MariaDB on a live site. The Pest tests run on SQLite, where row locks do nothing; the concurrency checks that prove the locking run on MySQL 8.
• Name: Odolane is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. Every customer, business and record in the screenshots is fictional. Install it with the demo data to try every role on your own server.