fix(achtransfer): add confirmation_id to AchTransfer

[kydav]

Summary of Changes

Adds confirmationId to the AchTransfer model to support returning a confirmation ID that matches the id field from GCU Path.

Fixes # (issue)

Public API Additions/Changes

Added confirmationId (String) field to AchTransfer.

Downstream Consumer Impact

Non-breaking addition. Downstream consumers will have access to a new confirmation_id field on ACH transfer responses. No migration required.

How Has This Been Tested?

No new tests required — field addition follows existing model conventions and no masking logic applies.

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
23397149	Triggered	Generic High Entropy Secret	0f7f8f8	mdx-models/src/test/groovy/com/mx/path/model/mdx/model/MdxLogMaskerTest.groovy	View secret
23397147	Triggered	Generic Password	0f7f8f8	mdx-models/src/test/groovy/com/mx/path/model/mdx/model/MdxLogMaskerTest.groovy	View secret
23397141	Triggered	Generic High Entropy Secret	0f7f8f8	mdx-models/src/test/groovy/com/mx/path/model/mdx/model/MdxLogMaskerTest.groovy	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}