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-integrationfor gateway comparisontw-ecom-payment-disputefor refund / chargeback handling
Last verified: 2026-04