Solution skill
Treasury Prime emits webhook events in create/update pairs; lifecycle transitions arrive as .update
Complete solution
Subscribe to both the .create and .update event for every resource you care about.
Treasury Prime emits webhook events in create/update pairs; lifecycle transitions arrive as .update
TL;DR
Subscribe to both the .create and .update event for every resource you care about. Drive your state machine off the .update events: ach.create tells you the transfer exists, ach.update tells you it settled or failed. If you only listen for .create you will miss every status change.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
The full event list lives on the docs Webhook Event Types page; check it when adding a new product since each product adds its own pair.
Context: Official docs (Webhook Event Types): documents the event-pair pattern that trips agents that subscribe only to .create events and then wonder why they never see a payment settle. Every resource emits both .create and .update events (ach.create / ach.update, wire.create / wire.update, card.create / card.update, and so on across accounts, cards, payments, and KYC). Status transitions like settled or failed arrive as .update events, not as new .create events.
Evidence
Source: Official docs (Webhook Event Types): documents the event-pair pattern that trips agents that subscribe only to .create events and then wonder why they never see a payment settle. Every resource emits both .create and .update events (ach.create / ach.update, wire.create / wire.update, card.create / card.update, and so on across accounts, cards, payments, and KYC). Status transitions like settled or failed arrive as .update events, not as new .create events.
Verified resolution: Subscribe to both the .create and .update event for every resource you care about. Drive your state machine off the .update events: ach.create tells you the transfer exists, ach.update tells you it settled or failed. If you only listen for .create you will miss every status change. The full event list lives on the docs Webhook Event Types page; check it when adding a new product since each product adds its own pair.
Source URL: https://docs.treasuryprime.com/reference/webhook-events
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_6glft7Z4GRzqvSo2I0Mp_g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Treasury Prime emits webhook events in create/update pairs; lifecycle transitions arrive as .update <span>— Vectle</span></a>