Limitations Of The Stripe Plugin In FrameAuth
This article outlines the current limitations of the Stripe plugin in FrameAuth. Understanding these constraints will help you design a more reliable billing and access-control experience for your users.
Purchases Outside of FrameAuth Checkout
Only purchases initiated through a FrameAuth checkout via the Action Button component are synchronized with FrameAuth.
If a customer completes a purchase using:
A Stripe Payment Link
A custom Stripe Checkout
The Stripe Dashboard
Any non-FrameAuth integration
that purchase will not be recognized or synced by FrameAuth. As a result, access rules, tags, and membership logic will not be applied.
Best practice: Always route purchases through FrameAuth Checkout when access control is required.
Data Stored by FrameAuth
FrameAuth intentionally stores a limited subset of Stripe data:
Customers
Checkouts
Products
Prices
FrameAuth does not store:
Invoices
Payments
Charge objects
Billing history, payment status, and invoice-level details should be viewed and managed directly in Stripe.
Refunds and Access Revocation
Refunding a purchase in Stripe does not automatically revoke access in FrameAuth.
If you issue a refund and want to remove access:
You must manually void the purchase in FrameAuth
An API for programmatically voiding purchases is planned and will be available in a future release.
Subscription Retry and Cancellation Settings
Stripe allows subscriptions to be automatically canceled after all payment retries fail. While this may seem convenient, it is not recommended when using FrameAuth.
If a subscription is canceled due to failed retries:
The user can no longer see that they have an active subscription
This can create confusion and a poor user experience inside your site
Recommended approach: Allow subscriptions to remain active while in a past-due or unpaid state and handle access logic accordingly.
Deleting Customers in Stripe
Deleting a customer directly in Stripe prevents that customer from completing future checkouts.
This is expected Stripe behavior, but it can result in confusing checkout failures for users attempting to repurchase or resubscribe.
Recommendation: Avoid deleting customers in Stripe. FrameAuth may introduce improved handling for this scenario in the future.