What problem does it solve?
Adding payments to a PinMe Worker project requires correctly wiring UniwebPay SDK calls, environment bindings, webhook signature verification, and currency/method constraints — mistakes like blocked webhook routes or forged fulfillment leave orders stuck or insecure.
Core Features & Use Cases
- Payment Flow Generation: Produces Worker code for payment links, products/prices, checkout sessions, subscriptions, refunds, and customers via the @uniwebpay/sdk.
- Webhook Integration: Enforces correct callback URL construction from WORKER_URL, raw-body signature verification with verifyWebhook, idempotency via event.id, and auth-guard exemption for the webhook route.
- Security & Validation Rules: Prevents secret leakage, enforces integer minor-unit amounts, restricts QR methods (wechat/alipay/paynow) to SGD, and blocks fulfillment based on browser redirects.
- Use Case: A user asks an agent to add a paid checkout to their PinMe app; the Skill generates a Worker route that creates a checkout session, persists the order in D1, and fulfills it only after a verified payment.succeeded webhook.
Quick Start
Ask the agent to add a UniwebPay checkout endpoint with webhook-based order fulfillment to your PinMe Worker project.
