Teya Payment Integration Skill Skill

Teya Payment Integration Skill

Complete reference for integrating with Teya's payment ecosystem, covering terminal integrations, e-commerce APIs, and SDK implementations.

Quick Decision Tree: Which Integration Do You Need?

Need to accept payments?
├── In-person (card present)?
│   ├── ePOS on separate device from terminal?
│   │   └── → POSLink Integration (cloud-based, Android/Windows)
│   │       See: references/epos-sdk/overview.md
│   │       See: references/poslink/overview.md
│   │
│   └── ePOS and terminal on same device?
│       └── → All-In-One Integration (Android only)
│           See: references/epos-sdk/all-in-one-introduction.md
│
└── Online (card not present)?
    ├── Need hosted checkout page?
    │   └── → E-Commerce API - Hosted Checkout
    │       See: references/apis/e-commerce-introduction.md
    │
    ├── Need to send payment links?
    │   └── → E-Commerce API - Payment Links
    │       See: references/apis/e-commerce-introduction.md
    │
    └── PCI compliant and want direct processing?
        └── → E-Commerce API - Direct Transactions
            See: references/apis/e-commerce-introduction.md

Integration Overview

1. POSLink (Cloud Terminal Integration)

Use when: Your ePOS runs on a separate device (tablet, PC) from the payment terminal.

Platforms: Android, Windows (iOS planned)

Key features:

Cloud-based communication between ePOS and terminal
SDK handles OAuth authentication and token refresh
Pre-built payment UI screens
Minimal setup required

Getting started:

Register at partner.teya.xyz (staging) or partner.teya.com (production)
Create OAuth application (Device Code Flow)
Get Client ID and Client Secret (per partner, not per merchant)
Request mock payment app APK from Partnership Manager
Integrate SDK into your application

References:

2. All-In-One Integration

Use when: Your ePOS app runs on the same Android device as the payment terminal.

Platforms: Android only (Sunmi, PAX terminals)

Key features:

Single-device workflow
Apps communicate via deeplinks
Receipt printing via Sunmi/PAX SDKs
No cloud dependency for device communication

Getting started:

Request debug terminal from Partnership Manager
Specify terminal model (Sunmi or PAX)
Get test merchant account assigned to terminal
Integrate SDK using provided guides

References:

3. E-Commerce API (Online Payments)

Use when: You need to accept online payments (card not present).

Options:

Hosted Checkout - Redirect customers to Teya's secure payment page (best for most merchants)
Payment Links - Send payment links via email/SMS for remote collection
Direct Processing - Full control for PCI-compliant systems

Getting started:

Get Teya merchant account from your representative
Access Business Portal: business.teya.xyz (staging) or business.teya.com (production)
Create API credentials under store settings → Integrations
Configure webhooks for payment notifications
Implement OAuth token exchange

References:

E-Commerce Introduction

4. Payments Gateway API

Use when: You're building card-present processing with direct API integration (advanced).

Supports:

Card-present transactions (EMV, contactless)
Pre-authorization and capture flows
Refunds and reversals
MOTO transactions
SoftPOS transactions

References:

5. POSLink REST API

Use when: You need programmatic access to stores, terminals, and receipt printing.

Features:

Payment request management
Store configuration
Terminal monitoring
Receipt printing (JSON and image formats)

References:

POSLink API

Authentication

All Teya APIs use OAuth 2.0:

Environments:

Staging: https://id.teya.xyz/oauth/v2/oauth-token
Production: https://id.teya.com/oauth/v2/oauth-token

Token lifetimes:

Production: 15 minutes
Staging: 24 hours

Example token request:

curl -X POST 'https://id.teya.com/oauth/v2/oauth-token' \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d 'grant_type=client_credentials' \
  -d 'client_id=<CLIENT_ID>' \
  -d 'client_secret=<CLIENT_SECRET>' \
  -d 'scope=checkout/sessions/create refunds/create'

Test Cards

| Brand | Number | Use Case | |-------|--------|----------| | Visa | 4242424242424242 | General testing | | Mastercard | 5555555555554444 | Mastercard testing | | Amex | 378282246310005 | Amex testing | | Mastercard | 2223600089700011 | DCC testing (EUR) |

Use any 3-digit CVV (4-digit for Amex)
Use any future expiry date
Test cards only work in staging environments

See Test Cards Reference for complete list.

Important Notes

Amount Format

All amounts are in minor units (cents/pence):

€1.00 = 100
€50.00 = 5000
$25.99 = 2599

Currency Format

ISO-4217 3-letter codes: EUR, USD, GBP, etc.

Environment URLs

Staging domains: *.teya.xyz
Production domains: *.teya.com

Idempotency

Always use Idempotency-Key headers to prevent duplicate transactions.

Certification Process (POSLink)

Design - Plan integration architecture
Develop - Implement authentication and payment flows
Test - Validate integration thoroughly
Get Certified - Schedule certification and go live

See Integration Checklist and Get Certified.

Support

Partnership Manager - For terminal requests, test accounts, APKs
Teya Representative - For merchant account setup
Developer Portal - partner.teya.xyz / partner.teya.com
Documentation - docs.teya.com

File Index

Agent Skills: Teya Payment Integration Skill

Install this agent skill to your local

Skill Files