After payment: the welcome email
Enlarge image Course Enrollment / Payment & Onboarding Automation
AI Mastery Class
Course Website & Automated Student Onboarding
A course enrollment system connecting a custom website, Paystack payment verification, student records and personalized welcome emails.
Portfolio implementation · Project walkthrough and evidence
- Cloudflare Workers
- Cloudflare D1
- Paystack
- Google Apps Script
- Google Sheets
- Gmail
Enlarge image The operational challenge
What needed
to work better.
Enrollment needs more than a checkout button. A successful payment must become a trustworthy enrollment record, followed by clear information about what happens next.
My contribution
I built a course enrollment experience and connected server-side payment verification to student records and personalized onboarding.
The workflow
From first step to follow-through.
- 01Course website
- 02Paystack checkout
- 03Server-side verification
- 04Enrollment record
- 05Google Sheets onboarding
- 06Welcome email
Verified → enrolledA successful payment is checked before onboarding
Verify first. Then enroll and welcome.
Cloudflare Workers verifies payment server-side before the enrollment record is created in D1. A signed Apps Script integration passes the verified information to the Google Sheets onboarding workflow. Duplicate-processing protections prevent the same payment event from creating repeated work. The signature acts as a check that the request came from the expected system; no keys or protected endpoints are displayed.
In motion / recorded demonstration
See the experience.
Read the workflow description
A course enrollment system connecting a custom website, Paystack payment verification, student records and personalized welcome emails.
Course website → Paystack checkout → Server-side verification → Enrollment record → Google Sheets onboarding → Welcome email.
Cloudflare Workers verifies payment server-side before the enrollment record is created in D1. A signed Apps Script integration passes the verified information to the Google Sheets onboarding workflow. Duplicate-processing protections prevent the same payment event from creating repeated work. The signature acts as a check that the request came from the expected system; no keys or protected endpoints are displayed.
Behind the interface
The work underneath.
Enlarge image Functional outcome
A connected operational experience.
The system links the customer-facing enrollment experience with verified records and a personalized welcome email. This is the newer Paystack-based AI Mastery Class, separate from the Base44/Selar NovaSync bootcamp.
Have a similar operational challenge?