AA

[rocky dawn]

I don't think there's a good way to test this specifically for refund failure, but we do also trigger it with refund success. If you have the CLI installed you can just do stripe trigger charge.refunded.updated to test this

[wheat raven]

so charge.refunded means the refund was requested? but not processed?

[rocky dawn]

Yeah, it just means the refund has started - depending on the PM type it could immediately be successful

or it could be pending

[wheat raven]

i see. how would i know if it was immediately successful?

[rocky dawn]

You can check the status of the Refund you get back

[wheat raven]

so follow up question. is there a way to tell a webhook to only receive live or test events?

or do i need to do that on my side

[vivid loom]

What do you mean by that, exactly?

Except for some Connect-related edge cases, you would only test testmode events to test mode configured webhook endpoints, and livemodfe events to live endpoints

Note that events do have a livemode attribute to check if necessary, or if you configured the same endpoint in live & test mode, for example

[wheat raven]

i have a staging and a prod environment. i wanted to route the correct events to the correct environment

but i suppose i should use a separate stripe account for both or route them internally depending on livemode setting

[vivid loom]

Stripe accounts only have test and live mode, so if you need other environments for your work then yes a separate test mode account could be used for eg staging

[wheat raven]

oh i see. that makes sense

thanks!

[vivid loom]

NP!