← Resources

The parts of a site where a mistake costs.
Done right, and checked from outside.

Payments with the price set by the server and a webhook that records once, share cards and videos generated on the fly, a link-in-bio on your domain counting clicks without cookies. Each part tested before real money and checked on the live site after every deploy.

Get the free guideTwo ways ↓
Real case3 sites checkedPaymentstest mode firstForClaude or ChatGPT

What a hard part costs.

Public ranges for integrating Stripe into a site, and the launch price of our service for one part.

Range source: projectcostestimator.com (16 Jun 2026), read 8 Oct 2026. Bars not to scale.

One recipe. One test. One check.

The part
Payments, share cards and videos, or link-in-bio: the parts where a mistake costs money or trust.
↓
The recipe
The rules that are not negotiable: the server sets the price, the signed webhook records once, a number is rounded once.
↓
The test
Everything in test mode, end to end, with the checklist ticked before real money.
↓
The review
Three lenses: payments, security, abuse and costs. What stays open is written down.
↓
The check
From outside, on the live site, after every deploy: HTTPS, headers, sharing tags, speed, webhook.

Two ways.

Do it with your AI agent, or I build it on your site.

The kit

Do it yourself

$19

→The ready folder: open it with your agent (Claude or ChatGPT), write "help me with my site's payments" and it builds it.
→The payments recipe with the checklist before real money.
→The recipes for on-the-fly cards and videos and for link-in-bio with counted clicks.
→The outside check: HTTPS, headers, tags, robots, speed, webhook.
→15-page full guide, in English and Italian.
Get the kit

The service

I do it for you

€490 €890

→One hard part built on your site.
→Tested in test mode with the checklist ticked.
→Review of payments, security, abuse, and the list of what stays open.
→Outside check and report. If you have the kit, its $19 comes off.
Tell me about your site

Launch price.

Before buying, read the free guide.

9 pages: the problem, what it costs, the method, the three parts, a case with three sites, real mistakes, the limits. Enough to know what to ask whoever builds your site.

Get the free guide

What you are probably thinking.

"Does it work with my site?"

The recipes apply to Next.js, Astro or serverless functions on Vercel and Netlify; the outside check to any public site.

"What if it gets money wrong?"

It always starts in test mode, with a list of tests: double webhook, unsigned webhook, tampered amount, orphan payment. Live keys come only after your OK.

"What does the check find?"

HTTPS, security headers, sharing tags and image, robots and sitemap, speed, and whether the webhook refuses unsigned calls. On my three sites it found two headers missing on all.

"Does it do the design?"

No: it does the technical parts where a mistake costs. Design and copy stay with whoever designs the site.

"Do I need to code?"

No. Your AI agent, Claude or ChatGPT, uses the kit on your site's code; you answer the questions and approve.

Where it comes from.

These are the parts I built on my own sites: a site selling ad spots with Stripe, a satirical counter with cards and videos generated for every share, the lucasgrilli.com link-in-bio counting clicks without cookies. On 8 October the outside check found two security headers missing on all three.

Read more: Stripe webhook: the rules that stop paid orders from getting lost.