Theteller Payment API

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.