Agente Pagokit

The agent that picks and implements the right payment method for your app — from your terminal, with Claude Code.

tododeia.com · @soyenriquerocha · enrique@tododeia.com

🇪🇸 Leer en español · 📖 About · 🗺️ Coverage

---

Why it exists.

Every guide frames payment integration as a choice problem: thirty gateways, pick one. Choosing takes an afternoon. What takes weeks — and what silently fails in production — is everything after:

• A webhook that verifies a signature but never checks a timestamp, so a captured event is replayable forever.
• A webhook verified against the API key instead of the signing secret. It fails every event, and the developer goes off to debug the hashing algorithm.
• amount * 100 on a Japanese customer. JPY has no minor unit, so that is a 100× overcharge.
• A refund endpoint on a Pix integration, where refunding a charge is not an operation that exists.
• A payment_intent.succeeded handler that grants access, on a URL anyone can post to.

None of these throw. Most pass code review. PagoKit exists to make them hard to write.

It analyses your project, asks three questions, and generates a vertical-complete integration: frontend, checkout endpoint, authenticated webhook, database migration, customer portal, refund path, error mapper, production checklist and an audit trail.

Everything runs locally. No account, no API key, no telemetry. The only network calls are the ones your generated code makes to your own provider.

---

Three deterministic engines.

An LLM asked to write payment code produces something plausible. Plausible is exactly the failure mode that matters here. So the parts that must be correct aren't left to the model — they're ordinary programs, with tests.

	What it does	Why it isn't the model's job
Validators	Node checks on PreToolUse / PostToolUse hooks that block an insecure write	The model cannot argue with a non-zero exit code
Advisor	scripts/advise.js — a pure function from situation to ranked providers	Same input, same answer, every rejection carries its reason. "Why not X?" has an exact answer
Signer	scripts/sign-event.js — generates a validly signed event for any provider	Testing a handler means a valid event accepted, a forged one rejected, a replayed one rejected

---

What it knows.

42 providers · 136 payment methods · 74 countries (71 with a local provider) · 106 currencies with their ISO 4217 exponent · 6 webhook verification families in use.

What PagoKit writes for you

Provider	Level	Role	Buyer coverage	Subscriptions	MoR	Onboarding
Lemon Squeezy	full build	mor	Global	✓	✓	application_review
Mercado Pago	full build	psp	AR · BR · CL · CO · MX · PE · UY	✓	—	self_serve
Stripe	full build	psp	US · CA · UK · EU · MX · BR · SG · AU · …	✓	—	self_serve
Wompi	full build	acquirer	CO	—	—	application_review

What PagoKit knows and recommends, but doesn't write