...
The SDK keeps local storage of each time the app requests data from the SDK for authentication. This is when either “authenticate” (Simplified Interface) or “getAuthenticationRequestParameters” (Spec Interface) is called. A time stamp and SDK Transaction ID is stored. About every 7 to 10 days the SDK will post this data to the licensing server (and verify the license is still valid). mSIGNIA uses the transaction data posted to the licensing server for billing the customer.
If the transaction goes to challenge flows where additional data is passed, the same “SDKTransactionID” is used and there are no more additional transactions counted.
If a customer repeatedly calls “authenticate” or “getAuthenticationRequestParameters” due to bad programming practice, this would cause a lot of sdkTrxnIDs to be generated but the 3DS Server would only be sent a subset of those sdkTrxnIDs. Thus, the customer can review mSIGNIA’s list of generated sdkTrxnIDs against their list of received sdkTrxnIDs and resolve which sdkTrxnIDs were ‘valid’ for billing. mSIGNIA is able to ID the app/browser creating extraneous sdkTrxnIDs and have the customer work to fix the problem. If the app/browser refuses to fix this issue, mSIGNIA can ultimately block that app/browser from generating any sdkTrxnIDs.
Does the license key ever need to be updated?
...