Prop Firm Software Subscription and License Management Guide

Prop firm trading tools often start with one trader, one subscription, and one main trading machine. Support problems usually appear when billing status, software access, device activation, and account troubleshooting are handled manually.

A good license management workflow keeps subscription status and product access aligned without making the buying process feel complicated.

The Subscription-First Model

For most traders, the correct purchase path is simple: buy one subscription, activate the product, and use it for the main NinjaTrader setup.

Additional subscriptions only matter when a customer needs separate devices, separate installations, or separate operating environments. That should be an advanced option, not the main marketing message.

Stripe as the Billing Source

Stripe Billing should be the source of truth for:

• Customer ID
• Subscription ID
• Price ID
• Subscription status
• Payment status
• Checkout metadata

Checkout creates the subscription. Webhooks or Make.com scenarios keep the license backend updated.

Make.com as the Provisioning Layer

Make.com can receive Stripe events and call the licensing backend with the fields the product expects:

• stripePriceId
• stripeQuantity
• stripeCustomerId
• stripeSubscriptionId
• stripeSubscriptionStatus

For PropFirmConnector, that means calling makeAuthorizeLicense after Stripe confirms or updates a subscription.

Firebase as the License Backend

Firebase can hold license records, subscription mapping, activation state, and entitlement status. When Stripe status changes, Firebase should reflect whether access is active, restricted, canceled, or unpaid.

Common status actions:

• active: provision or maintain access
• trialing: provision according to trial rules
• past_due: warn or restrict according to policy
• canceled: revoke or schedule revocation
• unpaid: suspend access

Affiliate Attribution

Affiliate codes should be attached before Checkout and passed into Stripe metadata. That makes attribution available later without adding friction to the checkout path.

The launch model for PropFirmConnector supports URLs like:

https://propfirmconnector.com/?ref=partnercode

The website stores that code and passes it to Stripe during checkout.

Recommended Companion: NinjaMobileTrader

For customers buying PropFirmConnector to copy trade multiple prop firm accounts, NinjaMobileTrader is the recommended companion environment. PropFirmConnector handles multiple Rithmic and supported account connections inside one NinjaTrader instance; NinjaMobileTrader is optimized for running NinjaTrader and local trade copiers with lower lag.

Together, they create a cleaner stack for fast local copy trading than routing every account through a slower cloud-sync copier. Execution speed and fills still depend on external market, platform, broker, prop firm, and connectivity conditions.

Operational Checklist

Before launch, confirm:

• Stripe product and price are live
• Checkout creates the subscription
• Make.com receives the required Stripe events
• makeAuthorizeLicense receives all required fields
• Firebase records match the current Stripe subscription status
• Canceled or failed subscriptions change access state

Why This Matters

Manual license handling creates support issues. A subscription-first provisioning model lets billing and access move together, which is easier for customers and easier to support.