Twill Brain

#573 Merchant status additions

2 min read

#573 — Merchant status additions

Repo: Twill-AI/twill-ai-ui State: closed | Status: done Assignee: raymondehizoba

Created: 2025-08-01 · Updated: 2025-08-18

Description

Current Issue: Users get blocked from submitting applications when validation fails, creating frustration and abandoned applications.

Solution: Allow “Submit as Lead” option when validation fails - user can always submit, table refreshes immediately, and they see their application progress as a “Lead” status.

Status Display Logic

  • Read merchant data from backend API
  • Display appropriate status based on merchant fields (not calculate/store status)
  • Show 7 status types in UI:
    • Action Required: Any merchant with status_message
    • Active: Processing volume > 0
    • Approved: Approved but 0 processing volume
    • Lead: Not frontend validated
    • In Review: Frontend validated, PayEngine not validated / Both validations passed
    • Sent to Merchant: Application sent to merchant
    • Rejected: Application rejected

UI Changes

  • Merchant Table: 8 tabs with real-time counts, add “Created Date” column
  • Dashboard: Update metrics to reflect 8 statuses
  • Status Badges: Color-coded badges for each status type
  • Submission Flow: “Submit as Lead” button when validation fails

User Experience Flow

  • User fills application → Validation fails → “Submit as Lead” option appears
  • User clicks “Submit as Lead” → Application submitted → Table refreshes → Shows “Lead” status
  • User sees immediate feedback that their application was received
  • No more blocked submissions due to validation errors

What Frontend Does NOT Do

  • Does

Notes

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets

Graph View