foir-billing
/foir-billing
Konfiguruje lub sprawdza płatności Stripe w sieci i RevenueCat w aplikacjach natywnych dla aplikacji z Fóir, z uprawnieniami po stronie serwera.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Konfiguruje lub sprawdza płatności Stripe w sieci i RevenueCat w aplikacjach natywnych dla aplikacji z Fóir, z uprawnieniami po stronie serwera.
Oryginalny opis (EN)
Set up or verify Stripe web and RevenueCat native billing for a Fóir-backed app, with shared identity and server-enforced entitlements. Use for provider setup, purchase reconciliation and billing release checks.
Jak działa
SKILL.md bez nagłówków drugiego poziomu · 82 linii, 695 słów
Podgląd SKILL.md
--- name: foir-billing description: Set up or verify Stripe web and RevenueCat native billing for a Fóir-backed app, with shared identity and server-enforced entitlements. Use for provider setup, purchase reconciliation and billing release checks. --- # Set up billing through scoped operations Read the app's root config, operations, current provider adapters and project profile before proposing changes. Discover OAuth Fóir tools, read served schemas, and explicitly select environment/workspace/project/organization before writes. Use current Stripe and RevenueCat skills/docs when available. Do not create a second user pool or a frontend proxy with broader credentials. Preserve the template's native/web subscription integration, purchase/restore and shared server-enforced entitlements. Adapt its plans, prices, allowances and benefits to the product brief. A free launch can leave billing inactive without removing that foundation; framework changes require explicit scope. Fóir is the hosted managed backend. Billing operations contain product-specific provider integration and entitlement decisions, not app-owned metering, financial ledgers, reservation services, queues or identity/access-control infrastructure. Fóir records are not a loophole for building those services. Use supported native limits and verify their exact accounting, failure and completed-success semantics before promising an allowance. Never infer those semantics from an execution-rate quota alone. Missing proof is a capability question, not proof the platform lacks it or permission to replace it. Discover the current [no-backend](https://docs.foir.dev/no-backend) and [app architecture](https://docs.foir.dev/guides/app-architecture) guides through Fóir's served documentation tools when choosing the integration contract. Local platform source alone does not establish deployed behavior. Map both providers to the verified app actor. Define a provider-neutral private subscription grant, its source/id, validity, revocation and quota relationship. Keep free allowances separate. Enforce access in signed operations using the verified ingress identity and dispatch-scoped data client; a client badge is not proof of payment. Do not allow one provider's cancellation to revoke a separate valid grant from another provider. Review the exact grant table and supported operation contract before enabling it. Store provider secrets in the credential mechanism the installed operation can actually read; project secrets and app-install credentials may differ. Never put secret keys in the client, public repo, command output or chat. Use restricted sandbox keys, existing installation credentials and minimum provider permissions. Preserve unrelated credentials when saving a form. Stripe: use the app's signed Checkout/Portal operations and configured product, price, currency, interval and return origins. Bind customer/subscription mapping to the verified actor, not a browser-supplied user ID. Validate webhook signature against raw bytes, use supported native idempotency and event delivery, fetch authoritative provider state, and reconcile grants idempotently. Do not build a replacement webhook/event-processing service. RevenueCat: identify the same actor, verify active entitlements server-side and reconcile restore/renewal/ expiration/refund/cancellation into the same grant mechanism. Use Fóir's supported awaited execution and continuations for long work. Do not introduce another queue or an unobserved promise after returning. Read the template's maintained known-gaps inventory when starting from a template. Only while developing the template itself, update that inventory when a verified limitation changes. Customers consume it; they are not asked to build workarounds or maintain a gap register while setting up or developing their own app. Keep unresolved capability questions, integration work and verification evidence in the issue tracker, outside the customer-facing inventory and setup docs. Prove in an isolated sandbox: unpaid Checkout/Portal; simulated purchase; refresh/restore and shared web/native entitlement; partial/full refund; cancel-at-period-end and expiry; renewal; duplicate/out-of-order delivery; invalid signature; wrong actor; expired dispatch; retry/recovery after failure. Record which outcomes were actually observed and which are fixtures. Do not count gateway acknowledgment alone as proof a consumer completed successfully. Use test transactions only within approved scope; hand off any action the tool's approval policy requires the user to perform. For a template that advertises subscriptions, billing is unfinished until the actual client purchase/restore and server-entitlement lifecycle pass acceptance. A disabled build, configured offering, local fixture or provider-only entitlement is not a completed integration. Missing app keys/grants and unconnected handlers are app/configuration work, not proof of a platform blocker. Report a genuine external dependency with evidence and impact; do not use it to silently disable promised features or call the release ready. The owner decides any scope change. Billing is always on; never ship it behind a switch or a test-user gate. App Store Sandbox purchases must unlock the paid tier for everyone, because App Review and TestFlight buy through Sandbox. Get explicit authorization before live keys, webhook routing or live charges. Provide exact rollback and leave existing subscriptions intact during hosting changes.
Wersje
W bazie nie ma innych skilli o nazwie foir-billing.
Migawka bazy z 13.11.2026 · wersja paczki 085511a73f3e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 86foir-go-live
Przygotowuje i sprawdza przeniesienie aplikacji Fóir z dev na produkcję, w tym hosting, tożsamość, operacje i wycofanie. - 100revenuecat-billing
Odpowiada na pytania o plan, rozliczenia i faktury RevenueCat oraz o to, ile użytkownik zapłaci RevenueCat. - 100asc-revenuecat-catalog-sync
Uzgadnia subskrypcje i zakupy w aplikacji z App Store Connect z produktami, uprawnieniami, ofertami i pakietami RevenueCat przez asc i RevenueCat MCP. - 100rc-revenuecat-vs-raw-billing
Pomaga wybrać między RevenueCat a surowym Google Play Billing na Androidzie, porównując, kto za co odpowiada. - 100stripe-operator
Sprawdza i obsługuje Stripe (klienci, płatności, subskrypcje, faktury, produkty) przez API lub CLI do pytań o rozliczenia, debugowania płatności i raportów przychodów. - 100payment-integration
Pomaga integrować Stripe, RevenueCat i rozliczenia subskrypcyjne, webhooki płatności, zgodność z PCI oraz podatki, a także przeglądać zakres rozliczeń i PCI.