Skip to content

Main branch / INR

BA

Collections workspace

Reminder operations

Policy-controlled follow-up that stops the moment verified payment arrives.

Delivery policy

How every send is decided

  1. 01Create a schedule (e.g. 3 days before, on, and 7 days after the due date) via the API.
  2. 02Preview any bulk send first — opted-out, quiet-hour and already-paid recipients are listed, never messaged.
  3. 03Jobs fire idempotently; a payment racing the queue always wins and suppresses its reminder.
  4. 04Delivery callbacks show sent, delivered, read or failed — with retry only for retryable failures.

No durable schedules yet

The API policy engine is ready. Persistent schedule management and live messaging providers remain production gates.