Independent and educational: this site does not process payments, hold funds or offer wallets.Independent and educational. No payment processing, no custody.How we work
    BlockchainPayments.caTest before you commit
    SIMULATIONRuns only in your browser. Testnet or simulated data. No real funds, no custody, never enter private keys or recovery phrases.
    Sandbox · mempool to finality

    Transaction lifecycle visualizer

    A payment is not one event but a sequence: request, broadcast, mempool, blocks, confirmations, finality and (if you convert) settlement to CAD. Step through it, including the ways it goes wrong.

    Free · runs in your browserAssumptions reviewed October 30, 2026Methodology

    Mitey the yeti with a testnet flag

    Scenario

    Controls

    Time is compressed. Block times are illustrative defaults; real networks vary with congestion.

    Step 1 of 9 · t + 0 s

    Payment request created

    Amount, asset, network, receiving address and expiry are fixed; the quote locks a CAD value.

    Webhook: payment_request.created · see payload

    No transaction yet.
    1. 0 s

      Payment request created

      Amount, asset, network, receiving address and expiry are fixed; the quote locks a CAD value. payment_request.created

    2. 5 s

      Waiting for the payer

      The payer scans the QR code or copies the address. Nothing has moved yet.

    3. 45 s

      Transaction seen (0 confirmations)

      The transaction is in the mempool. It can still be replaced, dropped or never confirmed: do not fulfil. payment.detected

    4. 51 s

      1 confirmation

      Included in a block. payment.confirming

    5. 1 min 3 s

      2 confirmations

      Another block was added on top. payment.confirming

    6. 1 min 15 s

      3 confirmations

      Another block was added on top. payment.confirming

    7. 13 min 33 s

      Finalized

      The protocol now treats the block as final; reversing it would require extraordinary, costly events.

    8. 13 min 34 s

      Confirmed: mark invoice paid

      Record transaction hash, amount, CAD value and rate source. Now fulfil the order. payment.confirmed

    9. 1 day

      Converted and settled to CAD (if you convert)

      Off-ramp timing depends on your provider and bank business days. conversion.settled

    When is it safe to fulfil?

    Not at detection. Decide a confirmation or finality threshold per network and payment size, write it down, and apply it in code. For larger amounts, wait longer. See on-chain settlement and finality.

    How to use it

    1. Choose a network profile and an outcome.
    2. Press play or step through each state.
    3. Note which webhook fires at each step and when it is safe to fulfil.
    Assumptions, not quotes

    Default values are illustrative planning inputs reviewed October 30, 2026, not market data or any provider’s pricing. Replace them with your own statements. This tool is educational and is not financial, legal or tax advice.

    Keep going

    Want a second look at your numbers?

    Describe your scenario and MITEY will review it with you by email. Free and educational; we do not sell or process payments.

    Request a scenario review