API测试
- 作者仓库星标 39
- 作者更新于 实时读取
- 作者仓库 awesome-omni-skill
- 领域
- 工程开发
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @diegosouzapw · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- Windows
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: teya
description: Teya payment integration guide covering POSLink (cloud-based terminal integration), All-In-One (…
category: 工程开发
runtime: 无特殊运行时
---
# teya 输出预览
## PART A: 任务判断
- 适用问题:代码实现、重构、调试或代码审查。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于代码实现、重构、调试或代码审查,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、会按任务需要访问外部网络、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: teya
description: Teya payment integration guide covering POSLink (cloud-based terminal integration), All-In-One (…
category: 工程开发
source: diegosouzapw/awesome-omni-skill
---
# teya
## 什么时候使用
- 用于组织测试、定位失败并形成修复闭环 适合处理工程开发场景下的代码实现、调试、重构、测试或代码审查,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需…
- 面向代码实现、重构、调试或代码审查,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "teya" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Quick Decision Tree: Which Integration Do You Need? / Integration Overview / 1. POSLink (Cloud Terminal Integration)
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 会按任务需要访问外部网络
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} 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:
- ePOS SDK Overview
- POSLink Getting Started
- POSLink Overview
- POSLink Design
- POSLink Testing
- POSLink FAQ
- POSLink Certification
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:
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:
- 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
APIs
- references/apis/payments-overview.md - Payments Gateway API
- references/apis/poslink-api.md - POSLink REST API
- references/apis/e-commerce-introduction.md - E-Commerce APIs
- references/apis/test-cards.md - Test card numbers
ePOS SDK
- references/epos-sdk/overview.md - SDK overview and integration options
- references/epos-sdk/glossary.md - Terminology
- references/epos-sdk/poslink-getting-started.md - POSLink quick start
- references/epos-sdk/all-in-one-introduction.md - All-In-One integration
POSLink Guides
- references/poslink/overview.md - POSLink overview
- references/poslink/design.md - Integration design
- references/poslink/test.md - Testing guide
- references/poslink/faq.md - Frequently asked questions
- references/poslink/get-certified.md - Certification process
- references/poslink/integration-checklist.md - Pre-launch checklist
- references/poslink/cancel-payment-request.md - Cancel payments
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核