You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UserBilling Component and Construct that connects to Stripe API. Likely don't need admin panel for billing since Stripe's is so good. This would just enable user to edit their billing info. Stripe has components we can pull in and user, but we'll want to use Amplify UI's to stay consistent. We'll need a lambda which will create a stripe session which is required I think. How will we handle stripe secrets?
Basic UI will be a table with payment methods? But if user only has 1 or 2 methods, is that too much? See how Amazon.com and others design it.
The text was updated successfully, but these errors were encountered:
UserBilling Component and Construct that connects to Stripe API. Likely don't need admin panel for billing since Stripe's is so good. This would just enable user to edit their billing info. Stripe has components we can pull in and user, but we'll want to use Amplify UI's to stay consistent. We'll need a lambda which will create a stripe session which is required I think. How will we handle stripe secrets?
Basic UI will be a table with payment methods? But if user only has 1 or 2 methods, is that too much? See how Amazon.com and others design it.
The text was updated successfully, but these errors were encountered: