A Stripe Payment Link on a test
A running test (a pre-sale, say) can read its Stripe Payment Link: each payment shows up in its results by itself, "from Stripe", within 15 minutes, or at once with Sync now.
Connect (the product's admin): on the test, Pre-payments from Stripe › pick one of your account's active links (Show my active links) or paste its id (plink_…), and say whether each pre-payment counts once or as its amount › Connect your Stripe link. It uses the product's Stripe connection. With none yet, paste a restricted key there (rk_live_… or rk_test_…; a secret sk_ key is refused). The key needs read access to Subscriptions, Products, Checkout Sessions and Payment Links; without the last two you're told to "Add Checkout Sessions: Read and Payment Links: Read to this key".
Only payments made after the test started count, each once (a re-sync adds nothing). A payer whose email is one of your People is matched to them; if you already logged that person's payment by hand within 2 days, it counts once. The test's line and its verdict work as before.
What we keep: the payment's Stripe id, when, and its amount. Never the payer's email or name: they're matched in memory and dropped. If Stripe stops answering: "Stripe stopped answering on {date}: log by hand". If the key can no longer read the link (a new key without the two permissions): "Stripe stopped letting this key read the link on {date}: add Checkout Sessions: Read and Payment Links: Read to it in Stripe, or log by hand." A new key for Stripe customer data is refused while a link is connected unless it has those two as well. Stop reading it keeps the pre-payments already in.