Is It Possible to Integrate With Another Type of Processor or Use Any Alternative Payment Methods To Stripe?

Stripe is the only payment method available. If Stripe isn't supported in your country, you'll need to consider other payment options or providers compatible with your location. 

While Memberstack is designed to work seamlessly with Stripe, you can integrate alternative payment processors through a custom implementation process. We strongly discourage this approach due to its complexity and maintenance requirements. If you still choose to proceed, this guide explains how to accomplish this using Memberstack's free plans, along with important technical considerations and requirements.

Note: If you live in a country that is not working with Stripe try contacting our support team so they can guide you on what to do.

1) Key Points

• Stripe is mandatory for paid plans in Memberstack
• Other payment processors can only be used with free Memberstack plans
• Stripe's PayPal integration is currently unreliable and may persist in checkout even after disabling

2) Implementation Overview

Unlike Stripe's native integration, using alternative payment processors requires custom development. Memberstack cannot directly connect to other payment processors, which means:

• Memberstack has no visibility into your plans, products, or purchases
• You'll need to manually map external processor products to Memberstack free plans
• You can still use Memberstack's authentication and permission features

3) Technical Requirements

Core Components Needed

1. Database to store relationships between your payment processor and Memberstack plans
2. Payment processor webhooks to monitor subscription status changes
3. Memberstack Admin Library to:
   • Create members and credentials
   • Add, update, and remove free plans to members (or you can use the DOM package in the front-end)
   • Trigger after successful payment processing
4. Email system (e.g., Sendgrid) to send user credentials and login links

Implementation Considerations

• Design UX flow for canceled subscriptions (e.g., upgrade prompts)
• For one-time purchases:
  • Webhook setup and subscription tracking can be skipped
  • Still requires mapping to Memberstack free plans
  • Still requires associating external product/plan IDs

4) Further Information

• Additional documentation on Make and Zapier implementations is available to assist in creating an automation flow for this use-case should you be interested in exploring this route.