Your loans renew themselves — you just tap Approve.

It doesn't. It drafts; you send. Every text sits in a queue until you tap Approve — there is no code path that sends model-written words on its own. Think of it as the world's fastest clerk who writes everything down and hands you the pad.

CASL is built into the plumbing, not bolted on. Reminders about an existing loan are largely exempt transactional messages — but every text still carries your business name, STOP is handled by machine onto a suppression list, and full send and approval logs are kept as your defence file. Sending stays disabled until the onboarding consent step is done. We give you the compliance file; your lawyer confirms your specifics.

Then you don't tap Approve — that's the whole design. A wrong draft dies in the queue; nobody ever sees it. On money, it never trusts itself over your ledger, so a wrong guess gets caught against your books, not sent to a customer. Guardrails cap sends per day and block anything outside 8 am–9 pm.

It only needs one thing: an export of open loans with due dates — the CSV your POS already spits out, even an ugly one. We map your columns once at setup. And messy books actually benefit most: Maya verifies payments against that export, so it surfaces the money taken at the counter but never applied.

There's nothing to lock. Your books stay in YOUR system — Maya reads an export; it never becomes your system of record. Cancel and you keep your POS, your texting number, your payment account, and a full export of your data: threads, logs, listings, the lot. Walking away costs you the rhythm, not your records.