#oxmarco
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- oxmarco, 23 hours ago, 15 messages
- oxmarco, 1 day ago, 4 messages
- marco-issuing-server, 6 days ago, 5 messages
hi! well to clarify, which webhook? because the merchant side(the person charging the card) obviously can't know that
I'm the card issuer
the Issuing side gets the issuing_authorization.request etc when a merchant charges one of the issued cards and can get the IDs that way
I would like to send a telegram message when there is a hold on the card
and when such hold is captured or released
Should I just use the issuing_authorization.request?
yeah, I 'd suggest reading through the docs for Issuing e.g. https://stripe.com/docs/issuing/controls/real-time-authorizations to understand how it works and the webhooks involved.
a hold is an auth.
there's an auth, and then later it might be captured or it might be captured immediately, or never captured
ok, how do I know that?
how do you know what?
When I get issuing_authorization.request event I'll send the user a Capture msg over tg
how do I know if such capture is acquired or released?
you don't capture it, the merchant does.
https://stripe.com/docs/issuing/purchases/authorizations#authorization-updates
When the authorization is captured, a transaction is created and the status of the authorization is set to closed.
Issuing is extremely complex so you'll need to read the docs in detail and do a lot of testing in test mode
ok then I'll need to handle another event