1
Ladder creates your organisation and issues test keys
You receive a
pk_test_… key id and a sk_test_… secret, first on UAT (https://api-dev.myladder.africa) for integration work, then on production once you are ready. The secret is shown once; store it in a secrets manager, never in code or logs.2
Complete KYB through the API
Business information, directors and owners, documents and a settlement account, then
POST /kyb/submit. GET /organisation lists whatever is still missing. See KYB.3
Build against the sandbox
With test keys everything settles instantly: fund a wallet and settle it with the sandbox endpoint, place orders, redeem, register a webhook receiver. Nothing here waits for approval.
4
Approval and live keys
Ladder reviews KYB. On approval you receive
pk_live_… keys. Live keys on an unapproved organisation are refused.5
Go live
Fund a live wallet on a real rail, place an order, act on
order.completed. Walk the go-live checklist first.Your first signed call
Sandbox and live are the same host. The key you sign with decides the environment, and every object you create belongs to that environment only.