🤖 Explain with AI

Implementing 3D Secure (3DS) for Fraud Prevention¶

Overview¶

3D Secure (3DS) is an authentication protocol that adds an extra layer of security to online card transactions. As a Merchant of Record, 4Geeks Payments handles 3DS implementation, but understanding how it works and how to configure it is essential for optimizing approval rates and reducing fraud.

In this tutorial, you will:

• Understand how 3DS works
• Configure 3DS settings in 4Geeks Payments
• Handle 3DS authentication flows in your application
• Optimize 3DS for better conversion rates
• Monitor 3DS performance metrics

What is 3D Secure?¶

3DS is a protocol developed by Visa and Mastercard that requires customers to complete an additional authentication step during checkout. The most common methods are:

• SMS OTP: One-time password sent via text
• Banking app approval: Customer approves in their bank’s app
• Biometric verification: Fingerprint or face recognition

3DS Versions¶

4Geeks Payments uses 3DS 2.2 by default, providing the best balance of security and user experience.

Step 1: Configure 3DS Settings¶

1. Log in to console.4geeks.io
2. Navigate to Payments → Settings → 3D Secure
3. Configure your 3DS preferences:

3DS Mode¶

Risk-Based Rules¶

Configure when 3DS should be triggered:

Trigger 3DS when:
├── Transaction amount > $500
├── Customer's first purchase
├── High-risk country
├── Unusual spending pattern detected
├── Card issuer requires it (mandated)
└── Velocity threshold exceeded (>5 transactions/hour)

Step 2: Handle 3DS in Your Application¶

Using Payment Links (Simplest)¶

If you use 4Geeks Payment Links, 3DS is handled automatically:

// Generate payment link with 3DS enabled
const response = await axios.post('https://api.4geeks.io/v1/payment-links', {
  amount: 9900,
  currency: 'USD',
  description: 'Premium Subscription',
  customer_email: 'customer@example.com',
  three_d_secure: 'automatic',  // or 'required', 'off'
  success_url: 'https://yoursite.com/success',
  cancel_url: 'https://yoursite.com/cancel'
}, {
  headers: { 'Authorization': `Bearer ${SECRET_KEY}` }
});

// Redirect customer to the payment link
// 3DS challenge will be handled automatically
window.location.href = response.data.url;

Using Direct API Integration¶

For custom checkout flows:

// Step 1: Create a charge with 3DS
const charge = await axios.post('https://api.4geeks.io/v1/charges', {
  amount: 9900,
  currency: 'USD',
  payment_method_id: 'pm_xxx',
  three_d_secure: {
    enabled: true,
    version: '2.2',
    challenge_indicator: 'no_preference'  // or 'no_challenge_requested', 'challenge_requested'
  },
  return_url: 'https://yoursite.com/3ds-callback'
}, {
  headers: { 'Authorization': `Bearer ${SECRET_KEY}` }
});

// Step 2: Check if 3DS is required
if (charge.data.status === 'requires_action') {
  // Step 3: Redirect customer to 3DS challenge
  const nextAction = charge.data.next_action;

  if (nextAction.type === 'redirect_to_url') {
    window.location.href = nextAction.redirect_to_url.url;
  } else if (nextAction.type === 'use_stripe_sdk') {
    // Handle in-app 3DS challenge (for mobile apps)
    handle3DSChallenge(nextAction.use_stripe_sdk);
  }
}

// Step 4: Handle the callback
// After 3DS completion, customer is redirected to return_url
// Verify the charge status
const chargeStatus = await axios.get(
  `https://api.4geeks.io/v1/charges/${charge.data.id}`,
  { headers: { 'Authorization': `Bearer ${SECRET_KEY}` } }
);

if (chargeStatus.data.status === 'succeeded') {
  // Payment successful
  showSuccessPage();
} else if (chargeStatus.data.status === 'failed') {
  // Payment failed (customer failed 3DS or declined)
  showFailurePage(chargeStatus.data.failure_message);
}

Step 3: Optimize 3DS for Conversion¶

Frictionless Flow¶

3DS 2.2 supports frictionless authentication — the bank approves the transaction without customer interaction when risk is low:

Customer enters card details
    │
    ▼
4Geeks sends authentication request to issuer
    │
    ├── Low risk → Frictionless approval (no customer action needed)
    │
    └── Higher risk → Challenge required (customer completes 3DS)

Optimization Tips¶

Regional Considerations¶

Step 4: Monitor 3DS Performance¶

Key Metrics¶

Access Reports¶

1. Go to Payments → Analytics → 3D Secure
2. View real-time dashboards for all 3DS metrics
3. Filter by region, amount, and card type
4. Export reports for analysis

Best Practices¶

Security¶

• Always enable 3DS for transactions above your risk threshold
• Use liability shift: 3DS shifts fraud liability from merchant to issuer
• Monitor fraud patterns: Adjust risk rules based on fraud trends
• Keep 3DS 2.2 updated: New versions improve both security and UX

Conversion¶

• Use Automatic mode: Let the system decide when 3DS is needed
• Optimize checkout flow: Minimize steps before 3DS challenge
• Mobile optimization: Ensure 3DS works smoothly on mobile devices
• Clear messaging: Tell customers why they need to authenticate

Compliance¶

• PSD2/SCA compliance: Required for EU transactions
• Exemption management: Apply exemptions where legally allowed
• Audit logging: Keep records of all 3DS authentication attempts
• Data retention: Follow local regulations for authentication data

What’s Next?¶

• Learn about Multi-Currency Checkout
• Explore Handling Refunds & Chargebacks
• Read about Tax Compliance as MoR

Need Help?¶

• Documentation: docs.4geeks.io/en/payments
• API Reference: docs.4geeks.io/en/api
• Support: Available through the console dashboard

Still questions? Ask the community.