Wallet-native APIs.
Request payments from Mytalu wallets, send payouts, issue refunds and reconcile — over a REST API with signed webhooks and a sandbox.
Environments and authentication
Sandbox
sk_test_…https://sandbox-api.mytalu.co/v1Test money in an isolated environment. Self-serve from the Developer Hub.
Live
sk_live_…https://api.mytalu.co/v1Real money. Enabled once your business is approved for live access.
Authenticate every request with your secret key: Authorization: Bearer sk_test_…
Everything a checkout needs.
Amounts are integers in ngwee: K150.00 = 15000.
Recipients
Collections
Payouts
Refunds
Account
Request, approve, get notified.
The customer approves in the Mytalu app. You fulfil the order on the collection.succeeded webhook.
Webhook events
Signed with HMAC-SHA256 in the Mytalu-Signature header. De-duplicate on the event id.
- collection.succeeded
- collection.failed
- collection.expired
- collection.cancelled
- payout.awaiting_approval
- payout.succeeded
- payout.failed
- refund.succeeded
Simple to integrate. Easy to maintain.
Predictable REST endpoints, JSON in and out.
Sandbox & live keys
Bearer secret keys: sk_test_ for sandbox, sk_live_ for live. Scoped per key, with IP allowlists for payouts and refunds.
Signed webhooks
Every event is signed with HMAC-SHA256 in the Mytalu-Signature header. Missed one? Poll GET /events.
Idempotent by reference
Your reference makes each request safe to retry. Same reference, same result; never a duplicate payment.
Dual approval aware
If your business has dual authorisation on, payouts wait as awaiting_approval until a second person approves.
Simple, per-transaction pricing.
The API works with Mytalu wallets. Full details in the API reference.
Ready to build?
Create a business account, then get sandbox keys from the Developer Hub.