Skip to main content
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.

Core APIs

Your screens and onboarding, every product. AI agents write most of it. Live in 1 day.

Widget

Zapyd’s screens with your logo and colors. One server call, or a link. Live the same day.

Client Dashboard

A browser portal for your operators. No code at all. Live the same day.

​
Compare

​
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.
  • Widget if you want to launch without building payment screens. Open it from a link, or prefill it with Widget Initialize. 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.
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.

​
From sandbox to production

Get a partner account

Email partnerships@zapyd.com. Sandbox credentials arrive the same day you’re approved.

Build in sandbox

No real money moves. Mock endpoints set any status. See Sandbox testing.

Pass the integration review

Work through the go-live checklist, then share your sandbox build with our team.

Switch to production

Swap in the production host and credentials, and run one small real order before you roll out.