#50an6xy06r6n - Duplicate Connected Accounts
tacit horizon
forest ore
I tried creating a new account link url for the duplicate via CLI but I got "You tried creating an account link with a livemode which does not match the livemode of the requested account." (the account is in live mode)
tacit horizon
In this case Support is best positioned to help you. They have more ability to investigate and resolve account issues. https://support.stripe.com/contact/email
forest ore
I guess I'm just trying to understand the general case, as these are accounts that we created as a test and I'm trying to figure out how we got into this state @tacit horizon
tacit horizon
And you cannot get the account ID?
forest ore
Also, I can't find documentation on how to force the stripe CLI to use live keys nvm figured this one out
forest ore
And you cannot get the account ID?
no I have the account ID
tacit horizon
But you don't want to make an API request?
https://stripe.com/docs/api/accounts/delete
forest ore
we were doing some final testing in live mode so it can't be deleted, as we're using standard connect accounts
tacit horizon
Ah, yeah that's an account that is outside of your direct control
forest ore
Ah, yeah that's an account that is outside of your direct control
well we created it with an email we control, so we theoretically have the ability to log into it
but logging in with that email takes us to the other account with the same email. And the duplicate doesn't show up in the account switcher
@tacit horizon
forest ore
acct_1KTXk3R29Lm8HgM9
oh also when you try to view the dashboard as that account it goes into test mode. Not sure if that's expected, as it doesn't happen with other live mode accounts
tacit horizon
When you try to create an Account Link are you using Live mode keys? Alternatively you can disconnect the account: https://stripe.com/docs/connect/oauth-reference#post-deauthorize
forest ore
I figured out the stripe cli so I'm about to try to set up the account again. Even if that works it feels weird that we can get into this state
tacit horizon
When you say "figured out the stripe cli", you mean using live mode?
forest ore
yeah
looks like completing the first step of the account link flow put it in a state where it could be closed
tacit horizon
THe account you shared has not completed it's application so it's not accessible in the dashboard
It shows up as "Application submitted: not yet submitted"
forest ore
I guess in the future we can just create a new link url, associate them with a dummy account, and delete them?
tacit horizon
Yes, you'll need to make sure you complete the initial onboarding process. Also that you use the same keys when generating the account link as were used when creating the account
e.g live mode / test mode
forest ore
Yes, you'll need to make sure you complete the initial onboarding process. Also ...
yeah using the wrong keys just gave me an api error
I think that's unrelated to the account redirecting to the test dashboard
How long should it take an invoice set to charge_automatically to actually charge the payment method? Clicking "Charge customer" on the dashboard works but I want it to go through automatically. The associated paymentIntent has a requires_confirmation status, but I don't really understand what that means, given that we can still charge from the dashboard
We're creating a platform where customers pre-enter their payment info and their associated provider charges them after every session, via one-off invoices
example is in_1KTr1YQpxbmlhy7X223dSCmG associated with acct_1KStXnQpxbmlhy7X
this worked in test mode, but we're running into some issues testing in live mode
gleaming meadow
THanks for moving those over, I'm taking a look
gleaming meadow
Alright, I think this is related to your webhook endpoint set up to receive invoice.created but with delivery failures, for example:
https://dashboard.stripe.com/events/evt_1KTr1ZQpxbmlhy7XQ48PZi7H
In live mode, if your webhook endpoint doesn’t respond properly, Stripe continues retrying the webhook notification for up to three days with an exponential back off. In test mode, we retry three times over a few hours. During that time, we won’t attempt payment unless we receive a successful response.
Read more here: https://stripe.com/docs/billing/subscriptions/webhooks#understand
but the key is in the callout:
To summarize: If Stripe fails to receive a successful response to invoice.created, then finalizing all invoices with automatic collection will be delayed for up to 72 hours.
SO you need to either fix that webhook endpoint to respond with a successful delivery, or remove invoice.created from the subscribed events
forest ore
@gleaming meadow I fixed the webhook issue but it's still stuck at PaymentIntent status: requires_confirmation
celest yarrow
Hello! I'm taking over, give me a minute to catch up...
This is still for the Payment Intent associated with Invoice in_1KTr1YQpxbmlhy7X223dSCmG?
If so, why did you finalize the Invoice instead of calling the pay API? https://stripe.com/docs/api/invoices/pay
forest ore
Hi, the new invoice is in_1KTvFxQpxbmlhy7XXg7G2MwO, still on acct_1KStXnQpxbmlhy7X
I don't remember seeing this pay api, but I'm probably just a dumbass
celest yarrow
Thanks. So if you call the pay API linked above on this Invoice does it work the way you want?
forest ore
lemme test that
this isn't a new endpoint right
I spent so long looking for something like this lmao
does the invoice need to be finalized to be paid? or can we call it directly on a draft
celest yarrow
It's not a new endpoint, no. I think you can call it on a draft Invoice if it's in a payable state, but the API should give you specific details if it doesn't work.