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.
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.
API Evangelist profiles Teya the way a machine reads it — 37 machine-readable artifacts across 4 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 45.9/100 (developing), with a separate agent-readiness read of 37/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Teya's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/teya/"
title="Teya on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/teya.svg"
alt="Teya Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/teya/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/teya/"
title="Teya on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/teya/card.svg"
alt="Teya Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 ·
Open Collections 17
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONTeya FX Captures API
OPEN COLLECTIONTeya FX Captures DCC API
OPEN COLLECTIONTeya FX Captures ePOS Registration API
OPEN COLLECTIONTeya FX Captures Hosted Checkout API
OPEN COLLECTIONTeya FX Captures '@internal' API
OPEN COLLECTIONTeya FX Captures Pay at Table API
OPEN COLLECTIONTeya FX Captures PayByLink API
OPEN COLLECTIONTeya FX Captures Payment Requests API
OPEN COLLECTIONTeya FX Captures Print Receipts (ePOS) API
OPEN COLLECTIONTeya FX Captures '@public' API
OPEN COLLECTIONTeya FX Captures Refunds API
OPEN COLLECTIONTeya FX Captures Reversals API
OPEN COLLECTIONTeya FX Captures Stores API
OPEN COLLECTIONTeya FX Captures Terminals API
OPEN COLLECTIONTeya FX Captures Tokens API
OPEN COLLECTIONTeya FX Captures Transactions API
OPEN COLLECTIONScroll within the panel for all 17 ·
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.
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.
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.
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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/teya · machine-readable index on apis.io
This is an independent, third-party profile of Teya, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.