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

# Quick Start

> Make your first successful Ingo Payments API call — credentials, authentication, and your first verify and process request.

## Start building in 4 steps

<AccordionGroup>
  <Accordion title="Step 1 — Get your credentials">
    Contact your Ingo integration manager to receive your HMAC username,
    HMAC secret, and participant identifier. All Ingo products use
    HMAC-SHA512 request signing — the same authentication standard
    across every API. See [Authentication](/docs/hub/authentication)
    for signature construction details.
  </Accordion>

  <Accordion title="Step 2 — Tokenize the account">
    Call `POST /gateway/verify` (IngoPay API) or launch the iFrame SDK
    (Embedded Account Capture) to validate and tokenize the recipient's
    payment account. Store the returned `customer_account_token` — you'll
    use it on every future process request for that account.
  </Accordion>

  <Accordion title="Step 3 — Process the payment">
    Call `POST /gateway/process` with the `customer_account_token` and
    your disbursement amount. Ingo routes the payment across the
    appropriate rail — card, ACH, check, PayPal, or Venmo — based on
    the `account_type` you tokenized.
  </Accordion>

  <Accordion title="Step 4 — Handle webhooks">
    Subscribe your endpoint to receive real-time event callbacks for
    payment status, OFAC screening updates, tokenization results, and
    more. Configure retry logic and authentication in your Ingo
    integration settings. See [Webhooks](/docs/ingopay/webhooks/overview)
    for the full event reference.
  </Accordion>
</AccordionGroup>

***

## Choose your starting point

Not sure which product to start with? Use this guide:

<CardGroup cols={2}>
  <Card title="I want direct API control" icon="bolt" href="/docs/ingopay/overview">
    Start with **IngoPay API** — call verify, then process. Full
    control over every disbursement request.
  </Card>

  <Card title="I want a drop-in UI" icon="window" href="/docs/iframe/overview">
    Start with **Embedded Account Capture** — drop in the iFrame SDK
    and let Ingo handle PCI-compliant account tokenization.
  </Card>

  <Card title="I want Ingo to manage recipient engagement" icon="bell" href="/docs/notify-classic/overview">
    Start with **Notify — Classic** — stage a disbursement and let
    Ingo handle authentication, verification, and OFAC screening.
  </Card>

  <Card title="I need multi-party approval flows" icon="users" href="/docs/notify-managed/overview">
    Start with **Notify — Managed Parties** — full party orchestration
    with role delegation and engagement lifecycle management.
  </Card>
</CardGroup>

***

## What you'll need

<Info>
  Before you begin, contact your Ingo integration manager to receive:

  * **HMAC username** — identifies your integration in the `Authorization` header
  * **HMAC secret** — used locally to sign requests, never transmitted
  * **Participant identifier** — identifies your account within API requests
  * **Sandbox credentials** — for testing before go-live

  All credentials are provisioned at onboarding. See
  [Authentication](/docs/hub/authentication) for the complete
  signature construction guide.
</Info>