Does Strkr integrate with Fiserv Portico, Jack Henry SilverLake, FIS IBS, or Finastra Phoenix cores?
Strkr integrates with every major community and regional bank core banking system through its standard webhook spec with HMAC signing and the published OpenAPI spec. The typical setup runs daily sync of account balances, transaction history, loan status, and customer demographics from the core to Strkr. For Fiserv Portico, Jack Henry SilverLake, FIS IBS, Finastra Phoenix, and the common community-banking cores the integration lands in an engineering sprint of two to four weeks. The result is CRM-side customer context matching core-side truth daily.
How does Strkr handle compliance workflow for BSA, AML, KYC, CIP, CRA, and fair lending?
The compliance review object tracks regime (BSA, AML, KYC, CIP, CRA, fair lending, Reg B, Reg Z), trigger (new account, suspicious activity, periodic review, exam request), documentation, resolution status, and compliance officer sign-off. The audit log captures every compliance event with 90-day default retention tunable to 7-year regulatory ceiling. For regulatory exam preparation the compliance log exports support JSON and CSV for ingestion into the exam package. For specific state or federal exam requirements the retention policy and documentation templates tune per bank preference.
What does Strkr cost compared to legacy banking CRM add-ons?
Strkr runs flat per seat at $29 on Starter, $59 on Pro, and $119 on Scale per user per month. For a 42-staff community bank on Pro the monthly spend runs $2,478 for seats plus $49 for AI Enhancement. Legacy banking CRM add-ons (Fiserv RelationshipCare, Jack Henry Customer Service Software, FIS Relationship Pricing) typically price in the $120 to $240 per seat range plus module add-ons. Salesforce FSC runs $150 to $300 per seat plus implementation partner retainer. Strkr sits meaningfully lower on total cost with the banking schema and compliance workflow shipped out of the box.
Can Strkr handle the loan pipeline from inquiry to funding?
Yes. The loan pipeline is a dedicated pipeline type with stages (inquiry, application, documentation, underwriting, approval, closing, funding, servicing), stage gates (credit decision, documentation complete, underwriting sign-off), and document checklist per stage. The AI-drafted loan status update workflow handles the weekly customer-facing update. The loan officer dashboard surfaces loans needing intervention. For commercial lending the custom field support handles collateral tracking, covenant monitoring, and servicing workflow.
How does Strkr handle the FFIEC, OCC, and FDIC exam audit trail?
The audit log captures every record read, record write, email send, document access, flow trigger, AI call, and admin action with timestamp, user, and metadata. Retention is tunable per tenant to the regulatory requirement (typically 7 years for banking books-and-records). Export supports JSON and CSV for ingestion into the exam package. Permission scoping on 54 resource types supports examiner-only read-only access during exam cycles. SSO (SAML and OIDC) is live on Scale tier through Clerk, MFA with TOTP plus text-based verification is live across all tiers.
What is the compliance posture overall for a banking migration?
Strkr is GDPR and CCPA compliant today, SOC 2 Type II is in progress with a target of 2026-Q4, and HIPAA with BAA is available on request for banks serving medical practice clients. Integration tokens live in AWS KMS, platform credentials live in AWS Secrets Manager, and the audit log retention is tunable to banking regulatory ceilings. For state-specific banking data residency requirements the common pattern is to configure the tenant storage region with the regulator-approved AWS region. For specific state regulations Strkr compliance team runs a per-tenant review before onboarding.