PCI DSS, SOC 2, and PSD2 address different questions and are not interchangeable. PCI DSS is a security standard that applies to entities that store, process, or transmit cardholder data, or whose systems can affect the security of a cardholder data environment. SOC 2 is an independent examination of an organization's controls against the AICPA Trust Services Criteria, typically requested by enterprise customers or partners requiring assurance. PSD2 is an EU regulatory directive that applies to payment services operating within its legal scope. Which of these applies to a fintech application depends on the business model, payment flow, organizational role, and jurisdiction — not on the category of app being built.
At a glance: A fintech app does not automatically need PCI DSS, SOC 2, and PSD2. PCI DSS may apply when an organization stores, processes, or transmits cardholder data or can affect the security of the cardholder data environment. SOC 2 may be requested by enterprise customers or partners requiring independent assurance. PSD2 is relevant to applicable payment service providers within its EU/EEA jurisdiction.
Compliance requirements in fintech are not paperwork added at the end of development. They are architectural and product-planning decisions that shape how the application handles payment data, what security controls must be built in, how third-party services are integrated, and what documentation must be maintained. Understanding which requirements may apply before development begins determines whether the architecture being built can support them, or whether it will need to be rebuilt.
Consider a practical example. A founder wants to build a payment application with a checkout interface, user accounts, payment processing, and transaction history. The first development conversation needs to resolve a decision that will shape almost everything else: will the application collect card numbers through its own forms? Will it redirect users to a hosted checkout page operated by the payment processor? Will it use processor-controlled payment fields embedded in the application interface? Each answer has different implications for how much cardholder data the application handles, what PCI DSS scope the organization takes on, what security engineering the developer must build, and what validation may be required.
If that architectural decision is deferred or resolved informally, the development work that follows is built on an unclear foundation. If the application is later found to be handling card data in ways that weren't anticipated, the security controls, logging, encryption, and access management required may not be in place. Retrofitting those requirements after development is typically more expensive and disruptive than designing for them from the start.
The same principle applies to SOC 2, PSD2, and other regulatory requirements. An enterprise customer that requires a SOC 2 Type II report needs to see evidence that controls have operated effectively over a period of time — not that an audit was initiated after they asked. A payment initiation service operating under PSD2 needs Strong Customer Authentication implemented in the authentication flow, not added as a workaround. Compliance considerations belong in the product discovery and architecture phase, not the launch checklist.
These three frameworks are frequently conflated by founders who encounter them together in fintech due diligence conversations. They are not versions of the same requirement, and having addressed one does not reduce obligations under the others.
| Framework or regulation | What does it address? | Who may need to consider it? | What does it mean for development? |
|---|---|---|---|
| PCI DSS | Security of payment card account data | Entities that store, process, or transmit cardholder data, or whose systems can affect the security of the cardholder data environment | Secure payment architecture, access controls, data protection, vulnerability management, secure software development |
| SOC 2 | Independent examination of an organization's controls against relevant Trust Services Criteria | Technology companies and service providers whose customers or partners require independent assurance about security and operational controls | Documented policies, access management, change management, monitoring, incident response, vendor risk — structured for auditability |
| PSD2 | EU payment-services regulatory framework covering payment service providers, payment initiation, account information services, and Strong Customer Authentication | Applicable payment service providers operating within the EU/EEA, depending on role, activities, and licensing | Authentication flows, secure communication, payment initiation, consent handling, open banking integrations, SCA implementation |
Several important distinctions apply:
TechRadiant lists human-verified development companies across fintech software, financial software, and fintech app development. Use these resources to understand the types of financial products being built and to evaluate technical partners with relevant fintech experience.
Whether PCI DSS applies to a fintech application depends on how the application and its supporting business handle payment card account data, and whether the organization's systems can affect the security of the cardholder data environment. The scope is not determined by whether the company considers itself a "payment company." It is determined by what the technology actually does.
An application that presents its own payment form and collects cardholder data through that form is processing card data directly. If the backend also stores, transmits, or processes that card data, the organization has established a cardholder data environment (CDE) — the systems, people, and processes that store, process, or transmit cardholder data, or that could otherwise affect its security. PCI DSS requirements apply to that environment.
The cardholder data covered by PCI DSS includes the primary account number (PAN), cardholder name, expiration date, and service code. Sensitive authentication data, which includes the full magnetic stripe data, CVV/CVC values, and PINs, has specific restrictions under PCI DSS: it must not be retained after authorization is complete, even if encrypted, subject to the applicable rules under the standard and any defined exceptions for issuers performing authorization-related functions.
Operating a CDE directly brings significant PCI DSS responsibilities, including encryption in transit and at rest, access controls and least-privilege principles, logging and monitoring of cardholder data access, vulnerability scanning and penetration testing, secure software development requirements, and patch management. The applicable validation method depends on the organization's volume of transactions, role, and merchant level, and is confirmed with the relevant acquiring bank or payment brand.
Using a third-party payment gateway can reduce the amount of cardholder data that passes through the fintech application, but the degree of scope reduction depends on the specific integration method. Not all gateway integrations are equal from a PCI DSS perspective.
| Integration method | Cardholder data in your application? | PCI DSS scope implication |
|---|---|---|
| Hosted checkout page (redirect) | No — user is redirected to processor's page | Potentially reduced scope; application does not handle card data |
| Hosted payment fields / iframes | No — form elements controlled and served by processor | Potentially reduced scope; depends on correct implementation |
| Direct API integration with custom form | Temporarily, before tokenization | Card data passes through the application; expanded scope considerations apply |
| Tokenization (post-capture) | Tokens only — not raw card data — are stored | Tokens replace PANs; scope can be reduced if card data is not stored |
Several security practices matter regardless of integration method: webhook signature verification, secure API credential management, avoiding card data in application logs (a frequent and significant error), handling payment status correctly without storing redundant card data, and understanding which security responsibilities are owned by the payment provider and which remain with the application.
Important: Using Stripe, Razorpay, or any PCI DSS-compliant payment provider does not make the integrating application compliant. The provider handles card data on its infrastructure; the merchant remains responsible for how it integrates with that provider, how it manages API keys and webhooks, what its application logs contain, and what other systems can access the payment environment. The final scope and applicable validation method must be confirmed with the relevant acquiring bank, payment brand, or a qualified security assessor (QSA).
An application that fully outsources payment data handling, with no cardholder data entering its own systems, may have significantly reduced PCI DSS scope. However, reduced scope is not automatic exemption. Several factors still require attention.
Scripts or third-party code on payment-related pages can affect the security of the checkout environment even when the application does not handle card data directly. The PCI DSS concept of system components that "can affect the security of the cardholder data environment" is relevant here. Web pages that load scripts from external sources, single-page applications that inject content into checkout flows, and content management systems that share infrastructure with payment pages all require assessment. Access to administrative systems that could affect payment security also brings those systems within scope considerations. The organization should document its payment data flows, understand what third-party services interact with payment-related pages, and confirm scope with a qualified assessor rather than assuming it has no PCI DSS responsibilities because card data never enters its own database.
Software developers do not independently certify the fintech company as PCI DSS compliant. However, the engineering decisions they make directly affect the organization's ability to meet applicable requirements. PCI DSS v4.0.1 includes specific requirements in Requirement 6 that apply to secure software development, developer training, and software vulnerability management.
| Development area | What the agency should implement | Evidence the founder should request |
|---|---|---|
| Secure coding practices | Documented approach to secure development including security in requirements, design, coding, and testing phases | Development security policy or secure SDLC process document |
| Code review before release | Manual code review of custom code before production deployment; review by personnel other than the developer where feasible (Req. 6.2.3) | Sample redacted code review workflow or policy |
| Developer security training | Role-appropriate software security training covering secure coding, relevant vulnerability types, and technologies used (Req. 6.3.2 area) | Training policy or records confirming developer security education |
| Authentication and access controls | Least-privilege access, secure credential storage, MFA where required, access review and revocation processes | Architecture and access control documentation |
| Payment integration security | Secure processor integration, token-based flows, webhook verification, sensitive data excluded from logs | Payment data-flow diagram showing what data is handled where |
| Vulnerability management | Vulnerability scanning, security testing of APIs and application components, remediation and retesting | Security testing process and sample remediation workflow |
| Logging design | Security event logging without exposing cardholder data or sensitive authentication data in log entries | Logging and monitoring design documentation |
| Change management | Controlled code changes and production deployments with documented testing and approval steps | Release and change-control process |
Scope note: Not every PCI DSS requirement applies to every system component or every development team. The applicable requirements depend on the organization's environment, the systems within scope, and what has been documented and agreed with relevant assessors and acquiring banks. The table above reflects development-relevant areas; it does not constitute a complete compliance checklist.
SOC 2 is not automatically required for every fintech startup before launch. It becomes commercially important when the company sells to banks, financial institutions, enterprise customers, or regulated partners that require independent assurance about the organization's security and operational controls as a condition of doing business. The need typically emerges during sales conversations, procurement due diligence, or partnership agreements, rather than from a universal regulatory mandate.
SOC 2 Type I examines whether relevant controls are suitably designed as of a specific point in time. It demonstrates that an organization has the right controls in place, but does not evaluate whether they operated effectively over time. SOC 2 Type II examines both control design and operating effectiveness over a defined period (typically six to twelve months). Enterprise customers and regulated partners most commonly require a Type II report, because it provides evidence of sustained control operation rather than a point-in-time assessment.
The SOC 2 framework uses five Trust Services Criteria: Security (the foundational criterion, included in every examination), Availability, Processing Integrity, Confidentiality, and Privacy. Which criteria are included in an examination depends on the organization's services, commitments to customers, and what the examination is designed to cover. Security is always present; others are added where relevant to the organization's services and stakeholder requirements.
What SOC 2 means for software development: preparing for a SOC 2 examination requires documented policies, role-based access controls, change management processes, secure development practices, incident response procedures, vendor risk management, monitoring and logging, and periodic reviews. These need to be in place and operating before the examination period begins, not assembled immediately before the audit.
What founders must understand about agency SOC 2 reports:
→ A development agency's SOC 2 report does not make the founder's company SOC 2 compliant. It covers the agency's own systems and controls, not the systems the agency builds for clients.
→ The scope of the report matters. A report covering the agency's internal development environment is different from one covering the hosted platform they operate on behalf of clients.
→ SOC 2 is an examination report, not a certificate or badge. A website that claims SOC 2 compliance without being able to produce a current, in-scope report from an accredited auditor should prompt follow-up questions.
→ Complementary user entity controls in the report describe what the client organization must do to rely on the service provider's controls. Those remain the client's responsibility.
PSD2 (Directive (EU) 2015/2366) applies to payment services within the EU/EEA, and its applicability depends on the type of payment service being provided and the organization's regulated role — not simply on whether the application processes payments from European users. A US-based SaaS company accepting European subscription payments through a payment processor is not automatically subject to PSD2. A company providing payment initiation services or account information services in an EU member state is a different matter.
Payment service types relevant to PSD2 include payment institutions, electronic money institutions, payment initiation service providers (PISPs), and account information service providers (AISPs). Whether a fintech business falls into one of these categories depends on its activities and the regulatory classification under applicable national law. Authorization and licensing requirements vary by member state and service type.
Strong Customer Authentication (SCA) is one of the most development-relevant aspects of PSD2. Article 97 of the directive, implemented through Commission Delegated Regulation (EU) 2018/389, requires that payment service providers apply SCA when a payer initiates an electronic payment transaction or accesses their payment account online. SCA must use at least two independent elements from:
SCA has defined exemptions, including low-value transactions, trusted beneficiaries, and transaction risk analysis-based exemptions, each with specific conditions. The applicable exemptions depend on the transaction type, payment service, and regulatory technical standards as interpreted by the relevant national competent authority.
Development implications of SCA and PSD2: authentication flow design, step-up authentication for transactions exceeding exemption thresholds, secure API communication with payment providers and banks, consent management for account access, payment initiation workflows, handling authentication failures, and integration with regulated payment infrastructure. These are architectural requirements that must be designed into the application, not patched in after the payment flow is built.
Jurisdiction note: PSD2 is EU/EEA legislation. Fintech founders building for India operate under RBI payment regulations, which include separate requirements for payment aggregators, payment gateways, and regulated lending entities. UK fintech businesses operate under UK PSR and FCA rules following Brexit. US fintech companies face a different and fragmented regulatory landscape across federal and state frameworks. Founders should not assume PSD2 is their governing payment regulation without advice specific to their jurisdiction and business model.
PCI DSS, SOC 2, and PSD2 do not cover every legal, regulatory, and security responsibility a fintech business may face. The following areas may apply depending on the business model, jurisdiction, and type of financial service being provided.
The applicable requirements are specific to the product, the business structure, and the jurisdictions of operation. Founders should obtain legal and regulatory advice specific to their situation from qualified professionals, not from development agencies or general market overviews.
These questions test whether a development agency has worked through real fintech compliance constraints, not just built payment applications. The goal is to find a partner who can explain their responsibilities clearly and provide evidence, not one who promises to handle everything.
This checklist is a practical starting point for a non-technical founder. It is not a compliance assessment or legal document. It is designed to surface the questions that must be answered before development begins — questions that become much more expensive to resolve after the architecture is built.
Warning signs to watch for during vendor evaluation:
→ "We are PCI compliant" without explaining the entity, environment, service scope, and validation method. PCI DSS compliance is specific to an organization's environment and assessed at a point in time, not a permanent status that transfers to client work.
→ Treating a payment gateway integration as proof of compliance. Integrating Stripe or Razorpay does not make the integrating application compliant. The integration method, what happens to card data, and what the application logs contain all matter.
→ Claiming SOC 2 is a certificate. SOC 2 is an examination report. It has a scope, an examination period, and may contain exceptions. A website badge is not a substitute for a current in-scope report.
→ Claiming their SOC 2 report covers your application. An agency's SOC 2 report covers the agency's own systems. Unless the client's application is explicitly within that scope, the report provides no assurance about the application being built.
→ Saying PSD2 applies to every fintech app globally. PSD2 is EU legislation applicable to specific payment service providers within its scope. It is not a universal requirement for every application that handles payments.
→ Promising guaranteed compliance without understanding the business model, payment flow, jurisdiction, or scope. Compliance is specific to the organization and its environment. No developer can guarantee it in a general proposal.
→ No payment data-flow diagram. Any agency with real fintech experience should be able to produce a diagram showing what data moves where in a proposed payment architecture.
→ Storing card details without a clear architectural reason. An agency that proposes storing raw card data should be able to explain precisely why and what security controls would apply. In most cases, tokenization or hosted payment solutions make direct card data storage unnecessary.
→ No documented secure development process, code review, or security testing. These are baseline expectations for fintech development, not advanced practices.
→ No clarity on incident response. Who is notified, in what timeframe, and what happens after a security incident are questions that must have answers before the contract is signed.
A non-technical fintech founder does not need to become a PCI assessor, SOC 2 auditor, or payments lawyer. The goal is to understand the product's regulatory and compliance context well enough to ask the right questions and recognize meaningful answers — and to involve qualified specialists for the decisions that require their expertise.
Three principles guide the approach:
1. Understand your payment data flow before development begins. Know whether your application will collect, transmit, or store cardholder data, which payment processor you will use, what integration method you will implement, and what systems will interact with the payment environment. This single set of decisions determines the PCI DSS scope your organization takes on and what your developer is responsible for designing securely.
2. Select a developer who can explain secure architecture, implementation, documentation, and testing. A capable fintech development partner can explain how their approach addresses your compliance context, what documentation they will provide, and where your responsibility begins and their responsibility ends. They will not promise to make the application compliant; they will explain what they will build, why, and what it means for your position. The questions and checklist in this article are designed to surface that capability.
3. Involve qualified compliance and legal specialists for formal scope and regulatory decisions. Confirm PCI DSS scope and validation requirements with your acquiring bank or a qualified security assessor. Obtain legal advice on PSD2, local payment regulations, and licensing requirements before building payment services. Engage a SOC 2 auditor before the examination period you need covered. These are decisions a development agency cannot and should not make on your behalf.
TechRadiant lists human-verified fintech development companies across fintech software, financial software, and app development disciplines — to support your partner evaluation process.
Research reports, industry breakdowns, and practical guides, written to simplify complex technology decisions.
Human-verified rankings across AI, development, and marketing — updated quarterly.