Saucebox Registry
← Browse

@asgard-ai-platform/tw-ecom-payment-tappay

A

Integrate TapPay for Taiwan e-commerce — TapPay Web/iOS/Android SDK, 3DS 2.0 flow, Apple Pay / Google Pay / LINE Pay integration via TapPay, TCS (TapPay Card Service) for tokenized recurring payments. Use when TapPay is chosen as PSP, comparing TapPay vs NewebPay, or debugging 3DS flows. Do NOT use for other gateways. STATUS: SKELETON — body pending.

skillclaude

Install

agr install @asgard-ai-platform/tw-ecom-payment-tappay --target claude

Writes 1 file into .claude/skills/, pinned to git-856b4569.

  • .claude/skills/tw-ecom-payment-tappay/SKILL.md

Document

name: "tw-ecom-payment-tappay" description: "Integrate TapPay for Taiwan e-commerce — TapPay Web/iOS/Android SDK, 3DS 2.0 flow, Apple Pay / Google Pay / LINE Pay integration via TapPay, TCS (TapPay Card Service) for tokenized recurring payments. Use when TapPay is chosen as PSP, comparing TapPay vs NewebPay, or debugging 3DS flows. Do NOT use for other gateways. STATUS: SKELETON — body pending." metadata: category: "WP-05 台灣創業" domain: "ecommerce-tw" layer: "payment" related_mcps: [] related_skills: ["tw-payment-integration", "tw-ecom-payment-newebpay", "tw-ecom-payment-dispute"] last_verified: "2026-04" status: "skeleton" tags: ["taiwan", "payment", "tappay", "fintech"]

TapPay Integration for Taiwan E-Commerce

STATUS: SKELETON — body pending.

When to use this skill

  • Integrating TapPay Web/iOS/Android SDK
  • Adding Apple Pay / Google Pay / LINE Pay via TapPay
  • Implementing TCS (tokenized recurring payments)
  • Debugging 3DS 2.0 flow issues on TapPay
  • Comparing TapPay vs NewebPay / ECPay for a specific use case

Do NOT use when

  • Generic TW payment gateway selection → tw-payment-integration
  • Non-TapPay provider → their specific skill

Core concepts

TODO: TapPay positioning (mobile-first), TapPay Direct vs TapPay Pay by Prime, TCS flow.

Decision tree

TODO: when TapPay outperforms NewebPay/ECPay.

Implementation guidance

TODO: Prime token acquisition, 3DS handling, TCS card binding + charge.

Gotchas

TODO: 5-6 pitfalls (Prime token TTL, 3DS interstitial UX, TCS unbind on card expiry, Apple Pay domain verification, sandbox-to-prod merchant switch).

IRON LAW

TODO.

Output Format

TODO.

Related

  • tw-payment-integration for gateway comparison
  • tw-ecom-payment-dispute for refund / chargeback handling

Last verified: 2026-04

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-856b45691c712026-07-31