The First Real Bill

The first money decision was not a dramatic one.

There was no big invoice. No fancy software package. No moment where I had to take out a credit card and stare at a monthly fee.

It was Stripe.

Technically, adding Stripe to the site was “free.” The AI wired the checkout into Beads of Hope T1D without me paying anything upfront. It built the shop, the cart, and the path where someone could choose a bracelet or badge reel and check out like this was a real store.

But then came the part I could not pretend was just playing around anymore.

Activating the real Stripe account.

That meant business information. Bank information. Two-factor authentication (that extra security step where they send you a code or make you verify it is really you). Real details. Real money going somewhere. Real orders possibly coming in.

And I remember thinking, am I really doing this?

Up until then, so much of the project still felt like a very intense experiment. A meaningful experiment, yes, because this whole thing is for my son. He was diagnosed with Type 1 Diabetes when he was two, and Beads of Hope T1D is my way of trying to make something good and useful out of that experience.

But it was still happening on a screen.

I could ask the AI to build a shop page. I could spend a ridiculous amount of time moving a blue ribbon down a quarter inch. I could ask for the heart symbol to sit closer to the crossover point. I could add white shading behind “T1D Hope” and then fuss over whether badge reel photos should zoom in three times or two times.

Those things made me feel particular, maybe even a little obsessive.

Stripe made me feel responsible.

Because once I connected the bank account, I was not just making a pretty website. I was creating a place where someone could trust me with their order. Their payment. Their shipping address. Their expectation that the thing they bought would actually arrive.

That is a different kind of pressure.

I also had to start thinking about shipping and tax, which are two words that can drain the joy out of almost anything. I do not mean that dramatically. I mean I was sitting there, a 50-year-old non-technical person, looking at settings and requirements and thinking, “There are probably twelve ways to mess this up.”

And then there was the security scan.

At one point, the scanner flagged nine issues with names that sounded like they belonged in a crime show. “Guest cart hijacking.” “Client-controlled unit price.” “RLS policies too loose.” RLS, I learned, means row-level security, which is basically database rules for who can see or change what.

I understood maybe 40% of it.

Maybe.

The AI fixed them and re-ran the scan, but it still made the money part feel heavier. If people were going to pay through this site, then I needed the site to behave like a grown-up.

That was the argument I used with myself.

I told myself: if this is for my son, and if this is for Type 1 Diabetes awareness, then I have to let it become real at some point. I cannot keep it forever in the safe little world of previews and test buttons.

I also told myself that the first real order was allowed to feel enormous.

Because it does.

Even now, the store is live-ready. Payments, shipping, tax, transactional emails, loyalty points — all of that is wired. The code-side work is basically done. What is still on me is the human part: activating Stripe live, connecting the bank, connecting social media, and pressing publish.

Funny how the AI could build twenty-two database tables in about twenty minutes, but it cannot click “I agree” for me.

That click belongs to me.

And honestly, that is probably why it felt like the first real bill, even if it was not a bill in the normal sense. It was the first time I had to agree to being responsible for the thing I had asked to be built.

Small takeaway: free tools can still come with a very real emotional cost.