How information moves between the app, the portal and Catch-e
What the app reads from Catch-e, what it writes back, and what the portal supplies.
Catch-e holds the records. The app reads from Catch-e and writes a defined set of things back to it. The portal supplies the app with your configuration and reads driver information from Catch-e for your team. This article describes each of those flows.
What the app reads from Catch-e
The driver's personal details, employer and brand
Vehicles and leases, including the term, the deduction for each pay and how it is made up
The running-cost budget for each category
Every transaction since the lease began
Benefit statements
The status of each claim
The history of odometer readings
Each figure is displayed as Catch-e holds it. The app does not recalculate balances, budgets or deductions.
What the app writes back to Catch-e
A field the driver leaves unchanged writes nothing, and a field the driver clears never blanks the Catch-e record. Deleting the app account from Profile removes only the app login; nothing in Catch-e changes.
What the portal supplies to the app
Branding, provider details, feature settings, questions and answers, documents, links and legal documents, all set per brand; and the promotions, push notifications and odometer requests your team sends.
What the portal reads from Catch-e
Everything on the Drivers list, the driver profile and the lease detail screen is read live from Catch-e. None of it can be edited in the portal. Changes are made in Catch-e.
Related articles
Was this helpful?
More in Getting started
Brands, channels and employersStill need help? Ask the team