newebpay-checkout

Automate NewebPay MPG checkout with AES-256 encryption and SHA-256 signing.

271|18|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/paid-tw/skills --skill newebpay-checkout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: newebpay-checkout
Source: https://github.com/paid-tw/skills/tree/main/plugins/newebpay/skills/newebpay-checkout
Command: npx skills add https://github.com/paid-tw/skills --skill newebpay-checkout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the integration of the NewebPay MPG checkout flow for developers by providing a clear structure to build the encrypted TradeInfo, TradeSha, and the front-end form, then handle callbacks reliably.

Core Features & Use Cases

  • AES256 encryption and SHA256 signing for secure payment requests.
  • Form-based submission to the MPG gateway with ready-to-use payloads.
  • Callback handling for NotifyURL and ReturnURL to update order status in your app.
  • Quick-start patterns for Laravel, Node.js, or Python backends to accelerate rollout.

Quick Start

Use the newebpay-checkout skill to generate a ready-to-submit payment form for an order, encrypt TradeInfo with AES256, compute TradeSha, and post to the MPG gateway.

Frequently Asked Questions about newebpay-checkout

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

FAQPage Schema
How do I encrypt TradeInfo for NewebPay MPG checkout integration?

To encrypt TradeInfo for NewebPay MPG checkout, you must apply AES-256-CBC encryption using your HASH_KEY and HASH_IV, then compute a SHA-256 signature for TradeSha to securely submit the payment form payload.

How do I handle NotifyURL and ReturnURL callbacks in a NewebPay MPG integration?

Handling NewebPay MPG callbacks requires configuring NotifyURL and ReturnURL endpoints to receive the encrypted response payloads, decrypt the TradeInfo, and update your application's order status accordingly.

Can I use this NewebPay MPG checkout integration with Laravel, Node.js, or Python backends?

Yes, the NewebPay MPG checkout integration provides quick-start patterns specifically designed for Laravel, Node.js, and Python backends to accelerate your payment gateway rollout across different frameworks.

What environment variables do I need to configure for NewebPay MPG payment form submission?

NewebPay MPG payment form submission requires proper configuration of MERCHANT_ID, HASH_KEY, and HASH_IV environment variables to securely generate the encrypted TradeInfo and TradeSha payloads.

What is the difference between TradeInfo and TradeSha in NewebPay MPG payment requests?

TradeInfo is the AES-256-CBC encrypted string containing your order data, while TradeSha is the SHA-256 hashed signature of that encrypted string, used by NewebPay to verify the integrity of the MPG payment request.