Install Jentic One Beta

Connect the Theteller Payment API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Theteller Payment 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%2Ftheteller.net%2Ftheteller" | 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%2Ftheteller.net%2Ftheteller" | 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 Theteller Payment API.

Initiate checkout payment

Check transaction status

Process fund transfer or payment

Authorize bank transfer

Reverse card transaction

GET STARTED

Start building with Theteller Payment API

Explore with Jentic One

View OpenAPI Document

Automated Checkout Management

Automate checkout operations by combining multiple Theteller Payment API endpoints. Agents can check transaction status and then process fund transfer or payment in a single workflow.

Call GET /v1.1/users/transactions/{transaction_id}/status to check transaction status, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Theteller Payment API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'initiate checkout payment', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — theteller payment processing api for checkout, mobile money, card payments, bank transfers, and transaction management.

METHOD

PATH

DESCRIPTION

POST

/checkout/initiate

Initiate checkout payment

GET

/v1.1/users/transactions/{transaction_id}/status

Check transaction status

POST

/v1.1/transaction/process

Process fund transfer or payment

POST

/v1.1/transaction/bank/ftc/authorize

Authorize bank transfer

POST

/rest/resources/card/reversal

Reverse card transaction

POST

/checkout/initiate

Initiate checkout payment

GET

/v1.1/users/transactions/{transaction_id}/status

Check transaction status

POST

/v1.1/transaction/process

Process fund transfer or payment

POST

/v1.1/transaction/bank/ftc/authorize

Authorize bank transfer

POST

/rest/resources/card/reversal

Reverse card transaction

Why Jentic?

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

Setup

Wiring the Theteller Payment API by hand means base64-encoding your username and key for basic auth, picking the right host among the live and test checkout and transaction servers, and handling your own retries. Through Jentic you install once, import the Theteller Payment API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Theteller Payment API puts the transaction id in the URL path (/v1.1/users/transactions/{transaction_id}/status), so a rule can pin your agent to one transaction for status reads. You choose the operations it may call, so money-moving actions like processing a transfer or reversing a card charge are not included unless you add them.

Credential isolation

Your Theteller credentials 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 'check a transaction status' or 'initiate a checkout payment', and Jentic returns the matching Theteller operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Theteller Payment API through Jentic.

What authentication does the Theteller Payment API use?

The Theteller Payment API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I initiate checkout payment with the Theteller Payment API?

Yes. Use the POST /checkout/initiate endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Theteller Payment API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I initiate checkout payment through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'initiate checkout payment'. Jentic returns the matching Theteller Payment API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Theteller Payment API have?

The Theteller Payment API exposes 5 endpoints covering checkout, transactions, reversals operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Theteller operations and credentials the agent may use. You can grant read-only access to GET /v1.1/users/transactions/{transaction_id}/status and, since the transaction id sits in the URL path, pin the agent to a single transaction for status checks. Money-moving operations such as POST /v1.1/transaction/process and POST /rest/resources/card/reversal stay off limits unless you explicitly add them.

Theteller Payment API

Name: Theteller Payment API
Brand: Theteller Payment API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbasic5 EndpointsREST

For Agents

Programmatically initiate checkout payment, check transaction status. Covers 5 operations with basic authentication.

Use for: I need to initiate checkout payment, I want to check transaction status, Search for process fund transfer or payment, Find all authorize bank transfer

Not supported: Does not handle communications, crm, or developer tools - use for payments only.

Theteller payment processing API for checkout, mobile money, card payments, bank transfers, and transaction management. The API exposes 5 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Theteller Payment API to your agent

Capabilities

Start building with Theteller Payment API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Theteller Payment API