#eoghanobrien
plain kelp
thorny stone
Hi, when yo say automatic charging are you referring to this, https://stripe.com/docs/invoicing/automatic-charging?
foggy yacht
I think so
the draft had a footnote about sending it today but I'm not sure what that means exactly
thorny stone
In this case, it would automatically charge the saved payment method right away.
Can you share the request id where you're seeing this?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
foggy yacht
I have the invoice id but I manually marked it paid - in_1McDxaE3c9sWyeruKS65u5ly
worried by this though: req_YPr8N20aoBYI9z
thorny stone
Let me look
foggy yacht
Everything okay...?
thorny stone
Form looking at these objects, it appears that at the time where you asked to automatically charge the invoice there was no default payment method on the customer. It looks like that customer has default payment method now so if you create another invoice it should work as expected.
foggy yacht
so I was told I could update the invoice_settings.default_payment_method at any point before creating the invoice and it would work as expected.
So that's what I'm doing, I change the customer's plan, then take the default_payment_method value on the subscription object and assign value that to the customer object via invoice_settings.default_payment_method and finally I call Invoice.create() for that customer.
Can I just pass the pm when creating the invoice? Is that better?
thorny stone
If the default payment method is set, creating the invoice would work. You should not have to pass the payment method
foggy yacht
okay, so it's normal for the invoice to go to draft and payment is charged later ... or is the fact that it wasn't charged immediately upon creation a problem?
thorny stone
With charge automatically, it would work, we try to charge the payment method right away. Can you create another invoice on that customer? (and not pay manually) Then, share the request id with me?
