Looks like you found a bug. Just reviewing this and there’s a gap appending return parameters to the x-success URL if the x-success URL does not have any parameters to begin with.
I’ll fix this for the next update, but in the meantime you can workaround by adding a parameter to the x-success URL - it will get ignored by the target app, but will workaround the bug - something like &a=b.