Dynamic Commission System #6

Open
opened 2026-06-13 21:58:17 +00:00 by padreug · 0 comments
Owner

Migrated from aiolabs/lamassu-next#6 — opened by @padreug on 2026-01-25.\n\n## Overview

Implement a dynamic commission system for the ATM kiosk that calculates fees based on multiple factors rather than a static percentage.

Requirements

Tiered Commission Rates

  • Commission tiers based on transaction amount (e.g., lower % for larger transactions)
  • Configurable tier thresholds and rates per operator

Environmental Factors

  • On-chain fee adjustment: When offering on-chain cash-in settlement, factor in current mempool fees
    • Query fee estimates and add appropriate markup to cover mining costs
    • Prevents operator losses during high-fee environments
  • Liquidity conditions: Potential adjustment based on channel capacity/balance

Configuration

  • Operator-configurable via dashboard
  • Per-machine overrides possible
  • Real-time fee estimation display to customer before confirmation

Technical Considerations

  • Fee calculation should happen in the state machine before presenting final amount to customer
  • Need integration with fee estimation service (mempool.space API or similar)
  • Commission structure should be part of the machine configuration (Kind 30078 beacon or operator settings)

User Experience

  • Customer sees final amount they will receive AFTER all fees
  • Transparent breakdown available (base commission + network fees)
  • No surprises at settlement time
  • Cash-in flow (ndebit implementation)
  • On-chain settlement option (future feature)
> _Migrated from [aiolabs/lamassu-next#6](https://git.atitlan.io/aiolabs/lamassu-next/issues/6) — opened by @padreug on 2026-01-25._\n\n## Overview Implement a dynamic commission system for the ATM kiosk that calculates fees based on multiple factors rather than a static percentage. ## Requirements ### Tiered Commission Rates - Commission tiers based on transaction amount (e.g., lower % for larger transactions) - Configurable tier thresholds and rates per operator ### Environmental Factors - **On-chain fee adjustment**: When offering on-chain cash-in settlement, factor in current mempool fees - Query fee estimates and add appropriate markup to cover mining costs - Prevents operator losses during high-fee environments - **Liquidity conditions**: Potential adjustment based on channel capacity/balance ### Configuration - Operator-configurable via dashboard - Per-machine overrides possible - Real-time fee estimation display to customer before confirmation ## Technical Considerations - Fee calculation should happen in the state machine before presenting final amount to customer - Need integration with fee estimation service (mempool.space API or similar) - Commission structure should be part of the machine configuration (Kind 30078 beacon or operator settings) ## User Experience - Customer sees final amount they will receive AFTER all fees - Transparent breakdown available (base commission + network fees) - No surprises at settlement time ## Related - Cash-in flow (ndebit implementation) - On-chain settlement option (future feature)
padreug changed title from [reserved] migration number alignment to Dynamic Commission System 2026-06-14 06:54:39 +00:00
padreug reopened this issue 2026-06-14 06:54:39 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aiolabs/bitspire#6
No description provided.