Stripe Checkout + SetupIntent + Scheduled Charges (Zapier/Sheets + Python) — Healthcare, Surcharging
Title:
Stripe Checkout + SetupIntent + Scheduled Charges (Zapier/Sheets + Python) — Healthcare, Surcharging
Description:
I already have the blueprint for this project — including:
A working bulk-charge Python script
A front-desk decision sheet (PDF) with compliance flow
Outline of required Stripe products, prices, and workflows
I need you to take these and:
Configure Stripe (Products/Prices) and enable card-brand-compliant surcharging for Checkout/Payment Element (and Terminal if needed).
Build a per-patient Checkout Session link generator (pay-now and store-only modes) with auto-calculated surcharge, link expiry, and basic logging.
Wire a no-code option (Zapier + Google Sheets) so staff can generate links without touching code.
Integrate the existing bulk-charge script into a daily or scheduled workflow (cron or no-code equivalent) that charges stored cards on exact due dates.
Test all flows end-to-end in Stripe Test mode and Live mode with sample patients.
Provide a 1-page front-desk SOP and a 30-minute staff training (can be screen-recorded).
Ensure no debit/prepaid cards are surcharged (Stripe’s built-in logic for supported flows; fallback guardrails in manual workflows).
Implement point-of-sale surcharge disclosure in manual keyed-in flows only. Point-of-entry compliance is already handled by the practice and not part of this scope.
Surcharge text for manual keyed-in flows:
“A 3% credit card processing fee is added to all credit card payments.”
Deliverables:
Configured Stripe environment with surcharging enabled where supported
Polished Checkout link generator (Python script and/or Zap) using our blueprint logic
Fully integrated bulk-charge process (Python or no-code) with logging, retries, and email alerts
Google Sheet + Zapier (or Make.com) workflow to send per-patient expiring links
Final SOP PDF and quick video walkthrough
Deployment guide (API key handling, cron setup, or Zapier automation)
Must-have skills:
Stripe Checkout / PaymentIntents / SetupIntents
Zapier (Google Sheets → Stripe → Gmail)
Python (script refinement, env vars, logging)
Payment compliance basics (surcharging limits, debit exclusions)
Nice-to-haves:
Healthcare payments experience (HIPAA awareness for comms)
Familiarity with Stripe Terminal
Acceptance criteria (pay on completion):
Per-patient Checkout links (pay-now & store-only) generated in less than 60 seconds from email + amount.
Links expire (configurable hours) and cannot be reused after payment.
Surcharge appears as a separate line when manually added OR is itemized by Stripe when built-in surcharging is enabled.
Debit/prepaid cards are never surcharged in supported flows; manual backup path has a staff checklist to prevent errors.
Daily auto-charge job captures all due accounts, logs, and emails on failures.
Staff can operate everything via short SOP with no coding (Zapier path).
End-to-end test: in both Test and Live mode, charge two sample patients successfully.
Completion by Aug 28; go-live Sept 1.
Budget: $1,000–$1,800 fixed-bid (Upwork post shows $1,400 midpoint; 10% bonus for final, accepted delivery before Aug 25).
Timeline: Start immediately; sandbox demo within 7 days; live by Aug 28.
Apply Now
Apply Now
Stripe Checkout + SetupIntent + Scheduled Charges (Zapier/Sheets + Python) — Healthcare, Surcharging
Description:
I already have the blueprint for this project — including:
A working bulk-charge Python script
A front-desk decision sheet (PDF) with compliance flow
Outline of required Stripe products, prices, and workflows
I need you to take these and:
Configure Stripe (Products/Prices) and enable card-brand-compliant surcharging for Checkout/Payment Element (and Terminal if needed).
Build a per-patient Checkout Session link generator (pay-now and store-only modes) with auto-calculated surcharge, link expiry, and basic logging.
Wire a no-code option (Zapier + Google Sheets) so staff can generate links without touching code.
Integrate the existing bulk-charge script into a daily or scheduled workflow (cron or no-code equivalent) that charges stored cards on exact due dates.
Test all flows end-to-end in Stripe Test mode and Live mode with sample patients.
Provide a 1-page front-desk SOP and a 30-minute staff training (can be screen-recorded).
Ensure no debit/prepaid cards are surcharged (Stripe’s built-in logic for supported flows; fallback guardrails in manual workflows).
Implement point-of-sale surcharge disclosure in manual keyed-in flows only. Point-of-entry compliance is already handled by the practice and not part of this scope.
Surcharge text for manual keyed-in flows:
“A 3% credit card processing fee is added to all credit card payments.”
Deliverables:
Configured Stripe environment with surcharging enabled where supported
Polished Checkout link generator (Python script and/or Zap) using our blueprint logic
Fully integrated bulk-charge process (Python or no-code) with logging, retries, and email alerts
Google Sheet + Zapier (or Make.com) workflow to send per-patient expiring links
Final SOP PDF and quick video walkthrough
Deployment guide (API key handling, cron setup, or Zapier automation)
Must-have skills:
Stripe Checkout / PaymentIntents / SetupIntents
Zapier (Google Sheets → Stripe → Gmail)
Python (script refinement, env vars, logging)
Payment compliance basics (surcharging limits, debit exclusions)
Nice-to-haves:
Healthcare payments experience (HIPAA awareness for comms)
Familiarity with Stripe Terminal
Acceptance criteria (pay on completion):
Per-patient Checkout links (pay-now & store-only) generated in less than 60 seconds from email + amount.
Links expire (configurable hours) and cannot be reused after payment.
Surcharge appears as a separate line when manually added OR is itemized by Stripe when built-in surcharging is enabled.
Debit/prepaid cards are never surcharged in supported flows; manual backup path has a staff checklist to prevent errors.
Daily auto-charge job captures all due accounts, logs, and emails on failures.
Staff can operate everything via short SOP with no coding (Zapier path).
End-to-end test: in both Test and Live mode, charge two sample patients successfully.
Completion by Aug 28; go-live Sept 1.
Budget: $1,000–$1,800 fixed-bid (Upwork post shows $1,400 midpoint; 10% bonus for final, accepted delivery before Aug 25).
Timeline: Start immediately; sandbox demo within 7 days; live by Aug 28.
Apply Now
Apply Now