Wave 2 Demo Walkthrough

1. What changed since Wave 1

2. The pipeline, step by step

The orchestrator is AvAchService in cam-movemoney-process-api/api/2-Domain/cam.movemoney.process.api.Business/Implementations/AvAchService.cs. Every ACH request flows through these steps. Wave 2 inserts a new step between eligibility and compliance.

3. The six new rule services — what each one does

Each card below describes one service in plain English, the exact rule it enforces, and the rejection message pulled directly from the service source code. Three of them are exercised live in the smoke tests in section 4. The other three are wired end-to-end but their primary path isn't yet triggered by a smoke test — the logic is present and the pipeline invokes them; they just need a payload variant to demonstrate rejection.

4. Live evidence — we actually exercised the pipeline

All five tests below ran against the local stack on 2026-04-24. Every response shown is the actual bytes returned by the running pipeline. Source: ~/code/ach-poc/WAVE2-LIVE-RULE-EXECUTION.md.

4.1 ContributionLimitService rejects $20,000 Roth IRA with catch-up detection

We send a $20,000 Roth IRA contribution for account 10000024 (age 65 in the mock fixture). The IRS 2026 Roth IRA limit is $7,000 plus a $1,000 catch-up for 50+ = $8,000.

curl -X POST http://localhost:5001/ach/contribution -H 'Content-Type: application/json' -d '{
  "transaction_request": {
    "account_id": 10000024, "lpl_account_number": "10000024",
    "amount": "20000.00", "firm_id": 1, "transaction_type": "ACHC",
    "origin_id": "AccountView", "beta_item_seq_no": "1",
    "requested_execution_date": "2026-04-24T12:00:00Z",
    "rep_id": "ABC1", "client_id": 1024,
    "transfer_reason": "IRA Contribution", "transfer_type": "contributionType",
    "user_context": {"advisor_user_name": "TestAdvisor"}
  },
  "contribution_metadata": {
    "contribution_year": 2026, "contribution_type": "Regular",
    "actor_type": "Investor", "ytd_contributions_amount": 0
  }
}'

Actual response:

{
  "status": "Fail", "status_code": 422,
  "data": {
    "error_message": {
      "type": "ContributionLimit",
      "code": 422,
      "errors": [{
        "message": "Projected contributions $20,000.00 exceed IRS limit $8,000.00 for RRH 2026"
      }]
    }
  }
}

Takeaway: the service correctly included the 50+ catch-up when computing the $8,000 limit, then rejected with the specific class code and year in the message.

4.2 Happy path — $3,000 Roth contribution completes

Same payload, amount "3000.00". The pipeline now runs all six rule services, passes each, advances through compliance, and short-circuits downstream BETA/RTT/Kafka because LocalPoc:ShortCircuitDownstream is on.

Actual response:

{
  "status": "Success", "status_code": 200,
  "data": {
    "scheduled_execution_date": "2026-04-27",
    "cm_request_id": "a697e969-f2ba-4426-8d76-b951b07afcde"
  }
}

Takeaway: full pipeline completion. Every rule passed and the orchestrator reached the Kafka-emit step (where the POC intentionally shorts).

4.3 HsaEligibilityService rejects HSA contribution without HDHP

Account 10000047 (HMM HSA, IsHdhpCovered=false in the mock), $1,000 contribution, metadata is_hdhp_covered: false.

Actual response:

{
  "status": "Fail", "status_code": 422,
  "data": {
    "error_message": {
      "type": "HsaEligibility",
      "code": 422,
      "errors": [{ "message": "HSA contribution requires HDHP coverage" }]
    }
  }
}

Takeaway: the rule fires only for accounts starting with H, and correctly gates on the HDHP metadata flag.

4.4 ContributionYearService rejects stale prior-year

Same IRA payload, contribution_year: 2025. Today is 2026-04-24, past the Apr 15 prior-year window.

Actual response:

{
  "status": "Fail", "status_code": 422,
  "data": {
    "error_message": {
      "type": "ContributionYear",
      "code": 422,
      "errors": [{ "message": "Prior-year 2025 contribution window closed (after Apr 15)" }]
    }
  }
}

Takeaway: the service enforces the exact IRS window (Jan 1 – Apr 15) and returns a clear, human-readable reason.

4.5 Withdrawal with RMD reason completes

Using the new POST /ach/withdrawal/with-reason endpoint with transfer_reason: "RMD", amount $5,000 from Roth IRA 10000024.

Actual response:

{
  "status": "Success", "status_code": 200,
  "data": {
    "scheduled_execution_date": "2026-04-27",
    "cm_request_id": "b2326ec5-3f83-4a96-b6fb-6f2a3f50c618"
  }
}

Takeaway: the TransferReason path is operational. UC-W2 (reason-coded withdrawals) is implementable against this endpoint.

5. The three new endpoints we added

Sources: AchController.cs lines 378 (contribution), 419 (withdrawal-with-reason), 459 (delete-queued).

6. The demo script — 5 minutes flat

Open two browser tabs: the static site at https://mandos.team/achwithdrawls/ and a terminal with the local stack running (~/code/ach-poc/start-all.ps1). Follow these steps.

1. (30s) Open the site. “This is the executive surface for the POC. Fourteen pages covering use cases, architecture, gaps, CAD / SD / SyDD, and today’s implementation status.” [Click through to Implementation Status to show the 37-implemented count.]
2. (45s) Set the stage. “Wave 1 proved the plumbing end-to-end for one path. Wave 2 widens eligibility to 32 account codes and adds a six-service rule layer between eligibility and compliance. I’ll show three rule services rejecting bad requests live, and the happy path completing.”
3. (45s) Over-limit rejection (hero moment). “I’m sending a $20,000 Roth IRA contribution for a 65-year-old investor. IRS 2026 limit is $7,000 plus $1,000 catch-up. Watch what the new ContributionLimitService does.” [Run the cURL from section 4.1.] “Notice the response says Projected contributions $20,000 exceed IRS limit $8,000 for RRH 2026. The service read the age from the mock and added the catch-up automatically.”
4. (45s) Happy path. “Drop the amount to $3,000 and the exact same pipeline runs, passes every rule, and returns a scheduled execution date.” [Run the section 4.2 cURL.] “Everything after the rule layer is short-circuited for the POC, but the orchestrator ran all ten steps.”
5. (45s) HSA without HDHP. “Different rule, different account. HSA contribution for an account where the mock says the holder is not HDHP-covered.” [Run section 4.3 cURL.] “HsaEligibilityService fires, pipeline halts with a specific reason.”
6. (30s) Prior-year window. “Today is April 24. The IRS prior-year window closed nine days ago. Watch ContributionYearService enforce the calendar.” [Run section 4.4 cURL.]
7. (30s) Withdrawal with reason. “The new POST /ach/withdrawal/with-reason endpoint supports RMD and excess-return paths.” [Run section 4.5 cURL.]
8. (30s) Close. “Three rule services live. Three more wired with their logic in place, waiting for a payload variant. Everything is in the repo, the static site is the durable artifact, and the code compiles clean. Wave 3 is recurring + tax withholding + real 1099-R / 5498 emission.”

8. If you want to play with it yourself

All four services run locally on Kaushik’s laptop.

• Start: powershell -File ~/code/ach-poc/start-all.ps1. Stops with stop-all.ps1. Also auto-starts at login via the ach-poc-services Windows Task Scheduler job.
• Health endpoints:
  • http://localhost:5001/health — process-api
  • http://localhost:5002/cam-movemoney-system-api/swagger — system-api
  • http://localhost:5003/cam-mm-instruction-system-api/swagger — instruction-system-api
  • http://localhost:5004/swagger — mock-api (plus /mock/accounts/10000024 for a sample)
• Canonical demo accounts:
  • 10000024 — RRH Roth IRA, holder age 65 (catch-up-eligible). Use for the over-limit and happy-path demos.
  • 10000047 — HMM HSA, HDHP=false. Use for the HSA rejection demo.
  • 10000001 — BBK brokerage. Use for non-retirement deposit/withdrawal demos.
• Copy-paste the cURLs from section 4 directly. They’re the exact bytes that produced the responses shown.