401 server error with recurring transactions

  • pflagpdx

    (@pflagpdx)


    10 years, 4 months ago

    Recurring Transactions (donations, subscriptions) create two transactions in PayPal – one creating a buyer profile for subsequent payments, the other containing the details of the recurring transaction.
    My IPN listener (Salesforce APEX), fed from the Button Manager, works fine with all single-event single notification transactions but throws a 401 (no authentication) error on the Transaction notification, although the transaction is processed properly. Subsequent transactions work fine, but the Transaction notification of a Recurring Transaction notification pair always fails.
    I’m wondering if others have seen this behavior and can offer any remedies.

    Thanks.

    https://wordpress.org/plugins/paypal-wp-button-manager/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor angelleye

    (@angelleye)

    10 years, 4 months ago

    So you’re saying there’s a problem happening within your IPN listener for the recurring payments that are related to a subscription?

    You would need to troubleshoot the IPN listener to figure out what’s going on there. Are you able to check PHP error logs where your IPN listener is running? Something must be happening in your listener with those types of transactions and the data that comes in them causing the IPN listener to fail. The logs are the best way to figure out what the problem is.

    Thread Starter pflagpdx

    (@pflagpdx)

    10 years, 4 months ago

    Aye, the problem is most assuredly in the IPN listener, but seems to be related to the near-simultaneous sending of the notification pair and possibly delays in the IPN listener’s verification handshake generation loop. I was interested in verifying my observation of the timing of the PayPal IPN notifications for recurring transaction.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘401 server error with recurring transactions’ is closed to new replies.