Scope
Share your storefront, products, expected order volume, countries, and the systems that need to connect.
Whether you are integrating a merchant backend or trying to find a connected purchase, this hub gets you to the guidance that matters without making you decode the platform first.
The guides follow the same model as MemberConsole itself: merchant identity is authenticated on the server, checkout state is canonical, and downstream systems consume scoped APIs and signed events.
See how merchant scope, canonical commerce state, APIs, and signed event delivery fit together before you write the first integration call.
Open resourceUnderstand how server-side credentials are provisioned, scoped to one merchant, protected, and rotated.
Open resourceCreate checkout sessions from your backend while MemberConsole resolves merchant ownership and freezes the commercial snapshot.
Open resourceVerify signed events, acknowledge them quickly, and keep downstream processing safe when a delivery is retried.
Open resourceRead canonical orders and keep fulfillment or CRM systems current without turning a copied record into payment authority.
Open resourceTest success, failure, retries, refunds, fulfillment changes, and recovery before real customers depend on the integration.
Open resourceKeep operational changes attached to canonical order identifiers so customer and merchant views continue to agree.
Open resourceReview tenant isolation, server-authoritative pricing, secret handling, row-level controls, and event integrity in one place.
Open resourceEach stage removes ambiguity before customers depend on the integration, from merchant scope and credentials to event delivery and recovery.
Share your storefront, products, expected order volume, countries, and the systems that need to connect.
Receive the merchant boundary and credential setup appropriate for your server-side integration.
Create checkout sessions, read canonical records, and verify signed merchant events.
Test failure paths, retries, refunds, fulfillment changes, and recovery as carefully as successful checkout.
Move traffic onto the verified production configuration and keep downstream consumers retry-safe.
Tell us what you sell, how checkout works today, and which systems need to stay in sync. We will use that to route the right merchant onboarding path.
Customer guidance keeps MemberConsole access questions clear while product, delivery, warranty, return, and merchant-policy questions stay with the responsible merchant.
Start a secure verification flow when you need a purchase record and are not already signed in.
Open resourceSign in, recover access, and understand how a verified customer identity connects eligible purchases.
Open resourceUnderstand the safe billing summaries, receipt records, and payment states available through MemberConsole.
Open resourceGet help with sign-in, order access, receipts, payment records, subscriptions, security, or platform issues.
Open resourceUse MemberConsole support for account and platform questions. Use the responsible merchant for product, delivery, warranty, service, return, or merchant-specific refund questions. Developers should keep secret credentials on the server and reconcile operational systems from canonical commerce state.