teya_skill

This skill guides integration with Teya payment ecosystem across POSLink All-In-One E-Commerce APIs and Payments Gateway.

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill majncz/teya-skill --skill teya

  • SKILL.md8.4 KB

Overview

This skill is a practical integration guide for Teya payment solutions covering POSLink (cloud terminal), All-In-One Android terminals, E‑commerce APIs (hosted checkout, payment links, direct processing), and the Payments Gateway. It consolidates decision trees, authentication patterns, test cards, environment URLs, idempotency guidance, and certification steps to speed up implementation and certification.

How this skill works

The guide helps you choose the correct integration path (separate ePOS + terminal, single-device Android, or online payments) and provides concrete steps to register, obtain credentials, and integrate SDKs or APIs. It explains OAuth 2.0 flows, token lifetimes for staging and production, how to format amounts and currencies, use test cards, and follow the POSLink certification checklist.

When to use it

  • Use POSLink when your ePOS runs on a separate device from the payment terminal (Android/Windows).
  • Use All‑In‑One when your ePOS and terminal share the same Android device (Sunmi, PAX).
  • Use Hosted Checkout for a quick, secure redirect-based online payment flow for most merchants.
  • Use Payment Links to request remote payments via email or SMS without a full checkout integration.
  • Use Direct Processing or Payments Gateway for PCI-compliant systems that require full control over transactions.

Best practices

  • Register partner and store accounts early and create OAuth apps to obtain client credentials before development.
  • Use Idempotency-Key headers for all transaction requests to avoid duplicate charges.
  • Keep staging and production credentials, domains, and token lifetimes separate; test cards only work in staging.
  • Send webhooks for asynchronous payment status updates and validate signatures where provided.
  • Follow the POSLink certification checklist: design, develop, test thoroughly, then schedule certification.

Example use cases

  • Retail chain: integrate POSLink so a tablet-based POS triggers payments on standalone terminals.
  • Quick-serve restaurant: implement All‑In‑One on Sunmi devices to run POS and terminal on one Android unit.
  • Online store: implement Hosted Checkout to redirect customers to Teya’s secure payment page with minimal PCI scope.
  • Service provider: send Payment Links for remote invoice collection via SMS or email.
  • Marketplace platform: use Payments Gateway and webhooks to manage captures, refunds, and MOTO flows programmatically.

FAQ

POSLink uses Device Code Flow; create an OAuth app in the partner portal and obtain client credentials.

Where do I find test card numbers and do they work in production?

Test card numbers are provided in the guide for staging only; they will not work in production.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational