Subscription payments transacton Issue

[orangecode]

Hi there,

I’m working on setting up subscription payments with the SWPM plugin using PayPal, and I’ve run into a few questions I was hoping you could help with:

1. Duplicate “Completed” Transactions

When someone subscribes using the PayPal button, two “Completed” transaction records are being saved in SWPM.
Do you know why this might be happening?

2. PayPal Plan ID Display

In the button editor, some subscription buttons show the PayPal Billing Plan ID automatically, while others don’t show any Plan ID at all.
Is one of these incorrect? How should the buttons be configured?

3. Shipping Address Showing During Payment

Even though we’re only collecting membership fees (not selling physical products), PayPal is still asking users for a shipping address.
Is there a way to turn that off?

Thanks a lot in advance — I really appreciate your help!

Best,

[The Assurer]

1. If you haven’t already done so, please turn on the SWPM debug logs.

2. Do you have a PayPal Business or Personal account?

3. Have you configured your subscription buttons according to these instructions?
https://simple-membership-plugin.com/create-paypal-subscription-buttons-paypal-api/

[orangecode]

Dear Assurer,

1. I hope this message finds you well.

2. I would like to share a few updates and ask for your expert opinion regarding the current configuration and structure of our SWPM-based membership and payment system:

3. After entering the SWPM API keys, we created a .env file and moved it outside of the WordPress directory for better security.
Additionally, we applied the following security rule to prevent unauthorized access:
<Files .env>
Order allow,deny
Deny from all
</Files>

4. We have revised the flow of the payment system to follow this sequence:
Registration → Email Activation → Payment,
and we have successfully completed payment testing with this structure.

5. Could there be any potential issues with changing the payment flow in this way?

6. Initially, about 500 users were manually registered by the admin team.
Could this cause any problems? If so, what steps should we take to ensure these bulk-registered users are safely configured?

7. In the wp_swpm_members_meta_tbl, we are seeing that all records with meta_key: session_tokens have values like a:0:{}.
Is this the expected behavior?

8. Lastly, the current payment system is nearly complete.
Do you think switching to Stripe would be a better option at this stage? We’d appreciate your advice on this matter.

Thank you for your continued support and guidance.

Best regards,

[Author]

Posts