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

# Choose your integration

> Compare Core APIs, the widget and the Client Dashboard by effort, control and time to launch.

Zapyd runs KYC, bank rails, blockchain transfers, FX and compliance behind every path. The paths differ in who builds the screens and who uses them.

<CardGroup cols={3}>
  <Card title="Core APIs" icon="code" href="/guides/getting-started/quickstart">
    Your screens and onboarding, every product. AI agents write most of it. Live in 1 day.
  </Card>

  <Card title="Widget" icon="window-restore" href="/guides/no-code/widget">
    Zapyd's screens with your logo and colors. One server call, or a link. Live the same day.
  </Card>

  <Card title="Client Dashboard" icon="gauge" href="/guides/no-code/client-dashboard">
    A browser portal for your operators. No code at all. Live the same day.
  </Card>
</CardGroup>

## Compare

| | Core APIs | Widget | Client Dashboard |
| - | - | - | - |
| Who uses it | Your users, in your app | Your users, in Zapyd's branded UI | Your operators |
| Engineering | Backend and frontend | One server call, or none | None |
| UI control | Full | Logo, colors and emails | None |
| KYC | [KYC sharing or KYC SDK](/guides/customers/overview) | Built in | Built in |
| Products | Payin, payout, prefunded payout, cross-border | Payin and payout | Payin and payout |
| You still run | Webhooks, order logic, your UI | Webhooks and order records | Nothing |
| Time to launch | 1 day | Same day | Same day |

## Pick one

* **Core APIs** if payments must feel native to your product, and you have engineers to own the integration and a webhook endpoint. Start with the [Quickstart](/guides/getting-started/quickstart).
* **Widget** if you want to launch without building payment screens. Open it from a link, or prefill it with [Widget Initialize](/guides/no-code/widget#initialize-api). Zapyd ships the UI updates.
* **Client Dashboard** if your team runs KYC, payouts and reports by hand, or wants to see live results before an API build. Access comes with onboarding.

<Tip>
  Paths combine. A common setup is the widget for end users, the dashboard for your operations team, and API calls added later. Not sure? [Talk to our team](mailto:partnerships@zapyd.com).
</Tip>

## From sandbox to production

<Steps>
  <Step title="Get a partner account" icon="handshake">
    Email [partnerships@zapyd.com](mailto:partnerships@zapyd.com). Sandbox credentials arrive the same day you're approved.
  </Step>

  <Step title="Build in sandbox" icon="flask">
    No real money moves. Mock endpoints set any status. See [Sandbox testing](/guides/development-and-testing/sandbox-testing).
  </Step>

  <Step title="Pass the integration review" icon="clipboard-check">
    Work through the [go-live checklist](/guides/development-and-testing/go-live), then share your sandbox build with our team.
  </Step>

  <Step title="Switch to production" icon="rocket">
    Swap in the production host and credentials, and run one small real order before you roll out.
  </Step>
</Steps>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.