Integrations

Stripe for J2Commerce is the payment rail for J2Commerce checkout. It integrates with Joomla and J2Commerce events, not with every RCA booking or download plugin unless your checkout flow already includes those products.

How does this plugin sit in J2Commerce?

J2Commerce owns cart, checkout, orders, and payment plugin dispatch. This plugin registers as a J2Commerce payment method, creates Stripe Checkout sessions on prepayment events, handles return URLs on postpayment flows, and verifies webhooks for session completion and async outcomes. Order status updates use J2Commerce OrderTable and order history helpers in the v6 line.

How does it relate to RCA OSB J2C Bridge?

Bridge adds mapped booking products to cart; Stripe charges whatever checkout total J2Commerce calculates after tax, coupons, and fees. Configure Bridge sid_map and Stripe payment assignment independently. A hold-to-cart success with failed payment is still a payment plugin or keys problem, not a bridge map problem.

How does it relate to downloadable products and sync plugins?

RCA J2C Downloadable Files Sync keeps product file rows aligned with ZIP folders; Stripe does not deliver files. Entitlement and download emails still follow J2Commerce rules after payment status reaches your configured paid state. Async payment methods make webhook reliability matter more for digital goods because shoppers expect immediate download links.

What Stripe Dashboard settings integrate implicitly?

Payment methods, Checkout appearance at Stripe side, radar rules, and capture settings live in Stripe. The plugin does not mirror every Dashboard toggle in Joomla by design, which keeps Joomla admin smaller and pushes method availability to where Stripe already manages compliance.

What legacy integrations are explicitly unsupported?

Legacy J2Store com_j2store, J2StorePaymentPlugin entry style, and plg_j2store_payment_stripe_rca package naming are out of scope for version 2.0.0. Migrate to J2Commerce v6 before installing this plugin.