Keep following up on promised refunds

TASK SETTINGS — fill only what is relevant
Scope: [selected accounts, records, or task]
Budget: [amount and currency, or no new spending]
Deadline: [date, time, and timezone]
Tone: [polite and concise]
Contact channel: [no contact until approved]
Approval: Read-only first. Ask before sending, calling, submitting, cancelling, booking, paying, signing, or changing anything.

Build a standing follow-through brief for refunds already promised or requested. Read only the case records, merchant messages and statements I authorize. Give each underlying charge one case ID and one owner; import existing cases before adding new ones.

For each case, separate requested, merchant accepted, processing, posted and rejected states. Record the original charge, promised amount and currency, merchant reference, stated processing window, payment destination and any filing deadline. Never replace a known date with a guessed typical window.

On each scheduled check, compare current evidence with the previous state. A merchant saying refunded is not proof of posting to my account. Ask for only the missing statement line or secure account access needed to reconcile it. If the merchant deadline passes, draft a factual follow-up in the existing thread and queue it for my approval; do not send it automatically.

Notify me immediately when an applicable dispute deadline might expire before routine follow-up. Avoid duplicate requests and prevent both agents working the same case. Close only with posting evidence, a confirmed final rejection, or my instruction. Preserve a redacted record rather than full payment credentials.

Standing-brief setup: First perform one read-only baseline check. Then propose the exact schedule, timezone, end/review date, trigger, cost limit, and notification destination for my approval. Create a recurring task only after approval and only with a real scheduler. Return the actual task ID, next run, and pause/stop instructions; otherwise say it is not scheduled. On subsequent runs, compare with the last successful checkpoint, deduplicate alerts, retain only necessary state, and report failures or stale access rather than treating them as no change. Respect service rules and rate limits. No external actions are authorized by a scheduled check.

Verification checkpoint: Do not call this filed, cancelled, changed, paid, or done without the relevant confirmation number, receipt, provider message, or before-and-after record. Distinguish drafted, blocked, submitted, accepted, and verified results. A provider promise is not posted money. Before any sworn statement, attestation, or signed claim, show me the exact facts and obtain my explicit confirmation; never invent facts or copy my signature.