
3D Secure Authentication: How to Use Fraud Scores to Decide When to Trigger 3DS
Introduction
3D Secure is the extra check that sits between a card payment and the issuing bank. When it works well, a genuine shopper barely notices it. When it is applied to every order without thought, it adds steps, timeouts, and abandoned carts.
That is why the real question is not "Should we use 3D Secure?" It is "Which payments should we send through 3D Secure authentication, and when?" The answer depends on risk. A small repeat order from a loyal customer is very different from a first order with a prepaid card, a proxy IP, and a disposable email.
Regulators in Europe have measured how much strong authentication matters for card payments. The joint report from the European Banking Authority and the European Central Bank is clear about the gap:
"In 2024, fraud rates for card transactions without SCA within the EEA were twice as high in both value and volume terms than transactions with SCA within EEA, while for transactions outside the EEA they were three times higher in value and four times higher in volume terms." Source: EBA and ECB, 2025 Report on Payment Fraud
This guide explains how 3DS works, where PSD2 rules apply, and how a real-time fraud score helps you decide when to trigger 3DS.
What 3D Secure Authentication Does at Checkout
3D Secure, often shortened to 3DS, is a protocol that lets the card issuer confirm that the person paying is the real cardholder. It applies to card not present payments, such as online checkout and in-app purchases. Our 3D Secure glossary entry covers the basics.
EMVCo, the body that maintains the EMV 3DS specifications, describes it as a way for merchants and issuers to exchange data about the transaction, the payment method, and the device. The issuer uses that data to decide how much proof it needs from the shopper. You can read the overview on the EMVCo 3D Secure page.
Frictionless flow and challenge flow
Modern 3DS has two main paths:
- Frictionless flow. The issuer reviews the data and approves the authentication without asking the shopper for anything.
- Challenge flow. The issuer asks the shopper to prove who they are, for example with a one time passcode, a banking app approval, or biometrics.
The issuer makes the final call on whether to challenge. As the merchant, you decide whether to request 3DS at all and what data and preferences you send with the request.
How 3DS2 differs from the original 3D Secure
The first version relied on static passwords and redirect pages that many shoppers found confusing. 3DS2, the EMV 3DS standard, shares much richer data and works inside mobile apps. EMVCo notes that version 2.1 supports SCA, and it recommends version 2.2 or higher for the best functionality.
Why Sending Every Payment Through 3DS Hurts Conversion
Every challenge is a moment where a real customer can give up. The passcode might arrive late. The banking app might not open. The shopper might be on a train with weak signal.
Blanket 3DS also wastes your best signal. If every order gets the same treatment, you learn nothing about which customers are genuinely risky. Good customers pay the friction cost for the few bad actors.
Skipping 3DS completely has its own cost. You lose an important layer against stolen card details. In many cases you also give up the chargeback liability protection that card networks link to successful authentication.
Liability rules for authenticated transactions are set by each card network and vary by region and dispute type. Ask your acquirer or payment provider how they apply to your business.
How PSD2 and Strong Customer Authentication Shape 3DS in Europe
In the European Economic Area, the revised Payment Services Directive (PSD2) requires strong customer authentication, or SCA, for many electronic payments. SCA means proof from at least two of three categories: something the customer knows, has, or is. Our SCA glossary entry explains the term.
For online card payments, 3DS is the common way to deliver SCA. EMVCo notes that an EBA Opinion published in June 2019 recognised that protocols such as EMV 3DS support the use of SCA.
The EBA and ECB report also shows why online card payments get so much attention. In 2024, the fraud rate for remote card payments was 13 times higher in value than for non remote card payments, at 0.091% compared with 0.007%.
Exemptions that keep low risk payments smooth
The detailed rules sit in the Commission Delegated Regulation (EU) 2018/389, the regulatory technical standards on SCA. It includes exemptions such as:
- Low value transactions. Remote payments up to EUR 30, within cumulative limits of EUR 100 or five consecutive payments since the last SCA.
- Transaction risk analysis. A payment service provider can skip SCA for a payment its real-time risk analysis rates as low risk. This applies only within value bands tied to the provider's own fraud rates. For remote card payments, the reference fraud rates are 0.13% up to EUR 100, 0.06% up to EUR 250, and 0.01% up to EUR 500.
These exemptions are applied by payment service providers, meaning your acquirer or the card issuer, not by the merchant alone. The issuer can still require SCA.
This section summarises public EU sources for context only. It is not legal or compliance advice. Confirm your obligations with your acquirer and qualified advisers.
Where a Fraud Score Fits in the 3DS Decision
Greip does not perform 3D Secure authentication. Your payment provider or 3DS server handles that. What Greip adds is the risk signal you use before that step.
Think of it as a traffic light at the start of your payment flow:
- Score the order with all the context you have.
- Use the result to decide whether to proceed without 3DS where that is allowed, request 3DS, or stop the order.
- Pass your decision to your payment provider, which runs authentication and authorisation.
This keeps friction for the orders that need it. It also means obvious fraud never reaches authentication, so you are not paying fees or risking declines on payments you already know are bad.
Scoring the Payment Before You Request Authentication
Greip's payment fraud detection analyses the order, customer, device, and card in real time. You send the details to POST /score/payments with your key in the Authorization header. Every field below is documented in the Payment Fraud Detection API reference.
POST https://v2.greipapi.com/score/payments
Authorization: Bearer <api_key>
Content-Type: application/json{
"data": {
"action": "purchase",
"website_domain": "domain.com",
"transaction_id": "ORD-20817",
"transaction_amount": 189.00,
"transaction_currency": "EUR",
"customer_id": "u_40318",
"customer_ip": "12.12.12.12",
"customer_email": "alex@example.com",
"customer_phone": "+12121234567",
"customer_country": "DE",
"customer_useragent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64)",
"billing_country": "DE",
"shipping_country": "DE",
"payment_type": "cards",
"card_number": "456789",
"cvv_result": true
}
}Reading the response
This is the sample response from the documentation:
{
"success": true,
"data": {
"score": 82,
"risk_level": "high",
"recommendation": "review",
"rules": [
{
"id": "PF10003",
"description": "Customer IP Address is probably VPN/Proxy/Bot/Hosting/Cloud."
},
{
"id": "PF10004",
"description": "Customer Email Address is probably invalid or spam."
},
{
"id": "PF10001",
"description": "High purchase rate, according to `customer_ip`."
},
{
"id": "PF10002",
"description": "High purchase rate, according to `customer_id`."
},
{
"id": "PF10013",
"description": "Customer device might not be a real device (according to `customer_useragent`)."
},
{
"id": "PF10014",
"description": "Customer device is registered as a high-risk device (according to `customer_useragent`)."
}
],
"rules_checked": 21,
"rules_detected": 6,
"velocity": {
"ip_24h_count": 4,
"ip_7d_count": 12,
"email_24h_count": 1,
"email_7d_count": 2,
"phone_24h_count": 0,
"phone_7d_count": 3
},
"custom_rules_applied": { "total": 0, "rules": [] }
},
"execution_ms": 5
}The score runs from 0 to 100. The risk_level is low, medium, or high. The recommendation is accept, review, or reject, and it maps neatly to a 3DS decision.
Mapping the recommendation to an action
accept: proceed with your standard flow. In the EEA, your provider may still apply SCA or an exemption.review: request 3DS and, if your provider supports it, signal that you prefer a challenge.reject: stop the order before authentication and authorisation.
The rules array tells you why. In the sample above, a proxy IP, a risky email, and high purchase velocity together explain the review result.
Adding Card Context With a BIN Lookup
The card itself carries useful risk context. A BIN lookup reads the first digits and returns the scheme, card type, issuing bank, and issuing country. You call GET /lookup/bin/{bin} as documented in the BIN Lookup API reference.
GET https://v2.greipapi.com/lookup/bin/456789
Authorization: Bearer <api_key>This trimmed example comes from Greip's guide to verifying card BINs before payment:
{
"success": true,
"data": {
"bin": "456789",
"is_valid": true,
"reason": null,
"is_blacklisted": false,
"scheme": {
"name": "Visa",
"is_luhn": true,
"is_prepaid": false,
"is_commercial": false,
"type": "debit",
"brand": "Traditional",
"currency": "SAR"
},
"bank": { "name": "AL RAJHI BANKING AND INVESTMENT CORP.", "city": "Riyadh" },
"country": { "alpha2": "SA", "name": "Saudi Arabia" }
},
"execution_ms": 2
}Compare data.country.alpha2 with the billing country and the IP country. A mismatch is a good reason to request 3DS. A true value in is_prepaid may also justify extra checks for high value orders.
Send only the first 6 to 8 digits to BIN lookup. The full card number is not needed, which keeps card data out of your fraud checks.
Network and Contact Signals That Sharpen the Decision
Payment scoring already weighs the IP, email, and phone. You can also call these checks on their own earlier in the journey, for example at signup or when a saved card is added.
IP and proxy checks
Greip's VPN and proxy detection flags VPN, proxy, Tor, and hosting traffic. Request it with params=security on IP lookup and read the data.security object. Anonymous networks hide the real location of the shopper, which weakens your country checks.
Email and phone quality
Disposable or invalid contact details suggest a shopper who does not expect a long relationship. Greip's email and phone validation returns fields such as is_valid, is_disposable, and risk_level that you can use in your rules.
Building a Simple 3DS Decision Policy
Keep the first version simple and explainable. A three tier policy works for most merchants.
Low risk orders
Orders with recommendation set to accept, consistent countries, and normal velocity go through your standard flow. Outside the EEA, where 3DS is usually optional, you may choose not to request it. Inside the EEA, let your provider apply SCA or any exemption it supports.
Medium risk orders
Orders with review, a country mismatch, or a prepaid card on a high value basket get 3DS with a challenge preference. Successful authentication adds confidence and may shift liability.
High risk orders
Orders with reject, a blocked BIN, or several strong warning signs stop before authentication. Sending them to 3DS only adds cost and noise.
Thresholds are yours to set. Start with Greip's recommendation value, then adjust using your own fraud and approval data.
Real Checkout Scenarios
A returning customer buys a small item
Same device, same country, clean email, low score. Proceed with minimal friction and let your provider handle any SCA requirement.
A new account orders electronics with a foreign prepaid card
The BIN country differs from the billing country, the card is prepaid, and the IP sits on a hosting network. Request 3DS with a challenge, or send the order to manual review.
A burst of small payments from one IP
Velocity counts such as ip_24h_count climb quickly, and several cards are tried. This looks like card testing. Block the pattern before it reaches authentication.
Common Challenges and How to Handle Them
Authentication failures look like fraud. A failed challenge can mean fraud, but it can also mean a shopper who lost signal. Offer a retry or another payment method before you block.
Exemptions are not guaranteed. Even when you ask for an exemption, the issuer can still require SCA. Design your flow so a challenge never breaks checkout.
Thin data gives weak scores. A score is only as good as its inputs. Send customer_id, customer_useragent, and billing and shipping details whenever you can. Velocity counts appear only when you send customer_id or a request user_id.
Rules drift over time. Fraud patterns change. Review which rules fire most often and update custom rules and blocklists as you learn.
Best Practices for Tuning Your Thresholds
- Run scoring in test mode first and compare results with your past fraud and chargeback data.
- Track challenge rates, authentication success rates, and approval rates side by side.
- Store the full score response with each order for later disputes and audits.
- Encode your own knowledge with custom rules, and check
custom_rules_appliedto see when they fire. - Review high value and cross border orders more strictly than small domestic ones.
Our payment fraud use case shows how this approach reduces chargebacks without blocking good buyers. For more checkout ideas, see our ten checkout checks for ecommerce.
Where 3DS and Fraud Scoring Are Heading
Authentication keeps moving toward less friction and more data. EMVCo has published a whitepaper with the FIDO Alliance on using FIDO authentication data in EMV 3DS messages to reduce both fraud and friction.
Regulators are also watching how fraud changes. The EBA press release on the 2025 report says strong authentication remains effective. It also warns that new fraud often targets transactions with an SCA exemption or manipulates real users into authenticating fraudulent payments. That makes behaviour and context signals more important, not less.
The direction is clear. Authentication proves who is paying. Risk scoring helps you decide when that proof is worth asking for. The same idea applies to logins, as covered in our guide to risk based MFA.
Frequently Asked Questions
What is 3D Secure authentication?
3D Secure is a protocol that lets the card issuer confirm that the person making an online card payment is the real cardholder. The issuer may approve silently in a frictionless flow or ask the shopper for extra proof in a challenge flow.
What is the difference between 3DS and 3DS2?
The original 3D Secure relied mostly on static passwords and redirect pages. 3DS2, the EMV 3DS standard, shares richer transaction and device data with the issuer, supports mobile apps, and allows many payments to be approved without a challenge.
Is 3D Secure required under PSD2?
PSD2 requires strong customer authentication for many electronic payments in the European Economic Area, subject to exemptions in the EU regulatory technical standards. 3D Secure is the common way to deliver SCA for online card payments. Confirm your obligations with your acquirer.
Does Greip perform 3D Secure authentication?
No. Greip does not run 3DS. Greip provides real-time payment fraud scoring, BIN lookup, IP and proxy checks, and email and phone validation. You use those signals to decide when to request 3DS from your payment provider.
How can a fraud score decide when to trigger 3DS?
Score the order before authentication. Low risk orders follow your standard flow, medium risk orders go through 3DS with a challenge preference, and high risk orders are stopped. Greip returns a recommendation of accept, review, or reject to support this mapping.
Can I skip 3DS for low risk payments?
Outside the EEA, 3DS is often optional, so many merchants skip it for low risk orders. Inside the EEA, SCA exemptions such as transaction risk analysis are applied by payment service providers, and the issuer can still require authentication.
Conclusion
3D Secure is a powerful tool against card not present fraud, but it works best when used with intent. Sending every payment through a challenge costs you good customers. Sending none leaves you exposed.
A real-time fraud score gives you the missing decision layer. Score the order, add card and network context, and then choose to proceed, request 3DS, or stop. Start with a simple policy, measure the results, and tune your thresholds as your data grows.
Get started
Start protecting your business today
Our service is trusted by thousands of businesses worldwide.
- 1,000 requests during trial
- Cancel anytime