How NWS connects to the institution’s systems

Working draft. Each section below is an unfilled field with the detail required.

Integration methods

To complete

[TO COMPLETE — James: list the supported connection methods (API, SSO, webhooks, file transfer), and for each, what it is used for.]

Data flows

To complete

[TO COMPLETE — James: describe what data moves between the institution’s core, NWS and any provider, in which direction, and how often. This will become a diagram.]

Core and digital banking touchpoints

To complete

[TO COMPLETE — James: name the specific integration points for Jack Henry, Q2 and Valiify — what NWS reads, what it writes, and what remains untouched.]

What the institution needs to provide

To complete

[TO COMPLETE — James: which teams are involved, what access is required, and roughly how much of the institution’s resource time.]

Testing and sandbox

To complete

[TO COMPLETE — James: what testing environment is available, what is tested, and who signs off.]

Implementation sequence

To complete

[TO COMPLETE — James: the phases from kick-off to launch. No durations unless we can commit to them.]

Ongoing support

To complete

[TO COMPLETE — James: support model, escalation path, monitoring, and who owns incidents.]