Managing Fikra API Payments and Token Credits

Fikra API uses a token-credit wallet system for billing. Developers purchase credits to use the API, and these credits are deducted as requests are processed. The platform integrates with Paystack for billing, and the public website states that M-Pesa and card payments are accepted.

Token-Credit Wallet

A token-credit wallet is a prepaid balance associated with your Fikra account. When you make API calls, the cost is calculated based on the tokens used (input and output) and deducted from this wallet. You do not pay per request in real-time; instead, you top up your wallet and consume credits as you go.

Account and Top-Up Flow

1. Access Dashboard: Log in to the Fikra dashboard at https://fikraapi.co.ke.
2. Top Up: Navigate to the billing or wallet section. Select a payment method (M-Pesa or card) via the Paystack integration.
3. Confirm Payment: Complete the transaction. Once processed, the credits are added to your wallet balance.

Note: Specific minimum deposit amounts, exchange rates, or country-specific availability are not publicly documented. Confirm current payment options and limits directly with Fikra support or the dashboard.

Monitoring Balance and Handling HTTP 402

Developers should monitor their wallet balance to avoid service interruptions. If the balance is insufficient to cover a request, the API returns an HTTP 402 (Payment Required) status code.

Best Practices: - Check Balance: Regularly query your account balance via the dashboard or available API endpoints (if provided). - Handle 402 Errors: Implement retry logic or user notifications when a 402 error is received. This indicates the wallet is empty or insufficient. - Set Alerts: Configure alerts in your application to notify developers when the balance falls below a certain threshold.

Security Advice

• Never Expose API Keys in Browser Code: Fikra API keys (e.g., fk_live_...) must be stored securely on your backend. Do not include them in client-side JavaScript, mobile apps, or any publicly accessible code.
• Use Environment Variables: Store your FIKRA_API_KEY in environment variables on your server.
• Proxy Requests: If building a web application, proxy API requests through your backend to keep the API key hidden from end-users.

Verification Note

If you are considering a payment method not explicitly listed (M-Pesa, card via Paystack), confirm its availability and support with Fikra before implementation. Do not assume support for other payment gateways or methods without explicit confirmation.