ezPay E-Invoice Methodology

When to use this skill

• Issuing B2B or B2C 統一發票 from a Taiwan storefront, POS, or SaaS backend through ezPay (藍新系) as the 加值服務中心
• Attaching a consumer carrier — 手機條碼 (/XXXXXXX), 自然人憑證, or 會員載具 — so the invoice is not printed on paper
• Voiding a wrongly-issued invoice within the same bimonthly period, or issuing an allowance (折讓) when the void window has closed
• Issuing or triggering a scheduled invoice (status="3") that must go live on a later date (e.g., subscription renewal)
• Reconciling ezPay-issued invoices against the 財政部電子發票整合服務平台 daily to catch upload lag or dropped records
• Debugging opaque ezPay responses: LIB10002 encryption failures, INV20002 void-window errors, ALW10001 allowance-over-invoice errors

Do NOT use when

• The merchant connects to the 財政部 platform directly (no 加值中心) — use tw-einvoice-guide for the MOF-direct pattern and concepts
• The storefront is on UniversalEC (統一發票整合服務) or another 加值中心 (ECPay 綠界, 銓葳) — they have different tool shapes; this skill's gotchas are ezPay-specific
• You only need the API schema for one ezPay endpoint — read the tool description in mcp-ezpay-einvoice or the ezPay developer portal at https://inv.ezpay.com.tw/
• The question is "what is a 手機條碼" or "B2B vs B2C invoice format" — that is foundational material already covered by tw-einvoice-guide. This skill assumes you know the landscape

Core concepts