Build autonomous AI features using the Polsia Agent API only; never call model providers directly for product AI.
3 installs
Security
Polsia Stripe Payments
Try itAccept payments via Stripe Connect payment links, then verify server-side — no Stripe SDK, no webhooks, no STRIPE_SECRET_KEY.
What it does
Accept payments on a Polsia-built site via Stripe Connect payment links, then verify them server-side — no Stripe SDK, no webhooks, no STRIPE_SECRET_KEY.
The skill document
Stripe Payments
Accept card payments through the company's auto-provisioned Stripe Connect account. You create payment links with MCP tools, then verify completed payments server-side. No Stripe SDK, no webhook setup, no STRIPE_SECRET_KEY.
How the money works
Every company has a Stripe Connect (Express) account. Polsia takes 20% platform fee, company keeps 80% (minus Stripe processing fees). Payouts are daily to their bank.
The account is RESTRICTED until owner finishes Stripe onboarding on the Polsia Payments page. Until then it cannot take payments.
NO bring-your-own-Stripe. Do NOT set STRIPE_SECRET_KEY, do NOT npm install stripe, do NOT build webhooks.
1. Create Payment Link
Call the MCP tool with name, amount, and success_url pointing at YOUR app with {CHECKOUT_SESSION_ID} placeholder.
Always pass success_url. Without it, the buyer is redirected to Polsia, not your app.
One-time fixed price: create_payment_link. Recurring: create_subscription_link.
2. Success Page — Poll, Don't Verify Once
The payment record is written asynchronously (Stripe to Polsia webhook, ~1s+ after redirect). A single synchronous verify on the success page usually returns verified:false. Render a loading page and poll every 1500ms up to 10 times.
3. Verify Server-Side
GET process.env.POLSIA_API_BASE_URL + '/api/company-payments/verify?session_id=' + sessionId Auth: Authorization: Bearer process.env.POLSIA_API_KEY
Use POLSIA_API_BASE_URL (NOT POLSIA_API_URL which points at AI proxy). Make fulfillment idempotent, keyed on sessionId.
DO NOT
- Set STRIPE_SECRET_KEY or install Stripe SDK
- Use POLSIA_API_URL for payment endpoints
- Verify only once on success page — poll
- Hardcode buy.stripe.com links
Related skills
Upload and manage files through Polsia's Cloudflare R2 proxy with authenticated API requests.
Builds and debugs Stripe integrations: payments, subscriptions, Checkout, invoices, webhooks, Connect, disputes, tax. Use when a charge, refund, payout or subscription behaves wrong, when a webhook never arrives or its signature fails, when a card is declined or stuck on 3D Secure, when a customer was billed twice or the amount came out 100x off, when proration, trials, dunning or a plan change has to be exactly right, when splitting money across a marketplace with Connect, when disputes, chargebacks or fraud rules need work, when the payout does not match the bank, or when moving from test mode to live. Covers Payment Intents, Checkout Sessions, Payment Links, the Billing Portal, metered and tiered pricing, Stripe Tax, Radar, test clocks, idempotency, API versioning, and reconciliation. Not for choosing which payment provider to use (`payments`), PayPal integrations (`paypal`), App Store and Play Store purchases (`in-app-purchases`), or tracking the subscriptions you pay for as a cons
10 installs
Integrate Stripe Identity safely through Pontx. Use for VerificationSessions, document, selfie, or ID-number checks, webhooks, retries, sensitive results, cancellation, or redaction.
1 installs
Safely inspect Stripe payments, customers, invoices, and subscriptions
21 installs
Stripe payments, subscriptions, invoicing, refunds, disputes, and balance — full read/write for customers. Use when an agent needs stripe, stripe direct connection, launch saas subscription billing with recurring prices and hosted payment links, automate customer onboarding and crm to stripe sync, generate stripe checkout payment links for e commerce orders, run customer support refund workflows with reason tracking, cancel subscription, subscription through AgentPMT-hosted remote tool calls.
1 installs