Install Jentic One Beta

Connect the Dusupay African Payments API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dusupay African Payments API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdusupay.com%2Fdusupay" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdusupay.com%2Fdusupay" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Dusupay African Payments API.

Initialize mobile money, bank, and card collection requests across African countries

Authorize a collection with the one-time password a customer receives

Send payouts and disbursements to recipients' bank accounts and mobile money wallets

Verify the status of a transaction by its reference

GET STARTED

Start building with Dusupay African Payments API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dusupay African Payments API for, with concrete tasks.

★ AI Agent Payment Collection

Let an AI agent take an inbound payment across African mobile money, bank, and card rails: it initializes a collection for the amount and provider, authorizes it with the one-time password the customer receives, and verifies the final status by reference. Through Jentic the agent discovers the right Dusupay operation by intent and calls it with the collection details, so a checkout flow runs without a developer wiring each step by hand.

Initialize a mobile money collection for 50000 UGX, authorize it with the customer's OTP, then verify the transaction status by reference

Cross-Border Payouts

Merchants disburse funds to recipients across African countries without integrating each bank or mobile money provider directly. The payout operation sends funds to a bank account or mobile money wallet, after looking up the correct payout bank codes, and the transaction verify operation confirms the disbursement settled. Payouts require the merchant's secret key in addition to the public key.

Look up the payout bank codes, send a payout to a recipient's bank account, then verify the disbursement by reference

Transaction Verification and Reconciliation

Finance teams confirm which payments cleared and reconcile them against expected amounts. The API verifies a transaction by its reference and returns merchant wallet balances by currency, so an agent can match settled collections to balances at the end of a day. This avoids polling a dashboard to check whether a specific payment succeeded.

Verify a transaction by its reference, then read the merchant wallet balances to reconcile the day's collections

Key Endpoints

7 endpoints — the dusupay african payments api collects and disburses funds across more than 15 african countries using mobile money, bank transfers, and card payments.

METHOD

PATH

DESCRIPTION

POST

/collections/initialize

Initialize a collection request

POST

/collections/authorize

Authorize a collection with OTP

POST

/payout/send-funds

Send funds (payout or disbursement)

GET

/data/transaction/verify/{reference}

Verify transaction status

GET

/data/wallet-balances

Get wallet balances

GET

/data/payment-providers

List available payment providers

GET

/data/payout-bank-codes

Get payout bank codes

POST

/collections/initialize

Initialize a collection request

POST

/collections/authorize

Authorize a collection with OTP

POST

/payout/send-funds

Send funds (payout or disbursement)

GET

/data/transaction/verify/{reference}

Verify transaction status

GET

/data/wallet-balances

Get wallet balances

GET

/data/payment-providers

List available payment providers

GET

/data/payout-bank-codes

Get payout bank codes

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Dusupay by hand means managing its public-key and secret-key headers, the initialize-then-authorize collection flow with its one-time password, and choosing the production or sandbox host. Through Jentic you install once, import Dusupay from the API Directory, store both keys once, and your agent calls it.

Permission scoping

Dusupay carries the amount, recipient, and provider in the request body rather than the URL path, so rules bound which operations your agent may call rather than which account it touches. You choose the operations it needs, such as initializing collections and verifying transactions, so sending payouts is not included unless you add it.

Credential isolation

Your Dusupay public and secret keys are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'collect a mobile money payment' or 'send a payout', and Jentic returns the matching Dusupay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Dusupay African Payments API through Jentic.

What authentication does the Dusupay African Payments API use?

The Dusupay API authenticates with API keys sent in request headers per its OpenAPI spec: a public-key header on every request and a secret-key header additionally required for payouts and balance inquiries. Through Jentic both keys are stored encrypted by your own Jentic One instance and injected at call time, so they never enter the agent's context.

Can I collect mobile money payments with the Dusupay API?

Yes. The collection initialize operation starts an inbound payment via mobile money, bank transfer, or card, and the authorize operation completes it with the one-time password the customer receives. You then confirm the result with the transaction verify operation.

What are the rate limits for the Dusupay African Payments API?

The OpenAPI spec does not specify rate limits; see https://developer.dusupay.com/ for current limits. Use the transaction verify operation to confirm a payment's final status rather than polling rapidly.

Is there a Dusupay MCP server?

You don't need an MCP server to give your agent the Dusupay API. Jentic connects it directly from the API Directory: import it, store your public and secret keys once, and your agent calls operations like initializing a collection or sending a payout. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

Can I limit what my agent is allowed to do with the Dusupay API?

Yes. Write a rule that allows only collection and verification operations, so the agent can take inbound payments and check their status but cannot send payouts, which also require the secret key. Dusupay passes the amount and recipient in the request body, so rules bound which operations run rather than which account, and every call is logged.

How do I collect a payment with the Dusupay API through Jentic?

Search Jentic for 'collect a mobile money payment' to find the collection initialize operation, authorize it with the customer's OTP, then verify the transaction by reference. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Dusupay African Payments API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey7 EndpointsREST

For Agents

Collect inbound payments via mobile money, bank, and card, send payouts to recipients, and verify transaction status across African markets. Covers 7 operations for collections, payouts, and balance checks.

Use for: Initialize a mobile money collection for a customer, Authorize a collection with the OTP the customer received, Send a payout to a recipient's bank account, Verify whether a transaction succeeded

Not supported: Does not handle invoicing, subscription billing, or accounting reconciliation. Use for African collections and payouts only.

The Dusupay African Payments API collects and disburses funds across more than 15 African countries using mobile money, bank transfers, and card payments. Agents can initialize a collection and authorize it with a one-time password, send payouts to bank accounts and mobile money wallets, and verify a transaction's status by reference. Utility endpoints return wallet balances, available payment providers, and payout bank codes so a payment is routed through the right rail. Authentication uses a public API key on every request, with a secret key additionally required for payouts and balance inquiries.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

12%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

56%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

88%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Dusupay African Payments API to your agent

Capabilities

Start building with Dusupay African Payments API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dusupay African Payments API

Jentic AI Readiness Score

Dusupay African Payments API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness