How to track KBA transactions?

BoldSign tracks knowledge-based authentication (KBA) usage separately from other document usage. Account admins can review KBA transactions to monitor usage, credit type, signer details, and billing activity.

KBA transactions are useful when you want to understand how many KBA challenges were started and whether they used plan credits or pay-as-you-go credits.

How to view KBA transactions?

To track KBA transactions, follow these steps:

1. Open Settings

   Go to Settings from the BoldSign sidebar.

2. Open Subscription

   Select the Subscription page.

3. Open transactions

   Click the option to view transactions or usage details.

4. Filter by KBA

   In the transaction dialog, select KBA from the feature filter.

5. Review KBA transaction details

   Review the transaction list for KBA usage details.

KBA transaction details

KBA transaction records can include:

• Document ID
• Created date
• Feature type as KBA
• Action, such as Challenge Started
• Credit type, such as Plan or Pay As You Go
• Signer name

The action Challenge Started means the signer started a billable KBA challenge and security questions were generated.

What KBA transactions help you track?

KBA transactions help admins:

• Monitor how many KBA challenges were started.
• Check whether KBA usage used plan credits or pay-as-you-go credits.
• Identify which signer triggered the KBA usage.
• Review KBA usage for a specific billing period.
• Export transaction records for internal reporting.

Exporting KBA transactions

If your account supports transaction export, you can download or export transaction records. Use the KBA filter before exporting if you want the report to include only KBA transactions.

Why a KBA transaction may appear even if verification failed?

A KBA transaction can appear even if the signer did not successfully complete KBA. KBA usage is recorded when a signer starts a billable KBA challenge, not only when the signer passes verification.

For example, if a signer starts KBA and security questions are generated, the KBA usage may be recorded as Challenge Started even if the signer later fails the questions or does not complete the verification.