///
The Quicksilver SDK provides powerful, fluent interfaces through its "active record" models: `Account` and `Transaction`. These objects not only hold data but also encapsulate behavior, allowing devel
32 views
~32 views from guests
Guest views are estimated from total page views. These include anonymous visitors and users who weren't logged in when they viewed the page.
The Quicksilver SDK provides powerful, fluent interfaces through its "active record" models: Account and Transaction. These objects not only hold data but also encapsulate behavior, allowing developers to interact with the Quicksilver Engine in an intuitive, object-oriented manner.
These interfaces define the raw data structures returned by the Quicksilver API that the Account and Transaction models wrap.
Represents the raw data structure for an account in the Quicksilver Engine.
Represents the raw data structure for a transaction in the Quicksilver Engine.
The Account class represents an active account in the Quicksilver Engine. It provides methods for account management, delegation, and initiating transactions or product purchases.
The Transaction class represents an active transaction in the Quicksilver Engine. It provides methods for managing the transaction lifecycle, interacting with conditional logic, and handling real-time events.