#Sharvari96
ripe tusk
sour dust
webhooks endpoints
1. /webhooks-payments
- "payment_intent.payment_failed"
- "payment_intent.processing"
- "payment_intent.succeeded"
2. /webhooks-invoice
- "invoice.payment_succeeded"
- "invoice.payment_failed"
3. /webhooks-verification
- identity.verification_session.processing - processing
- identity.verification_session.verified - success
- identity.verification_session.requires_input - failure
Do we need any other important events?
or is there a reason why we need to listen to as many events as possible?
desert vector
The type and number of events you listen to would depend on what actions you're trying to take. Overall looks fine, except we recommend invoice.paid over invoice.payment_succeeded
desert vector
It accounts for paid Invoice scenarios where there's no actual payment (i.e. fully discounted)
If you had a $0 Invoice paid, .payment_succeeded wouldn't fire (as there's no Payment Intent)
sour dust
oh ok, got it
we will use that
One more question:
every once in a while I am getting this error from stripe:
(Network error: ConnectionError: HTTPSConnectionPool(host='api.stripe.com', port=443): Max retries exceeded with url: /v1/checkout/sessions?payment_intent=pi_3NOghGLbsWAvIKo93wFuFYAo (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f4f3c1d28e0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')))
is there any rate limiter that is acting in between?
I am testing and possibly making a lot of API calls..
my network is fine, I think, yet getting this error
desert vector
That's not a rate limit API error, that'd be a 429 error
That's indicative of a connectivity issue. Perhaps you have a firewall on your host blocking requests? Our recommendation is to ensure all IPs here are on the allow list: https://stripe.com/docs/ips#ip-addresses
sour dust
ok thank!
Does Transfers - have any statuses?
I dont see any status in the API reference - just want to confirm - https://stripe.com/docs/api/transfers/object
We are assuming that the transfer is success when the API gives back the transfer object and we are storing the id...
desert vector
Transfers are synchronous so would fail at the request level
If you get a 2xx response, then the transfer succeeded
sour dust
thank u!