Skip to main content

FAQ - sales, diligence, and integration

Answers are general. Your contract, jurisdiction, and deployment always win. If something is not standardized, we say confirm with AIS team (account manager, solution architect, or support channel you were given).

:::tip Key takeaways

  • Use this page in steering committees and first workshops.
  • Treat “yes” answers as conditional until written into your agreement.

:::

Product & positioning​

1. What is the difference between AIS and Decision PRO?​

AIS is the intelligence layer (scores, risk, explainability). Decision PRO is the staff workspace where teams act on those outcomes. Confirm exact modules in your scope with AIS team.

2. Does AIS replace our core banking system?​

No in typical programs. AIS supports credit decisions and workflows; ledger and master data stay with you unless explicitly contracted otherwise-confirm with AIS team.

3. Which lending products can AIS cover?​

Personal loans, BNPL, salary advance, and others have appeared in partner conversations-exact product catalog depends on models, integrations, and regulation in your country-confirm with AIS team.

4. Is Decision PRO the only way our staff interact with AIS?​

Usually Decision PRO is the main human interface; APIs serve channels and middleware. Some banks add custom portals-confirm with AIS team.

5. Do you support Islamic / specialized lending structures?​

Product fit is jurisdiction- and roadmap-dependent-confirm with AIS team; do not infer from this portal.

Data, privacy, and residency​

6. Where is our data physically stored?​

Regions and hosting depend on deployment (dedicated vs shared, cloud vs on-prem). Obtain a written answer in your DPA / security annex-confirm with AIS team.

7. Are you GDPR / PDPL / “local law” compliant?​

AIS can describe technical and organizational measures; legal adequacy is your counsel’s determination-confirm with AIS team and your lawyers.

8. Who is controller vs processor?​

Typically the bank is controller for customer relationship data; AIS may be processor as defined in your contract-confirm with AIS team.

9. Can we get a subprocessors list?​

Yes in most enterprise programs-usually under NDA as part of diligence-confirm with AIS team.

10. How long do you retain scores and logs?​

Retention must match your schedule and law-confirm with AIS team in writing.

Security & access​

11. Do you support SSO and MFA?​

SSO / OIDC and MFA are common requirements; exact IdP and MFA methods are deployment-specific-confirm with AIS team (see also Security & access).

12. Can we map AIS roles to our HR job codes?​

RBAC is configurable within product limits; mapping is a joint workshop task-confirm with AIS team.

13. Do you provide penetration test summaries?​

Often yes under NDA, redacted, and dated-confirm with AIS team (see Evidence pack).

14. Is traffic encrypted?​

TLS in transit is standard for modern deployments; encryption at rest posture is architecture-specific-confirm with AIS team.

Integration & APIs​

15. What is the main API we integrate with?​

Most bank machine integrations target the Pro Gateway REST API-confirm with AIS team (see Integrations and /openapi).

16. How do we authenticate API calls?​

Typically JWT bearer after login, sometimes API keys for batch-confirm with AIS team; never copy sample hosts from engineering repos as production truth.

17. Do you support webhooks?​

Loan lifecycle and rules webhook families exist in published OpenAPI for many deployments; enablement and events vary-confirm with AIS team.

18. Are rate limits published?​

The gateway applies rate limiting; numeric defaults are tunable per deployment-confirm with AIS team and test in sandbox.

19. How much notice for breaking API changes?​

Deprecation policy should be in your technical annex-not standardized here-confirm with AIS team.

20. Do you support file-based bulk import?​

Bulk import patterns exist for some domains; formats and limits are scope-specific-confirm with AIS team.

Operations & SLAs​

21. What uptime SLA do you offer?​

Numeric SLAs belong in your contract-this portal uses placeholders only-confirm with AIS team.

22. How do we learn about releases?​

Typically partner bulletins, workshops, and sometimes blog posts-confirm with AIS team (see Releases & notifications).

23. What is the support escalation path?​

Use the tier template in Incident response and replace placeholders with contract contacts-confirm with AIS team.

24. Do you publish a public status page?​

Varies by program-confirm with AIS team.

25. What are your support hours and time zone?​

Hours and regions are contractual-confirm with AIS team.

Model risk & governance​

26. Will we receive model documentation for committee review?​

Model packs are a standard diligence ask; depth and cadence depend on regulator expectations-confirm with AIS team.

27. Can we override a model score?​

Policy is yours; product may support manual override with audit-confirm with AIS team and your credit committee.

28. How do you handle model drift?​

Monitoring and revalidation are joint topics; exact metrics are program-specific-confirm with AIS team.

29. Do explanations always use SHAP?​

Explainability can use multiple methods; the right answer is whether outputs meet your disclosure and fairness needs-confirm with AIS team.

Commercial & legal​

30. Can you share pricing, liability caps, and IP terms here?​

No-commercial and legal terms are outside this documentation portal-confirm with AIS team and your procurement.

Next: Download PDF pack · Overview