This guide covers the native SureCart integration in BricksMembers. It is the recommended access-assignment path when SureCart runs on the same WordPress site as BRM. It lets BRM react directly to SureCart purchase events without building a generic webhook mapping first.
Why Use the Native Integration?
BricksMembers registers as an official SureCart integration, so it appears in the SureCart product integration UI. For same-site SureCart setups, this should usually be your base layer. If you also enable the Payments module, those same SureCart purchases can also feed BRM billing sync for billing tags, billing conditions, subscription/payment loops, and member-facing billing screens.
- Zero configuration complexity — No webhook URLs, secrets, or field mappings
- Instant level assignment — Levels assigned when checkout completes (purchase_created)
- Subscription support — purchase_invoked (subscription restored) and purchase_revoked (refund, cancel, expiry) handled automatically
- Product-level or centralized mapping — Map in SureCart product settings or on BricksMembers → Integrations → SureCart
- Prices and variants support — Map products, individual prices, or product variants to different membership levels
Important: Payments does not replace SureCart’s checkout. SureCart still handles the store and the actual sale. Payments extends that setup by letting BRM understand and display billing data in a more native way.
Prerequisites
- SureCart installed and active
- At least one SureCart product created
- At least one membership level created in BricksMembers
Step 1: Enable the SureCart Integration
- Go to BricksMembers → Integrations
- Stay on the Overview tab and find SureCart in Commerce & CRM
- Enable the toggle and confirm the change
Once enabled, the SureCart tab is available inside BricksMembers → Integrations.
Step 2: Configure Integration Settings
Open BricksMembers → Integrations → SureCart.
If you also want BRM billing sync, enable the Payments module too. SureCart product, price, and variant identifiers can then be used to resolve the matching BRM offer in the billing layer.
Integration Settings
Create WordPress users for guest checkout
- When enabled: Guest checkout creates a WordPress user and assigns the mapped level
- Default user role: Select the role for new users (default: Subscriber)
Remove levels when purchase is revoked (refund, cancel, or subscription ended)
- When enabled: Levels are removed when SureCart fires purchase_revoked (refund, cancellation, subscription expiry)
- Recommendation: Enable for memberships so access matches payment status
Step 3: Map Products, Prices, and Variants to Levels
On the SureCart tab, use the Product → Level Mapping section to connect SureCart products, prices, or variants to BricksMembers levels.
Product Types
Products
- Base SureCart products. Checking a product grants the level when that product is purchased (any price or variant).
Prices
- Individual prices within a product (e.g., “Monthly $19”, “Annual $149”). In SureCart, a product can have multiple prices.
- Check specific prices to grant different levels for different billing options.
Variants
- Product options (e.g., size, color, plan tier). Variants are distinct from prices in SureCart.
- Check specific variants to map different options to different levels.
Alternative: In SureCart, edit a product and use the Integrations section. BricksMembers appears as an integration—select the level to assign when the product is purchased.
SureCart vs Payments vs Webhooks
- Use native SureCart integration only when SureCart is on the same site and you mainly need access assignment.
- Use native SureCart integration + Payments when SureCart is on the same site and you also want BRM-native billing tags, billing-aware frontend elements, synced subscriptions/payments, and better member billing UX.
- Use webhooks instead when the checkout system is external, on another site, or not SureCart at all.
How It Works
- purchase_created — Checkout complete → levels assigned
- purchase_invoked — Access granted (e.g., subscription restored) → levels assigned
- purchase_revoked — Refund, cancellation, or expiry → levels removed (if “Remove when revoked” is enabled)
Related Guides
- WooCommerce Integration
- FluentCart Integration
- SureContact Integration (sync level changes to tags and lists)
- Webhooks and Field Mapping (for platforms without native integrations)
- Payments Module and Billing (billing sync, dynamic tags, checkout elements)