Stack

Fintech KYC Onboarding Stack

KYC onboarding flows with WebApplication + Service context, FAQs, and breadcrumb navigation.

Open generator Validate in Rich Results Test

When to use this stack

KYC/verification onboarding flows for fintech apps
Account verification pages tied to financial services
Pages where FAQs clarify documentation and review timelines

What's included

Web Application
Open generator
Defines the onboarding application experience.
Service
Open generator
Captures the financial service being onboarded.
Frequently Asked Questions
Open generator
Answers questions about documents, timelines, and verification status.
Breadcrumb
Open generator
Provides navigation context for the onboarding 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

url

Recommended properties (stack union)

description

itemListElement[].item

mainEntity[].acceptedAnswer.text

mainEntity[].author.name

mainEntity[].name

offers.price

offers.priceCurrency

offers.url

serviceType

softwareVersion

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/onboarding/kyc#app",
    "name": "Identity Verification Onboarding",
    "description": "Secure KYC onboarding to verify identity and activate your account.",
    "applicationCategory": "FinanceApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/onboarding/kyc",
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/onboarding/kyc"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "Service",
    "@id": "https://www.example.com/financial-services#service",
    "name": "Digital Wallet Service",
    "serviceType": "Payments",
    "provider": { "@type": "FinancialService", "name": "Northwind Fintech" },
    "areaServed": { "@type": "AdministrativeArea", "name": "US" },
    "offers": {
      "@type": "Offer",
      "price": "0.00",
      "priceCurrency": "USD",
      "url": "https://www.example.com/financial-services"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What documents do I need?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Provide a government-issued photo ID and proof of address to complete verification."
        }
      },
      {
        "@type": "Question",
        "name": "How long does verification take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most checks complete within minutes, but some reviews may take up to 1 business day."
        }
      },
      {
        "@type": "Question",
        "name": "Will I be notified of the status?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. You will receive an email and in-app notification once verification is complete."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Onboarding", "item": "https://www.example.com/onboarding" },
      { "@type": "ListItem", "position": 3, "name": "Identity Verification", "item": "https://www.example.com/onboarding/kyc" }
    ]
  }
]

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 multiple services?

Only include services that are directly tied to the onboarding flow shown on the page.

Can I link to a third-party verification provider?

Yes. Keep the WebApplication URL on your domain, and reference the provider in your page content.

SwiftSchema

Intuitive Schema Generation at Your Fingertips