BLVCK MINDZDOCS
Try demo ↗GitHub ↗

BLVCK MINDZ × NEAR / Payment lifecycle

Follow the execution, not the animation clock.

Simulation explains a calculation. A live run advances through observed execution and verified evidence.

What happens after the click

  1. Reserve: bind the invoice to its right, payer, amount and ledger hash.
  2. Fund: receive the configured project test token for that reservation.
  3. Approve: the authorized operator approves the matching fixed-sample ledger.
  4. Distribute: schedule transfers according to the confirmed shares.
  5. Verify: compare the rights receipt and successful token transfers with the expected payment.

Scheduled is not received

The contract’s Paid status means transfers were scheduled. Individual outcomes must still be checked. A receipt event or submitted transaction hash alone does not prove that every participant received funds.

Retries and interruptions

Repeated request IDs recover the stored run. A repeated distribution on the same paid batch is rejected. This does not establish economic deduplication across different invoice IDs or networks.

When a transfer fails

The contract includes held amounts, claims and a refund path. Complete recovery from a failed callback remains unfinished. The public demo is bounded to isolated testnet accounts and fixed recipients; it is not ready for commercial funds.

Inspect the evidence →

Documentation maintenance · 16 November 2026 · Source and scope