Treating "settled" as the end of the story
How you'll know: A consumer debit is marked settled and the loan or invoice is closed, then it comes back weeks later.
Fix: For consumer debits (web or phone authorized), the customer's bank can return them as unauthorized for up to 60 calendar days after settlement. Keep the record open to returns, and reopen the balance automatically when one arrives.
Payouts failing on a short Ledger
How you'll know: Authorizations for credits come back declined with NSF on a busy day.
Fix: Payouts draw on the available balance, not the pending one. Watch it, set a minimum balance, or schedule a deposit ahead of payout runs.
Retrying a returned payment the wrong way
How you'll know: A debit came back R01 or R09 for insufficient or uncollected funds and you simply send it again.
Fix: Plaid requires those retries to carry the description "Retry 1" or "Retry 2". Build that in, along with a cap on attempts.
An approved decision taken as a guarantee
How you'll know: You see approved and assume the payment won't bounce.
Fix: Plaid can approve by default when it can't predict return risk. Read decision_rationale and decide what your product does in that case.
Your records and the Ledger drifting apart
How you'll know: Finance can't say which bank deposit covered which payouts.
Fix: Sync sweep.* events next to transfer events, and store Plaid's transfer and sweep IDs on your own payment records.