Skip to main content
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.
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.
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.
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.
You can combine paths. For example, use the widget for end users and the dashboard for your operations team, then add API calls later.
Not sure which path fits? Talk to our team.

​
Going live

1

Get a partner account

Book a call. After approval, you get sandbox credentials the same day.
2

Build and test in sandbox

Build the full flow with sandbox credentials. No real money moves. See Sandbox testing.
3

Pass integration review

Work through the integration checklist, then share your sandbox build with our team.
4

Switch to production

Replace the sandbox host and credentials with the production ones. Run one small real transaction before full rollout.