ECPay B2C E-Invoice

When configured, eligible paid orders can be issued by the system

Pain points

• Peak-hour manual invoices slow the counter line
• Typed tax IDs and carriers get rejected
• Payments and invoices live in different systems

Capabilities

• ECPay B2C (VDINE proxy issue)
• Mobile carrier / donation
• Tied to VDine orders and payments
• Retry and lookup in Hub
• Less counter manual entry

1. Connect ECPay B2C Confirm plan ecpayEInvoiceEnabled; choose VDINE in Hub and enter ECPay credentials (online B2C setup often needs track/number allocation); run test issues.
2. Issue on eligible paid orders Not every order complete auto-issues—paid-order rules apply. Default SHOP_SELF does not platform-issue for the shop.
3. Support mobile carrier and donation Guests enter carrier at checkout—less paper.
4. Hub retry and void Central handling for failures and voids reduces tax risk.

FAQ

Do I need a new POS for e-invoice?

No. With plan and VDINE mode ready, VDine can issue on eligible paid orders; if POS also invoices, plan roles to avoid duplicates.

Do you support B2B tax IDs?

Guest checkout supports company tax ID and related invoice fields; this module focuses on ECPay B2C issuance, and a full B2B e-invoice product path may still be limited—confirm in Hub settings and your plan.