#oxmarco

1 messages · Page 1 of 1 (latest)

stiff quarryBOT
#

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.

sturdy crypt
#

hi! well to clarify, which webhook? because the merchant side(the person charging the card) obviously can't know that

boreal kernel
#

I'm the card issuer

sturdy crypt
#

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

boreal kernel
#

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?

sturdy crypt
boreal kernel
#

it's not very clear tbh

#

that document just talks about payment auth, not holds

sturdy crypt
#

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

boreal kernel
#

ok, how do I know that?

sturdy crypt
#

how do you know what?

boreal kernel
#

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?

sturdy crypt
#

you don't capture it, the merchant does.

sturdy crypt
#

Issuing is extremely complex so you'll need to read the docs in detail and do a lot of testing in test mode

boreal kernel
#

ok then I'll need to handle another event