DocuSign C# SDK – Recipient View works in one demo account but fails in another

Question

I’m using the DocuSign C# SDK to generate a Recipient View URL and load it inside an <iframe> in my application.The code and integration configuration are essentially the same, but I’m seeing different behavior depending on the demo account:Demo Account A: The Recipient View URL initially loads correctly inside the iframe and displays the authentication/verification process. However, after the authorization code is entered, the flow fails and the next page cannot be loaded inside the iframe due to X-Frame-Options / Content-Security-Policy (frame-ancestors).	Demo Account B: The exact same implementation works correctly, including the step after entering the authorization code.So, the issue does not occur when the Recipient View URL is initially loaded. The iframe successfully loads the authentication flow. The problem happens after the authorization code is entered, when DocuSign redirects/loads the next page. The browser error is related to the page not being allowed to be displayed inside a frame because of X-Frame-Options / frame-ancestors, for example:Refused to display 'https://demo.docusign.net/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.  My question is:Is there an account-level setting in DocuSign that determines whether a Recipient View URL can be loaded inside an iframe?

troy.w · Answer

Hi,The envelope you have created requires phone authenticationhttps://support.docusign.com/s/document-item?bundleId=gav1643676262430&topicId=kvc1578456523785.html&_LANG=enus&language=en_US&rsc_301This is not supported in an iframe, see the snipped and documentation:Classic signing session.This signing session works with the most authentication options including Access code, KBA, and ID verification. This signing session can be used with desktop and mobile browsers.You can use iframes, but they are not supported with all types of authentication options or SBS pen types. Only full-screen iframes are supported for signers on mobile devices.Documentation:https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing/Either the envelope you created is triggering Phone Authentication, or the other demo account has phone authentication as required for all senders on the account, either way this authentication option isn’t supported in an iframe.

Sign up

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Docusign Community

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.