Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Teya

Teya (formerly SaltPay) is a European payments and business-services provider serving local businesses with card machines, online and in-person card acquiring, a business account, and flexible business funding. Its developer platform exposes REST APIs for the full card-payment lifecycle: Online Payments (Hosted Checkout, PayByLink, e-commerce transactions, captures, refunds, digital receipts, tokens), a Payments Gateway (card-present, MOTO, refunds, captures, reversals), POSLink for cloud terminal control (payment requests, tabs, stores, terminals, ePOS registration, receipt printing), and a Teya FX API for Dynamic Currency Conversion, plus a SOAP-based Settlement API for payout reporting. Authentication is OAuth 2.0 (authorization code and client credentials) against id.teya.com, write operations support Idempotency-Key, and first-party SDKs cover web (Teya Blocks) and Android/iOS point-of-sale.

agent native

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Teya the way a machine reads it — 21 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Teya scores 53.2/100 (developing), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 53.2/100 · developing
Contract Quality 13.5 / 25
Developer Ergonomics 16.1 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Regulatory · Payments 11.4 / 15
Agent readiness — 78/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3

How we profile Teya

Each block below is one kind of artifact we hold for Teya. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 16

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Teya Captures API

Operations related to capturing pre-authorised transactions.

Teya DCC API

Operations related to dynamic currency conversion

Teya ePOS Registration API

The ePOS Registration API from Teya — 1 operation(s) for epos registration.

Teya Hosted Checkout API

APIs exposed for session management

Teya '@internal' API

The '@internal' API from Teya — 2 operation(s) for '@internal'.

Teya Pay at Table API

The Pay at Table API from Teya — 9 operation(s) for pay at table.

Teya PayByLink API

APIs exposed for pay by link customers

Teya Payment Requests API

The Payment Requests API from Teya — 4 operation(s) for payment requests.

Teya Print Receipts (ePOS) API

Create a receipt print job and fetch its status/events

Teya '@public' API

The '@public' API from Teya — 4 operation(s) for '@public'.

Teya Refunds API

The Refunds API from Teya — 2 operation(s) for refunds.

Teya Reversals API

The Reversals API from Teya — 1 operation(s) for reversals.

Teya Stores API

The Stores API from Teya — 3 operation(s) for stores.

Teya Terminals API

The Terminals API from Teya — 1 operation(s) for terminals.

Teya Tokens API

Token management for saved payment methods

Teya Transactions API

Transactions

Scroll within the panel for all 16 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

teya-mcp.yml

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Teya Authentication

oauth2 · 2 schemes

SECURITY

Teya Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Teya Scopes

2 scopes · authorizationCode/clientCredentials

2 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Teya Agentic Access

42 operations · 29 acting

42 operations · 29 acting

AGENTIC

Resources

Every other property we hold for Teya — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 2

Reference material describing how the API behaves

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/teya · machine-readable index on apis.io