Repository navigation
Tags
Tags
Add StripeCheckoutClient.Refund A plain full refund (POST /v1/refunds, payment_intent) for a Checkout Session that charged successfully but genuinely couldn't be fulfilled — EphemNet's own first use: a domain-register purchase that turns out, after payment, to already be registered. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add StripeCheckoutClient.GetPrice Fetches a Price's real amount/currency -- lets a trigger page show a human what something actually costs without hand-maintaining that figure separately from the Stripe dashboard. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Extract Stripe webhook verification and Checkout session creation Both are genuinely Stripe-generic mechanics with no product vocabulary of their own -- extracted from EphemNet's own internal/ packages once a second consumer (cinder/offgridapp) needed the identical code, rather than tripling the same hand-rolled signature verification and form-encoded REST call across repos. Matches StripeBackend's own reasoning for living here rather than per-repo. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add MultiBackend: accept a token valid against any of several backends Needed the moment a second payment rail exists alongside an existing one -- different signing keys, different wire formats, one listener that has to accept either's output without caring which produced it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add StripeBackend: self-verifying Backend+Issuer with signed Quantity An interim/parallel billing rail alongside HMACBackend, not a replacement -- same nonce+expiry+HMAC-SHA256 wire shape, no network call, no shared state. Adds one real capability HMACBackend doesn't need: a signed, tamper-evident Quantity (IssueTopUp/Quantity), so a metered product sold in predefined top-up packages can recover how many units were purchased, not just whether the purchase was valid. Contains zero Stripe-specific vocabulary -- webhook verification, price IDs, and Checkout Session parsing stay entirely in the embedding product. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>