CCQ-014 customer payment intent gate
Create payment intent after order and availability evidence.
Customer can choose COD or Upaisa/SBP partner-powered payment intent. This is not payment execution, callback, wallet balance, ledger posting, settlement, or payout.
Hard boundary
Payment intent is not payment.
FAEDA may show COD intent or Upaisa/SBP partner intent, but it must not claim a fake wallet, stored value, successful charge, partner callback, ledger truth, settlement release, or payout from this screen.
Avail
0
Pending
0
Held
0
Failed
0
Payment intent gate state
Loading availability evidence for payment intent.
Allowed payment intents
COD and licensed partner rail stay separate.
COD means cash expected later with handover/deposit proof. Upaisa/SBP means partner-powered intent only. Both can be pending, held, or failed without claiming successful payment.
Pending
COD intent
Pending
Upaisa/SBP partner intent
Held
Held for review
Failed
Failed intent
No payment intent records in this lane.
Record availability first, then return here to prepare COD or Upaisa/SBP partner-powered intent.
Open availability gateNext connected gates
After payment intent, dispatch can be planned.
CCQ-015 can plan pickup or delivery only after availability plus payment intent evidence. This screen still does not execute payment, receive callback, or dispatch riders.
Requirement
Order draft plus availability evidence must exist before payment intent.
Wallet
No fake FAEDA wallet, balance, custody, callback, settlement, or payout claim.