payuni

Guide PAYUNi integration setup and route to checkout, query, or webhook flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers configure PAYUNi integration by guiding environment setup and directing users to the appropriate integration flow for checkout, query, or webhook handling.

Core Features & Use Cases

  • Guided environment setup: Walks users through configuring required environment variables (PAYUNI_MERCHANT_ID, PAYUNI_HASH_KEY, PAYUNI_HASH_IV) and exposing them securely in the project.
  • Integration routing guidance: Determines whether the user needs a checkout, query, or webhook integration and points to the correct Skill paths.
  • Environment awareness: Provides base API endpoints for test and production to avoid misconfigurations and ensure correct routing.

Quick Start

Set up environment variables (PAYUNI_MERCHANT_ID, PAYUNI_HASH_KEY, PAYUNI_HASH_IV) in your project and ask Claude to route you to the appropriate integration flow (/payuni-checkout, /payuni-query, or /payuni-webhook).

Frequently Asked Questions about payuni

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

FAQPage Schema
How do I configure PAYUNi environment variables for payment integration?

PAYUNi payment integration requires configuring three core environment variables: PAYUNI_MERCHANT_ID, PAYUNI_HASH_KEY, and PAYUNI_HASH_IV. These credentials securely expose your merchant account and enable API authentication for payment processing.

What is the difference between PAYUNi test and production API endpoints?

PAYUNi integration provides distinct base API endpoints for test and production environments. This separation prevents misconfigurations and ensures developers route payment requests to the correct environment during development and deployment.

How do I choose between checkout, query, and webhook integration paths for payments?

Choosing the right payment integration path depends on your use case: use checkout for initiating payments, query for verifying transaction status, and webhook for receiving asynchronous payment notifications. The skill routes you to the correct flow.

Can I use PAYUNi integration for both test and production environments safely?

Yes, PAYUNi integration supports both test and production environments safely. The skill provides environment awareness with specific base API endpoints to prevent misconfigurations and ensure correct routing across different deployment stages.

Why does my PAYUNi payment integration require a hash key and hash IV?

PAYUNi payment integration requires a hash key and hash IV to encrypt and verify API requests. These credentials ensure data integrity and secure communication between your application and the PAYUNi payment gateway.

What's the best way to set up a PAYUNi webhook for payment notifications?

The best way to set up a PAYUNi webhook is to configure your environment variables first, then ask the skill to route you to the /payuni-webhook integration flow, which handles asynchronous payment notification processing securely.