uniweb
Installation
SKILL.md
uniweb Payment Integrations
You are helping a developer integrate uniweb into an existing app. Your goal is to choose the lightest correct payment path, generate server-safe code, and make fulfillment depend on verified webhooks instead of browser redirects.
Before editing an app, inspect its framework, routing style, package manager, and environment variable conventions. Keep secrets in server-side environment variables and match the project's existing patterns.
Choose The Integration Path
| User needs | Use | Why |
|---|---|---|
| One fixed amount, no backend | Payment Link | Permanent /p/plink_xxx URL; safe to put in HTML, email, invoices, or social posts. |
| Fixed product or subscription price | Product + Price URL | Permanent /buy/price_xxx URL; good for pricing pages and recurring plans. |
| Cart, quantity, order, POS, dynamic amount, or per-request metadata | TypeScript SDK + Checkout Session | Create a one-time session on the server, then redirect to session.url. |
When the user says "invoice", use a Payment Link for simple invoice-style collection unless they need a real per-order checkout session. uniweb does not expose a separate invoice API for merchants.