Overview
Becoming an Iron partner is a structured process: an intro conversation, a commercial agreement, KYB onboarding, and a sandbox integration before you go live. Fast-moving teams can complete the full sequence in a matter of days. More complex setups — especially those requiring tailored compliance or commercial structures — typically take a few weeks.
This article walks through what to expect at each step.
The onboarding flow
1. Reach out
Start by submitting the Iron contact form or emailing [email protected]. Share a brief description of your business, your use case, and your expected timeline. The more specific you can be about volumes, geographies, and target products, the faster the partnership team can scope the conversation.
2. Intro call
Iron's partnership team will set up an intro call to learn about your business and align on what you're trying to build. Expect questions about:
Your product and the role Iron would play in it
Target geographies and currencies
Projected volumes and timeline
Existing compliance setup and any licenses you hold
Engineering capacity and preferred integration model
You'll come away with a clear view of which Iron products fit and what the next steps look like.
3. Commercial agreement
Once the use case is scoped, Iron's commercial team will share terms — pricing, SLAs, and a Master Services Agreement (or equivalent). Most agreements close within a few business days once both sides have aligned.
4. KYB onboarding
Iron runs Know Your Business (KYB) onboarding for every partner. You'll be asked to provide:
Business registration documents — incorporation certificates, registered address, structure
Beneficial ownership information — typically for owners holding 25% or more
Director and officer information — ID for principals authorized to act on behalf of the business
Source of funds — for the business's operating capital and projected transaction flows
Compliance program documentation — your AML policy and procedures (for regulated entities)
Use case description — including target customer profile and projected volumes
Note: Iron may request additional documents depending on your jurisdiction, product mix, or risk profile. Having these ready up front significantly speeds up onboarding.
5. Dashboard setup and API keys
Once KYB is approved, you get access to your partner dashboard at app.iron.xyz. From there you can:
Generate API keys for sandbox and production environments
Configure webhooks for transaction events
Invite team members and set role-based permissions
Manage customers and transactions once you're live
6. Sandbox integration
Sandbox lives at app.sandbox.iron.xyz. It mirrors production with test data and no real money movement. Use it to:
Build and test your integration against the full Iron API
Validate webhook flows
Run end-to-end test scenarios for your specific use case
Iterate without affecting real customers
Iron's integration team is available during sandbox testing — typically through a shared Slack or Telegram channel — to help debug and answer technical questions.
7. Production launch
When you're ready to go live, the Iron team will:
Review your integration against the production checklist
Enable production credentials
Set initial limits and monitoring thresholds
Establish ongoing communication for compliance and operations
Tip: Many partners do a gradual rollout in production — starting with a small cohort of internal or pilot users before opening up to broader traffic. This is the safest path and Iron's team can help structure it.
What you get during onboarding
A dedicated partnership manager — single point of contact for commercial, integration, and operational questions
Sandbox and production access — including dashboard, API keys, and webhooks
A joint Slack or Telegram channel — for fast back-and-forth during integration
Compliance and integration documentation — the full developer docs at docs.iron.xyz plus partner-specific materials
Ongoing operational support — once live, you have access to Iron's support team for transaction and integration issues
FAQs
How long does onboarding take?
How long does onboarding take?
It depends on your use case and KYB complexity. Fast-moving teams with simple use cases can go from intro call to production launch in days. Complex setups — multi-region, regulated entities, custom commercial structures — typically take a few weeks.
What documents do I need for KYB?
What documents do I need for KYB?
See the list under KYB onboarding above. Iron may request additional documents depending on your jurisdiction and risk profile.
Can I get sandbox access before signing a contract?
Can I get sandbox access before signing a contract?
Sandbox access is typically provided after commercial terms are agreed. For some partners, Iron can grant limited sandbox access earlier — discuss this with your partnership manager.
Is there a minimum volume to be considered as a partner?
Is there a minimum volume to be considered as a partner?
There's no published minimum. Iron works with partners across a wide range of sizes. Reach out and the partnership team will scope your use case.
Who do I contact during onboarding?
Who do I contact during onboarding?
Your dedicated partnership manager. For technical questions during sandbox integration, use the joint Slack or Telegram channel set up at the start of integration. For general inquiries, email [email protected].
Can I start integration before commercial terms are signed?
Can I start integration before commercial terms are signed?
You can review the developer documentation at docs.iron.xyz at any time. Live sandbox access and engineering support generally start after a signed agreement.
What happens if my business profile changes after onboarding?
What happens if my business profile changes after onboarding?
Material changes — for example, ownership changes, jurisdictional expansion, or a significant volume increase — should be flagged to your partnership manager. Iron may need to re-review certain elements of your KYB or commercial terms.