#stripe

[redacted]

does stripe email notify me for every payment made? or just the first one

i dont have access to the phone that has two step authentication, so im recovering it but it takes 1-3 business days

orlondow, you available?

psmvac, ?

Hi, i have implemented the SOFORT payment method in my application and it works fine. The only problem is that it takes a very long time for stripe to send the webhook that the payment was successfull and no not pending anymore. usually when i use SOFORT directly i get the respons in a few seconds, but on stripe i am still waiting for it since 30 minutes ... any idea why?

leo-unglaub: do you mean 30 minutes for the `charge.succeeded` webhook to be receieved?

karllekko: yes, sometimes even longer

leo-unglaub: and this is in live mode? unfortunately I'm not hugely familiar with SOFORT, that may be normal — it's an asynchronous payment source so I believe we have to wait for the customer's bank to notify us that the charge was successful, so 30 minutes might be normal. It might be worth writing to https://support.stripe.com/email with the details so they can look into this for you.

maddy: sure, what's up?

@stripedude: if you are calling the List charges API method you could always use pagination if you aren't already doing so. All List API methods supports it. So originally you would load a list of say 20 charges and have your UI provide an option to paginate

Hi @maddy: I can try to help

@maddy: not very familiar with Atlas and the application process. This doc shows the conditions:

- https://stripe.com/docs/atlas#should

- https://stripe.com/docs/atlas#cannot

Other than referring you to the above doc, I won't be able to help.

if you haven't done so already I would suggest contacting: atlas@stripe.com

They will be better positioned to answer your questions about Atlas

hey karllekko, sorry i had a disconnect

(12:55:30) karllekko: leo-unglaub: do you mean 30 minutes for the `charge.succeeded` webhook to be receieved?

(12:55:58) leo-unglaub: karllekko: yes, sometimes even longer

@leo-unglaub: do you have an example of an `charge.succeeded` event ID which took a long time after you created the charge

psmvac: evt_1D7fFCIHtsw2sjWkW2QwiZVk

that was the test we did with "real money" and we still did not get the charge.succeeded

@leo-unglaub: so this is a `charge.pending` webhook (not a charge.succeeded one). this would be expected: https://stripe.com/docs/sources/sofort#charge-c...

> Since SOFORT is an asynchronous payment method, the Charge object’s status remains in a pending state for up to 14 days from its creation

psmvac: yes, i read that on your page but i dont get that. Before we moved this method to stripe we had it implemented directly and there we always got the response imidiatly. Thats why people use SOFORT, because they get it instantly back. Sofort is german for imidiatly

i always thought this 14 days in there is just some legal stuff you write in for layers and stuff

@matze_: for expiration I believe we would send a webhook to let you know: https://stripe.com/docs/saving-cards#automatic-...

for decline you would only know when an auth is made, so when you charge the card/source

@leo-unglaub: I'm not very familiar with the details for this, so as karllekko suggested I would suggest sending an email to support

@matze_: depends on your use case but you could use auth and capture: https://stripe.com/docs/charges#auth-capture

psmvac: okay, i will ask the official support. Do you have internal stats on how long the average waiting periot for sofort is?

@leo-unglaub: other than what is stated in the docs no.

psmvac: okay, thanks.

using the official support chat was a bad idea ... just automated text snippets and a link to the docs page

@KazLu75: sorry. You can retrieve a source_transaction associated with a source using this: https://stripe.com/docs/sources/ach-credit-tran...

for testing have you checked this: https://stripe.com/docs/sources/ach-credit-tran...

@leo-unglaub: I'm sorry I can't help much but not very familiar with SOFORT sources. From my understanding what you are seeing would be expected. After the source was authorized and you charge the source the source status is `pending` and can stay like this for up to 14 days as the doc says