Customer journeys
Map registration, login, recovery, and account closure.
B2C customer identity
Protect customer actions beyond the login screen.
Architecture guidance for consumer applications: connect identity and recovery journeys to explicit controls for sensitive account changes, exports, and agent-assisted actions.
Purpose-built capabilities
What B2C customer identity covers.
Sensitive actions
Identify when recent verification or human approval is required.
Action boundaries
Specify the recipient, operation, amount, and expiry where relevant.
Integration validation
Measure completion and refusal paths in the application before release.
Use case / Consumer application owner
Design exact controls for a customer-account change.
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.
Inspect the flow
Stage 1
Define scope
Design exact controls for a customer-account change.
Follow B2C customer identity from identity to evidence.
Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.
- 01IdentityWho or what is acting
- 02IntentSigned purpose and limits
- 03PolicyDeterministic evaluation
- 04ApprovalA named human when required
- 05ExecutionSingle-use grant, redeemed at the resource
- 06EvidenceReceipt joined to the audit chain