Global In-House Centers (GICs) in FinTech: Regulatory Compliance & Architecture Blueprint

Executive Summary

More FinTech and financial services firms are building Global In-House Centers (GICs), also called Global Capability Centers (GCCs), in India to scale engineering, data and AI work. In this sector, the center sits inside a dense web of rules: EU DORA, UK outsourcing and operational resilience rules, US third-party risk guidance, PCI DSS, and India’s own payment data and privacy laws. This article sets out the regulations a FinTech GIC has to satisfy, a reference architecture that keeps data, access and change under control, and the governance that keeps the center audit-ready. It closes with a comparison of five partners that help financial firms build compliant GICs in India.

This article is general information, not legal or regulatory advice. Confirm your obligations with your compliance, legal and audit teams.

Which regulations does a FinTech GIC in India have to satisfy?

A FinTech GIC answers to the regulators of its parent’s home markets as well as to Indian law. Even when the center is wholly owned, most regimes treat the services it provides as third-party or outsourced arrangements that need contracts, oversight and exit plans.

  • EU: DORA covers intra-group ICT services. The Digital Operational Resilience Act has applied since January 17, 2025. As Morgan Lewis notes, contracts with ICT providers, both intra-group and external, must include mandatory provisions on service locations, data, business continuity, incident reporting and security standards. Firms must also keep a register of information that records data storage locations and subcontracting.
  • UK: outsourcing and operational resilience rules. The PRA’s SS2/21 on outsourcing and third-party risk management applies to UK banks, building societies, PRA-designated investment firms, insurers and UK branches of overseas firms. Under the FCA’s operational resilience rules, firms had until March 31, 2025 to show they can keep important business services within impact tolerances, and new incident and third-party reporting rules take effect on March 18, 2027.
  • US: interagency third-party risk guidance. The Fed, FDIC and OCC issued joint guidance on third-party relationships in June 2023, covering the full relationship life cycle from planning and due diligence to contracts, ongoing monitoring and termination. The OCC’s earlier guidance on foreign-based service providers still applies alongside it.
  • Card data: PCI DSS v4.x. Any center that touches cardholder data falls under PCI DSS. According to the PCI Security Standards Council, 51 of the 64 new requirements in version 4 became effective on March 31, 2025, including stronger authentication and e-commerce controls.
  • India: payment data localization and the DPDP Act. The RBI’s 2018 directive on storage of payment system data requires payment system data to be stored only in India, with unfettered supervisory access. India’s Digital Personal Data Protection Rules were notified on November 13, 2025, and, per AZB & Partners, most obligations, including cross-border transfer requirements, apply from May 12, 2027.

What does a compliant architecture blueprint for a FinTech GIC look like?

Design the center so that regulated data stays where it must, engineers see only what they need, every change is traceable and every action is logged. These five layers form the blueprint.

  • Data residency and segmentation by design. Classify data before the center starts work: payment data, personal data, card data, and non-sensitive engineering data. Keep regulated data in approved regions (India for RBI-scoped payment data, home-market regions where required) and give the GIC access through segmented environments rather than copies. Production data should rarely leave production.
  • Zero-trust identity and access. Every engineer authenticates with multi-factor authentication through the parent’s identity provider, with role-based and just-in-time access to sensitive systems. Privileged sessions are brokered and recorded. Access is reviewed regularly and removed the same day someone changes roles or leaves.
  • Tokenization, encryption and key control. Replace card numbers and sensitive identifiers with tokens wherever engineers don’t need the real value. Encrypt data in transit and at rest, and keep encryption keys under the parent’s control in a hardware security module or cloud key management service, so the GIC can build and support systems without ever holding the keys.
  • Secure software delivery. Build security into the pipeline: code review, static and dependency scanning, secrets management, signed builds and approvals before production. Development and test environments use masked or synthetic data. This gives auditors a clear, automated trail showing who changed what and why.
  • Logging, monitoring and incident reporting. Send logs from the GIC’s environments into the parent’s central security monitoring, with alerts mapped to incident categories and time limits under DORA, UK and US rules. Clear runbooks mean an incident in India is detected, escalated and reported on the same clock as one at headquarters.

How should a FinTech GIC be governed to stay audit-ready?

Treat the GIC as a regulated service provider to the parent, even if you own it. Clear contracts, registers, testing and evidence turn a regulator’s questions into a routine conversation.

  • Write intra-group agreements as if the GIC were external. Service agreements between the parent and the GIC should cover scope, service levels, data locations, security standards, subcontracting, audit and access rights, incident reporting and termination. DORA requires these terms for intra-group ICT services, and UK and US supervisors expect equivalent controls.
  • Keep the GIC on every register and risk map. Record the GIC in the DORA register of information, the UK outsourcing register and the US third-party inventory where they apply. Map which important or critical business services depend on it, so its role is clear in every resilience assessment.
  • Plan and test exit and continuity. Regulators expect a credible plan if a service provider fails or has to be replaced. For a GIC, that means documented knowledge, code and data access held by the parent, backup teams for critical services, and periodic scenario tests, such as a regional outage or loss of a key site.
  • Give supervisors and auditors clear access. The RBI circular requires unfettered supervisory access to payment data, and parent-country regulators expect audit rights over service providers. Build these rights into contracts and keep evidence (access reviews, change records, test results) ready to share.
  • Build a compliance-aware engineering culture. Engineers in the GIC should understand the rules behind their controls as well as follow them. Regular training on data handling, secure coding and incident response, plus a named risk and compliance lead in India, keeps standards consistent with the parent’s. Security certifications such as ISO 27001 or SOC 2 reports for the GIC can also simplify parent and client audits.

Which companies help financial firms build compliant GICs in India?

India has about 170 BFSI GCCs running 333 units, roughly 8% of all centers, according to Zinnov. The partners that help set them up range from engineering specialists to large IT services firms. Here’s how five compare.

  • OptiSol Business Solutions: An engineering, data and AI services company with more than 450 people, registered US and UK entities and a presence in Australia, and vertical offerings for BFSI and FinTech. It sets up GICs through Build-Operate-Transfer, Managed GCC and Hybrid models, with embedded engineers working within the client’s team and following its security standards, plus accelerators for AI agents (elsai) and data modernization (iBEAM). [CONFIRM: OptiSol security certifications and BFSI client proof] Best fit for FinTech and mid-sized financial firms that want a GIC delivering engineering and AI under their own compliance controls.
  • Coforge: Rated a Major Contender in Everest Group’s 2026 GCC Setup Capabilities PEAK Matrix. Best fit for larger financial institutions looking for an established IT services firm to support GCC setup.
  • Persistent Systems: Also a Major Contender in the same Everest assessment. Best fit for firms that want a large engineering services partner alongside the GCC build.
  • Zensar Technologies: Rated an Aspirant in Everest’s 2026 GCC setup assessment, and has published research on architecting next-generation BFSI GCCs. Best fit for BFSI firms wanting a partner with a stated BFSI GCC point of view.
  • SA Technologies: Headquartered in San Jose, California, with delivery centers in Pune and Bangalore. It offers Build-Operate-Transfer and managed dedicated teams and lists banking and financial services and fintech among its industries. Best fit for US firms wanting a BOT partner with a California base.

This comparison is based on publicly available information about each company, as of November 2026.

Conclusion

For FinTech firms, the question about an India center has shifted from whether it saves money to whether it can be trusted with regulated systems. Regulators in Brussels, London and Washington now ask the same things about an in-house center that they ask about any outside provider: where the data sits, who can touch it, how incidents are reported and what happens if it fails. The firms that build their GIC around those questions from day one find audits easier and expansion faster. OptiSol works with FinTech and financial services firms on exactly that foundation, setting up GICs through Build-Operate-Transfer, Managed GCC and Hybrid models, with embedded engineers working within the client’s team and under its security and compliance controls. With registered entities and client partners in the US and UK, the people accountable for the center are available for the reviews regulators expect. Mapping your regulatory obligations to a target architecture is a practical first step before a single engineer is hired.

FAQs:

What is a Global In-House Center (GIC)?

A Global In-House Center is an offshore unit owned by a company to deliver technology, operations or other services to the parent. The term is used interchangeably with Global Capability Center (GCC). In FinTech, GICs usually handle engineering, data, AI and risk operations under the parent’s regulatory controls.

Does DORA apply to a bank's own offshore technology center?

Yes. DORA’s ICT third-party rules cover intra-group ICT services as well as external providers, so contracts with an in-house center must include the mandatory provisions on service locations, data, continuity, incident reporting and security, and the center must appear in the register of information.

Can payment data be processed by a center outside India?

Under the RBI’s 2018 directive, payment system data covered by the circular must be stored only in India, with an exception for the foreign leg of a transaction. Firms should confirm with counsel how this applies to their specific payment flows before designing offshore processing.

When do India's DPDP Rules take full effect?

The Digital Personal Data Protection Rules were notified on November 13, 2025, with phased commencement. Most obligations, including cross-border transfer requirements, apply from May 12, 2027, so FinTech GICs handling personal data should build those controls into their design now.

What security controls should a FinTech GIC have?

Core controls include data classification and residency, zero-trust identity with multi-factor and just-in-time access, tokenization and encryption with keys held by the parent, secure software delivery pipelines, and centralized logging linked to incident reporting. OptiSol’s embedded engineers work within the client’s security controls rather than alongside them.

Connect With Us!