# Dryfit Scenario: Transaction / volume-based SaaS

> Payment and transaction platforms where value tracks with successful throughput. Positive signals end in payment completion; negative signals include refunds and invoice stall.

*Source: [https://www.getbeton.ai/oss-tools/dryfit/scenarios/posthog-transaction-volume/](https://www.getbeton.ai/oss-tools/dryfit/scenarios/posthog-transaction-volume/)*

**Scenario kind:** posthog_transaction_volume
**Use-case kind:** volume
**Value metric:** Transactions processed, GMV, payments
**Config file:** `configs/posthog_transaction_volume_mvp.yaml`
**Dataset id:** `posthog_transaction_volume_mvp_v1`

## Scale

- Accounts: 280
- Users per account (mean): 4
- Sessions per user (mean): 7
- Duration: 30 days

**Success event:** `payment_completed` (account)

## Research metrics

- Transaction volume trend
- Avg transaction value growth
- Transaction frequency per account

## Positive signals (ground truth)

- **order_to_payment** (count 90): `order_created → payment_completed`
- **invoice_to_payment** (count 50): `order_created → invoice_generated → payment_completed`

## Negative signals (ground truth)

- **invoiced_not_paid** (count 55): `order_created → invoice_generated`
- **refunded_volume** (count 30): `payment_completed → refund_issued`