Skip to main content

VeriScute - Verify users with Scute

Verifications are useful if you want to verify a user and approve an action by an user identifier, such as an email or a phone number. With Scute, there are a few different ways to create a verification flow, depending on your system's architecture, security requirements, and user experience goals.

Verification includes 2 elements:

  • VerificationRequest
  • VerificationAttempt

VerificationRequest​

{
  "id": "uuid", // Unique identifier
  "app_id": "uuid", // Scute App id
  "app_user_id": "uuid", // User id
  "status": { "pending", "failed", "verified", "cancelled", "expired" },
  "created_at":"datetime",
  "to_user_id":"uuid", // Recipient user id
  "attemtps": [ // maxAttempts can be set at application settings
    {
        "id":"uuid", // attempt id
        "channel":{"sms","email"}, // channel
        "verified_at" : "datetime|null", // if verified
        "created_at" : "datetime", // 
        "data" : {}, // attached data (analytics)
        "metadata" : {}, // metadata
        "magic_link_id" : "uuid" // if attached

    },
    ...
  ]
}

Email verification​

See Self-serve email verification for a guide on implementing user verification with email.

OTP Verification​

OTP Verification (with Temporary user / Bypass)​

Checking status of verifications​

Webhooks​

In development