Find the right NadaPay guides and endpoints for your integration path.

⏱️

Time to integrate: Most teams can make a first successful API call in under 10 minutes and complete a basic sandbox integration in about 1 hour after onboarding approval and API access are ready.

NadaPay provides APIs for organization management, verification status, beneficiary management, account funding, quotes, and transaction execution. Use this page to choose the fastest path based on where you are in the integration lifecycle.

What NadaPay is

NadaPay is a financial API platform for onboarding organizations, managing accounts and balances, validating recipients, funding wallets or accounts, pricing transactions, and executing money movement flows.

It is designed for backend engineers, solutions architects, platform teams, and operations teams building or operating regulated payment, payout, treasury, and partner workflows.

Sandbox signup

Use sandbox first to validate authentication, account retrieval, beneficiary setup, quote generation, and transaction execution before you move to production.

⚠️

Needs confirmation: Add the official sandbox signup URL or onboarding entry link here so new developers can request access without contacting support manually.

What you can do with the API

Use NadaPay to:

• retrieve organization accounts and balances
• track verification status for KYC or KYB
• create and manage beneficiaries
• validate payout destinations
• generate quotes before execution
• execute transactions from funded accounts
• retrieve deposit instructions and transaction limits

Core integration flow

Follow this sequence for the fastest path to a working integration:

1. Authenticate with x-api-key.
2. Retrieve your organization accounts.
3. Check verification status.
4. Create a beneficiary.
5. Add a beneficiary account or resolve bank details.
6. Generate a quote.
7. Execute the transaction.

This flow is the best starting point for both first-time implementers and enterprise teams validating production readiness.

Recommended path by team type

Small teams

Start with the minimum working flow:

• accounts
• verification
• beneficiaries
• quote
• execute transaction

Use sandbox first. Add webhook handling and production controls after the end-to-end request flow is working.

Enterprise teams

Start with architecture and operational planning before scaling traffic.

Focus on:

• secure API key storage
• static outbound IP planning
• environment separation
• centralized logging and monitoring
• support and escalation ownership

Then validate the same core API sequence in sandbox before production rollout.

Platform and partner teams

Review child organization support early if you manage multiple business entities under one partner account.

Start with:

• organization and child organization endpoints
• verification status checks
• beneficiary and transaction flows per managed business
• markup or treasury configuration only if your operating model requires it

API groups

Common workflows

Check organization readiness

Use these endpoints first:

• Fetch all accounts belonging to the organization
• Fetch verification status (KYC/KYB)
• Get Currency Balance

Prepare a payout destination

Use these endpoints next:

• Create Beneficiary
• Add Beneficiary Account
• Resolve Bank Account

Price and execute a transaction

Complete the funds movement flow with:

• Get transaction limits for a currency and country
• Generate Quote
• Execute Transaction

Fund an account before execution

Use these endpoints when your transaction flow depends on available balance:

• Fetch all accounts belonging to the organization
• Get Currency Balance
• Get Deposit Instructions

Authentication and environments

Authenticate every request with your API key in the x-api-key header.

⚠️

Needs confirmation: Official base URLs, exact rate limit values, webhook signature details, and environment-specific behavior still need dedicated documentation.

Enterprise review areas

Security and compliance teams usually review these topics before production approval:

• API key storage and access control
• IP allowlisting for production traffic
• auditability of transactions and account activity
• data handling for beneficiary and verification information
• monitoring, alerting, and support escalation paths

Use these pages for those reviews:

• Getting Started
• Onboard with us
• Going Live

Troubleshooting entry points

Start with these checks when integration work stalls:

• If authentication fails, verify the x-api-key header and environment configuration.
• If onboarding progress is unclear, check the verification status endpoint.
• If transactions fail, verify account funding, beneficiary data, quote timing, and field validation.
• If production calls return 403, verify IP allowlisting and production key usage.

Explore the full reference