Summary
The Authorize.Net debug log in MemberPress creates a detailed log file that records payment information sent from Authorize.Net to MemberPress. This log is essential for troubleshooting recurring payment issues, such as subscription payments not being recorded in MemberPress or payment failures.
Enabling debug logging allows support teams to identify whether MemberPress is receiving payment notifications from Authorize.Net and to diagnose subscription matching issues that prevent payments from being processed correctly.
Troubleshooting
Enabling the Authorize.Net Debug Log
To troubleshoot recurring payment issues, the debug log must first be enabled on the site.
- Access the site’s files via FTP, cPanel File Manager, or hosting control panel.
- Navigate to the site’s root directory and locate the wp-config.php file.
- Open the wp-config.php file for editing.
- Add the following line of code:
define('WP_MEPR_DEBUG', true);
- Place this line above the following line in the file:
/* That's all, stop editing! Happy publishing. */
- Save the wp-config.php file.
Locating and Accessing the Debug Log
Once debugging is enabled, MemberPress will create a log file when payment notifications are received from Authorize.Net.
- Navigate to the site’s /wp-content/ folder.
- Look for the authorize-net.log file.
- Download or open the authorize-net.log file to view the payment information.
Interpreting the Debug Log
1) Issue: Payment Information Not Recorded in MemberPress
When a recurring payment is successfully sent to MemberPress from Authorize.Net, the log will contain specific information that can be used to troubleshoot recording issues.
How to Test/Fix: Look for the following line in the log file:
New recurring payment came.
Below this line, detailed payment information will be displayed, including:
- Member ID and information;
- Subscription number;
- Payment amount;
- Transaction details;
If the subscription number in the log does not match the subscription number in WordPress Dashboard > MemberPress > Subscriptions, the payment will not be recorded in MemberPress. Verify that the subscription numbers match between Authorize.Net and MemberPress.
2) Issue: No Payment Notification Received
If MemberPress is not receiving payment notifications from Authorize.Net, this will be evident in the debug log.
How to Test/Fix: Check the log file for the absence of “New recurring payment came” entries for expected payment dates. If no entries exist for a specific payment, this indicates:
- Authorize.Net is not sending payment notifications to MemberPress;
- The webhook URL in Authorize.Net may be incorrect;
- There may be connectivity issues between Authorize.Net and the site;
Verify the webhook URL is correctly configured in the Authorize.Net merchant account and that the site can receive external requests.
3) Issue: Subscription Matching Problems
Payment notifications may be received but not processed due to subscription matching issues.
How to Test/Fix: Compare the subscription details in the log with the subscription information in WordPress Dashboard > MemberPress > Subscriptions. Look for:
- Matching subscription IDs;
- Correct member associations;
- Active subscription status in MemberPress;
If subscription details don’t match, verify the subscription setup in both Authorize.Net and MemberPress, ensuring they were created properly and remain synchronized.
Disabling Debug Logging
After troubleshooting is complete, disable debug logging to prevent log file growth and potential security concerns.
- Open the wp-config.php file.
- Remove or comment out the following line:
define('WP_MEPR_DEBUG', true);
- Save the file.