Creating Sender AccountTuesday, August 2, 2022 at 12:08am
We will have a multiple subscribers using our service. Currently, we have one single account under onespan for the integration of onespan into our system. We are using the saved layout for applying the fields in the document. Since, we will have different subscribers, if we save a layout for each of them, the layouts can be accessed by all the clients, which we don't want them to. So, we have decided to separate the account for each of them via sender account.
Looking into the sender account, I found that, yes, we can have sender API key and use that for creating a transaction on subscribers level. The problem with this approach is, subscribers can access the account and can use the onespan feature via sandbox.esignlive.com. We do not want our subscribers to access the onespan account and use the transaction feature via onespan. The other solution, I thought would be to create a new role with limited permission but in this approach to create a transaction via our iframe, the user should still be provided with the permission of creating a transaction, in doing so, they can again access the onespan login via the user credentials.
The last option I had was creating a sub account. Currently, the subaccount feature is not available into our account, please suggest a best possible solution or workaround so that the different account can be distributed to the clients and still stop them from accessing the transaction. If creating a subaccount would fix the problem, I will request the same to OneSpan.
Please let me know.