Why BaaS Providers and Card Processors Are Adopting In-House 3D Secure
For a Banking-as-a-Service provider or issuer processor, moving 3D Secure authentication in-house can make sense when issuer portfolios need different risk policies, branding and operational controls. But owning the ACS software does not automatically deliver lower costs, better authentication rates or easier compliance. The decision depends on the operating model and the requirements of the banks and card programmes you serve.
This guide explains when to consider an in-house 3D Secure Access Control Server (ACS), what to evaluate before buying, and which FinOn capabilities an issuer processor can verify during a technical demonstration.
What “in-house ACS” means for an issuer processor
The Access Control Server is the issuer-side EMV 3-D Secure component responsible for evaluating authentication requests and, where appropriate, authenticating the cardholder. It operates in the issuer domain, unlike a 3DS Server used on the merchant or acquiring side.
“In-house” may mean deploying licensed software within the processor's infrastructure, running it in a private or hybrid environment, or taking more configuration control over a vendor-supplied service. These arrangements are different. A licence does not by itself determine who hosts, patches, monitors or secures the platform.
For BaaS providers: the purchasing question is usually not just “Can this ACS authenticate a cardholder?” It is “Can we operate several issuing programmes with the appropriate separation of rules, permissions and cardholder experience?”
When a third-party ACS becomes an operational constraint
An external service can be the right choice for a smaller portfolio. The reasons to revisit that model tend to appear when the issuing business becomes more complex:
- Slow rule changes. A fraud team needs an adjustment, but the change depends on the vendor's queue or an additional development request.
- Limited portfolio separation. Credit, debit, prepaid and sponsored issuing programmes require distinct policies, branding or administrative access.
- Weak investigation tools. Operations teams cannot readily retrieve an authentication result, inspect a challenge outcome or report by relevant BIN or programme.
- Deployment constraints. Data residency, security controls or an issuer's outsourcing policy require a different infrastructure arrangement.
- Commercial pressure. Transaction-based service costs rise as authentication volume grows, although a licensed alternative still brings infrastructure, support and maintenance costs.
None of these automatically justifies replacing a working ACS. They justify an assessment of what control the organisation actually needs, and what it would cost to deliver.
What issuer processors should be able to manage
During vendor evaluation, ask for a demonstration rather than relying on a list of features. The following capabilities are particularly relevant to multi-issuer operations.
| Requirement | What to test in the ACS | Why it matters |
|---|---|---|
| Multi-issuer and multi-BIN management | Show different programme configurations and confirm how data, settings and roles are separated. | Issuer processors should not have to apply one authentication policy across unrelated clients. |
| Risk-based authentication | Change a supported threshold or rule, validate the change, and review the resulting authentication decision. | Fraud teams need defined operational control over permitted adjustments. |
| Authentication methods | Demonstrate eligible frictionless, challenge and out-of-band journeys, including interruptions. | Programmes may require different issuer-app and cardholder experiences. |
| Administrative permissions | Show issuer-appropriate roles, access restrictions and available change history. | Access should reflect security and operating responsibilities. |
| Investigation and reporting | Find a transaction and review the available outcome, diagnostic information and segmentation. | Operations teams need evidence when a cardholder or bank reports a failed authentication. |
| Integration and deployment | Review processing, card management, fraud engine and issuer-app integration points. | ACS adoption depends on the surrounding issuer infrastructure. |
A supported configuration does not mean every setting is available for self-service. Ask which changes require vendor involvement and how those changes are documented.
Security, EMVCo approval and scheme readiness are separate checks
A regulated issuer processor should ask for evidence covering the specific ACS product and deployment. EMVCo product approval, card-scheme onboarding and infrastructure security assessment serve different purposes. Approval of a software product does not automatically establish that a proposed hosted environment is approved for every card scheme or market.
FinOn ACS: published EMVCo approval
ACS FINON, version 2.3.1, has an EMVCo Letter of Approval for EMV 3DS specification versions 2.2.0 and 2.3.1.1. Approval reference: 3DS_LOA_ACS_FITC_020301_01044, dated 10 July 2025, with an expiration date stated as 26 May 2027. The current status and applicable approval conditions should be checked in the EMVCo directory.
Read the official FinOn ACS Letter of Approval · Check current EMVCo listings.
For each proposed deployment, request the applicable card-scheme readiness evidence and a written responsibility matrix for hosting, monitoring, access control, maintenance, incident response and security obligations.
How to compare a licensed ACS with a managed service
Choosing an ACS operating model involves cost, control and responsibility. A transaction-based hosted service may reduce the need to operate infrastructure; a licensed deployment may offer greater infrastructure control but also requires an operating team.
| Buying question | Licensed or self-operated ACS | Managed ACS service |
|---|---|---|
| Hosting | Usually the issuer processor or its infrastructure partner | According to the provider's service scope |
| Authentication configuration | Defined by the permitted administration functions | Defined by service controls and role model |
| Updates and monitoring | Responsibility must be agreed, not assumed | Provider obligations must be specified in the agreement |
| Cost comparison | Licence, integration, infrastructure, security, maintenance and support | Service charges, usage, integration, support and exit terms |
| Evidence to request | Approval scope, architecture and deployment responsibility matrix | Approval scope, environment assessment evidence and SLA |
Model the total cost over the same period and expected authentication volume. Do not assume that an in-house ACS eliminates all variable or scheme-related costs.
Evaluating an ACS for multiple issuing programmes?
Share your card schemes, BIN portfolios, deployment preferences and current integration landscape. FinOn can demonstrate the relevant ACS capabilities and discuss a scoped proposal.
Where FinOn ACS fits in a BaaS or processor architecture
FinOn describes multi-issuer and multi-BIN configuration, configurable risk-based authentication, an ACS administrative interface, integration with issuer systems and external fraud engines, and cloud, on-premises and hybrid deployment options. The exact operating model and administrative scope should be confirmed for a particular project.
Discuss BIN portfolios, supported authentication methods, required branding and policy separation.
See rule configuration, user management and transaction investigation in a representative environment.
Review product approval, scheme requirements, integration responsibilities, deployment and commercial terms.
Issuer-app authentication should be evaluated as a separate integration component. For more detail, see Mobile Authentication SDK for Issuers. If a bank already operates another ACS, the ACS migration playbook addresses data portability, cutover and rollback considerations.
Questions to ask before purchasing an in-house ACS
Does an in-house ACS necessarily improve authentication approval rates?
No. Authentication outcomes depend on transaction data, issuer risk policies, the cardholder journey and other factors. A good evaluation tests frictionless and challenge rates alongside fraud outcomes, rather than treating uplift as guaranteed.
Can one ACS support multiple issuing banks?
Some ACS platforms support multi-issuer operations. FinOn describes this capability, but buyers should verify programme isolation, separate configuration, user roles and administration boundaries in the proposed setup.
Do we need to change our card processor to deploy a new ACS?
Not necessarily. The answer depends on your existing processing contract, issuer integration points, scheme registration and the operational model. Request an integration assessment before deciding.
Can we deploy the ACS in our own infrastructure?
FinOn publicly describes on-premises, cloud and hybrid options. The supported architecture, system requirements, update process and security responsibilities should be confirmed for the individual implementation.
What should we send to request an ACS quotation?
Provide the issuing organisation type, target schemes and markets, number of BINs or card programmes, projected authentication volume, current ACS arrangements, integrations and deployment preference. Ask for an itemised proposal and technical demonstration.
Move from an ACS feature list to a technical evaluation
FinOn's team can review your issuer and processor requirements, demonstrate supported operational controls and clarify the commercial scope.


