Skip to content

Getting Started with PayNetWorx 3D Secure ​

Welcome to PayNetWorx 3D Secure! This guide will help you understand and implement 3DS authentication to reduce fraud and increase your payment approval rates.

What is 3D Secure (3DS)? ​

3D Secure is an authentication protocol that adds an extra layer of security to online card payments. Think of it as the online equivalent of using a PIN when paying with your card in-store.

Key Benefits for Your Business ​

  • Reduce Fraud: Up to 95% reduction in fraudulent transactions
  • Liability Shift: Transfer fraud liability from your business to the card issuer
  • Higher Approval Rates: Issuers approve more transactions when they have additional verification
  • Regulatory Compliance: Meet requirements for PSD2, SCA, and other regulations
  • Customer Trust: Show customers you take security seriously

How 3DS Works: The Two Authentication Flows ​

1. Frictionless Flow (most transactions) ​

  • Customer Experience: Completely invisible to your customers
  • Process: Authentication happens in the background using 100+ data points
  • Speed: Instant (adds no time to checkout)
  • When Used: Low-risk transactions (returning customers, familiar devices, normal purchase patterns)

2. Challenge Flow ​

  • Customer Experience: Additional verification step (OTP, biometric, or PIN)
  • Process: Customer must complete authentication challenge
  • Speed: Adds 30-60 seconds to checkout
  • When Used: High-risk transactions (new customers, unusual amounts, new devices)

Prerequisites ​

Before starting your 3DS integration, ensure you have:

  • Existing PayNetWorx payment API integration
  • Business registered with PayNetWorx for 3DS
  • Development environment for testing
  • Basic understanding of API integration

Quick Start Checklist ​

Phase 1: Planning & Setup ​

  • Review this documentation
  • Register for 3DS with PayNetWorx
  • Set up test environment
  • Install PayNetWorx 3DS SDK

Phase 2: Backend Implementation ​

  • Implement transaction initiation
  • Add data gathering flows
  • Add challenge flows handling
  • Test error scenarios

Phase 3: Frontend Integration ​

  • Integrate 3DS SDK
  • Test customer flows
  • Implement fallback handling

Phase 4: Testing & Go-Live ​

  • Complete end-to-end testing
  • Configure production environment
  • Monitor initial transactions

Pro Tip: Start with our demo to see 3DS in action before implementing!