Open Banking

Account access and payment initiation put a bank in the path of real money movement. A model in that path can echo a credential or repeat an instruction it should not hold. This starter constrains the model traffic that surrounds those flows.

Credential and payment wording is blocked by three terms: secret, client account export and wire instructions. National identifier numbers found in a prompt are masked. Injection screening runs before both, which stops a crafted instruction from reaching the later stages. A blocked prompt is refused outright, and the caller sees that refusal.

Answers that discuss insider trading or material non-public information are blocked by a market abuse screen. A returned message that offers guaranteed returns, or that says buy this stock, is stopped. Those screens read generated text, so they catch phrasing that the model produced rather than phrasing a user sent.

The quality gate expects 0.86 overall, plus 0.78 for relevance and 0.80 for accuracy, in equal weight. Length below 120 characters fails, as does a single sentence. Streaming skips the gate, so a streaming client needs its own control.

This starter governs model traffic and not the payment interface. Consent capture, strong customer authentication and payment initiation stay with your banking platform under PSD2 and the Open Banking Standard. The review stage carries no configuration, and it takes no action until your team defines one. The marker at the end allows and notes, while storage and retention stay outside the starter.