Skip to main content
New Voice
October 5, 2026
Question

Focused View blocked in production for EU accounts: eu.verify.docusign.net missing from frame-src CSP (phone Identity Verification)

Hello,

 

We are using embedded signing with the Focused View (DocuSign.js) for a captive recipient (ClientUserId is set) whose recipient definition includes phone-based Identity Verification (RecipientIdentityVerification with a phone_number_list input option).

 

This works correctly in our demo/sandbox environment, but fails in production. In production the Focused View iframe never renders the document, because the identity-verification step attempts to frame https://eu.verify.docusign.net/ and it is blocked by the Content Security Policy served on apps.docusign.com.

 

Browser console error:

 

Framing 'https://eu.verify.docusign.net/' violates the following Content Security Policy directive: "frame-src 'self' https://docucdn-a.akamaihd.net/ https://apps.docusign.com https://na.verify.docusign.net https://eu.docusign.net ... https://verify-d.docusign.net https://verify.docusign.net ...". The request has been blocked.

 

Key point: the frame-src allowlist in that CSP includes https://na.verify.docusign.net, https://verify.docusign.net and https://verify-d.docusign.net, but it does NOT include https://eu.verify.docusign.net. Our production account is provisioned in the EU region (base URI eu.docusign.net), so the IDV step is routed to eu.verify.docusign.net, which is not in the allowlist. This is consistent with the flow working in demo, where IDV is served from verify-d.docusign.net (which is allowlisted).

 

Request: please can you add https://eu.verify.docusign.net to the frame-src allowlist used by the Focused View host (apps.docusign.com) for EU-region accounts, so that phone / ID verification can load inside the embedded signing iframe.

 

Thank you

3 replies

New Voice
October 5, 2026

+1 🙏

Translate
Docusign Employee
October 6, 2026

Hi ​@RomainC ,
Thank you for bringing this issue to our attention.

Our team is already working on a fix, which can be tracked under AIE-18726. Once deployed, this bug number will be included in the Docusign product release notes.

For further updates, you can also reach out to your Account team. If the issue persists after several releases, please open a support case and reference AIE-18726 so we can follow up with our Engineering team on your behalf.

Thank you again for helping us improve the Docusign experience.

Translate
RomainCNew VoiceAuthor
New Voice
October 7, 2026

Hi ​@Felipe.Alarcon,

Thank you for the quick reply and for confirming that a fix is in progress under AIE-18726.

We will follow the incoming release notes and reach out to our Account team for updates.

Thanks again,

Romain

Translate