KERSHI DEVELOPERS

Get Started

Skip the boilerplate code and integrate payment verification in minutes, not days.

Real-provider checks use the server-side Ethiopian Payment Verify SDK. Only bank-fetched evidence with matching amount and receiver is marked verified.

1. Choose an Integration Flow

REST API

Use one verification endpoint for your app or backend.

Jump to REST API →

Polling or SSE

Use the returned request ID to follow the processing status.

Jump to Polling or SSE →

Webhooks

Send a callback URL with your request to receive the final result.

Jump to Webhooks →

Create an API Key

Sign in

Open the dashboard and authenticate with your account.

Create a key

Open the developer API keys page, create a key, and save it securely.

Set permissions

Set verification permissions required by your integration.

Send the header

Add x-api-key to server-side requests. Never expose keys in browser code.

Credits are account-level

Developer plans and credit limits apply to the account.

✧ Kershi Agent Skill is here

Let your AI agent integrate Kershi and help with production workflows.

Install

npx skills add https://YOUR_KERSHI_HOST/skill

Works with Codex · Claude Code · Cursor · Gemini · OpenCode

Use the Production Endpoint

Keep keys on your server. These values are illustrative placeholders from the documentation.

Environment

KERSHI_API_URL=https://YOUR_KERSHI_HOST
KERSHI_API_KEY=your_server_side_key

Submit Your First Verification

Send a bank and the receipt details. Review the returned result before continuing your workflow.

curl

curl -X POST 'https://YOUR_KERSHI_HOST/api/v1/verifications' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer $KERSHI_API_KEY' \
  -H 'Idempotency-Key: <unique-request-id>' \
  -d '{
    "provider": "cbe",
    "reference": "<receipt-reference>",
    "accountSuffix": "<8-digits>",
    "amountMinor": 13500,
    "settlementAccountId": "<saved-account-id>"
  }'

Next Steps

Explore API Documentation →