Distinguish a pending Hedera airdrop from delivered tokens

A successful TokenAirdropTransaction may create a pending transfer when the intended recipient lacks an available association. The distribution report needs an intermediate state for that case.

Inspect transfer results for each recipient

The SDK example builds a transfer intent for 25 smallest units. For ordinary eligible transfers, an existing association or available automatic slot can permit immediate delivery. If the receiver has neither, inspect the pending airdrop record. Keep sender, receiver and token identity together.

const intent = new TokenAirdropTransaction()
  .addTokenTransfer(tokenId, distributorId, -25)
  .addTokenTransfer(tokenId, recipientId, 25);

Close the distribution row on the actual outcome

Keep a pending item open until it is claimed or canceled. For an NFT, include its serial number to distinguish it from other items in the collection. When reconciling a mixed distribution, count immediate credits independently from pending entries. A single success receipt for the outer airdrop is insufficient to mark every intended recipient as funded.

Sources