The sequence
1
Request an account
Contact us at getspendin.co with the corridors
you intend to use and your expected monthly volume. We create your account
and give you access to the dashboard.
2
Complete KYB
Submit your business details and supporting documents — certificate of
incorporation, directors’ identification, proof of address, and the
ownership structure. Our compliance team reviews and issues a decision.Your profile has to reach
APPROVED. Any other state blocks payouts with
403 COMPLIANCE_NOT_APPROVED, including a profile that is submitted and
still under review.3
Receive your API keys
On approval we issue your keys. You get a separate key for testing and for
live traffic — they are distinct credentials on distinct accounts, so a test
key can never move real money.A key is displayed once, at issue. We store only a hash and a short
prefix for lookup. A lost key is revoked and replaced, never recovered.
4
Register a refund destination
Before your first payout, tell us where failed-payout money goes back to.
See Refunds. This is the one setup step you do through the
API yourself, and payout creation is blocked until it is done.
Choosing scopes
Ask for the narrowest set of scopes that does the job, and ask for separate keys per system. A reconciliation job that reads payouts has no business being able to create them. A typical split:What you need before you write code
Your base URL
https://api.spendin.app, with every route under /v1/.Your webhook endpoint
An HTTPS URL that returns
2xx fast. Register it and store the signing
secret — it is shown once.Keys carry no expiry by default but can be issued with one, and can be revoked
at any time. Several keys can be active at once, which is what makes rotation
possible without downtime — see
Authentication.