Forums

Hello Duo, 

We are implementing sender account API key for creating transaction on behalf of the sender. While creating a sender's API key, I have found that if the sender ID is same, the API key generated is always the same. In this case, we can save the sender's API key in the database so that next time we don't have to generate the API key again hitting the onespan end point.

If the API key generated for particular sender is always same, we can save the API key in the database otherwise we have to hit the api key generator end point every time? 

Forums

Hello Duo, 

Our requirements: 

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.