get in touch
Enhancing Security and User Experience with 3D Secure Risk-Based Authentication (RBA)

Enhancing Security and User Experience with 3D Secure Risk-Based Authentication (RBA)

Risk-based authentication (RBA) in EMV 3-D Secure helps issuing banks decide when a cardholder can be authenticated without additional interaction and when a challenge is necessary. The decision is made by the issuer's Access Control Server (ACS), using the transaction context, available cardholder and device information, and the issuer's risk policies.

For an issuer, the objective is not simply to maximise the number of frictionless transactions. It is to apply authentication consistently, reduce unnecessary challenges and monitor the impact on fraud, completion rates and operational performance. This guide explains how an ACS risk decision works, which signals matter and what banks should assess when selecting or upgrading an ACS.

What is risk-based authentication in 3D Secure?

Risk-based authentication is an assessment performed during an EMV 3DS authentication request. The ACS evaluates the information available for that request and determines an authentication outcome in line with issuer policy and applicable scheme or regulatory requirements.

Depending on the assessment, the issuer may allow a frictionless flow, request a challenge such as an OTP or banking-app approval, or return another protocol outcome. A high-risk transaction does not automatically lead to a challenge: the issuer may also reject authentication under its policies.

Important: Authentication and payment authorisation are separate decisions. A successful 3DS authentication does not guarantee that the subsequent payment will be authorised. Liability shift, where applicable, depends on scheme rules and transaction circumstances rather than on the mere presence of a 3DS request.

How does the ACS make an RBA decision?

The merchant or payment service provider initiates the authentication through its 3DS Server. The relevant Directory Server routes the authentication request to the issuer's ACS. The ACS uses the data supplied in the request, together with issuer-side policies and any connected risk services, to determine how authentication should proceed.

Simplified 3D Secure authentication decision flow:

  1. 3DS Server: sends the authentication request (AReq).
  2. Directory Server: routes the request to the issuer's ACS.
  3. Issuer ACS: evaluates the relevant signals and the issuer's risk and step-up policies.
  4. Authentication response (ARes): indicates a frictionless result, a required challenge or another applicable outcome.
Example ACS outcomeWhat happens next
Frictionless (ARes transStatus = Y)Authentication is successful without an additional cardholder challenge.
Challenge (ARes transStatus = C)The cardholder completes additional verification. In a typical browser or SDK challenge, CReq/CRes messages support the interaction, and RReq/RRes communicate the final result.
Other outcomesAuthentication can be denied, rejected or unavailable depending on the circumstances and protocol status.

In an app-based checkout, the merchant-side 3DS SDK supports the authentication interface. If the issuer uses out-of-band approval, the cardholder may approve the request in a separate banking app. This is different from an issuer-side mobile authentication SDK.

Which risk signals can an issuer ACS use?

The quality of an RBA decision depends on both the available data and the issuer's policy. The ACS may assess information from the EMV 3DS authentication request and, where integrated, other systems operated by the issuer.

Signal categoryExamplesWhy it matters
Transaction contextAmount, currency, merchant, channel and transaction typeHelps identify whether the purchase fits the relevant transaction pattern.
Device and networkBrowser or app information, device attributes, IP and location-related contextCan reveal unfamiliar devices or technical anomalies.
Cardholder activityPrevious behaviour, account history and relevant merchant relationshipsHelps distinguish familiar behaviour from unusual activity.
Issuer intelligenceCard programme rules, account signals, fraud engine results and watchlistsAllows the bank to apply its own risk appetite and risk controls.

The exact information available varies by transaction, channel, protocol version and integration. Features such as device binding or trust lists can also contribute to risk assessment where supported. Neither guarantees a frictionless outcome.

Technical RBA example: the same payment amount, two different decisions

Consider two online card purchases of €240. Their amounts are identical, but the issuer may make different authentication decisions because their risk contexts differ.

SignalScenario A: familiar behaviourScenario B: unusual behaviour
DevicePreviously recognisedNot previously recognised
Merchant relationshipEstablished purchase historyNo known relationship
Transaction patternConsistent with recent account activityUnusual frequency or context
Issuer policyNo additional verification rule triggeredStep-up rule triggered
Possible ACS decisionFrictionless authenticationChallenge required

These are illustrative examples, not actual issuer data or FinOn ACS default thresholds. A transaction can have additional signals, and a bank may reach a different decision using its own policy and regulatory requirements.

For issuer teams, the operational question is whether the ACS makes the appropriate distinction. Overly strict rules may increase unnecessary challenges and abandonment. Overly permissive rules may expose the bank to unacceptable fraud risk. Effective RBA balances these outcomes rather than optimising the frictionless rate in isolation.

How should banks measure RBA performance?

Issuers should assess authentication outcomes and downstream performance before and after rule changes. Six metrics are particularly useful:

  1. Frictionless authentication success rate: the share of eligible requests successfully authenticated without a challenge, using a consistent denominator.
  2. Challenge rate: how often the ACS requires additional verification, segmented by BIN, channel and other relevant dimensions.
  3. Challenge completion rate: the proportion of initiated challenges completed successfully; distinguish abandonment, expiry and failed verification.
  4. Authentication latency: ACS response time and the time required to reach a final authentication result.
  5. Technical failure rate: unavailable results, timeouts, integration errors and failures by channel or version.
  6. Subsequent fraud and dispute outcomes: downstream indicators evaluated with an appropriate time lag and reliable data definitions.

Where reporting systems permit, the bank should also connect authentication results with payment authorisation outcomes. This helps distinguish an ACS authentication problem from a later decline in the authorisation process.

Questions to ask during an ACS demonstration: Can the team filter results by issuer programme, BIN, scheme, country and device channel? Can operators inspect transaction-level logs? Can they compare performance before and after changes to an RBA rule?

How can an issuer implement and tune RBA rules?

  1. Document authentication policy. Identify mandatory step-up cases, scheme requirements, issuer risk appetite and the policies applied to different card programmes.
  2. Review available inputs. Confirm which EMV 3DS fields reach the ACS and what card, account, fraud and device information can be provided by issuer systems.
  3. Test representative scenarios. Evaluate familiar and unfamiliar devices, missing data, suspicious transaction patterns, conflicting rules and timeout cases before production rollout.
  4. Monitor and adjust. Compare frictionless results, challenge completion, technical failures and fraud outcomes. Maintain an audit trail of policy changes.

For out-of-band authentication, the issuer should also test push delivery, banking-app availability, expiry behaviour and session matching. These elements can determine whether a challenge succeeds even when the ACS risk decision is correct. For more on issuer-app verification, see Mobile Authentication SDK for Issuers.

What should banks check when choosing a 3DS ACS with RBA?

Most ACS vendors describe their solutions as supporting risk-based authentication. The differences become clearer when issuers examine how rules are configured, how decisions can be investigated and how the ACS integrates with existing risk infrastructure.

  • Can issuer teams configure and update risk and challenge rules without extensive vendor development?
  • Can policies differ by BIN, card programme, issuer or channel where required?
  • Can the platform use the bank's existing fraud engine or other external risk services?
  • How are decision logs, policy versions and rule changes recorded?
  • Which challenge methods are supported, including OTP and out-of-band approval?
  • What deployment models, integration interfaces and operational responsibilities apply?
  • Which protocol versions, approvals and payment scheme requirements are supported for the exact component being offered?

A useful vendor demonstration should include the issuer's own decision scenarios and reporting requirements, not only a standard frictionless checkout example.

How FinOn 3DS ACS supports issuer risk-based authentication

FinOn 3DS ACS is designed for banks, card issuers and issuer processors. Its documented capabilities include configurable risk-based authentication policies, built-in scoring and the option to integrate with an external fraud engine.

  • Configurable risk policies: support for issuer-defined rules and challenge logic.
  • Multi-issuer and BIN configurations: separate authentication settings for different programmes and issuer environments.
  • Risk integrations: built-in assessment options and connectivity to existing fraud systems.
  • Monitoring and reporting: transaction search, logs, analytics and operational visibility.
  • Challenge options: support for OTP and out-of-band authentication scenarios.
  • Deployment flexibility: cloud, on-premise and hybrid arrangements, depending on implementation scope.

During a technical discussion, issuer teams can review rule configuration, monitoring views, fraud engine integration and the responsibilities of each party. Exact scoring logic, integration scope and deployment conditions should be confirmed for the proposed solution.

Planning an ACS upgrade or reviewing your risk policies? Request a FinOn ACS demo to discuss your issuer programmes, challenge methods, fraud systems and reporting requirements.

Frequently asked questions about risk-based authentication

What is risk-based authentication in 3D Secure?

It is the issuer's assessment of the information available during EMV 3DS authentication to determine whether a transaction can be authenticated frictionlessly, requires additional verification or leads to another authentication outcome.

Who decides whether a 3DS transaction is frictionless or challenged?

The issuing bank's ACS makes the authentication decision according to the available information and issuer policies. The merchant-side 3DS Server may send relevant data and a challenge preference, but it does not unilaterally determine the ACS outcome.

Is a 3DS challenge the same as risk-based authentication?

No. RBA is the assessment process. A challenge is one possible outcome that asks the cardholder to complete an additional verification step, such as an OTP or approval in a banking app.

Does risk-based authentication remove the need for OTP?

No. Risk-based authentication can reduce unnecessary challenges, but an issuer may still request OTP or another method when its rules, the transaction context or applicable requirements call for additional verification.

Can FinOn ACS work with an existing fraud engine?

FinOn states that its ACS can use built-in scoring or integrate with an external fraud engine. Specific integration methods and signal mapping should be reviewed during technical scoping.

Which RBA metrics should an issuer monitor?

Core measures include frictionless success, challenge rate, challenge completion, authentication latency, technical errors and downstream fraud. Comparing these measures by BIN, channel and policy version is more informative than tracking one overall rate.

Further reading

Technical references: EMVCo: Improving Risk Analysis and Frictionless Flow and EMVCo: Challenge Flow.

Ready to see the Full Picture?

Let’s connect - and walk you through a personalized demo.

Your message has been sent.
We will contact you shortly.