paynow

Integrate PayNow Taiwan payment and E-Invoice APIs into WooCommerce.

17|5|Updated Aug 7, 2023
One-click install
npx skills add https://github.com/zenbuapps/woomp --skill paynow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paynow
Source: https://github.com/zenbuapps/woomp/tree/main/.claude/skills/paynow
Command: npx skills add https://github.com/zenbuapps/woomp --skill paynow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves the complexity of integrating PayNow's three distinct API systems, preventing common errors in authentication, encryption, and webhook handling for WooCommerce developers.

Core Features & Use Cases

  • Multi-System API Reference: Provides clear, separated documentation for REST API (PaymentIntent), Legacy CashFlow (etopm.aspx), and E-Invoice services.
  • Security & Encryption: Includes verified implementations for HMAC-SHA256, AES256 (CBC/Zeros), TripleDES, and SHA-1 PassCode generation.
  • Use Case: When building a new WooCommerce payment gateway, use this Skill to correctly implement the PaymentIntent flow and verify incoming payment webhooks using the merchant's PrivateKey.

Quick Start

Use the paynow skill to generate the correct HMAC-SHA256 signature for a payment webhook payload using the merchant private key.

Frequently Asked Questions about paynow

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

FAQPage Schema
How do I integrate Taiwan PayNow e-invoice and payment gateway APIs into WooCommerce?

To integrate Taiwan PayNow e-invoice and payment gateway APIs into WooCommerce, use this Skill to handle the distinct authentication, encryption, and webhook verification requirements for REST, Legacy CashFlow, and E-Invoice API systems.

What's the best way to generate an HMAC-SHA256 signature for a PayNow payment webhook?

The best way to generate an HMAC-SHA256 signature for a PayNow payment webhook is to use the merchant's PrivateKey to validate the incoming payload, ensuring correct implementation of the PaymentIntent flow.

How does AES256-CBC encryption work for PayNow Taiwan API authentication?

AES256-CBC encryption for PayNow Taiwan API authentication works by applying verified implementations alongside TripleDES and SHA-1 PassCode generation to secure data transmitted across their distinct API systems.

Do I need a separate implementation for the PayNow Legacy CashFlow API versus the REST API?

Yes, you need a separate implementation for the PayNow Legacy CashFlow API versus the REST API because they have distinct authentication, encryption, and webhook verification requirements, including different endpoints like etopm.aspx and PaymentIntent.

Why does my PayNow WooCommerce integration fail webhook verification?

Your PayNow WooCommerce integration fails webhook verification when the HMAC-SHA256 signature validation is incorrectly implemented, often due to errors in applying the merchant PrivateKey to the payment payload.

Can I use the PayNow Skill for both payment processing and electronic invoicing?

Yes, you can use the PayNow Skill for both payment processing and electronic invoicing, as it provides multi-system API references covering the REST PaymentIntent workflows and E-Invoice services.