How banks verify outcomes & request evidence
Verification is not “more software.” It is repeatable proof that AIS behaved as your bank intended under your governance.
Evidence banks commonly request (placeholders)
| Artifact | What it shows (plain English) | Notes |
|---|---|---|
| Decision log sample | Inputs allowed, outcome, reasons, time, user/system | Redact PII for samples |
| Policy version record | Which policy text governed the decision | Tie to committee minutes |
| Model / scorecard card | Intended use, limitations, validation summary | Often called a model card-format varies |
| Change record | What changed between two dates and who approved | Joint bank + AIS for platform releases |
:::caution Placeholders only
Names like “model card” are industry shorthand. The exact documents AIS provides depend on your contract and jurisdiction.
:::
Audit trails (concept)
An audit trail answers: who saw or changed what, when, and why-for both bank users and AIS operators (as applicable). It supports segregation of duties reviews.
Technical log formats - not published in this partner portal.
When APIs misbehave (what to capture for AIS support)
AIS integration materials describe structured errors and correlation identifiers so bank IT can open actionable tickets. Patterns banks see often:
| Situation (plain English) | Typical meaning | What to send AIS |
|---|---|---|
| 401 Unauthorized | Missing, expired, or invalid Bearer token | Time (UTC), user role, whether refresh was attempted |
| 403 Forbidden | Authenticated but not allowed for the action | Endpoint purpose and role expected by your policy |
| 422 Unprocessable Entity | Validation failed (limits, mandatory fields, policy breach) | Response detail payload (redact PII if needed) |
| 429 Too Many Requests | Throttling | Whether Retry-After was honored; peak volume context |
| 502 / 503 / 504 | Upstream dependency slow or unreachable | Whether health checks show a specific subsystem degraded |
Aggregated health: operators can often call a detailed health endpoint on the Pro Gateway to see whether database, cache, and upstream scoring services are reported up-exact path is in your integration pack and OpenAPI, not repeated here.
How you run a verification workshop (90 minutes)
- Pick five real-ish scenarios (approved, declined, referred, exception, re-score).
- Walk from application to decision record to committee pack field mapping.
- Log gaps as questions for AIS-not as accusations.
Next: Overview · How products fit