Appearance

Troubleshooting & FAQ: Common 3DS Implementation Issues ​

This guide addresses the most common issues developers encounter when implementing PayNetWorx 3D Secure and provides clear solutions.

Quick Diagnostic Checklist ​

If you're experiencing issues, check these first:

  • API Credentials: Are you using the correct merchant ID and API key?
  • Environment: Are you pointing to the right endpoint (sandbox vs production)?
  • HTTPS: Is your site running on HTTPS (required for 3DS)?
  • CORS: Are cross-origin requests properly configured?
  • Dependencies: Is the PayNetWorx 3DS SDK properly installed?

Getting Support ​

Before Contacting Support ​

  1. Check Logs: Look for specific error messages
  2. Test with Demo Cards: Verify basic functionality works
  3. Review Documentation: Ensure you're following the guides correctly
  4. Check Network: Verify connectivity to PayNetWorx APIs

What to Include in Support Requests ​

Subject: 3DS Implementation Issue - [Brief Description]

Environment: Sandbox/Production
Merchant ID: merchant-123
Error Code: ERROR_CODE_HERE
Timestamp: 2024-01-15 14:30:00 UTC

Steps to Reproduce:
1. Customer enters card number
2. Challenge iframe appears but remains blank
3. Console shows CORS error

Expected Behavior:
Challenge iframe should display OTP input form

Actual Behavior:
Blank iframe, no authentication prompt

Browser: Chrome 120.0.0.0
Device: Desktop Windows 11
Console Errors: [Paste console errors here]

Prevention Tips ​

Code Review Checklist ​

  • Error Handling: All API calls have try/catch blocks
  • Timeouts: Set reasonable timeouts for all operations
  • Retry Logic: Implement exponential backoff for retries
  • User Feedback: Clear messages for all user states
  • Mobile Testing: Tested on actual mobile devices
  • Cross-Browser: Tested on Chrome, Firefox, Safari, Edge

Pro Tip: Most 3DS issues are related to improper error handling or missing device data. Focus on robust error handling and comprehensive data collection for the best results!