[milloly]

Looking forward to it.

[milloly]

Thank you very much.

[milloly]

Thank you for your response.

I now fully understand the registration and payment logic of Simple Membership.

However, I still believe that keeping PayPal/Stripe emails decoupled from the member emails in the database could help avoid duplicate payments or reduce user confusion.

Perhaps in a future version of Simple Membership, a toggle option could be added, allowing developers to manually enable or disable the coupling of these email addresses.

[milloly]

Thank you for your response.
Perhaps I didn’t explain it clearly enough.

What I meant is:
In Simple Membership → Settings → Email Settings → Email Settings (Account Upgrade Notification), you can configure the email content sent when a user changes their membership level.

However, for renewals and new subscriptions, there doesn’t seem to be a dedicated place to set up email content. As a result, the same Account Upgrade Notification email is sent for subscriptions, renewals, and membership upgrades/downgrades.

If Simple Membership currently doesn’t have a built-in option to customize email content specifically for renewals and new subscriptions, how can I achieve this? How can I customize the emails sent for renewals and paid subscriptions separately?

Thank you very much for your help!

[milloly]

Thank you for your reply, Boss.

I have a deep understanding of the standard registration process and the “register first, then pay” process in Simple Membership.

I would like to confirm something with you.

Is the current design of Simple Membership such that in the standard registration process (purchasing a membership level), if a user has already used the email abc@outlook.com, and the PayPal account is also bound to abc@outlook.com, then when using PayPal to pay, no registration link will be sent?

If this is the case, it might actually be problematic.

The PayPal email and the user’s email should be independent of each other and not interfere with one another.

On the “Join Us” page, when purchasing a membership level via PayPal, a registration link should always be sent.

Looking forward to your reply. Thank you.

[milloly]

Hello, Boss,

Preconditions:
System Design: There is no free user tier. Users purchase membership levels via PayPal and complete registration through a registration link.

Operation 1: The PayPal email is nisinger@outlook.com, and the newly registered user’s email is also nisinger@outlook.com. Below is the system log (everything works normally):

[2025/06/18 01:56:28] – SUCCESS: Empty caps. Calling get_wp_user_roles_by_id() to retrieve role.
[2025/06/18 01:56:28] – SUCCESS: Cancelling all subscription of member id: 40
[2025/06/18 01:56:28] – SUCCESS: No active subscriptions found for member ID: 40
[2025/06/18 01:56:28] – SUCCESS: Empty caps. Calling get_wp_user_roles_by_id() to retrieve role.
[2025/06/18 01:56:28] – SUCCESS: Cancelling all subscription of member id: 39
[2025/06/18 01:56:29] – SUCCESS: No active subscriptions found for member ID: 39
[2025/06/18 01:56:46] – SUCCESS: swpm_pp_create_order ajax request received for createOrder. Button ID: 107, On Page Button ID: swpm_paypal_button_0
[2025/06/18 01:56:46] – SUCCESS: Using the cached PayPal API access token (since it is still valid). Environment mode: sandbox
[2025/06/18 01:56:46] – SUCCESS: Executing order create (v2/checkout/orders) using URL and args.
[2025/06/18 01:56:48] – SUCCESS: PayPal Debug ID from the REST API (by URL) request. Debug ID: f7235671520be, Request URL: https://api-m.sandbox.paypal.com/v2/checkout/orders
[2025/06/18 01:56:48] – SUCCESS: PayPal Order ID: 1KF02029W5577644J
[2025/06/18 01:56:55] – SUCCESS: Received request – swpm_pp_capture_order. Order ID: 1KF02029W5577644J, Button ID: 107, On Page Button ID: swpm_paypal_button_0
[2025/06/18 01:56:57] – SUCCESS: PayPal Capture ID (Transaction ID): 1KF02029W5577644J
[2025/06/18 01:56:57] – SUCCESS:
Array
(
[gateway] => paypal_buy_now_checkout
[txn_type] => pp_buy_now_new
[custom] => subsc_ref=2&user_ip=127.0.0.1&reference=1KF02029W5577644J
[txn_id] => 7EJ461603U7168612
[subscr_id] => 7EJ461603U7168612
[payment_button_id] => 107
[item_number] => 107
[item_name] => Buy: Basic US$5.8/month
[status] => Completed
[payment_status] => Completed
[mc_gross] => 0.10
[mc_currency] => USD
[quantity] => 1
[ip] => 127.0.0.1
[first_name] => John
[last_name] => Doe
[payer_email] => nisinger@outlook.com
[payer_id] => JT9LPDX5SEGC8
[address_street] => 1 Main St
[address_city] => San Jose
[address_state] => CA
[address_zip] => 95131
[address_country] => United States
)
[2025/06/18 01:56:58] – SUCCESS: Validation passed. Going to create/update member account and save transaction data.
[2025/06/18 01:56:58] – SUCCESS: Transaction type: pp_buy_now_new, Transaction ID: 7EJ461603U7168612
[2025/06/18 01:56:58] – SUCCESS: Membership payment paid for membership level ID: 2
[2025/06/18 01:56:58] – SUCCESS: swpm_handle_subsc_signup_stand_alone(). Custom value: subsc_ref=2&user_ip=127.0.0.1&reference=1KF02029W5577644J, Unique reference: 7EJ461603U7168612
[2025/06/18 01:56:58] – SUCCESS: Could not find any record using the given email address (nisinger@outlook.com). Attempting to query database using the unique reference: 7EJ461603U7168612
[2025/06/18 01:56:58] – SUCCESS: Did not find a match for an existing member profile for the given reference. This must be a new payment from a new member.
[2025/06/18 01:56:58] – SUCCESS: Creating new member account. Membership level ID: 2, Subscriber ID value: 7EJ461603U7168612
[2025/06/18 01:56:58] – SUCCESS: Member signup URL: http://localhost:1000/membership/sign-up/?member_id=42&code=67671a3fdcc97086e2a7df41b4d1b5e7
[2025/06/18 01:56:59] – SUCCESS: Member signup (prompt to complete registration) email successfully sent to: nisinger@outlook.com
[2025/06/18 01:56:59] – SUCCESS: Saving transaction data to the database table.
[2025/06/18 01:56:59] – SUCCESS: Transaction data saved.
[2025/06/18 01:56:59] – SUCCESS: Payment Notification Forwarding is Enabled. Posting the payment data to URL: /membership/paid/
[2025/06/18 01:56:59] – SUCCESS: There was an error posting the payment data. Error message: A valid URL was not provided.

Operation 2: The PayPal email is nisinger@outlook.com, and an existing user has already used the nisinger@outlook.com email. When purchasing a membership level without logging into the system, the expected behavior should be to send a registration link to the nisinger@outlook.com email to register a new user. However, the result is that the system directly upgrades the account bound to the nisinger@outlook.com email (duplicate purchase).

[2025/06/18 01:43:52] – SUCCESS: swpm_pp_create_order ajax request received for createOrder. Button ID: 107, On Page Button ID: swpm_paypal_button_0
[2025/06/18 01:43:52] – SUCCESS: [New Token] Creating a new PayPal API access token for environment mode: sandbox
[2025/06/18 01:43:53] – SUCCESS: PayPal Debug ID from the REST API (by URL) request. Debug ID: f125956279ef1, Request URL: https://api-m.sandbox.paypal.com/v1/oauth2/token?grant_type=client_credentials
[2025/06/18 01:43:53] – SUCCESS: PayPal access token created successfully.
[2025/06/18 01:43:53] – SUCCESS: Executing order create (v2/checkout/orders) using URL and args.
[2025/06/18 01:43:54] – SUCCESS: PayPal Debug ID from the REST API (by URL) request. Debug ID: f1326181347be, Request URL: https://api-m.sandbox.paypal.com/v2/checkout/orders
[2025/06/18 01:43:54] – SUCCESS: PayPal Order ID: 6CT414362L0591824
[2025/06/18 01:44:22] – SUCCESS: Received request – swpm_pp_capture_order. Order ID: 6CT414362L0591824, Button ID: 107, On Page Button ID: swpm_paypal_button_0
[2025/06/18 01:44:24] – SUCCESS: PayPal Capture ID (Transaction ID): 6CT414362L0591824
[2025/06/18 01:44:24] – SUCCESS:
Array
(
[gateway] => paypal_buy_now_checkout
[txn_type] => pp_buy_now_new
[custom] => subsc_ref=2&user_ip=127.0.0.1&reference=6CT414362L0591824
[txn_id] => 4HD18712T4963311A
[subscr_id] => 4HD18712T4963311A
[payment_button_id] => 107
[item_number] => 107
[item_name] => Buy: Basic US$5.8/month
[status] => Completed
[payment_status] => Completed
[mc_gross] => 0.10
[mc_currency] => USD
[quantity] => 1
[ip] => 127.0.0.1
[first_name] => John
[last_name] => Doe
[payer_email] => nisinger@outlook.com
[payer_id] => JT9LPDX5SEGC8
[address_street] => 1 Main St
[address_city] => San Jose
[address_state] => CA
[address_zip] => 95131
[address_country] => United States
)
[2025/06/18 01:44:25] – SUCCESS: Validation passed. Going to create/update member account and save transaction data.
[2025/06/18 01:44:25] – SUCCESS: Transaction type: pp_buy_now_new, Transaction ID: 4HD18712T4963311A
[2025/06/18 01:44:25] – SUCCESS: Membership payment paid for membership level ID: 2
[2025/06/18 01:44:25] – SUCCESS: swpm_handle_subsc_signup_stand_alone(). Custom value: subsc_ref=2&user_ip=127.0.0.1&reference=6CT414362L0591824, Unique reference: 4HD18712T4963311A
[2025/06/18 01:44:25] – SUCCESS: Found a match in the member database. Member ID: 39
[2025/06/18 01:44:25] – SUCCESS: Modifying the existing membership profile… Member ID: 39
[2025/06/18 01:44:25] – SUCCESS: This is a payment for the same membership level (renewal scenario).
[2025/06/18 01:44:25] – SUCCESS: Going to use the current expiry date for the Access Starts date.
[2025/06/18 01:44:25] – SUCCESS: Setting access starts date value to: 2025-08-16
[2025/06/18 01:44:25] – SUCCESS: Updating the current membership level (2) of this member to the newly paid level (2)
[2025/06/18 01:44:25] – SUCCESS: swpm_membership_level_changed action triggered. Member ID: 39, Old Level: 2, New Level: 2
[2025/06/18 01:44:25] – SUCCESS: The to (Level ID: 2) and from (Level ID: 2) values are the same. Nothing to do here.
[2025/06/18 01:44:26] – SUCCESS: Member upgrade/update completion email successfully sent to: nisinger@outlook.com
[2025/06/18 01:44:26] – SUCCESS: Saving transaction data to the database table.
[2025/06/18 01:44:26] – SUCCESS: Transaction data saved.
[2025/06/18 01:44:26] – SUCCESS: Payment Notification Forwarding is Enabled. Posting the payment data to URL: /membership/paid/
[2025/06/18 01:44:26] – SUCCESS: There was an error posting the payment data. Error message: A valid URL was not provided.

The current issue is:
Once a user registers with the PayPal email, it becomes impossible to register a new user because PayPal payments always match the previously registered user and upgrade their account. The only workaround is to use a different PayPal account.

My expectations:
1. When a user makes a payment, do not match the PayPal email with the email field in the database. Treat PayPal solely as a payment tool.
2. Allow the same PayPal account to register any number of accounts, regardless of whether those accounts use the PayPal email or not.

I hope to receive your answer. Thank you very much.

[Author]

Posts