Skip to main content

EPS Python SDK

Backend-only Python client for Eko Platform Services APIs — DMT, AePS, BBPS, KYC and verification — with HMAC request signing built in.

pip install eps-sdk
from eps_sdk import EpsClient

client = EpsClient(
    developer_key="<your_developer_key>",
    access_key="<your_access_key>",
    environment="sandbox",      # or "production"
    initiator_id="9962981729",  # registered mobile of the API user
    user_code="20810200",       # retailer/agent code
    timeout=30.0,               # whole-request budget in seconds (default)
)

sender = client.call("dmt-get-sender", {"customer_id": "9123456789"})

One generic call(slug, params) covers every endpoint. The slug list, each endpoint's params and which of them are required all come from the same generated API surface the docs are built from, so the client validates your input before it signs and sends anything.

timeout is the whole-request budget in seconds, defaulting to 30.0 — the same 30s every EPS SDK defaults to. (Node names its knob timeout_ms / timeoutMs because it is milliseconds there.) The response and error contract is shared by all five SDKs; see docs/sdk-golden-vector.md.

Backend only

access_key signs every request. Never run this in anything a browser can reach — a leaked access key lets anyone transact as you.

What it does for you

  • Signs the request — secret-key, secret-key-timestamp and developer_key headers on every call.
  • Validates first — missing required params and wrong types raise EpsError before a request goes out.
  • Routes the params — path tokens, query string, JSON body, or multipart/form-data for file-upload endpoints, per the endpoint's spec.
  • Fails loudly — a non-2xx response raises EpsHttpError (with the decoded envelope on .body); a non-JSON body raises rather than returning {}.

Files can be a path or an in-memory pair:

client.call("activate-aeps-fingpay", {
    "pan_card": "/path/to/pan.jpg",
    "aadhar_front": ("aadhar.jpg", image_bytes),
    # ...
})

Zero dependencies

Standard library only (urllib, hmac, json). Nothing to keep patched.

Development

The runtime asset data/sdk-surface.json is generated from the API specs, not committed. From the repo root:

npm run build                            # bakes data/sdk-surface.json
cd packages/sdk-python
PYTHONPATH=src python3 -m unittest discover -s tests

The test suite is the cross-language conformance suite described in docs/sdk-golden-vector.md — the same cases the Node.js and PHP SDKs must pass.

MIT licensed.

Metadata

Release files for eps-sdk 2.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eps-sdk 2.0.0
File Size Uploaded
eps_sdk-2.0.0.tar.gz 17.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for eps-sdk 2.0.0
File Interpreter ABI Platform
eps_sdk-2.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 32.2 kB

Release files / eps_sdk-2.0.0.tar.gz

Download URL eps_sdk-2.0.0.tar.gz
Size 17.7 kB
Tags Source
SHA-256 checksum
How to use checksums
02473602bf2801534937367be997a3063264a2cae05c903b1031d51b2d383296
BLAKE2b-256 checksum
How to use checksums
ed3977872ed7c3733c29826eeab79d80491f859ff4b99b86b3e14641da14fc8e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.

Transparency log

Release files / eps_sdk-2.0.0-py3-none-any.whl

Download URL eps_sdk-2.0.0-py3-none-any.whl
Size 14.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c3555cfb1ba4e1a29a7aa598a3b8b54249e5d4d9908c4d763795aa0527beb28
BLAKE2b-256 checksum
How to use checksums
70f50b7eeb64caa5bf88f7ef5d1bd0cc77a49182ac54321030338214b28ed7ee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.

Transparency log

Release history Release notifications | RSS feed

3.0.11

2 release files

3.0.10

2 release files

3.0.9

2 release files

3.0.8

2 release files

3.0.7

2 release files

3.0.6

2 release files

3.0.5

2 release files

3.0.4

2 release files

3.0.3

2 release files

3.0.2

2 release files

3.0.1

2 release files

3.0.0

2 release files

This release

2.0.0 This release

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page