WooCommerce集成Barclaycard ePDQ支付网关插件交易失败及回调URL疑问求助

Let’s walk through the key steps to diagnose and fix this issue:

• Verify the Callback URL Validity
  The URL format https://example.com/wc-api/RapidDive_WC_Gateway_Barclay/ aligns with WooCommerce’s standard gateway callback structure (wc-api/[Gateway_Class_Name]). Here’s what to check:

  • Replace example.com with your actual domain, and ensure the URL uses HTTPS—Barclaycard ePDQ requires secure callback addresses.
  • Test accessing the URL directly: you should get a 403 Forbidden or blank page (since it only accepts POST requests from Barclaycard’s servers). A 404 error means the plugin hasn’t registered the endpoint correctly—double-check the plugin is activated, or try reinstalling it.

• Cross-Check Barclaycard ePDQ Backend Settings

  • Log into your Barclaycard ePDQ merchant portal, navigate to Technical Settings > Transaction Feedback (or similar, depending on your portal version). Confirm the "Direct HTTP server-to-server request" URL matches your plugin’s callback URL exactly (including trailing slashes, if present).
  • Ensure your hosting provider isn’t blocking incoming requests from Barclaycard’s IP addresses. You can find their official IP list in the ePDQ documentation, and ask your host to whitelist these addresses.

• Inspect WooCommerce and Plugin Logs

  • Go to WooCommerce > Status > Logs in your WordPress dashboard. Filter logs for entries containing barclay, epdq, or RapidDive—these will show detailed request/response data from the gateway, including specific error codes (e.g., non-10000 codes indicate validation or configuration issues).
  • If the plugin has its own logging feature (check its settings page), enable it to capture additional transaction details.

• Rule Out Compatibility Issues

  • Make sure you’re running the latest version of the plugin and WooCommerce—outdated versions often have compatibility gaps that break callback handling.
  • Temporarily disable all other plugins and switch to a default WooCommerce theme (like Storefront). Retest the payment flow to confirm the error isn’t caused by a conflict.

• Validate Merchant Credentials

  • Double-check your plugin’s settings for correct Merchant ID and SHA Secret Key. These must match exactly what’s configured in your ePDQ portal. Also confirm the SHA hash algorithm (SHA-1/SHA-256) is set identically in both the plugin and ePDQ backend—mismatched hashes will fail transaction validation, triggering the error.

内容的提问来源于stack exchange，提问作者hmd