Prerequisites
Before you start integrating, make sure you have the following in place.
Partner ID
Your Partner ID is a UUID assigned to you by Coinify during the partner onboarding process. It is required for every integration - whether you're using the Trade Widget, the SDK, or the full API.
You'll use it to:
- Register end-users under your partner account in Coinify's system
- Configure the Trade Widget or SDK
- Authenticate API requests
Don't have a Partner ID yet?Reach out to Coinify to get onboarded as a partner before proceeding.
In case you still haven't applied for an account, please do so using our Trade Partner Form.
Sandbox access
Coinify provides a full sandbox environment for development and testing. The sandbox is a safe replica of the production environment where no real money moves and no real KYC has to performed.
| Description | URL |
|---|---|
| Sandbox API base URL | https://app-api.sandbox.coinify.com |
| Sandbox Trade Widget URL | https://trade-ui.sandbox.coinify.com |
You should build and verify your entire integration in the sandbox before switching to production. See Sandbox & Testing → for a full guide on working with the sandbox, including test credit cards and how to skip the KYC flow.
Understanding trader account types
Every end-user you sign up through the Coinify API is created as one of two account types. You define this at sign-up and it determines the onboarding flow they go through.
Individual - for private customers. After sign-up, they must provide personal information (address, citizenship, employment, source of funds, etc.) and complete a KYC identity verification before they can trade.
Corporate - for business clients. After sign-up, they must provide business details (company info, address, source of funds, shareholder relations, PEP status, etc.) and complete a KYB document review, which is triggered automatically via email once the mandatory information is provided.
The onboarding data requirements are defined by financial regulations that Coinify operates under. Neither account type can complete trades until their respective onboarding is done.
For the full list of mandatory endpoints for each type, see Mandatory User Information →.
What you'll need from your end-users at sign-up
Regardless of account type, you must collect the following from your end-user at the point of sign-up and pass it in the API request:
- Email address - must be collected from direct user input
- Country of residence - ISO 3166-1 alpha-2 code (e.g.
"US","DK"). Must be collected from direct user input, not inferred - State — required if the country is
"US", ISO 3166-2 format (e.g."IL")
Country and state must always come from the end-user's own input — never pre-fill or infer these values on their behalf.
Next steps
- Sandbox & Testing → — set up your test environment
- Integration Options → — choose the right integration path for your use case