SwiftSchemaGenerate
    Schema stack

    Fintech KYC Onboarding Stack

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

    Open generatorValidate in Rich Results Test
    Included schema
    Web Application
    Service
    Frequently Asked Questions
    Breadcrumb
    Fit

    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
    Composition

    What is included

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • applicationCategory
    • areaServed.name
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • provider.name
    • url

    Recommended properties

    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.price
    • offers.priceCurrency
    • offers.url
    • serviceType
    • softwareVersion
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live 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" }
    ]
  }
]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack 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.

    Primary sources

    References