wompi-node

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Initialize WompiClient from @pulgueta/wompi. Covers publicKey, privateKey, sandbox flag, the error-first Result<T> tuple [error, data] that every SDK method returns, WompiError subclass narrowing (.type on NOT_FOUND_ERROR / INPUT_VALIDATION_ERROR, .statusCode on request errors), and subpath exports (/server, /schemas). Load when setting up the SDK, configuring API keys, or writing error-handling code.

Go-live checklist for @pulgueta/wompi integrations. Verifies environment variables for publicKey, privateKey, and integrityKey; sandbox vs production URL switching; unique transaction references per charge; amount_in_cents integer precision (never floats, already in cents); and complete error-tuple handling before responding to clients. Includes a full end-to-end card transaction example from client form data through server response. Load before deploying a Wompi integration or reviewing production readiness.

Create, retrieve, and manage Wompi hosted payment links using @pulgueta/wompi. Covers createPaymentLink (name, description, single_use, collect_shipping, amount_in_cents, currency, taxes, customer_data, redirect_url), getPaymentLink (no auth required), updatePaymentLink to activate/deactivate, Tax union (TaxByAmount with amount_in_cents, TaxByPercentage with percentage 1–50), and CustomerReference constraints (max 2, label max 24 chars). Load when building hosted checkout pages or no-code payment collection.

Create and retrieve reusable Wompi payment sources using @pulgueta/wompi. Covers createPaymentSource (CARD or NEQUI, requires acceptance_token and privateKey), getPaymentSource, PaymentSourceStatus (AVAILABLE/PENDING), and charging a customer via payment_source_id in createTransaction. Load when building recurring billing, saved payment methods, or subscription flows.

Wire @pulgueta/wompi into a Hono or Elysia backend. Covers importing Zod schemas from @pulgueta/wompi/schemas for route-level request validation, processing a Wompi transaction inside a server handler, persisting transaction results (id, status, reference, amount_in_cents) to a database before responding, and mapping WompiError subclasses to HTTP error responses. Load when integrating the SDK into a server framework or adding payment endpoints to an existing backend.

Full Wompi transaction lifecycle using @pulgueta/wompi. Covers getMerchant for acceptance_token, tokenizeCard and tokenizeNequi, getSignatureKey for SHA-256 integrity signature (amountInCents as-is, never multiplied), createTransaction with payment_method or payment_source_id, getTransaction, listTransactions with from_date/until_date/status filters, voidTransaction with nested data.transaction result, and pse.getFinancialInstitutions. Load when processing payments, tokenizing cards, computing signatures, or querying transaction history.