My bad the issue was caused by a bad configuration server side... We passed as initiativeContext parameter a domain name with https://, while our verified domain in our developer account doesn't include this prefix... Now it's fixed and operational.