Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt

Use this file to discover all available pages before exploring further.

Real-World Example

Jane signs in from a new link and the portal sends a one-time code. She enters the code, the portal confirms it belongs to her current profile, and only then shows her account offers.

Visual Flow

How It Should Work

  • It should validate the OTP against the current consumer and requested verification type.
  • It should allow resend behavior without creating duplicate account access.
  • It should move the consumer forward only after successful verification.

How It Should Not Work

  • It should not accept expired, reused, or mismatched codes.
  • It should not verify one consumer by using another consumer OTP.
  • It should not reveal protected account details after a failed code attempt.

Developer Notes

  • OTP verification protects login and contact-change workflows.
  • Keep failure messaging helpful but avoid exposing which account details exist.
  • routes/consumer/index.php
  • app/Livewire/Consumer/VerifyOTP.php
  • app/Livewire/Consumer/Forms/VerifyOTPForm.php
  • app/Livewire/Consumer/Forms/ConsumerVerificationForm.php
Last modified on May 25, 2026