Hello,
I would like to ask about the callback_url on the Mobile App use case.

Environment

The satispay deeplink is invoked with IAB (ionic plug-in) via a PWA that is run on a docker container and tested through a mobile device with chrome.

On the mobile, the satispay dev apk is installed and set up with a developer account.

The link I use to open the satispay app and charge is:

satispay-stag://external/generic/charge?token=${this.paymentId}&callback_url=${this.callbackUrl}

and the paymentId is the id I get by calling the endpoint g_business/v1/payments with the appropriate parameters, again in staging.

I have tried both using the callback_url on the g_business/v1/payments POST call and in the url scheme as shown above in the url scheme, but neither open the url I pass to the callback_url after the payment is completed on the satispay app.

The callback_urls I tried passing were an https url and a localhost url.

What happens

Satispay app is launched via the browser from the PWA and the payment is made, then satispay app minimizes and displays an overlay showing that the payment has been sent. However after that I am still on the payment page of my PWA and not redirected to the page assigned to (e.g: a success page on my PWA)

Expected Behaviour

Satispay app is launched via the browser from the PWA and the payment is made, then satispay app minimizes and displays an overlay showing that the payment has been sent
and redirects to the url provided in the callback_url (e.g: to a success page on my PWA).

Is there something that I am missing? Perhaps some limitations on how it is used or should be used?