OTP Challenges

OTP Challenges logs the one-time-password authorisations issued for sensitive savings actions - large withdrawals, transfers or profile changes - where a code is sent to the member to confirm the instruction. Each mfi.savings.otp.challenge records the action, status and verification outcome for audit.

Workflow

Open Savings > Transactions > OTP Challenges.
Locate the challenge by member, action or date.
Review whether the OTP was verified, expired or failed.
Use it to investigate a disputed or stalled transaction.
Confirm the linked transaction proceeded only on a verified OTP.

Fields reference

Every field on this screen, drawn from the live data model.

Field	Type	Required	Description
OTP Hash `otp_hash`	Text	—	SHA-256 of issued code. Plaintext is never persisted.
Transaction Type `txn_type`	Choice: Deposit, Withdrawal, Transfer	Yes	Transaction Type
Member `member_id`	Link → mfi.member	Yes	Member
Amount `amount`	Money	Yes	Amount
Currency `currency_id`	Link → res.currency	Yes	Currency
State `state`	Choice: Pending, Verified, Failed, Expired	Yes	State
Company `company_id`	Link → res.company	Yes	Company
Account `account_id`	Link → mfi.savings.account	—	Account
Sent At `sent_at`	Date & time	—	Sent At
Verified At `verified_at`	Date & time	—	Verified At
Expires At `expires_at`	Date & time	—	Expires At
Attempts `attempts`	Number	—	Attempts
IP Address `ip_address`	Text	—	IP Address
Recipient Phone `recipient_phone`	Text	—	Recipient Phone

Status lifecycle

Records on this screen move through these statuses:

Pending → Verified → Failed → Expired

Notes & rules

Records on mfi.savings.otp.challenge for step-up authentication.
Tracks issued, verified, expired and failed states.
Provides an audit trail for OTP-gated savings actions.

Technical model: mfi.savings.otp.challenge · Record: Savings OTP Challenge