Discuss your project Internal tool
An Android application for the manager: collect supporting documents, calculate amounts owed to drivers and prepare settlements with human approval.
Internal project
Collect supporting documents for the driver and payment period.
Extract document text to prepare the entries.
Check transactions and the elements of the amount due.
Prepare the transfer; the account holder confirms it with the bank.
Understand the implementation
Forever Pay addresses a concrete internal need: preparing driver settlements while preserving the link between an amount, its period and its supporting documents. The Android application supports the manager from collection to recording the settlement.
Drivers can have different settlement periods. Revenue, tips, cash collected, advances and charging costs also play different roles in the calculation. The amount due must reflect those differences.
The project groups entries around the relevant driver and period. The manager can return to the components of a calculation before confirming it, instead of keeping only a final number that is difficult to explain.
What to look for This static reconstruction illustrates payment preparation. Amounts are fictional; no button in the image initiates a payment.
Reconstruction of the Forever Pay interface based on the project report. The driver, amounts and Telegram connection are entirely fictional.
The interface shown is in French.Enlarge the previewDocuments arrive through manual input, screenshots, PDF files or Telegram. Text recognition prepares information for review. The manager then approves or rejects the proposed entry.
A pending document blocks settlement for the driver concerned. Duplicate checks and explicit adjustments support the process: a document received twice or a correction should not silently become an extra payment.
Once the record is checked, Forever Pay prepares the amount and supports the transition to KBC Mobile or a SEPA export. The account holder confirms the payment with their bank.
The history retains settlements and periods. A correction is made through an explicit adjustment or cancellation. This continuity between document, calculation and settlement is the core of the project, beyond the payment screen itself.
React and TypeScript form the interface; Capacitor makes it available in the Android application. A Node server and SQLite organise entries and their history.
Telegram supports collection and Tesseract extracts text from documents. These integrations feed a review step; they cannot independently initiate a bank transfer.
The manager adds an entry, screenshot or PDF. Drivers can also submit documents through a private Telegram group linked to their profile.
Text recognition prepares an entry for review. The manager approves or rejects the information; a pending document blocks settlement for the driver concerned.
The sharing rules account for revenue, tips, charging costs, cash, advances and expenses. Settlement periods are set individually for each driver.
The application prepares the amount, can open KBC Mobile and can generate a SEPA file. The account holder confirms the transfer in their banking application.
Settlement history and exports make amounts traceable by driver and period. Corrections use explicit adjustments or cancellations.
The supporting document is linked to a driver and their settlement period.
The manager checks the data and adjustments, then reviews the calculated amount.
The payment is confirmed in the bank and the settlement is recorded in the history.
Forever Pay is used as an internal management tool. It is separate from Mesio, which helps drivers handle ride requests on WhatsApp. This presentation provides no access to driver records or supporting documents.
This page describes document collection, calculations, approval and settlement preparation. A direct Uber connection, notifications when the application is fully closed and support for multiple administrators remain planned developments.