- This topic has 8 replies, 3 voices, and was last updated 9 years, 8 months ago by
.
-
Posts
-
I had a member today, who already had one kind of membership (individual), and she want to create a new account for one of the group memberships I offer.
She logged out of her individual account, then used a Stripe button to pay for the group membership, using a different email address to the one I have on file.
Somehow, the SM found her original, individual record and applied the payment to that one. I see from the Debug Log that a Custom value is created, with the user’s IP address. Does SM use this if it cannot find a record in any other way? If so, it is leading to this kind of mix-up.
[I have redacted sensitive information]
[02/08/2017 6:23 PM] – SUCCESS: Stripe Buy Now IPN received. Processing request…
[02/08/2017 6:23 PM] – SUCCESS: Stripe Buy Now charge successful.
[02/08/2017 6:23 PM] – SUCCESS: swpm_handle_subsc_signup_stand_alone(). Custom value: subsc_ref=16&user_ip=xx.xx.xx.xx&swpm_id=8533, Unique reference: ch_xxxxxxxxxxxxxxx
[02/08/2017 6:23 PM] – SUCCESS: Modifying the existing membership profile… Member ID: 8533
[02/08/2017 6:23 PM] – SUCCESS: Setting access starts date value to: 2017-02-08
[02/08/2017 6:23 PM] – SUCCESS: Updating the current membership level (3) of this member to the newly paid level (16)
[02/08/2017 6:23 PM] – SUCCESS: Member signup/upgrade completion email successfully sent to: xxxxx@xxxxx.com
[02/08/2017 6:23 PM] – SUCCESS: Transaction data saved.
[02/08/2017 6:23 PM] – SUCCESS: Redirecting customer to: http://johnfletchermusic.org/thank-you-choir/
[02/08/2017 6:23 PM] – SUCCESS: End of Stripe Buy Now IPN processing.A second “wrong” thing then occurred. If SM decided that this was a renewal to an existing record, why is that, although her existing record was set to expire on 2017-08-31, SM set the new renewal date as 2017-02-08?
I’m loving the plug-in, so hope you can find what is going wrong here.
Cheers,
JohnFHi JohnF, I believe that is the issue in your case. The plugin must be picking up the members Name or email address or IP address. Are they using a different name and e-mail address?
The way you have set up the Stripe payment system means that the members only give an email address and their card details. There is no box for Name or anything else.
The member assured me that they used a different email address, and this was verified by the Debug Log (although I changed it to xxxxs in the message above).
They had logged out of their individual account before clicking on the Stripe button.
As you see in the 3rd line of the Debug Log above, your code seems to create a Custom Value consisting of:
New membership Level ID;
IP address;
Member ID (where did it get this from?)
Stripe Paymemt referenceI was able to sort the member’s records out, by comparing the Debug Log (which I have running all the time), PayPal logs (they used PayPal for their previous payment) and Stripe Payments logs.
Let me know if you need more information.
JohnF
Hi, can you explain the following further.
Somehow, the SM found her original, individual record and applied the payment to that one.
If a member wants to create a new account. The account must have a different user name, email address and probably a different IP address, although I am not 100% about the IP address theory of mine.
After clicking the Stripe Buy Now button on the Join Us page, she entered a different email address from the one I already had on file.
The User Name doesn’t come into the equation at this point in time, but that’s only,asked for when SM decides that there isn’t a match. In this case it somehow discovered the match, and I can only assume it the IP address.
The user must have used the same computer (most people only have one) and SM must have searched the existing database for this IP address toomdeclare that there was a match.
There is still the problem that SM ignored the fact that the record it found was only 6 months in to its 12 months active period, yet ignored this expiry date.
I hope I’m explaining this OK.
J
Thank you for the extra information it helps a lot. The plugin developers will investigate further your issue.
Regards
The user needs to be logged into the site as a member before they click on the payment button. If they are logged into the site then the plugin knows which profile that payment should be applied to.
If the user is not logged in, then the plugin will try to find an existing member profile using the email address that was used in the transaction.
If it doesn’t find any of the above, it will treat it as a brand new payment from someone totally new to this site.
You can’t have multiple different membership account using the same email address. ONE email address gives you ONE membership account. Email address need to uniquely identify a member account. Just the same way you can only use one address for one email account.
Thanks, admin, for responding.
We seem to be going round in circles.
There are two separate problems to my query.
Problem 1
There was an existing membership 1:
Username 1
Email Address 1
Membership Level 3This person wanted to have a separate membership at a different level. They ensured they were logged off from their existing Membership Level 3
They clicked on the Stripe Buy Now button for Membership Level 16on the Join Us page:
In the Stripe window they entered Email Address 2 (different from 1)
They entered their card details.So, there is no commonality between the existing record and the data they are supplying on this new registration, other than SM deciding the IP address is the same.
Simple Membership shouldn’t have found a match. The only way way it could have found the match is by identifying the IP address. This way of trying to find a match shouldn’t apply, because there could be more than one person in a house using the same computer, who both want to have their own membership.
Problem 2
Taking that Simple Membership decided there was a match, the existing record had an expiry date of 2017-08-31, yet applied 2017-02-08 as the new access start date when it should have been 2017-08-31.
I could send you privately the Debug Log snippet containing the sensitive date if you wish.
I have sorted the problem 1 manually, as the member contacted me to tell me about it. And perhaps it was just a glitch that the wrong access start date was applied.
Don’t worry if you can’t find the problem. I can always sort things out manually.
JohnF
- You must be logged in to reply to this topic.