Authentication
Use internal JWT authentication for dashboard actions. Public API integrations require key-based authentication and signed requests where applicable.
Documentation
Integration references for secure payment workflows
This documentation hub covers API patterns, operational controls, and rollout guidance to help your team build with confidence. Use it alongside dashboard tooling for key lifecycle management, webhook diagnostics, and reconciliation support.
Transfers and payouts
Initiate MozoPay-to-MozoPay and bank transfers, enforce idempotency, and monitor webhook outcomes for final settlement state.
Bills and checkout
Access bill categories, create hosted payment links, and consume transaction events for customer notifications.
Errors and retries
Implement deterministic retry rules for safe operations. Use status endpoints for eventual consistency during provider callbacks.
Production best practices
- Always send an Idempotency-Key for money movement endpoints.
- Treat webhook delivery as the source of final provider state.
- Store only non-sensitive references in logs and analytics systems.
- Rotate credentials periodically and revoke keys that are no longer in use.
- Keep Sandbox and Live credentials isolated across environments.