The web client hides many of the details of Veriplace's OAuth-based authorization process, providing a persistent state across transactions that may involve redirects and callbacks.

An instance of WebClient manages the following resources:

• A VeriplaceClient which handles communication with the Veriplace server. This is the lower-level client API, which you can still access if desired.
• Asynchronous request managers which allow time-consuming requests to run on background threads.
• Token caches to preserve user access tokens transparently across callbacks.
• An optional IStatusViewRenderer allowing Veriplace to display error or waiting pages automatically.

The web client serves as a factory for instances of VeriplaceState, representing the status of Veriplace transactions within the current HTTP request. Most transactions are done through methods on the VeriplaceState object.