New Payments

Payments to teams now raise a site alert

Supporter subscriptions, Store orders and paid Form submissions previously left no trace beyond a database row.

Magpie already emailed the site administrator about new accounts and about subscriptions to Magpie itself. Money paid to a team through Stripe Connect did not: a Supporter subscription, a Store order or a paid Form submission was recorded in the database and nowhere else.

Every Connect event the payments webhook applies now raises an alert instead, naming the commerce area, what happened, the selling team, the amount, any refunded portion, the customer, and the Stripe references needed to find the transaction. Refunds, disputes, failed payments and a team disconnecting its Stripe account are all included, as is an event that fails to apply, since Stripe will keep retrying it.

This is administrative only. Nothing changes for teams selling through Magpie or for their customers, and the alert is sent after the payment has been recorded so a mail problem can never affect a payment.

The recipient is configured as ADMIN_NOTIFICATION_EMAIL, which also receives the existing new-account and Magpie billing alerts. It falls back to the previous NEW_SIGNUP_NOTIFICATION_EMAIL setting, so no deployment change is required.