# Free lead magnet: Base USDC receive checklist

A practical pre-flight checklist for taking your first (or next) **USDC payment on Base**.  
Public addresses and tx hashes only — never paste seeds, private keys, or recovery phrases into notes, chat, or agent memory.

**Also free:** [payment-proof email template](./payment-proof-email.md) · [sales log stub](./sales-log-template.md)

---

## Before you publish a pay address

1. Confirm chain id **8453** (Base). Reject Ethereum mainnet (1), Base Sepolia, or “whatever the wallet defaults to.”
2. Confirm the **native USDC** contract on Base: `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`  
   (bridged / fake USDC tokens with similar names do not count.)
3. Publish only a **public** receive address. Never a seed, private key, keystore, or “sign this blank message to verify.”
4. Prefer a dedicated receive address (or clear label) so sales ops stay separate from long-term holdings.
5. Write down your support email and the exact amount / product SKU on the sales page before anyone pays.

## When a buyer says they paid

1. Ask for: **tx hash**, **amount**, **chain (Base)**, and **buyer email**.
2. Open a Base explorer (e.g. basescan.org) and paste the tx hash yourself — do not trust screenshots alone.
3. Confirm: status success, token = USDC (correct contract), amount matches invoice, **to** = your published address.
4. Only then deliver the zip / download link. Log the sale (date, email, tx, product version).
5. If anything mismatches (wrong chain, wrong token, wrong amount), reply with the mismatch and do not ship until corrected.

## Soft red flags (pause and re-check)

- Buyer pressures you to “send product first, tx pending”
- Payment on Ethereum / Arbitrum / “Base but wrong USDC”
- Requests that you connect a wallet, sign a permit, or refund a “test” amount
- Emails that ask you to re-enter a seed to “unlock” delivery

## After delivery

1. Keep the sales log row forever (tax / dispute / re-send).
2. Do not promise refunds for “changed my mind” on instant digital goods unless your policy says so.
3. Never move buyer funds with their keys — you only receive.

---

## Upgrade paths

| Asset | Price | What you get |
|-------|-------|----------------|
| This checklist + email template | Free | Receive ops + proof email |
| [Base Invoice Kit](https://gitlab.com/kasperwallet/base-invoice-kit) | Free | Invoice Markdown |
| Agent Bounty Claim Checklist | 9 USDC | Claim/verify checklist for fixed-pay agent bounties |
| [Agentic Crypto Ops Pack](../crypto-ops-pack/) | **19 USDC** promo (29 list) | Full tracker, pitches, cadence, scam filter, board gate |

Pay USDC on Base to `0x0Ae3CC597f332906f29bBd24b57bDEb60C0a95B3`, then email the tx hash to `kasperwallet@outlook.com`.

Sales page: see `LIVE_URL.txt` / `SALES.md` in the product folder, or GitLab `BUY.md`.