#Dona-integration
1 messages · Page 1 of 1 (latest)
Hi there
Let's back up a bit
You stated "daily/weekly/monthly"
Are you looking for recurring payments?
Or are these just one-off payments but the product you are providing would be for a day/week/month type of deal?
Hello there, we are into warehousing service and depending on storage/shipping and all service we provide our customer and their payment term we generate statements in our system. And then we provide them a link to Pay via Stripe or if they have agreed for automatic payment we charge them with the payment option they selected during Setup.
Okay so that doesn't sound like recurring (like a Subscription)
It does sound like one-off
So you would either use the Invoices API or use the PaymentIntents API.
The Charges API is our legacy API
Do you prefer having an invoice for your customer?
Or is the invoice not a deciding factor?
No invoice is not a deciding factor. We are looking for most simple solution.
Invoice looks like fills our product page with products per invoice
Got it. Sounds like you do want PaymentIntents. Your two options are to integrate Stripe Checkout which would involve you redirecting your customers to a hosted payment page to collect payment. Or, you can use Stripe Elements if you want to embed the payment form directly in your web page.
Hmm actually. If you want the simplest solution, and want to provide a link to your customers, then Payment Links are actually what you would want to utilize.
Take a look at https://stripe.com/docs/payments/payment-links
In terms of charging for an already-saved payment method. That is where you would use PaymentIntents.
You could collect payment methods using Payment Links for first time payments and then save the Payment Methods via that Payment Link and use them for charging saved Payment Methods going forward if that is what your customer wants.
I know I'm throwing a lot at you, so feel free to ask any clarifying questions.
I am using Connect if the customer action is is needed for collecting the payment. If we are doing a job to automatically collect the payment we was more thinking of Invoice object.
I will look into Payment methods instead of Invoice object for nightly automatic job
You would need PaymentMethods either way if you are using Invoices or PaymentIntents for charging customers using stored cards or other types of payment methods.
I'd recommend stepping back and focusing on one thing at a time though.
Like, how you are going to accept payments for a new customer.
Did you take a look at Payment Links?
I am using connect with SetupIntent for new customers to set up there payment.
Sorry, not sure what you mean exactly by "connect with SetupIntent". Those are basically two separate things that wouldn't exactly relate...
Are you a platform?
And using SetupIntents is great to set up a payment method. Then you can just charge it using a PaymentIntent when you are ready.
I meant new checkout session with mode as 'setup'