StartingLineProductions.com/startinglineproductions.com-bizopprodplan
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

STLP: update website tech plan to use Hyperswitch (self-hosted) with Stripe as initial PSP

Browse Source
This commit is contained in:
Charles N Wyble - admin
2025-09-12 10:53:32 -05:00
parent 97bf315bde
commit 863b37b460
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
src/stlp/website-tech-plan.md
View File

@@ -7,8 +7,8 @@ Phase 0 (same day)
- Domain: confirm and point DNS.
- Single-page site: static page (e.g., simple HTML/Bootstrap or lightweight Astro/Vite) deployed on your existing infra.
- Intake: embedded Typeform/Tally (file upload enabled) or simple HTML form to inbox.
- Payments: Stripe Payment Links for 3 starter SKUs; add “custom quote” CTA.
- Analytics: Matomo tag + a basic goal (form submitted / payment link click).
- Payments: Hyperswitch (self‑hosted) using Stripe as the initial processor. Expose simple “Pay Now” links or a minimal checkout that creates a payment intent via Hyperswitch and redirects to card entry.
- Analytics: Matomo tag + a basic goal (form submitted / checkout start / success).
Phase 1 (week 2)
- Add product tiles (entry/core offers) with price ranges, FAQs, materials allowed/disallowed.
@@ -16,10 +16,17 @@ Phase 1 (week 2)
- Add gallery from portfolio folder.
Phase 2 (weeks 3–4)
- Migrate to a simple storefront if needed: Shopify or a static-site + Snipcart/Stripe checkout.
- Migrate to a simple storefront if needed: keep self-hosting; use static site + Hyperswitch checkout or a lightweight headless cart.
- File handling: gated upload after order (order # + file link) to reduce spam.
- CRM: push leads/orders to Dolibarr (optional if it slows us down).
Hyperswitch MVP Architecture
- Host Hyperswitch (Docker) behind your existing reverse proxy. Configure OIDC admin access.
- Processors: start with Stripe credentials; expand to additional PSPs later. Routing stays in Hyperswitch.
- Server endpoint: tiny service to create payment intents via Hyperswitch API for fixed SKUs and custom quotes.
- Client: simple button → calls server → redirects to Hyperswitch-hosted entry or embeds minimal card form.
- Events: record checkout start/success to Matomo with order/quote IDs.
SEO/Local
- Google Business Profile: ensure NAP consistent with site footer; add UTM links.
- On-page basics: title/description, H1 for “Custom laser, embroidery, CNC in Pflugerville, TX”.