Thank you for being patient! We're working hard on resolving the issue
tento-stripe wraps generated Stripe model crates, product catalog macros, and
Stripe app helpers for checkout and webhooks.
StripeApp is the configured API entry point.StripeValidatedJson validates webhook signatures before deserialization.stripe_product! and stripe_product_catalog! declare typed product
catalogs.tento_stripe_models::* modules expose typed Stripe resource
clients and models.fixtures::{StripeFixture, StripeFixtureList} supports local test data.scripts::ScriptsConfig exposes local customer and checkout commands.Generated Stripe models live in tento-stripe-models; code generation lives in
tento-stripe-codegen; product macros live in tento-stripe-macros. The parent
crate should be the ergonomic integration surface that callers import.
Application code should not hand-roll Stripe request payloads or webhook signature verification. Add typed model or app methods here when a Stripe workflow becomes part of Lona.