#swe_api

1 messages ¡ Page 1 of 1 (latest)

twilit quailBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1297889797829955584

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

wet plinth
#

hi there!

#

are you trying to simulate a failed SetupIntent for SEPA in test mode?

tardy blaze
#

Yes, exactly.

#

Failed as well as delayed success

wet plinth
tardy blaze
#

We attempted one of these test values - AT321904300235473204 and the setup intent moved to succeeded status, whereas the document suggests that it should move to requires_payment_method or processing state.

#

Clarifying that this behaviour is happening in setup intent and not payment intent. We want to basically simulate failed setup intent flow in test mode as you mentioned.

wet plinth
#

Can you share your SetupIntent ID (seti_xxx) so I can check?

#

But maybe that's expected and we don't have tests values that would work like this for SetupIntents.

tardy blaze
#

seti_1QCKNSJv9j0DyntJqZKg0ll7

#

How can we make sure that this behaviour works in production? Since these are direct debit schemes, there are high chances of late failures.

wet plinth
#

that good feedback. I'll share it with the team working on this.
But for now you can test this with PaymentIntents, and maybe mock the answer with SetupIntents?

tardy blaze
#

Wanted to confirm if the behaviour is going to the same for payment intent and setup intent in this case?

#

Or, how does it vary?

wet plinth
#

Wanted to confirm if the behaviour is going to the same for payment intent and setup intent in this case?
you mean in test mode or in live mode?

tardy blaze
#

In live mode.

#

I can mock in test mode for now, but wanted to confirm the behaviour in live mode

wet plinth
tardy blaze
#

Okay, thank you. Please take this as a feedback that this is not testable in test mode.

#

Also. I have a follow up question and would like to validate the flow.

#
  1. Create customer.
  2. Create confirmed setup intent for the customer.
  3. Use the payment method and mandate returned in setup intent and create a confirmed payment intent.
  4. Payment status can be found using status of charge and payment intent.
  5. To verify the status of the payment method, what status should we rely on here? Mandate status is always active, paymetn method doesn't have status, setup intent is always succeeeding.
wet plinth
#

yep that looks correct!

To verify the status of the payment method, what status should we rely on here?
what do you mean by this? a Payment Method doesn't have a status

tardy blaze
#

Whether the bank account number used is valid or not. We will only know after the payment intent succeeds. But, before that, what do we do?

wet plinth
#

I'm guessing if the SetupIntent succeeded, then the number should be valid. But later when you create a PaymentIntent, it could still fail for a number of reasons, like insufficient funds.

tardy blaze
#

Yes, but can setup intent fail firstly? Wanted to confirm this theoretically, as we are unable to test this.

wet plinth
#

yes that's a good question. I'm not super familiar with this flow, so again I would recommend to get confirmation of this with Stripe support.

tardy blaze
#

Thanks, will check with them.