#localpath_best-practices

1 messages ¡ Page 1 of 1 (latest)

gusty echoBOT
delicate gateBOT
#

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.

gusty echoBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1245485122061340692

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

broken steppe
#

Are you only using the Charges API? Or are you using Payment Intents as well?

rain quarry
#

A mixture sometimes but mostly payment/setup intents

#

we have some legacy flows that still use deprecated charges

#

I guess it also depends on the capture setting of the payment as well right? I think it may be auto capture? Would that mean all charges move to refunds only since we won't have a chance to void?

broken steppe
#

Hmmm, I'm a bit confused. If a refund is created, you would get a charge.refunded webhook. Are you seeing instances where a refund was created and that Event did not trigger?

rain quarry
#

no. that works as expected. I'm more trying to figure out if a charge is canceled/voided how would we know via webhooks. like before the charge is captured, it gets canceled/voided from dashboard, what would I check? the charge object?

broken steppe
#

You're using a separate auth and capture workflow? E.g. you place a hold on a card (an authorization), then you manually capture those funds at some later point?

rain quarry
#

no we do not

#

so if that being the case cancel/void is never exposed huh?

broken steppe
#

I'm just trying to understand what you mean by cancel/void. Are you referring to canceling a Payment/Setup Intent? Are you referring to voiding an Invoice?

Sorry, there are just a lot of terms here that are ambiguous. Terms like "void" and "cancel" could have a bunch of different meanings.

rain quarry
#

no just canceling a charge made via charges or payment intents. It sounds like we don't do manually or deferred capture so all of our charges are only eligible for refunds

broken steppe
#

The only way you would cancel a charge in this case would be if you used a delayed payment method type (e.g. ach, SEPA, BACS, etc.) where the payment takes multiple days to land, as opposed to cards which are instant.

rain quarry
#

ok awesome. I'll test that out with some ACH. in the case that the charge for an ACH is canceled what or how would you recommend we track that via a webhook? On the charge record itself?

broken steppe
rain quarry
#

cool. thanks for the help