Stripe
Stripe billing experience in this portfolio includes FULCRUM customer and subscription integration code. The IMBA.TV rebuild also includes Stripe account and payment-workflow development, which remains in progress.
Where the engineering matters
The billing integration is distinct from FULCRUM’s Square retail-terminal adapters. Customer selection, subscription operations, and billing state belong to their own application paths rather than being used as proof that every in-store tender runs through Stripe.
Work represented in the portfolio
- FULCRUM customer and subscription integration
- Product and subscription selection interfaces
- IMBA.TV account and payment-workflow development
IMBA.TV’s rebuild remains in progress, targeting mid-2027. FULCRUM’s billing and Square terminal work have separate responsibilities within the retail product.
Stripe billing experience: planning a similar project
A billing brief should separate customer identity, product selection, subscription state and the application access that depends on them. Those records can change at different points in a workflow. This dossier documents the Stripe paths represented in the portfolio. Square terminal work is covered separately, and IMBA.TV’s unfinished rebuild should not be read as a completed production launch.
For a new project or changes to an existing system, explore custom API integration services.