#kinghawk - Sunscriptions
1 messages · Page 1 of 1 (latest)
HI 👋
This doc is a good place to start when considering how to integrated Subscriptions into your system
https://stripe.com/docs/billing/subscriptions/designing-integration
To add context -- I'm looking to add an existing charge, to a new subscription
I can't seem to find whether that's possible in the docs
When you ca you are looking to "add an existing charge" what do you mean?
I am creating a stripe user, charging their payment, if the customers request for the subscription is accepted, I then create a stripe subscription and settle the transaction
I am looking to assign that charge to the subscription
You can add one-off charges to the first invoice created by a Subscription by creating an InvoiceItem for that customer
The first code snippet here is doing exactly that: https://stripe.com/docs/invoicing/integration#create-invoice-code
To make sure I understand you correctly. I would create an InvoiceItem for that customer with my initial charge, then once the subscription is created I can add that InvoiceItem to the new subscription. This way I could charge the full amount, then add that to the subscription and settle the transaction?
In that process you would create the Invoice Item for the initial charge yes, then when the user is presented with the first invoice for the subscription they would see an additional line item and charge for that charge. Then the user pays for the subscription & the initial charge together on the first invoice and only the subscription for invoices after that.
So I'm looking for an approach where that initial charge would be the only line item and considered the subscription payment, rather than a separate item.
Okay. So wouldn't you just create the Subscription and invoice without a one-off payment in that scenario? Or is the price different?
So the initial charge is to ensure payment, I've gotten a ton of insufficient funds returning so I'm trying to ensure I can secure the funds prior to going through the customer request form, and voiding the initial charge and just processing the subscription payment would result in duplicate charges appearing on the customer cc
So would collecting the initial subscription payment up front not be an acceptable solution?
So thats what I'm trying to figure out, is to how to collect the initial subscription payment up front and sync it as a payment against the newly created subscription
That is what this doc does. It even has the option to use a Stripe hosted Checkout page so you don't have to create your own UI to collect payment information: https://stripe.com/docs/billing/subscriptions/build-subscriptions
I already have a working solution, am just trying to move the subscription processing workload over to stripe to eliminate dunning on my end. So I am not looking to change the flow for my system to create a subscription before charging the payment method sucessfully
I can understand that, I just thought the Checkout approach might help you test out this solution quickly to you can evaluate if it meets your needs.
The default approach for Stripe is to collect payment for the first invoice immediately. You can use a more custom code approach with this guide: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements