#Nebojsa

1 messages · Page 1 of 1 (latest)

modern arrowBOT
rotund hornet
#

Is there a reason you can't use Subscriptions? This is going to be way more difficult to implement and require a lot of time tracking on your end to implement if you don't use Subscrtiptions

tough gazelle
#

I'm just thinking of the possibility to disable the auto-pay feature

#

It's a real estate e-commerce, so they enter into a contract and I'd like to allow the option of having autopay

#

I suppose I could cancel the subscription at any point with an interaction on users' end

rotund hornet
tough gazelle
#

Yep, I'm aware and of course I'll keep researching. It's more of a question of backend architecture, but ty for the help! If you don't mind, I have an idea and would love your opinion.

On a checkout all the payments are created in the servers' database with an unpaid status. If autopay is enabled a subscription is created. Have an event listener via webhook for subscription payments to update the internal database. Allow disabling the autopay which would cancel the subscription and also allow reenabling, which would create a subscription taking into account remaining payments

rotund hornet
#

What's your question specifically?

tough gazelle
#

Is that a decent way of building out the backend side of this integration?

#

That way I can utilize subscriptions but still retain the option of manual payments after that

rotund hornet
#

There are a lot of nuances to that scenario, as it's fairly complex, but nothing seems out of place. That should work just fine

tough gazelle
#

Yep, the whole app is built and I've left ample time to get everything about this integration wrong multiple times 😄 Thank you for your help!

rotund hornet
#

Sure thing!

tough gazelle
#

@rotund hornet me again... Sorry! So the same question this time. Could this be a better way to handle these autopay options.

There's an initial charge on checkout before a customer enters into a contract. Therefore I can use a PaymentIntent there to store their payment method info into the Customer object I create on Stripe. I then create the payment schedule in my database and just create PaymentIntents with an off_session when they need to be charged. In case it fails or something, I'm planning to send emails to the customer to check into their customer portal.

This would allow for the customer to pay in advance if they have funds available, enable/disable autopay as they see fit etc. As the only "automatic" thing about autopay is the server creating PaymentIntents

I believe it might be more suitable than subscriptions, as it's more of a payment plan option with a chance for them to pay ahead of time, switch between autopay and manual etc. etc. It's not really a saas or anything of that sort...

What are your thoughts? Can I use PaymentIntents this way?

rotund hornet
#

You can definitely use Payment Intents in that way, though you'll have to track on your end how many payments have been made and when they should be stopped

#

That will likely be a more complex integration, but I don't see any reason it wouldn't work

tough gazelle
#

Okay, perfect. Thank you so much. Turns out I needed much more flexibility than what subscriptions provide as it's aimed more at saas platforms.

Again, thanks so much for the help!