canonical: https://jentic.com/apis/theteller.net/theteller

# Theteller Payment API

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

## For AI agents

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

## Scope

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

## Capabilities

- Initiate checkout payment
- Check transaction status
- Process fund transfer or payment
- Authorize bank transfer
- Reverse card transaction

## Use cases

### Payments Operations

Use the Theteller Payment API to perform payments operations programmatically. The API provides 5 endpoints covering core functionality including initiate checkout payment, check transaction status, process fund transfer or payment.

Example prompt: Call POST `/checkout/initiate` to initiate checkout payment

### 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Checkout** — Checkout payment initiation
- **Transactions** — Transaction processing and status
- **Reversals** — Card transaction reversals

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 41 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/theteller.net/theteller/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### 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.