We are excited to release DigiPay API version 2.0, our biggest platform update since launch. This release focuses on three areas developers have requested most: faster transaction processing, more reliable webhook delivery, and better tools for querying transaction status. All improvements are backward-compatible with existing integrations.
40 Percent Faster Processing
API v2.0 reduces average transaction processing time from 2.3 seconds to 1.4 seconds for M-Pesa STK Push initiation. Card payment authorization is now completed in under 800 milliseconds for domestic cards. These improvements come from infrastructure upgrades including edge caching of authentication tokens, optimized database queries, and direct routing to payment providers.
Guaranteed Webhook Delivery
The most common developer complaint was missed webhooks due to temporary server downtime. API v2.0 introduces guaranteed delivery with automatic retries. If your webhook endpoint returns a non-200 status code, we retry with exponential backoff for up to 24 hours. A new webhook replay endpoint lets you manually re-trigger any webhook for debugging.
New Transaction Query Endpoints
Developers can now query transactions by date range, status, payment method, and amount range using new filter parameters. A dedicated mini-statement endpoint returns the last 10 transactions optimized for mobile app dashboards. The transaction detail endpoint now includes full timeline data showing every status change from initiation to completion.
Improved Error Responses
Every API error now returns a structured JSON response with a human-readable message, machine-readable error code, and suggested fix. Instead of generic 400 errors, you get specific codes like INVALID_PHONE_FORMAT with the message "Phone number must be in 254XXXXXXXXX format" and a link to the relevant documentation section.
Idempotency Support
API v2.0 supports idempotency keys on all POST requests. Include a unique key in the header and DigiPay guarantees the request is only processed once, even if your application sends it multiple times due to network issues or timeouts. This eliminates the risk of duplicate charges that plague applications with unreliable connectivity.
Rate Limiting Improvements
Rate limits have been increased from 100 to 500 requests per minute for production API keys. Sandbox keys now have unlimited requests for testing. Rate limit headers are included in every response so your application can implement proper backoff without guessing. Merchants processing high volumes can request custom rate limits through support.
Migration Guide
Existing v1 endpoints continue to work without changes. When you are ready to adopt v2 features, simply change your base URL from api/v1 to api/v2. All request and response formats remain identical. New features like webhook replay and advanced filtering are only available on v2 endpoints. Consult our migration guide at digipay.co.ke/api-reference for complete details.
