> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ezyshield.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Verify payees, receive outcomes, and check payment details before money moves.

ezyshield helps you decide whether the business identity, contact identity, and bank account details you hold for a payee can be trusted.

Most integrations start with a [verification](/objects/verification). You send the details you have for a payee, ezyshield runs the verification flow, and your system stores the result. Later, before a payment or after details change, you can run a [check](/objects/check) against that verified fingerprint.

<CardGroup cols={2}>
  <Card title="How ezyshield works" icon="diagram-project" href="/objects/overview">
    Organizations, verifications, checks, webhooks, and ABA checks.
  </Card>

  <Card title="Create your first verification" icon="shield-check" href="/guides/first-verification">
    Create a verification, receive completion events, and store the verification ID.
  </Card>

  <Card title="Choose a confirmation mode" icon="user-check" href="/guides/confirmation-modes">
    Decide whether the contact should complete KYC, biometric confirmation, or no contact confirmation.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/using-the-api">
    Endpoint fields, response schemas, authentication, pagination, and errors.
  </Card>
</CardGroup>

## What to build first

Build the verification path first. A useful first integration usually does four things:

<Steps>
  <Step title="Create an API key">
    Create a key in the Dashboard with the abilities this integration will need. API key abilities are chosen when the key is created; if you need different abilities later, create a new key.

    `verification:read` and `verification:write` are enough to create and retrieve verifications. Webhook subscription abilities are only needed if your app will create or manage webhook subscriptions through the API.
  </Step>

  <Step title="Confirm your organization">
    Call [Get the current organization](/api-reference/organizations/get-the-current-organization) to confirm the key works and belongs to the organization you expect.
  </Step>

  <Step title="Create a verification">
    Send business, contact, and bank account details to [Create a verification](/api-reference/verifications/create-a-verification). Store the returned verification ID in your system.
  </Step>

  <Step title="Listen for completion">
    Use [webhooks](/guides/webhooks) as the normal completion path. Polling is useful while debugging, but production integrations should react to events.
  </Step>
</Steps>