> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dollarpe.xyz/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.

export const IntegrationPathGraphic = () => {
  const cards = [{
    icon: "⚙️",
    name: "Core APIs",
    tagline: "Build your own UI on top of our full payment backend",
    colorClass: "dp-ipath__card--green",
    seqClass: "dp-ipath__card--seq-1",
    checks: ["Build the exact experience your users need", "KYC, Payin, and Payout ready to use", "Build any flow your product needs", "Works with your existing stack"],
    chooseIf: "you want to build payments exactly the way your product needs them, with full ownership."
  }, {
    icon: "🎨",
    name: "Widget Integration",
    tagline: "Drop in a payment widget styled to match your brand",
    colorClass: "dp-ipath__card--blue",
    seqClass: "dp-ipath__card--seq-2",
    checks: ["Looks like your product, not ours", "Live with a few lines of code", "We handle all UI updates", "Ship in a day, not months"],
    chooseIf: "you want to go live fast and keep your engineers focused on your core product."
  }, {
    icon: "📊",
    name: "Client Dashboard",
    tagline: "Run KYC, payouts, and reports from a dashboard, no code required",
    colorClass: "dp-ipath__card--purple",
    seqClass: "dp-ipath__card--seq-3",
    checks: ["Zero engineering required", "KYC, payouts, and reports in one place", "Start the same day", "Your ops team runs it independently"],
    chooseIf: "your ops team wants to move now and doesn't need to wait on an engineering sprint."
  }];
  return <div className="dp-ipath not-prose" role="img" aria-label="Zapyd integration paths: Core APIs, Widget Integration, Client Dashboard">
      <p className="dp-ipath__eyebrow" style={{
    textAlign: "center"
  }}>Choose your integration path</p>

      <div className="dp-ipath__grid">
        {cards.map(card => <div key={card.name} className={`dp-ipath__card ${card.seqClass} ${card.colorClass}`}>
            <div className="dp-ipath__card-top">
              <span className="dp-ipath__icon" aria-hidden="true">
                {card.icon}
              </span>
              <div>
                <div className="dp-ipath__name">{card.name}</div>
                <div className="dp-ipath__tagline">{card.tagline}</div>
              </div>
            </div>

            <ul className="dp-ipath__bullets">
              {card.checks.map(item => <li key={item} className="dp-ipath__bullet dp-ipath__bullet--check">
                  <span className="dp-ipath__bullet-icon" aria-hidden="true">✓</span>
                  {item}
                </li>)}
            </ul>

            <div className="dp-ipath__choose">
              <span className="dp-ipath__choose-label">Choose this if </span>
              {card.chooseIf}
            </div>
          </div>)}
      </div>
    </div>;
};

Zapyd handles KYC, banking rails, blockchain transfers, FX and compliance. How you connect depends on how much engineering time you have and how much control you need over the user experience.

<IntegrationPathGraphic />

| | Core APIs | Widget | Client Dashboard |
| - | - | - | - |
| Engineering effort | Backend and frontend | One server call, or none | None |
| Who uses it | Your users, in your UI | Your users, in Zapyd's branded UI | Your operators |
| UI control | Full | Logo, colors, emails | None |
| KYC | [Sharing or SDK](/guides/customers/overview) | Built in | Built in |
| Typical time to launch | 1 to 2 weeks | Days | Same day |
| Start here | [Quickstart](/guides/getting-started/quickstart) | [Widget integration](/guides/no-code/widget) | [Client Dashboard](/guides/no-code/client-dashboard) |

<AccordionGroup>
  <Accordion title="Core APIs: when does it make sense?" icon="code">
    Choose this if you have your own app and payments must feel native to it: your own screens, your own onboarding, and Zapyd connected to your product logic. You need backend engineers who can own the integration and run a webhook endpoint. In return you get every product: payin, payout, remittance and prefunded payout.
  </Accordion>

  <Accordion title="Widget: when does it make sense?" icon="window-restore">
    Choose this if you want to launch without building payment screens. Open the hosted widget from a link, or embed it in an iframe. It handles KYC, rate display and transaction confirmation, with your logo and colors. Zapyd ships widget updates, so you have nothing to maintain.
  </Accordion>

  <Accordion title="Client Dashboard: when does it make sense?" icon="gauge">
    Choose this if your team runs payments manually: review KYC, run payouts and pull reports from a browser. It's also a fast way to go live and see results before you commit to an API build. Access comes with onboarding.
  </Accordion>
</AccordionGroup>

You can combine paths. For example, use the widget for end users and the dashboard for your operations team, then add API calls later.

<Tip>Not sure which path fits? [Talk to our team](https://calendly.com/kushal-dollarpe/30min).</Tip>

## Going live

<Steps>
  <Step title="Get a partner account">
    [Book a call](https://calendly.com/kushal-dollarpe/30min). After approval, you get sandbox credentials the same day.
  </Step>

  <Step title="Build and test in sandbox">
    Build the full flow with sandbox credentials. No real money moves. See [Sandbox testing](/guides/development-and-testing/sandbox-testing).
  </Step>

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

  <Step title="Switch to production">
    Replace the sandbox host and credentials with the production ones. Run one small real transaction before full rollout.
  </Step>
</Steps>