teya

Teya payment integration guide covering POSLink (cloud-based terminal integration), All-In-One (single-device Android), E-Commerce APIs (hosted checkout, payment links), and Payments Gateway. Includes decision trees, authentication patterns, test cards, and certification guidance.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "teya" with this command: npx skills add majncz/teya-skill/majncz-teya-skill-teya

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:

  1. Register at partner.teya.xyz (staging) or partner.teya.com (production)
  2. Create OAuth application (Device Code Flow)
  3. Get Client ID and Client Secret (per partner, not per merchant)
  4. Request mock payment app APK from Partnership Manager
  5. 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:

  1. Request debug terminal from Partnership Manager
  2. Specify terminal model (Sunmi or PAX)
  3. Get test merchant account assigned to terminal
  4. 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:

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

References:

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:

Authentication

All Teya APIs use OAuth 2.0:

Environments:

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

BrandNumberUse Case
Visa4242424242424242General testing
Mastercard5555555555554444Mastercard testing
Amex378282246310005Amex testing
Mastercard2223600089700011DCC 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)

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

See Integration Checklist and Get Certified.

Support

File Index

APIs

ePOS SDK

POSLink Guides

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

fakturoid

No summary provided by upstream source.

Repository SourceNeeds Review
General

digisign

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

openclaw-version-monitor

监控 OpenClaw GitHub 版本更新,获取最新版本发布说明,翻译成中文, 并推送到 Telegram 和 Feishu。用于:(1) 定时检查版本更新 (2) 推送版本更新通知 (3) 生成中文版发布说明

Archived SourceRecently Updated
Coding

ask-claude

Delegate a task to Claude Code CLI and immediately report the result back in chat. Supports persistent sessions with full context memory. Safe execution: no data exfiltration, no external calls, file operations confined to workspace. Use when the user asks to run Claude, delegate a coding task, continue a previous Claude session, or any task benefiting from Claude Code's tools (file editing, code analysis, bash, etc.).

Archived SourceRecently Updated