115 pointsSerious WPMU DEV-sterI'm helpful
Chris M.
Member
—
23rd December 2011
I have a customer who was paying monthly ($15), and then changed his account to yearly ($150). He was billed $15 on Nov 23, then $15 on Dec 23 and $150 on Dec 23. The Pro Site log shows the following on Nov 29th:
- User modifying subscription via PayPal Express: New subscription created (XXXXXXX: $150.00 USD every 12 months), first payment will be made on December 23, 2011 - XXXXXXXX
- Reminder to cancel previous PayPal Express/Pro subscription sent to XXXXXXXX
- User modifying subscription via PayPal Express: PayPal returned an error: The token is invalid
- User modifying subscription via PayPal Express: PayPal returned an error: The token is invalid
So either Pro Sites requires that a user MANUALLY cancel their subscription (which would seem like a major problem with the plugin), or there was an issue cancelling the subscription. PayPal is configured correctly, though, because everyone else is getting billed normally.
Now his Pro Sites account says:
Pro Site priviledges will expire on: December 24, 2012
Payment Gateway: PayPal Express/Pro
Payment Term: 1 Month
Last Payment Amount: $15.00
Next Payment Date: December 23, 2012
(Note that there's a typo there: "priviledges" should be "privileges")
I've refunded the $15 and the subscription was cancelled when he filed a dispute, but I'm not sure a) what happened or b) if I need to fix anything with his account. It looks like the expiration date is correct, but the term and amount are not. When I click the PayPal Profile ID link, it takes me to the correct subscription. I don't want to mess with the database until I'm sure I won't break anything else. My inclination is to update the term field to 12 and the amount field to 150.00, but that's only a fix for this particular situation. I need to figure out what happened in the first place…
I have a customer who was paying monthly ($15), and then changed his account to yearly ($150). He was billed $15 on Nov 23, then $15 on Dec 23 and $150 on Dec 23. The Pro Site log shows the following on Nov 29th:
- User modifying subscription via PayPal Express: New subscription created (XXXXXXX: $150.00 USD every 12 months), first payment will be made on December 23, 2011 - XXXXXXXX
- Reminder to cancel previous PayPal Express/Pro subscription sent to XXXXXXXX
- User modifying subscription via PayPal Express: PayPal returned an error: The token is invalid
- User modifying subscription via PayPal Express: PayPal returned an error: The token is invalid
So either Pro Sites requires that a user MANUALLY cancel their subscription (which would seem like a major problem with the plugin), or there was an issue cancelling the subscription. PayPal is configured correctly, though, because everyone else is getting billed normally.
Now his Pro Sites account says:
Pro Site priviledges will expire on: December 24, 2012
Payment Gateway: PayPal Express/Pro
Payment Term: 1 Month
Last Payment Amount: $15.00
Next Payment Date: December 23, 2012
(Note that there's a typo there: "priviledges" should be "privileges")
I've refunded the $15 and the subscription was cancelled when he filed a dispute, but I'm not sure a) what happened or b) if I need to fix anything with his account. It looks like the expiration date is correct, but the term and amount are not. When I click the PayPal Profile ID link, it takes me to the correct subscription. I don't want to mess with the database until I'm sure I won't break anything else. My inclination is to update the term field to 12 and the amount field to 150.00, but that's only a fix for this particular situation. I need to figure out what happened in the first place…
I'm pretty sure the upgrade should have automatically canceled the prior subscription and those 2 errors from PayPal are referencing some trouble doing so. Let me check with the developer on this.
-David
So either Pro Sites requires that a user MANUALLY cancel their subscription (which would seem like a major problem with the plugin
That is correct if they originally signed up with supporter 2.x, which you log seems to indicate. This is due to PayPal API limitations which sucks. They are however warned in big letters on the confirmation page after changing their plan, and sent an email reminder as well that they need to cancel their old subscription via their paypal account to avoid getting double billed. Direct cancellation links/buttons are even included in those messages.
So they ignored 2 separate warnings.
If his new sub is still active and the old is cancelled theres nothing you have to do. If it bugs you you can change the term in the db to 12, but it's not necessary for functionality.
Responses (6)
Member — 23rd December 2011 #
It also looks like when the user issued a dispute, "Pro Site status has been withdrawn." was logged, but their Pro Sites subscription is still active.
WPMU DEV Fanatic — 23rd December 2011 #
Hi Chris,
I'm pretty sure the upgrade should have automatically canceled the prior subscription and those 2 errors from PayPal are referencing some trouble doing so. Let me check with the developer on this.
-David
Lead Developer — 23rd December 2011 #
That is correct if they originally signed up with supporter 2.x, which you log seems to indicate. This is due to PayPal API limitations which sucks. They are however warned in big letters on the confirmation page after changing their plan, and sent an email reminder as well that they need to cancel their old subscription via their paypal account to avoid getting double billed. Direct cancellation links/buttons are even included in those messages.
So they ignored 2 separate warnings.
If his new sub is still active and the old is cancelled theres nothing you have to do. If it bugs you you can change the term in the db to 12, but it's not necessary for functionality.
Lead Developer — 23rd December 2011 #
Oh, and I'll fix the spelling error!
Member — 23rd December 2011 #
I started using Pro Sites at version 3.0 beta 7, so it's definitely not an issue with 2.0.
Lead Developer — 23rd December 2011 #
Did he signup with a beta? That might cause it. Basically pro sites did not determine that he had an existing sub so didn't cancel it.
I wouldn't worry at the moment, but for sure let me know if it happens again.
Become a member