Remittance exceptions
Every non-paid GlomoPay order surfaced, so ops can act on stuck / failed / RFI-pending remittances that the standard ingest doesn't touch.
The problem it solves
The standard ingest only books status=paid orders. But orders sit in many
other states: active (pending), action_required (documents pending),
under_review, failed, expired, cancelled. Without this view, a stuck
or failed remittance is silent — the customer's money didn't move, they
don't know why, and nobody's told to look.
Categories
| Category | Actionable? | Meaning |
|---|---|---|
failed | yes | Money did NOT move; customer needs to be notified |
action_required | yes | Documents pending (RFI) — customer needs to upload |
under_review | yes | GlomoPay compliance review — Ops may need to help |
pending | no | In-flight, informational |
expired | no | Auto-expired quote — background noise |
cancelled | no | Customer or GlomoPay cancelled |
Actionable = "needs someone to do something".
What the report shows
- Total orders swept, paid count, exception count, actionable count, RFI-pending count.
- Category breakdown.
- Per-customer breakdown for those with exceptions.
- Detail list (up to 200), actionable first: order id, customer, PAN, status, category, amount, age, reason.
What tends to surface
Most non-paid orders are auto-expired quotes — informational, not
actionable. Actionable ones (failed, action_required, under_review) are
the signal.
Where to see it
- Frontend: load-on-demand card on
/glomopay(India book). - API:
GET /v1/india/remittance-exceptions.