Glossary - Akafay, Decision PRO, AIS & integration
Definitions here are plain-language. Capitalized product names follow published branding (Decision PRO, Akafay, AIS). If a term has a legal meaning in your jurisdiction, rely on counsel-not this page.
:::tip Key takeaways
- Use this page to align steering committees and RFP writers on vocabulary.
- Product fit in one picture: How products fit.
- Anything deployment-specific (exact field names, URLs, roles) is confirm with AIS team.
:::
Products
| Term | Bank-friendly meaning |
|---|---|
| Akafay | The customer / channel lending experience-how applicants and digital journeys interact with credit offers. Staff work happens in Decision PRO. See Akafay for banks. |
| Decision PRO | The workspace where bank staff review, approve, explain, and act on applications and decisions powered by AIS. |
| AIS (Akafay Intelligent Services) | The intelligence layer that supports credit decisions: scores, risk signals, explainability, and related analytics-usually behind Akafay and Decision PRO. |
AIS & intelligence layer
| Term | Bank-friendly meaning |
|---|---|
| Credit scoring (general) | Automated assessment of creditworthiness using data you approve; may combine models and rules-exact methodology is contract and model documentation. |
| Default probability (PD) | An estimate of likelihood of default over a horizon; often shown as a probability or percentage depending on UI-confirm formatting with AIS. |
| Explainability | Human-readable reasons for a score or decision (for example top contributing factors). Techniques (e.g. SHAP) are implementation details-what matters is whether explanations meet your fairness and disclosure policy. |
| Model drift | When model performance degrades over time because the world changed; monitoring and revalidation are joint governance topics. |
| Policy / rules | Business rules (eligibility, caps, exceptions) that sit alongside models-who may edit them is a bank governance decision within product limits. |
Decision PRO & workflows
| Term | Bank-friendly meaning |
|---|---|
| Origination | The front half of lending: intake, data capture, scoring, and decision before disbursement (exact stages depend on your products). |
| Underwriting | Risk assessment and conditions before approval-may be automated, manual, or hybrid. |
| Loan lifecycle | The end-to-end story of a loan from application through servicing events your program includes-not every bank uses every stage in AIS. |
| Exception | A case that does not fit straight-through rules and needs human review or override per your policy. |
| Approval workflow | Queues and steps so the right roles act in order-segregation of duties depends on how you configure roles. |
| Collections (when in scope) | Post-disbursement workflows such as reminders and case management-confirm whether your contract includes AIS support here. |
Risk, compliance, and audit
| Term | Bank-friendly meaning |
|---|---|
| Segregation of duties (SoD) | No single person should control incompatible steps (for example create and approve the same high-risk change) without compensating controls. |
| RBAC | Role-based access control: permissions bundled into roles (analyst, approver, admin). |
| MFA | Multi-factor authentication: password plus a second factor (app, token, SMS where policy allows). |
| Audit trail | Time-stamped record of significant actions for investigations and internal audit-retention and export are contract-specific. |
| Evidence pack | The set of documents a bank collects for vendor diligence (architecture, tests, subprocessors, etc.)-see Compliance & risk. |
| DPIA | Data protection impact assessment-often required before high-risk processing; your DPO leads. |
| Controller / processor | Legal roles under privacy law: the bank is often the controller; AIS may be a processor only as your contract states. |
| Subprocessor | A vendor of your vendor who may touch data-lists and transfer mechanisms belong in legal annexes. |
Integration & operations
| Term | Bank-friendly meaning |
|---|---|
| Pro Gateway | The primary REST API surface many banks use for machine integrations with AIS-backed lending-see Integrations. |
| Sandbox / non-production | A safe environment for testing without live customer impact-availability and refresh policy vary by contract. |
| Production | The live environment affecting real customers-stricter change control. |
| JWT / Bearer token | A common pattern: short-lived access token sent on each API call after login-confirm token lifetimes with AIS. |
| API key | A secret sent on API calls for machine access when enabled-rotation is bank + AIS operations discipline. |
| Correlation ID | An identifier that ties logs across systems for support-header names confirm in your integration pack. |
| Idempotency key | A client-supplied key so retries do not duplicate side effects-behavior may depend on infrastructure; see Reliability. |
| Webhook | Outbound HTTPS callback from AIS to your server on events you subscribe to-delivery guarantees are not universal; design reconciliation. |
| Rate limit (429) | Server asks client to slow down; use backoff-limits are deployment-tuned. |
| BFF (backend-for-frontend) | A small server inside a web app that holds secrets and calls upstream APIs so the browser never sees those keys-Decision PRO uses this pattern toward Pro Gateway in typical designs. |
| Mixed content | Browser security rule: a page loaded over HTTPS cannot call plain HTTP APIs-often shows up as a generic network error to users until URLs are aligned. |
| SLA | Service level agreement: measurable commitments (uptime, response time)-placeholders on this portal until your contract text is attached. |
| RTO / RPO | Recovery time and recovery point objectives for disasters-BCP annex topic. |
| Maintenance window | Planned downtime or degraded service-see Maintenance windows. |
| Release bulletin | Curated description of what changed for partner banks-distinct from engineering changelogs. |
| Core banking | Your system of record for accounts and loans-AIS does not replace it unless explicitly contracted. |