Sznd Business API

Introduction to Sznd

Sznd is a business payments backend: your servers call our JSON REST API under /api/v1, and we coordinate collections, payouts, FX-style quotes, balances, and customer data across many payment and banking providers (card acquirers, bank rails, mobile money, stablecoin and crypto partners, and more). You do not integrate each rail separately—we expose a single authenticated contract for your product, while we handle the complexity of working with those providers on your behalf.

The integration surface you will spend most of your time on is /api/v1/client/.... Those routes require business API keys and signed requests so only your systems can act on behalf of your business. The Authentication section covers how to attach credentials and validate each call.

What you can build on it

Price and execute money movement

Create quotes (with current rates), inspect them by id, and accept them when you are ready to commit. Accepted work surfaces as transactions you can list, summarize, and look up by reference—your operational view of what settled, what failed, and what is still in flight.

Collect from payers

Initialize checkout and card flows (including verification and refund APIs) so customers pay with methods appropriate to their corridor. You can track outcomes through transactions the same way you do for other money movement on your account.

Pay out and hold balances

Register beneficiaries, manage virtual wallets, and read wallet balances so payouts and liquidity are explicit. Customer records support onboarding and compliance checks where your flow requires them.

Keep your systems aligned

Configure a webhook URL on your API key so you receive signed callbacks when transaction state changes. Treat every delivery as untrusted until you verify the signature and handle retries idempotently—the Webhooks guide describes what to expect on your endpoint.

Validate international payout inputs

Use regions helpers (subdivisions, postal formats, phone checks) and bank catalogues plus bank-account lookup so the beneficiary payloads you submit match what downstream rails expect.

Test without production traffic

Non-production environments expose mock helpers (for example simulating deposits or webhook payloads) so you can run end-to-end tests without touching live money. They are not available in production.

How the documentation maps to the product

• Guides walk the main journeys this product is built around: Collections (money in), Payouts (money out), Quotes (rate lock-in), Wallets (balance management), and Webhooks (event notifications).
• Reference covers technical details for Authentication, KYC, and Mocks, as well as object definitions for Transactions, Transfers, Customers, and shared Resources (banks, currencies, etc.).

If you are new, read Authentication first, then open the guide that matches your first milestone: Collections, Payouts, or Wallets. For lookup tables and object semantics, start from Resources.

Operating safely

Use staging credentials and mock flows until your integration is reviewed for production. Rotate API keys when people or vendors change, and never treat a webhook as genuine without signature verification and idempotent handling of duplicate deliveries.

Support

For business onboarding, production base URLs, and integration review: support@sznd.app.