#dystroy

1 messages · Page 1 of 1 (latest)

fringe thornBOT
novel grotto
#

Hi! Let me help you with this.

#

Sepa Debit normally takes days to succeed, so you shouldn't rely on the timing, even in test mode, unfortunately. Stripe doesn't guarantee that it will be completed immediately.

violet spear
#

So how do you test this ?

#

Until now, 15 seconds was pretty reliable with a sk_test key, so I assumed I could depend on it for my CI. And this morning, it always fails, even after 10 minutes. Is there maybe a broken job on your side ?

novel grotto
#

Let me check

fringe thornBOT
novel grotto
#

Yes, I see it's taking slightly longer than usual.

thin owl
#

Do you have an example pi_xxx? Which SEPA test data are you using? Not sure how your secret key is relevant here

violet spear
#

pi_3NFZ5tR8MPee098r1L9q0526

#

cus_MzBxGEwfkayZjO, pm_1MFEGGR8MPee098rXmWoBSZQ

thin owl
#

Are they eventually succeeding?

violet spear
#

My last test was with a 600 seconds timeout and was still returning the same Processing status. The goal is having a unit test

thin owl
#

You're using AT611904300234573201, yes?

#

Let me try a test quickly

violet spear
#

(sorry for not answering faster, I don't have those curl queries ready as I had automated everything ^^)

thin owl
#

Ok, I tested a payment with that same IBAN and it doesn't seem to be progressing ~instantly as expected

#

Wil raise this internally

violet spear
#

Is there an expected duration in test for this ?

thin owl
#

What do you mean?

violet spear
#

I mean: when everything correctly works, is it reasonable to wait, say, 15 seconds , for a test SDD payment to go to succeded ? Is there some guidance on testing SDD ?

thin owl
#

I'm not sure what the specific timeframe is I just know it's 'immediate' (a few seconds)

violet spear
#

OK. I had had failures at 5 seconds and 15 seconds were 100% OK until this weekend

#

Is there a place I can track progress on the issue you'll raise ? I'd like to know when I can enable this unit test again

thin owl
#

What specifically are you testing, by the way?

violet spear
#

In this specific unit test, I'm checking my payment processing job which, in case of a Sepa payment method, creates the payment intent and regularly checks its status. In prod it's asynchronous but in my unit test I rerun the job after a short delay and check it's succeded. It's in a connected accounts context btw.

#

When you say I should write to suport to know whether this has been solved, is there a reference ? A ticket number ?

thin owl
#

Yeah I mean SEPA is async by nature so in practice the status transitions should be tracked as such. In reality, you'd stub responses/mock the API in your unit tests – we don't recommend calling the API in test suites

thin owl