Stack

Identity Verification Stack

Identity verification and KYC pages with WebApplication + Service context, FAQs, and breadcrumbs.

Open generator Validate in Rich Results Test

When to use this stack

KYC onboarding portals for fintech or marketplaces
ID verification pages for secure access
Compliance verification flows with upload instructions

What's included

Web Application
Open generator
Defines the identity verification portal experience.
Service
Open generator
Describes the identity verification service and provider.
Frequently Asked Questions
Open generator
Answers document requirements, processing time, and data security questions.
Breadcrumb
Open generator
Provides navigation context for the verification page.

Required properties (stack union)

Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

applicationCategory

areaServed.name

itemListElement[].name

mainEntity[].@type=Question

mainEntity[].acceptedAnswer.text

name

operatingSystem

provider.name

serviceType

url

Recommended properties (stack union)

description

itemListElement[].item

mainEntity[].acceptedAnswer.text

mainEntity[].author.name

mainEntity[].name

offers.url

softwareVersion

url

Combined JSON-LD

Paste as a single script tag. Keep product details, offer data, shipping/returns, and FAQ answers in sync with the page.

Validate

[
  {
    "@context": "https://schema.org",
    "@type": "WebApplication",
    "@id": "https://www.example.com/verify#app",
    "name": "Identity Verification Portal",
    "description": "Verify your identity to complete account setup.",
    "applicationCategory": "SecurityApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/verify"
  },
  {
    "@context": "https://schema.org",
    "@type": "Service",
    "@id": "https://www.example.com/verify#service",
    "name": "Identity Verification Service",
    "serviceType": "IdentityVerification",
    "provider": { "@type": "Organization", "name": "Northwind Identity" },
    "areaServed": { "@type": "Country", "name": "United States" },
    "description": "Secure identity checks with document and selfie verification."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What documents are accepted?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We accept government-issued IDs such as passports and driver licenses."
        }
      },
      {
        "@type": "Question",
        "name": "How long does verification take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most verifications complete within a few minutes, but some may take up to 24 hours."
        }
      },
      {
        "@type": "Question",
        "name": "Is my data secure?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Data is encrypted in transit and stored according to compliance standards."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Verify", "item": "https://www.example.com/verify" }
    ]
  }
]

Implementation steps

Start from your live product detail page content; ensure titles, prices, and availability match the page.
Embed one JSON-LD script in the head or just before the closing body tag using the combined example as a template.
Fill shipping details for each region you serve and keep them aligned with on-page shipping tables.
Attach your canonical MerchantReturnPolicy URL and keep the policy text in sync with Merchant Center.
Add 3–6 FAQs that address purchase blockers (shipping, returns, compatibility) and keep answers consistent with visible content.
Validate in the Rich Results Test and revalidate after price/availability/policy changes.

Common errors and fixes

Missing currency or availability: ensure `offers.priceCurrency` and `offers.availability` use ISO currency codes and schema URLs.
ShippingDetails missing destination or transit time: include `shippingDestination.addressCountry` and `deliveryTime.transitTime` with units.
MerchantReturnPolicy not linked: reference it from the Offer via `hasMerchantReturnPolicy` and provide a stable policy URL.
FAQ answers don't match the page: keep FAQ content identical to visible answers to avoid review or manual actions.

FAQs

Should I include selfie requirements?

If selfie capture is required, mention it in the FAQ answers and portal instructions.

How do I show supported countries?

List supported countries in the Service description or FAQ answers and keep them aligned with the UI.

SwiftSchema

Intuitive Schema Generation at Your Fingertips