MemberConsole
Resources

Start in the right place and get to production faster.

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.

Merchants & developers

Everything you need from first request to steady-state operations.

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.

Production path

A simple path from storefront to live traffic.

Each stage removes ambiguity before customers depend on the integration, from merchant scope and credentials to event delivery and recovery.

01

Scope

Share your storefront, products, expected order volume, countries, and the systems that need to connect.

02

Provision

Receive the merchant boundary and credential setup appropriate for your server-side integration.

03

Integrate

Create checkout sessions, read canonical records, and verify signed merchant events.

04

Validate

Test failure paths, retries, refunds, fulfillment changes, and recovery as carefully as successful checkout.

05

Launch

Move traffic onto the verified production configuration and keep downstream consumers retry-safe.

Ready to connect your business?

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.

Start merchant onboarding
Reference

Clear boundaries make the whole experience easier to operate.

Use 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.