DzalekaPay API documentation

Add DzalekaPay payment links, embed buttons, and public checkout APIs. No API key is required for the public catalog.

• OpenAPI: https://pay.dzaleka.com/openapi.json
• API index: https://pay.dzaleka.com/api
• DzalekaPay API authentication: public checkout needs no key. Merchant integrations send a scoped Bearer key from their server. Never expose it in a browser or prompt.
• DzalekaPay merchant webhooks: signed transaction.updated events, up to five delivery attempts, history in Developer platform.
• DzalekaPay MCP server: Streamable HTTP at https://pay.dzaleka.com/mcp. No authentication; no payment initiation tools.
• DzalekaPay versioning and deprecation: current public URLs use version 1.0.0. API-Version reports the contract, not a request pin. Removal requires 180 days of notice using Deprecation and Sunset headers. No endpoints are deprecated today.
• Machine-readable lifecycle policy
• Errors: REST 4xx/5xx JSON includes message and error.code. Check any transactionId before retrying a payment. MCP uses JSON-RPC errors instead.
• Limits: use RateLimit and RateLimit-Policy (IETF draft-11), or the legacy RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset. On 429 wait for Retry-After. Unauthenticated merchant API probes advertise policy only.

Open a store and share its payment link. Customers pay on a DzalekaPay checkout page without creating an account. Completed payments appear in your dashboard, and settled funds can be paid out using the methods currently enabled for merchants.

DzalekaPay is not a bank, mobile-money operator, personal wallet, remittance provider, or foreign-exchange service.