Paddle Dunning & Failed Payment Alerts

When transaction.payment_failed fires, the agent checks how many retries remain, looks at the customer's history, and either waits for Paddle's automatic dunning or pings your CS team for high-value accounts.

Webhook + WhatsApp DMdunningfailed-paymentswebhook

Conversation example

Webhook received: transaction.payment_failed — txn_01HVR4Y (sub_01HWPQ2)
http_request → Paddle API

Payment failed on Paddle. Checking retry schedule and customer context...

Paddle payment failure Customer: Horizon Robotics (billing@horizon-r.com) Plan: Business Annual — $4,800/year Transaction: $4,800.00 (annual renewal, first attempt) Failure reason: 'issuer_unavailable' (bank-side) Paddle retry schedule: Apr 14 (retry 1), Apr 17 (retry 2), Apr 21 (retry 3 + cancel) This is a high-value account ($4,800 ARR) and the failure is bank-side (not card-dead). Paddle dunning will likely recover this automatically, but I suggest a courteous ping to their finance contact now so they know. Want me to send a light-touch WhatsApp message to their finance lead (we have her number) and schedule a check-in for Apr 15?

More Paddle use cases

Deploy this in minutes

Create a LunoGen agent, connect Paddle, and start running this workflow from WhatsApp today.

Back to Paddle