
Payment Confirmation Policies for Blockchain Apps
Choose blockchain payment confirmation rules with network finality, event validation and workflow states, instead of treating submission as settlement.
Read the guideIndexbase journal / ideas for builders
Practical guides to blockchain APIs, wallet data and the evidence behind a useful answer. Clear concepts, worked examples and better questions for your next integration.
Follow the article feed200 articles / page 8 of 13
In-depth introductions and focused field guides, organised around practical questions.

Choose blockchain payment confirmation rules with network finality, event validation and workflow states, instead of treating submission as settlement.
Read the guide
Model invoices with multiple transfers, partial payments and excess receipts, while keeping settlement eligibility and refund decisions explicit.
Read the guide
Track source and destination bridge evidence as separate stages, preserve message identity, and avoid treating a source-chain lock as destination delivery.
Read the guide
Calculate portfolio exposure without hiding debt, collateral restrictions or duplicate representations of the same underlying claim.
Read the guide
Use Solana signature history with explicit address scope, commitment and pagination, and avoid treating one address lookup as complete wallet economics.
Read the guide
Distinguish Solana wallet ownership from token-account balances, and keep mint identity, authority and account lifecycle in portfolio data.
Read the guide
Interpret Solana pre- and post-token balances with account indexes, mint identity and missing-side handling, without inventing a zero-valued historical account.
Read the guide
Use inner-instruction evidence to understand composed Solana execution, while preserving top-level instruction context and decoder coverage.
Read the guide
Choose processed, confirmed or finalized Solana observations according to workflow requirements, and keep commitment separate from freshness and transaction success.
Read the guide
Understand Bitcoin change-output inference, avoid treating every output as an external payment, and preserve uncertainty in wallet transaction reports.
Read the guide
Use Bitcoin outpoints to identify spendable outputs, resolve input references correctly, and avoid treating a transaction ID as a unique holding.
Read the guide
Calculate Bitcoin fees from resolved input values and outputs, preserve exact satoshi arithmetic, and distinguish total fee from fee rate.
Read the guide
Explain why one Bitcoin address rarely defines a complete wallet, and use authorised address sets or descriptors with explicit discovery boundaries.
Read the guide
Keep rollup execution transactions separate from parent-chain settlement records, linking them without assuming one hash or timestamp represents both layers.
Read the guide
Compare rollup data interpretation through execution, publication and settlement stages, without assuming that every rollup shares the same finality or withdrawal rules.
Read the guide
Distinguish block-depth confirmations from protocol finality, and build cross-chain reporting policies without pretending one numeric threshold fits every network.
Read the guideThe editorial approach
Each guide starts with a concrete developer question and separates technical observations from the interpretation an application adds. Worked examples use illustrative values; references point to standards and technical documentation.
Published by Indexbase. Explore related guides as your requirements develop, from a first data question to a more deliberate integration workflow.