Urgent: PayPal broken and can't get through to HelpDesk

Discussion in 'Troubleshooting' started by insidenetwork_admin, Mar 24, 2010.

  1. insidenetwork_admin

    insidenetwork_admin New Member

    Joined:
    Mar 12, 2010
    Messages:
    15
    We integrated aMember with PayPal Standard using the paypal_r plugin but we're getting an error and no success with membership validation.

    Details:
    * paypal_r ERROR: IPN validation error: Paypal claims it is not-valid IPN transaction: [INVALID]<br />
    * The customer is able to pay, and the payment shows up in our PayPal account
    * On the backend, we're getting response to aMember coming back from PayPal, but not aMember is not dealing with the information correctly
    * It looks like aMember cannot validate the IPN transaction, even though we're successfully getting IPN info from PayPal each time

    I left a note on the forum, and was told to contact helpdesk.

    I've contacted multiple times the past few days and still no answer. I even have the confirmation numbers, if that helps. I'm using the contact form, but I also sent an email to support@

    I'm pretty sure my tickets are not being logged in the system.

    Please help, this is a really urgent problem that is blocking us from doing business.

    Susan
  2. alexander

    alexander Administrator Staff Member

    Joined:
    Jan 8, 2003
    Messages:
    6,279
    Susan,
    I see ticket from you and I see that it was updated by our staff who requested info from you.
    I will take this ticket personally and will update in next hour or so.
  3. insidenetwork_admin

    insidenetwork_admin New Member

    Joined:
    Mar 12, 2010
    Messages:
    15
    'Subscription ID empty' error for cancellations, and recurring subscription broken

    Hey guys,

    Problem 1:
    When I attempt a cancellation from an active account, I get the error:

    Subscription ID empty for XX (the payment number)

    The person can't cancel.

    This is the record we see in aMember payments:

    payment_id: 31
    member_id: 21
    product_id: 1
    begin_date: 2010-03-25
    expire_date: 2010-03-26
    paysys_id: paypal_pro
    receipt_id: 967046801R7582354
    amount: 0.01
    completed: 1
    remote_addr: 76.21.42.190

    It looks like none of these is specifically the 'subscription ID' -- is
    there something we missed in installation, or why else are we getting this
    error? (and user cannot cancel)

    Problem 2: (perhaps related to problem 1)

    We have subscriptions that have 'expired' in aMember, but whose payments successfully recurred in PayPal. It looks like some info is not being correctly passed between PayPal and aMember, telling aMember to allow these subscribers to continue their access.

    * These subscriptions were initiated on 3/25/10 and (since a 1 day subscription period), expired on 3/26/10
    * These subscriptions should have automatically renewed on 3/26/10
    * PayPal shows them as re-billed on 3/26/10, after the expiration of their initial 1-day subscription
    * aMember shows them as 'expired' in the payments section of the Admin Console
    * I cannot log in as one of these 'expired' subscribers (I end up back on the signed out landing page)


    The debug log shows NO errors related to this, during this time period.

    It seems to me that the 'subscription ID' field is not being correctly written, and is affecting both cancellation and renewal functionality.

    Is this a problem with the plugin itself (old /wrong version? we just got it from Helpdesk 2 days ago), or with installation? Or something else?

    Please help, any insights are much appreciated.

    Susan
  4. alexander

    alexander Administrator Staff Member

    Joined:
    Jan 8, 2003
    Messages:
    6,279
    Susan,
    Answered in helpdesk:

    The problem is protection that you enabled for your site root folder.
    Paypal sent IP notifications for recurring payments, amember take subscription ID from first notification.
    But these notifications are not received by aMember because you have your site protected by htaccess.
    So remove that protection and test again.

Share This Page