What is Delegated authentication?
Also: DA
EMVCo framework letting merchants or wallets perform SCA on the issuer's behalf using device biometrics, honoured under FIDO-based scheme programmes.
Delegated authentication is an EMVCo framework enabling a merchant or a wallet provider to perform Strong Customer Authentication (SCA) on behalf of the card issuer.
This is achieved through the merchant's or wallet's secure capture of a biometric from the cardholder's device, which is then cryptographically bound to the transaction and sent to the issuer via the payment scheme.
The issuer, having pre-authorised the merchant to perform this function, receives the biometric authentication data within the authorisation request and uses it to satisfy the SCA requirement, effectively shifting the authentication liability to the merchant or wallet for that transaction.
For a merchant, this translates into a streamlined checkout experience where cardholders authenticate directly within the merchant's application or website, often using fingerprint or facial recognition, bypassing traditional 3D Secure redirects.
The merchant must integrate with a certified authentication provider to support delegated authentication and ensure compliance with scheme-specific programmes, such as those leveraging FIDO standards for biometric enrolment and verification.
A common pitfall is mismanaging the security of the biometric data capture or failing to meet the scheme's stringent requirements for delegated authentication, which can lead to liability shifts back to the issuer or increased fraud rates.
Worked example
A merchant reviews a €240 transaction where Delegated authentication is the deciding factor. The Checkout submits device and transaction data, the issuer risk engine decides whether to challenge the customer, and the authentication result is passed into the authorisation request.
The operational cost is modelled at 0 basis points of interchange change, but a materially different fraud-liability outcome, and the relevant action must complete under 10 seconds.
Step 1 is to capture the original request data, including amount, currency, issuer country, MID, and response or status code. Step 2 is to apply the merchant's rule set, for example whether to retry, challenge, refund, release goods, or hold for review.
Step 3 is to reconcile the result against acquirer reporting so finance can see the cash impact. If the rule improves the outcome by even 50 basis points on 2,000 similar monthly transactions, the merchant protects roughly 10 extra orders from avoidable failure or loss.
Scheme notes
Visa Secure, Mastercard Identity Check, American Express SafeKey, and Discover ProtectBuy all sit on EMV 3D Secure principles, but issuer challenge rates and liability treatment differ by scheme, region, and enrolment status.
ECI values, exemption flags, challenge indicators, and authentication results must be passed correctly into authorisation. In the EEA and UK, PSD2 SCA creates a regulatory overlay, while non-European transactions may use the same protocol mainly for fraud control and liability shift.
Why it matters for merchants
Commercially, this affects conversion, fraud liability, SCA compliance, and the balance between frictionless Checkout and challenge rates. For a merchant processing £500,000 per month, a 25 basis point movement is worth £1,250 before secondary effects such as disputes, reserves, support tickets, or failed delivery costs.
The impact is larger in high-risk, subscription, travel, digital-goods, and cross-border models because issuer decisions and scheme monitoring can compound quickly.
Cardflo can help by combining acquiring access, MID routing, orchestration rules, KYB review, and chargeback tooling where relevant, so the merchant is not dependent on one processor interpretation or one fixed transaction path.
Frequently asked
Which data should a merchant store for Delegated authentication?
Store the transaction ID, MID, acquirer, amount, currency, issuer country, card scheme, response or status code, timestamp, and any 3DS, exemption, refund, or dispute reference. For card transactions, keep authorisation and Clearing identifiers because settlement or chargeback questions may arrive 30 to 120 days later.
For regulated flows, keep customer consent and evidence records for at least the period required by local law or scheme rules. Good records reduce investigation time from hours to minutes when acquirer reporting does not match the order system.
How often should Delegated authentication be reviewed?
High-volume merchants should review exception rates weekly and trend the main metric monthly by scheme, acquirer, issuer country, MCC, and payment method. A movement of 20 to 50 basis points can be material if the merchant processes thousands of orders.
Finance should reconcile the cash impact at settlement level, while risk or payment operations should analyse the root cause. Reviewing only blended totals hides problems that appear on a single BIN range, region, or MID.
What threshold usually triggers action on Delegated authentication?
The threshold depends on the category, but merchants should investigate any sudden change above 10% relative movement or 25 basis points absolute movement. For disputes and fraud, scheme thresholds such as 0.9% under Visa monitoring or 1.5% under Mastercard ECM can create immediate escalation risk.
For settlement or pricing items, even 5 to 15 basis points can justify routing or contract review. The key is to set thresholds before month-end, not after a processor invoice or scheme notice arrives.
Can Delegated authentication differ between acquirers?
Yes. Acquirers can map response codes differently, apply different risk rules, support different data fields, and settle on different cycles.
One acquirer may return a generic decline while another exposes issuer advice that allows a safe retry. Fee treatment can also vary by contract, especially for cross-border, FX, premium cards, and alternative payment methods.
This is why merchants using orchestration should compare performance by acquirer and scheme rather than relying on a single blended approval or cost figure.
What is the first remediation step when Delegated authentication creates losses?
Start with a 30-day sample and split it by scheme, issuer country, card product, payment method, MID, and response or dispute code. Quantify the value at risk in cash terms, not just percentage points.
Then decide whether the fix is operational, such as better evidence or customer communication, technical, such as richer data or 3DS indicators, or commercial, such as a different acquirer route.
Recheck the same metric after one full settlement or dispute cycle to confirm the change worked.
See how Delegated authentication plays out in practice
Industries and regions where this term drives real acquiring, routing, or dispute decisions.
Related terms
PSD2 requirement that customer-initiated electronic payments in the EEA and UK be authenticated with two of: knowledge, possession, inherence.
The current EMVCo authentication standard, sending 100+ data elements to the issuer for risk-based, mostly frictionless customer verification.
A scheme-issued token that replaces the PAN end-to-end and is automatically updated when the underlying card is reissued.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.