A core banking system is the foundational platform that manages accounts, transactions and financial products, it is the system of record. A digital banking accelerator sits above the core (or replaces it for new banks) and provides pre-built, pre-compliant modules for the digital experience layer: account opening, KYC, PIX, cards, and customer channels. An accelerator compresses time-to-market from years to weeks by providing working implementations of common banking capabilities that would otherwise have to be built from scratch.

KYC (Know Your Customer) automation is the use of technology to verify customer identity digitally, document scanning and validation, biometric liveness checks, CPF/CNPJ validation, sanctions screening, and PEP (Politically Exposed Person) checks, without manual review for standard cases. Without automation, KYC creates a bottleneck that limits how many accounts can be opened per day and adds friction that drives customers away before completion. At scale, manual KYC simply isn't viable: it must be automated to maintain conversion rates.

FAPI is a security standard built on OAuth 2.0 that adds requirements necessary for high-risk financial data access: mutual TLS for transport security, JWT-protected authorization requests, certificate-bound access tokens and specific PKCE requirements. BACEN requires FAPI compliance for all APIs participating in Brazil's Open Finance ecosystem. For a bank building Open Finance connectivity, FAPI compliance is not optional, it is the security baseline that determines whether the regulator accepts the implementation.

PIX is Brazil's instant payments infrastructure operated by BACEN's SPI (Sistema de Pagamentos Instantâneos). Technically, participating institutions connect to SPI via DICT (Diretório de Identificadores de Chaves) for key management, implement the ISO 20022 message standard for transaction flows, and handle the full transaction lifecycle including error flows, DICT queries, and reconciliation. Native PIX support means the platform has all of this pre-implemented and pre-tested, a bank activating PIX through Amplify doesn't build the SPI integration, it configures it.

Pre-compliant means the platform was built to satisfy specific regulatory requirements by design, so institutions using it inherit compliance instead of building it. Amplify's pre-compliance covers: BACEN regulatory requirements including PIX and Open Finance standards, LGPD (data protection), FAPI and PCI-DSS security requirements for card data handling. This doesn't eliminate all compliance work, institutions still need their own regulatory authorizations, but it means the technology layer doesn't create additional compliance risk.

Building from scratch gives full control over architecture, features and roadmap, but requires 2–3 years and a large engineering team before going to market. Licensing a platform means paying for access to pre-built features, receiving continuous updates, but accepting the vendor's architectural decisions and feature roadmap. Using an accelerator like Amplify is a middle path: pre-built modules dramatically reduce time and cost, but are implemented by the Sciensa team and adapted to the institution's specific requirements rather than being a rigid off-the-shelf product.

The 8-week timeline covers: environment setup and infrastructure provisioning (week 1), core banking module configuration and business rules (weeks 2–3), integration with the client's existing systems and data sources (weeks 3–4), compliance review and regulatory documentation (weeks 4–5), user acceptance testing and issue resolution (weeks 5–7), and deploy preparation and go-live (week 8). This timeline assumes regulatory authorization is already in place, technology and regulatory processes run in parallel, not sequentially.