# DamageBDD Payments: Execution Credits and Accepted Work

How payment records relate to execution evidence, without assuming guaranteed liquidity or automatic settlement.

Canonical HTML: <https://damagebdd.com/articles/payments.html>



<a id="connect-the-payment-to-a-defined-service"></a>

## Connect the payment to a defined service

The platform distinguishes Lightning top-ups, DAMAGE execution spend,
contractor compensation and conditional swap/hold-invoice jobs. Read the
[payment-flow reference](../payments.md) for the units, custody and
confirmation boundaries.

A top-up pays for execution credits. A scenario reports an observed outcome.
A contractor is paid under an agreed work item and acceptance process. These
are related records, not interchangeable payment triggers.


<a id="liquidity-is-not-an-execution-guarantee"></a>

## Liquidity is not an execution guarantee

Earlier versions of this article described guaranteed buybacks, immediate
liquidity exits and reserve backing. Those promises are not supported by the
implementation evidence referenced by this documentation and are withdrawn
from the current description.

There is no general promise here of token redemption, a market price,
automatic contractor payment or financial returns. Check the actual quote,
service terms and payment receipt for the specific workflow.


<a id="start-with-a-bounded-job"></a>

## Start with a bounded job

Use the [paid verification evaluation](lightning_api_economics.md) to define
a unit of work and exercise interruption/retry cases. The
[contractor process](../contractors.md) describes acceptance and BTC/Lightning
compensation. [Tokenomics](../tokenomics.md) explains execution accounting.