RevenueFlow.Commerce.Abstractions 0.1.0-alpha.7.2

This is a prerelease version of RevenueFlow.Commerce.Abstractions.
dotnet add package RevenueFlow.Commerce.Abstractions --version 0.1.0-alpha.7.2
                    
NuGet\Install-Package RevenueFlow.Commerce.Abstractions -Version 0.1.0-alpha.7.2
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="RevenueFlow.Commerce.Abstractions" Version="0.1.0-alpha.7.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="RevenueFlow.Commerce.Abstractions" Version="0.1.0-alpha.7.2" />
                    
Directory.Packages.props
<PackageReference Include="RevenueFlow.Commerce.Abstractions" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add RevenueFlow.Commerce.Abstractions --version 0.1.0-alpha.7.2
                    
#r "nuget: RevenueFlow.Commerce.Abstractions, 0.1.0-alpha.7.2"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package RevenueFlow.Commerce.Abstractions@0.1.0-alpha.7.2
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=RevenueFlow.Commerce.Abstractions&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=RevenueFlow.Commerce.Abstractions&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Tool

RevenueFlow.Commerce.Abstractions

Validated contracts for a trusted, confirmed quantity-one purchase, frozen order, independent entitlement grants, resource credit ledger entries and integer balances. IPurchaseFulfillmentService exposes scoped fulfillment and reads. These payloads do not authenticate callers or verify payment evidence.

The application supplies a verified PurchaseSource with the integration provider, provider account and underlying transaction ID. Optional origin store, origin account and per-purchase origin transaction IDs must be supplied together. Origin subscription ID records lineage only. A webhook delivery ID or subscription-chain ID is not a per-purchase economic transaction ID. The application resolves the existing user and exact catalog terms from trusted context.

Providers are selected per purchase. One scope and one user can receive purchases from Stripe, RevenueCat, direct Apple or Google stores and other adapters. There is no global provider or one-provider-per-user setting. Supplying canonical origin identity allows the same underlying store purchase observed through multiple integrations to converge on one fulfillment.

ConfirmedPurchase.RawEvent optionally captures the verified source JSON object. It owns a validated clone so it survives disposal of the caller's JsonDocument. Fulfillment preserves it in immutable business history beside normalized event fields; orders retain normalized frozen commerce terms.

IRevenueLifecycleService supplies monotonic subscription reconciliation, trial/paid-through/access and scheduled-change policy, paid-period fulfillment, partial refund/dispute/reversal and explicit consumed-resource policy. Source lots support entitlement-gated spend, reservation/capture/release, transfer, expiry and rollover. Every mutation can attach non-commerce completion writes to the same transaction. Entitlement access reports the effective end after source grant and subscription/trial policy. Every durable adapter must implement shared atomic store requirements; see the implementation README for scan/batch limits and supported recovery behavior.

User registration is a separate operation. Users must already exist in the exact tenant, project, environment and app; creating a user and fulfilling a purchase is not a shared transaction through this API.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (7)

Showing the top 5 NuGet packages that depend on RevenueFlow.Commerce.Abstractions:

Package Downloads
RevenueFlow.Teams.Abstractions

Provider-neutral scoped commerce building blocks for .NET.

RevenueFlow.Commerce

Provider-neutral scoped commerce building blocks for .NET.

RevenueFlow.Customers.Abstractions

Provider-neutral scoped commerce building blocks for .NET.

RevenueFlow.Payments

Provider-neutral durable payment operations and verified purchase intake orchestration.

RevenueFlow.Analytics

Idempotent commerce analytics, scoped reports and recoverable scheduled exports.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.1.0-alpha.7.2 117 11/10/2026