How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Teya Transactions API

Transactions

Teya Transactions API is one of 16 APIs that Teya publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 7 paths, and defines 43 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.teya.com, https://api.teya.xyz.

7 operations 7 paths 43 schemas 1 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.teya.com
Resource Areas
1

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 1 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Transactions 7

Transactions

POST
/v3/transactions/online
Process an online transaction v3
processOnlineTransactionV3 1 param body → 201202400401403409422500
GET
/v2/transactions/online/{authentication_id}
Get an online transaction
getOnlineTransactionV2 1 param → 200400401403404500
POST
/v3/refunds
Process a refund of a transaction
refunds 1 param body → 201202400401403404409460
POST
/v1/transactions/{transaction_id}/receipts
Create a digital receipt for a transaction
createReceipt 1 param body → 202400401403429500
POST
/v1/transactions/{id}/capture
Capture a pre-auth
captureRequest 2 params body → 201202400403409500503
POST
/v1/transactions/moto
Process a mail order or telephone order transaction
motoTransactions 1 param body → 201202400401403409500522
POST
/v1/transactions/card-present
Process a transaction with card present
cardTransactions_2 1 param body → 201202400401403409500503

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are TransactionRequest (14 properties), Ecommerce_Transaction_Payments_-_Public_ProcessTransactionRequestV2 (14 properties), Ecommerce_Transaction_Payments_-_Public_OnlineTransaction (8 properties), RefundResponse (8 properties). Each schema is shown below with its type and property counts.

RefundResponse
object
A response to refund a transaction
8 properties 5 required
Teya_Digital_Receipts_Service_CreateReceiptRequest
object
Request to initiate creation of digital receipts
5 properties 1 required
Ecommerce_Transaction_Payments_-_Public_ProcessTransactionResponseV2
object
The response for a transaction request
3 properties
CaptureIssuerResult
object
Issuer result data for capture transactions
3 properties
IssuerResult
object
Result data from the issuer
4 properties
PinBlock
object
PIN block data
4 properties 4 required
DccRequest
object
Dynamic Currency Conversion request
2 properties 2 required
TerminalData
object
Terminal specific data for transactions
2 properties
Ecommerce_Transaction_Payments_-_Public_CustomerContact
object
Customer contact details
2 properties
Teya_Digital_Receipts_Service_CreateReceiptResponse
object
Creates a url for customers to view their receipt.
3 properties 3 required
Ecommerce_Transaction_Payments_-_Public_IssuerResult
object
Result data for the transaction according to issuer's response
2 properties
RefundRequest
object
A request to refund a transaction
3 properties 2 required
Ecommerce_Transaction_Payments_-_Public_BrowserData
object
Browser information transmitted during the authentication request process to enhance verification accuracy.
5 properties 3 required
Ecommerce_Transaction_Payments_-_Public_PaymentMethod
object
4 properties 1 required
RequestedAmounts
object
3 properties 2 required
EncryptedTrack
object
Encrypted track data from card reader
3 properties 3 required
Ecommerce_Transaction_Payments_-_Public_ApplePayAuthenticationData
object
Represents the decrypted data from an Apple Pay payment token, including card details, transaction information, and merchant metadata.
5 properties 4 required
Ecommerce_Transaction_Payments_-_Public_OnlineTransaction
object
The response for a transaction request
8 properties 5 required
MotoTransactionResponse
object
The response for a processed MOTO transaction
5 properties 3 required
EncryptedMotoCard
object
5 properties 3 required
Ecommerce_Transaction_Payments_-_Public_RedirectTransactionResponse
object
The response for a transaction request where 3DS challenge is returned
6 properties 6 required
Payments_Refunds_Wrapper_API_Amount
object
2 properties 2 required
MotoIssuerResult
object
2 properties
Ecommerce_Transaction_Payments_-_Public_LineItem
object
3 properties 3 required
Payments_Refunds_Wrapper_API_DccResponse
object
4 properties 3 required
CaptureRequest
object
A request to capture pre-authorised transaction
2 properties 1 required
MotoTransactionRequest
object
A request to process a MOTO transaction
7 properties 4 required
TransactionRequest
object
A request to process a transaction
14 properties 6 required
Ecommerce_Transaction_Payments_-_Public_Cardholder
object
Information about the cardholder
3 properties 1 required
TransactionResponse
object
The response for a processed transaction
6 properties 4 required
Payments_Refunds_Wrapper_API_RefundIssuerResult
object
2 properties
CaptureResponse
object
The response for a processed capture
6 properties 4 required
Amount
object
Amount object
2 properties 2 required
InvalidParams
object
Invalid parameter details
2 properties 2 required
Ecommerce_Transaction_Payments_-_Public_Amount
object
The transaction amount in the smallest currency unit according to ISO 4217 format. For example: - 100 ISK (Icelandic króna): the amount is 100 (since 1 ISK = 1…
2 properties 2 required
Ecommerce_Transaction_Payments_-_Public_TokenCreationResponse
object
Details of the token which was created and if any failures will have the failure reason
3 properties 1 required
Ecommerce_Transaction_Payments_-_Public_Address
object
Customer's address
8 properties 1 required
Teya_Digital_Receipts_Service_Error
object
Error response
2 properties 2 required
Ecommerce_Transaction_Payments_-_Public_ProcessTransactionRequestV2
object
A request to process a transaction
14 properties 5 required
Ecommerce_Transaction_Payments_-_Public_Card
object
4 properties 4 required
Ecommerce_Transaction_Payments_-_Public_Token
object
A saved payment method token for recurring or card-on-file transactions
2 properties 2 required
Error
object
Error response
3 properties 2 required
CardData
object
Card details for payment
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

teya-transactions-api-openapi.yml Raw ↑

Other APIs Teya publishes across the network.

Teya Captures API
Teya DCC API
Teya ePOS Registration API
Teya Hosted Checkout API
Teya '@internal' API
Teya Pay at Table API
Teya PayByLink API
Teya Payment Requests API
Teya Print Receipts (ePOS) API
Teya '@public' API
Teya Refunds API
Teya Reversals API
Where this information came from

This is an independent, third-party profile of Teya Transactions API, 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.