skills.rest
Moksa1123
Moksa1123COMMUNITY
Explore all skills by this author →
WebsiteGitHub

taiwan-invoice

Integrate Taiwan e-invoice APIs for B2C and B2B issuance across providers.

43|9|Updated Jan 28, 2026
Search Tags:#automation#integration#CLI#multi-provider#invoice#e-invoice#provider-factory
One-click install
npx skills add https://github.com/Moksa1123/taiwan-ecommerce-toolkit --skill taiwan-invoice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taiwan-invoice
Source: https://github.com/Moksa1123/taiwan-ecommerce-toolkit/tree/main/taiwan-invoice
Command: npx skills add https://github.com/Moksa1123/taiwan-ecommerce-toolkit --skill taiwan-invoice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pycryptodome, requests, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill enables seamless automation of Taiwan e-Invoice API integration across multiple providers (ECPay, SmilePay, Amego), reducing manual setup and boilerplate.

Core Features & Use Cases

  • Unified multi-provider support for B2C and B2B invoice issuance, printing, and allowances.
  • Provider-aware workflow using a service factory to choose the correct backend at runtime.
  • Operational guidance with API references and code examples to accelerate integration.

Quick Start

Use the taiwan-invoice skill to generate test code for a B2C scenario (TotalAmount 1050) with ECPay, BuyerIdentifier 0000000000, and a single ProductItem. Then try a B2B flow by issuing a total of 1050 with SalesAmount 1000 and TaxAmount 50.

Frequently Asked Questions about taiwan-invoice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate multiple Taiwan e-invoice providers without writing separate API logic?▼

Taiwan e-invoice integration uses a provider service factory to dynamically select ECPay, SmilePay, or Amego backends at runtime, abstracting provider-specific differences for B2C and B2B issuance.

What is the difference between B2C and B2B e-invoice issuance in Taiwan?▼

B2C e-invoice issuance requires a BuyerIdentifier like 0000000000 with a TotalAmount, while B2B issuance splits amounts into SalesAmount and TaxAmount for tax reporting purposes.

How to automate Taiwan e-invoice API signing and encryption across different gateways?▼

Automate Taiwan e-invoice API encryption and signing by using built-in cryptographic handlers that format payloads according to each provider's specific security requirements.

Does this e-invoice integration support printing and allowance workflows?▼

Taiwan e-invoice integration supports complete operational workflows including invoice issuance, printing, and allowances for both B2C and B2B scenarios across multiple providers.

What dependencies do I need for Taiwan e-invoice API automation?▼

Taiwan e-invoice API automation requires the pycryptodome library for encryption and signing operations, and the requests library for HTTP API communication with providers.

Can I switch between ECPay and SmilePay e-invoice APIs at runtime?▼

Switching between ECPay and SmilePay e-invoice APIs is handled dynamically at runtime by the service factory, which selects the correct backend based on your specified provider.

Related Skills

Explore More Software Engineering Skills→
dascarddascard
2

image-generation-diagnostics

Diagnose image_generation tool chain failures by validating network connectivity, API authentication, and model responses.

Community
Advanced
NaveedTechLabNaveedTechLab
11

odoo-mcp-server

Automate Odoo accounting operations with human-in-the-loop approval controls.

Community
Advanced
RytassRytass
6

invoice-adapters

Integrate Taiwan e-invoice services across ECPay, EZPay, BankPro, and Amego via a unified adapter interface.

Official
Intermediate
merge-apimerge-api
1

Migrate Direct Provider SDKs to Merge Gateway

Migrate OpenAI, Anthropic, and Google SDK usage to Merge Gateway.

Official
Advanced