Skip to content

Monitor USDT / USDC Deposits and Payouts

Monitor supported USDT and USDC transfers for deposits, merchant notifications and payouts; a notification alone does not establish final settlement.

For developers and AI Agents. Start with your API key and your HTTPS receiver; filter token contracts and amounts in your application.

Basic transfer monitoring is available

Amount and token filtering runs in your receiver. Server-side conditions, multiple confirmation stages and IM alerts are coming soon.

Before you start

Developers and AI Agents follow the same setup flow. Set BLOCKVECTRA_API_KEY securely and install curl and jq. Choose CHAIN from the task coverage below; verify the token contract on that chain, recipient and integer amount in smallest units. For Push, deploy your own HTTPS receiver on port 443 and check the authenticated chain list, confirmation range and halted status before creating a subscription.

See the programmatic sign-up guide →

Verify exchange deposits

Poll ERC-20 Transfer logs for your deposit address. Set TOKEN_CONTRACT and RECIPIENT from trusted payment configuration; set FROM_BLOCK and TO_BLOCK to hex heights within node coverage and the published block range limit. Advance a durable cursor only after processing each range.

set -euo pipefail
: "${BLOCKVECTRA_API_KEY:?}" "${CHAIN:?}" "${TOKEN_CONTRACT:?}" "${RECIPIENT:?}"
: "${FROM_BLOCK:?}" "${TO_BLOCK:?}"
TOPIC_TO="0x000000000000000000000000${RECIPIENT#0x}"
jq -n --arg token "$TOKEN_CONTRACT" --arg to "$TOPIC_TO" \
  --arg from "$FROM_BLOCK" --arg end "$TO_BLOCK" \
  '{jsonrpc:"2.0",id:1,method:"eth_getLogs",params:[{address:$token,
    fromBlock:$from,toBlock:$end,topics:[
      "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",null,$to]}]}' |
  curl --fail-with-body -sS "https://api.blockvectra.com/v1/$CHAIN" \
    -H "x-api-key: $BLOCKVECTRA_API_KEY" -H 'Content-Type: application/json' --data-binary @-

Result to verify

Match the contract, recipient and integer amount; check the receipt and your confirmation policy before crediting. Deduplicate by chain, transactionHash and logIndex, retaining blockHash to reconcile reorgs.

Read the full guide

Receive merchant payment notifications

Set RECIPIENT and RECEIVER_URL, then create a basic address subscription with the chain default confirmations. Store the returned secret securely. Wait for applied_version >= change_version and record applied_from_block before expecting matching activity.

Supported chains

Choose CHAIN for this example from the chains currently executable below

set -euo pipefail
umask 077
: "${BLOCKVECTRA_API_KEY:?}" "${CHAIN:?}" "${RECIPIENT:?}" "${RECEIVER_URL:?}"
PUSH_URL='https://api.blockvectra.com/v1/push'
curl --fail-with-body -sS "$PUSH_URL/chains" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" > push-chains.json
jq -e --arg chain "$CHAIN" 'any(.chains[]; .chain == $chain and .halted == false)' push-chains.json
jq -n --arg url "$RECEIVER_URL" --arg chain "$CHAIN" \
  '{url: $url, chains: {($chain): {}}}' > create.json
curl --fail-with-body -sS "$PUSH_URL/subscriptions" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  -H 'Content-Type: application/json' -d @create.json > subscription.json
SUBSCRIPTION_ID=$(jq -er '.id' subscription.json)
jq -n --arg recipient "$RECIPIENT" '{addresses: [$recipient]}' > addresses.json
curl --fail-with-body -sS "$PUSH_URL/subscriptions/$SUBSCRIPTION_ID/addresses/add" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  -H 'Content-Type: application/json' -d @addresses.json > address-change.json
curl --fail-with-body -sS "$PUSH_URL/subscriptions/$SUBSCRIPTION_ID" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY"

Result to verify

The first matching event counts only after raw-body signature verification, token/recipient/integer-amount checks, durable deduplication by event id and a receiver 2xx response. Subscription HTTP 201 is not a delivered payment notification.

Read the full guide

Track payouts

Set TX_HASH to a transaction already submitted by your payment system. Read its receipt with JSON-RPC; compare receipt.blockNumber with the current head and reconcile the expected token transfer logs.

set -euo pipefail
: "${BLOCKVECTRA_API_KEY:?}" "${CHAIN:?}" "${TX_HASH:?}"
jq -n --arg hash "$TX_HASH" \
  '{jsonrpc:"2.0",id:1,method:"eth_getTransactionReceipt",params:[$hash]}' |
  curl --fail-with-body -sS "https://api.blockvectra.com/v1/$CHAIN" \
    -H "x-api-key: $BLOCKVECTRA_API_KEY" -H 'Content-Type: application/json' --data-binary @-

Result to verify

A null receipt or pending transaction is not a received payment. Check receipt.status, the token contract, recipient, integer amount and your confirmation policy; a successful receipt alone does not prove the expected transfer.

Read the full guide

Confirmation and coverage boundaries

N confirmations are not chain finality. Basic Push has no server-side amount or token filters; filter in your receiver. Contract-internal native-coin transfers are not covered. Pending is not payment received. Reconcile replaced blocks on chain.reorg and process canonical replacements idempotently. Some chains exclude system transactions from coverage; see the corresponding chain page.

Recover gaps and reconcile history

Replay resends retained matches only; it does not recover history before subscription or address activation. Use bounded RPC polling for earlier intervals or gaps. Keep a per-chain cursor and reconcile reorgs using the full guide.

Read the full guide

Optionally query indexed ERC-20 transfers on the chains below. Set FROM_BLOCK and TO_BLOCK to decimal heights within indexed coverage; check freshness and coverage, and follow next_cursor until absent. Verify each token contract, recipient and integer amount; indexed data is not proof of finality.

: "${BLOCKVECTRA_API_KEY:?}" "${CHAIN:?}" "${RECIPIENT:?}" "${FROM_BLOCK:?}" "${TO_BLOCK:?}"
curl --fail-with-body -sS --get \
  "https://api.blockvectra.com/v1/data/$CHAIN/addresses/$RECIPIENT/transfers" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  --data-urlencode 'standard=erc20' --data-urlencode 'direction=in' \
  --data-urlencode "from_block=$FROM_BLOCK" --data-urlencode "to_block=$TO_BLOCK"
Read the full guide

Pricing & Billing Rules

eth_getLogs method weight: 30 CU ($3.00 per 1,000,000 requests).

Requests rejected by the service (such as block range exceeded or rate limited) are not billed. See the billing rules guide or view the full pricing table.

Webhook push

CU weights from GET /v1/plans. Automatic retries are free.

Free addresses per account per UTC day: 1000

Free address allowance per account per UTC day, shared by all subscription groups regardless of plan. For each group, count its maximum address count while online during that day; allocate the allowance in ascending group ID order. The same address in two groups counts twice; the number of chains in a group does not multiply its address count. A group offline or deleted for the entire day contributes nothing. For each group, the remaining count after its share of the allowance is multiplied by the `push.address_day` CU weight in `method_weights`. The current configured allowance comes from the same pricing policy used for the address-day charge; it is not an account capacity limit or a separate allowance per group.

MethodBilling unitCU
push.address_dayBillable address-day33
push.historySuccessful history request25
push.logDelivered data event150
push.native_transferDelivered data event150
push.token_transferDelivered data event150

Start Monitoring Payments