I know Knack doesn't support Subscriptions through Stripe. Is there a way to work around this? Right now, a user can buy a subscription to my Knack database via my Stripe checkout page. When their purchase goes through successfully with Stripe, they are shown a URL that lets them setup a Knack membership. My memberships are recurring with 6 month or 12 month terms. I would like Knack to change the User Status from "active" to "inactive" after the membership term has expired unless the proper payment is received from Stipe. If a user buys a 6 month membership, then can I set the "Timer" field to "180 days" when the Timer gets to 0, can I change the User Status to "Inactive" and show a message that says, "To continue, please insert coins"?
We're tracking this feature request here: https://support.knack.com/hc/en-us/community/posts/115000718312-Recurring-Payments-
Please add any feedback / requests in that thread. Thanks!
As we ramp up our development for subscriptions, we'd love to hear about your subscription use cases to better align our features with your needs. If you're planning on using subscriptions in your Knack app we would appreciate it if you could fill out this short survey: https://www.knack.com/knackstars#subscriptions-survey/
And if you haven't done so yet, sign up for the Knackstars program so you can join the beta when it's ready: https://www.knack.com/knackstars#register/
I have the same issue, but I want to do a 30-day free trial and then charge them if they don't cancel. The short answer is there isnt' a way around it...yet.
I noticed last week when I was building a form, on the Option section where you enable ecommerce, it said "Create customer to charge later". I reached out to Knack Support asking what this meant (other than the obvious), because I'd never seen it before. They said, "Yeah it's something that's in beta at the moment. Should release by next week. It integrates with Stripe Customers..so you don't store the cc info in Knack.. it's stored in your Stripe account. You can use those stored details to make a payment, or even charge a customer on their behalf."
Sounds like what we need!