You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would make organizer's lives easier, while also introducing some risks because it deals with automatic actions taken on payments. Thoughts:
We may want to add a popup with a tickbox that says "Also refund registration" - a good in-between option that let's organizers not always have the refund be processed [this could also act as an "Are you sure you want to cancel/reject?']
If we passed in a refund: true argument in the update payload we could have a hook as part of the update process that triggers a refund. This would make it quite easy to allow an organizer to trigger multiple refunds at once - but whether it is easy is not as important a question as whether it is secure
The text was updated successfully, but these errors were encountered:
This would make organizer's lives easier, while also introducing some risks because it deals with automatic actions taken on payments. Thoughts:
refund: true
argument in the update payload we could have a hook as part of the update process that triggers a refund. This would make it quite easy to allow an organizer to trigger multiple refunds at once - but whether it is easy is not as important a question as whether it is secureThe text was updated successfully, but these errors were encountered: