teya

Name: teya
Author: diegosouzapw

Engineering Community

Repo stars 39
Author updated Live
Author repo awesome-omni-skill

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Engineering
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @diegosouzapw · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Windows
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Network behavior: External requests
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview teya.preview

---
name: teya
description: Teya payment integration guide covering POSLink (cloud-based terminal integration), All-In-One (…
category: engineering
runtime: no special runtime
---

# teya output preview

## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.

## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: teya
description: Teya payment integration guide covering POSLink (cloud-based terminal integration), All-In-One (…
category: engineering
source: diegosouzapw/awesome-omni-skill
---

# teya

## When to use
- Teya payment integration guide covering POSLink (cloud-based terminal integration), All-In-One (single-device Android)…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "teya" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | may access external network resources
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Teya payment integration guide covering POSLink (cloud-based terminal integration), All-In-One (single-device Android), E-Commer…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Quick Decision Tree: Which Integration Do You Need?”, “Integration Overview”, “1. POSLink (Cloud Terminal Integration)”, “2. All-In-One Integration”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name teya directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add diegosouzapw/awesome-omni-skill/skills/backend/teya -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
diegosouzapw/awesome-omni-skill
中文

More by @diegosouzapw

Category & tags

Category Engineering

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

Teya Payment Integration Skill

Quick Decision Tree: Which Integration Do You Need?

Integration Overview

1. POSLink (Cloud Terminal Integration)

2. All-In-One Integration

3. E-Commerce API (Online Payments)

4. Payments Gateway API

5. POSLink REST API

Authentication

Test Cards

Important Notes

Amount Format

Currency Format

Environment URLs

Idempotency

Certification Process (POSLink)

Support

File Index

APIs

ePOS SDK

POSLink Guides

Discussion