urgent: do we need a separate sandbox?

Hi Jamel, In short, my suggestion would be having separate accounts for both Sandbox and Production environments. If only talk about Signing Ceremony Customization, it's possible to add your customer's email under your Sandbox main account, cause almost all settings(logo, layout, handover link, etc) can be set in package level which allows your different senders/customers to have different signing experience. But if your existing implementation replies on Account level Setting, it would add extra work for you to adjust your code using package level setting. And there could be some other unexpected defects if you do so, depending on how much OneSpan Sign capabilities your platform has been integrated with. There're many options that can only be set in account level and be shared by all senders, such as Email Notification customization, and even Callback Event Notification settings! Overall, it's easier and more flexible to create another account, migrate all account level settings through our support team ([email protected]) and adjust account level signing ceremony to your customer's logo. But as I mentioned above, if your integration scope was limited and just for a test purpose, it's also possible to add the account under your main account. Hope this could help! Duo