#nollix_api

1 messages · Page 1 of 1 (latest)

bold spindleBOT
#

👋 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/1448814020709715988

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

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.

kindred echo
#

Hi there

#

I think it is likely that we emit both events. Do you have an example refund failure I can look at?

real void
#

no, I'm just trying to figure it out the whole logic behind the refund because I have to implement in the system

kindred echo
#

When I try a refund with the 4000000000005126 card, after the refund fails we send a refund.failed event but not refund.updated

real void
#

ok thank you! Is refund.updated used for something? I thought that refund.updated is called when the status of the Refund Object changes.

kindred echo
#

Yeah I mean we send a refund.updated when a refund's status goes from pending to successful. I don't know why specifically we don't send it when a refund fails but probably because we have a specific event namespace for that happening. If we sent a refund.updated and refund.failed I think the payloads would be identical, so it wouldn't make any sense to send both

real void
#

ok thank you

bold spindleBOT
real void
#

Is the refund.updated event triggered when the refund is canceled (so not failed) by the user/admin of the system?

young pelican
#

👋 refund cancelled means its failed intentionally by the user/admin

#

if a refund is not failed by the user/admin but the refund is not successful, means it probably failed for other reasons like customer's bank not being able to process it

#

And if a refund failed, only refund.failed will be send. .updated is if there are other updates, like the ARN for example

real void
#

so if the status of Refund object is "canceled" or "failed", the refund.failed is triggered (and not the refund.updated), right?

young pelican
#

Yes you are correct. As long as a refund failed (whether its cancelled by the merchant or the bank couldn't process it), a refund.failed will fire. There will be no refund.updated

real void
#

About the status of the Refund Object: is the refund.updated used for the status pending and succeeded?

young pelican
#

when a refund change from pending to succeed, refund.updated will fire, yes

real void
#

and for the other status the refund.updated isn't used and there are used other event like refund.created and the refund.failed, right?

young pelican
#

i'm not usre what you meant by other status

#

but refund.created is when a refund is created

#

refund.failed is when a refund is cancelled or failed due to not being able to processed like what we discussed earlier

real void
young pelican