If a payment is made (same address, amount, OP_RETURN data), still fire the success toast as well as onSuccess/onTransaction just like if they had the dialog open or were using the widget.
The goal here is to increase payment detection reliability from the client's perspective. Some websites may entirely rely on the client to let them know about payments (eg. people who have opted not to create a paybutton.org account) so we want to give them as much of a chance to have those functions fire regardless of what the paying user is doing.
If a payment is made (same address, amount, OP_RETURN data), still fire the success toast as well as onSuccess/onTransaction just like if they had the dialog open or were using the widget.
The goal here is to increase payment detection reliability from the client's perspective. Some websites may entirely rely on the client to let them know about payments (eg. people who have opted not to create a paybutton.org account) so we want to give them as much of a chance to have those functions fire regardless of what the paying user is doing.