Developers

Build connected payment and financial operations.

Use governed APIs, webhooks and a controlled integration path. Privileged merchant API keys are never embedded into public client applications.

Integration principles

Build with server-side credentials

Keep merchant API keys in trusted backend services. Browser applications should use only approved public flows and never receive privileged secrets.

Make requests safe to retry

Use idempotency and request identifiers when creating money-moving operations so repeated delivery can be handled predictably.

React to signed events

Use webhook signatures and event identifiers to verify notifications, update your own systems and reconcile the resulting business activity.

Example request

curl --request POST https://api.ekash.co/payments/v1/payments \
+  --header "Idempotency-Key: <UUID>" \
+  --header "X-Request-Id: <UUID>"

A practical integration lifecycle

A reliable integration covers more than making a request. It needs clear business ownership, safe credentials, predictable retry behaviour and a way to reconcile event outcomes with your own systems.

Phase 1

Plan the integration

Identify the business events, data ownership, supported products and server-side services involved before creating payment or settlement workflows.

Phase 2

Build and test safely

Use controlled credentials, request identifiers and expected webhook handling to test the integration without placing secrets or sensitive operational logic in a browser.

Phase 3

Operate and observe

Monitor event delivery, reconcile API outcomes and maintain clear ownership for retries, exceptions and support escalation.