#mitsu_api
main hamletBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
radiant spireBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1257152460095619103
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
untold citrus
In https://docs.stripe.com/api/accounts/login_link/create:
Creates a single-use login link for a connected account to access the Express Dashboard.
Your server would need to create a new login link every time when user the old link has been used. Every login link can only be used once.
untold citrus
Let me double check
untold citrus
I'm still checking why your login link is re-usable.
However, we recommend to generate the new login link when needed as suggested in the doc as a general guideline: https://docs.stripe.com/connect/integrate-express-dashboard#redirect-to-login-link
Typically, you generate a login link URL on demand when a connected account intends to visit the Express Dashboard. For example, you include an Open Dashboard button in your application. When a connected account user clicks it, your application calls the API to generate a login link and redirects them to that URL.
lunar fossil
https://connect.stripe.com/express/acct_1PTyBiIZ1JuRr5wx/1vwv6G3BDWik
I created this link ~ 1 week ago, try accessing it, I will send you an OTP
I created that link on June 24 and can still log in regularly
untold citrus
I totally understand your concern. We are checking why your link is multiple use. By default, the login link should only be single use
I still can't find out why your login link is multiple use. Can I suggest you writing to Support https://support.stripe.com/contact, so that they can check for you?
By default, the login link should be single use and your system should create the new login link when needed.
lunar fossil
ok, thanks
Please let me know more about the paymentintent api
Please wait a moment and I will send the question
untold citrus
Please let me know more about the paymentintent api
Feel free to let us know here if you have any question
lunar fossil
untold citrus
What is your question about?
lunar fossil
lunar fossil
What is your question about?
Please wait a moment and I will send the question
stripe->paymentIntents->create
=>pi_3PXaXIIJOXcdaYNk0BMw4JGM
$this->stripeService->paymentIntentsCapture('pi_3PXaXIIJOXcdaYNk0BMw4JGM')
status: "succeeded"
As I understand it, from the requires_capture state when calling the capture api, it will switch to the processing state
But in reality, I see the status: "succeeded" returned.
succeeded
requires_payment_method
These 2 statuses will be returned via webhook, right?
untold citrus
As I understand it, from the requires_capture state when calling the capture api, it will switch to the processing state
As mentioned in the above section that "Other payment methods, such as cards, are processed more quickly and don’t go into the processing status."
In pi_3PXaXIIJOXcdaYNk0BMw4JGM, it's a card payment. Therefore, it doesn't go into processing status and will become succeeded immediately
processing status is only for asynchronous payment methods
lunar fossil
Use card payment
Is there ever a time when the requires_capture state calls api
stripe->paymentIntents->capture('pi_3PXaXIIJOXcdaYNk0BMw4JGM') which returns failure
untold citrus
There is a rare chance that the capture can be failed. I'd recommend handling the failure as well in case if capture isn't successful
lunar fossil
from requires_capture state
when calling the capture api
stripe->paymentIntents->capture('pi_3PXaXIIJOXcdaYNk0BMw4JGM')
failed: requires_payment_method
How long will it take for the money to be returned to the payer?
untold citrus
How long will it take for the money to be returned to the payer?
Stripe will release the funds immediately to the card issuer, but it will be up to the card issuer about when the funds will be returned to the customer's bank account
lunar fossil
That is, after failure, the money will be refunded to the original payer.
It won't be possible to call capture again, right?
untold citrus
Yes, you're right!
lunar fossil
Thank you very much
untold citrus
No problem! Happy to help 😄