dusk bot
routinesstripe failed payments

dusk botroutines

which of yesterday's failed stripe payments still need attention?

look up the payment again before chasing the customer. yesterday’s failure can belong to an order that went through on a later attempt.

by the dusk bot team · checked · how we made this

this morning routine matches stripe failure events to their current payment intents. the list in dusk chat keeps only payments that still need attention and flags any status it couldn’t confirm.

pixel art: a cyan pixel bot, a blue pixel bot and an indigo cat bot beside the Stripe mark on a white tile, a long receipt and an alarm clock and a calendar, on a grassy meadow in front of green terraced fields, one saying "already paid this one"

the message

paste this into a chat with your bot

every morning at 9am utc, read payment_intent.payment_failed events from the previous utc calendar day in my live stripe account. fetch every results page. group failed attempts by payment intent id. retrieve each intent again for its current status.

for intents that require a payment method or customer action, put the id, amount, currency and current status here. include the last failure time. omit succeeded and canceled intents. list other statuses separately by their actual name. if a lookup fails, list the id as unknown.

never retry a payment, issue a refund or contact anyone. skip card details and customer emails. stay quiet when all reads succeed and no item remains.
when
daily at 09:00 utc, covering midnight to midnight the day before
needs
read-only stripe access to events and payment intents in the intended live account

what comes back

an example, not a real run

billing review for paul lewis · 18 november utc
pi_7142 · 48.00 usd · requires_payment_method · last failure 21:13 utc
other statuses: pi_7151 · processing · leave pending
one later success omitted.

make it yours

  • use your billing day. if the team closes its books in another time zone, change both midnights and the report label.
  • narrow by currency. keep the original currency beside every amount. never add pounds and dollars into a single total.
  • keep distinct attempts visible. ask for the number of failure events beside each intent if repeated retries matter.

when it goes wrong

  • a payment shows up twice. compare intent ids first. the same customer can place two separate orders for the same amount.
  • a test decline makes the queue. confirm which stripe account the bot can read. rerun for the same date using live data.

what to do with a payment on the list

open the intent before deciding on follow-up. the customer might pay after the morning run. the amount beside a failed attempt tells you what someone tried to pay. it does not tell you how much revenue you lost.

if you need to collect money automatically, dusk bot’s read-only morning list is the wrong pick. use your billing process for collections.

questions

does a failed attempt mean an invoice is overdue?

a payment attempt alone can’t answer that. this routine reads events and payment intents. consult the invoice and its due date before treating a balance as overdue.

the stripe events read covers the past 30 days. choose a date inside that window. an older intent’s current status can’t reconstruct each earlier attempt.1

sources

  1. composio: stripe actions, checked 12 november 2026
  2. dusk bot docs: routines
  3. dusk bot docs: connected apps

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].