Notifications of change now update your saved payment methods automatically

When a bank returns a notification of change (NOC) correcting a routing number, account number, or account type, dhango now applies that correction to the saved payment method instead of just telling you about it. Future payments go out with the corrected details, so you stop re-sending entries against an account the bank has already told you is wrong.

• The masked account number on the token updates too, so what you see in the dashboard matches what's on file.
• Payer tokens fire a token-update webhook event when the correction is applied, so your system can stay in sync.
• Email notifications now say the information has been updated, rather than asking someone to update it manually.
• A correction is applied only when the change code's required fields are all present and valid, and only to the payment method the original entry was sent against. Anything else stays notification-only — nothing is partially applied.
• Change codes that carry no correctable data (C04, C08, C09, C13, C14) keep the existing "an update is required" email.

This applies to the NACHA TPS rail. NACHA Direct is unchanged for now and is on the roadmap.

Retried ACH entries are now marked as reinitiated

Batch fund attempts that get retried now carry RETRY PYMT in the company entry description of the NACHA batch header, per NACHA Operating Rules §2.12.3 for reinitiated entries. First attempts are unaffected and continue to use the company entry description configured on your processor credential. This applies to both NACHA TPS merchant files and NACHA Direct files.