Product, delivery, warranty, return, or merchant refund question?
Those questions stay with the business you purchased from. Open your connected order to confirm the responsible merchant and the latest available purchase details.
Practical guidance for customer accounts, orders, payments, refunds, subscriptions, merchant integrations, privacy, and security.
Verify ownership and securely open a purchase without already being signed in.
Open guideRecover sign-in access and understand secure email authentication.
Open guideUnderstand merchant decisions, platform records, partial refunds, and processing state.
Open guideStart with API credentials, checkout, signed webhooks, testing, and canonical orders.
Open guideUse your order number and purchase email to start a privacy-preserving order access flow.
Learn what paid, processing, fulfilled, shipped, delivered, cancelled, and refunded states mean in MemberConsole.
See where delivery updates come from and which questions should go directly to the merchant.
Know when an address can be updated and why a completed order may need merchant assistance.
Use the merchant identity on your connected order for product, warranty, delivery, and merchant-policy questions.
Use password or secure email access methods and recover gracefully when a sign-in link does not arrive.
Understand how verified customer identity can bring purchases together without weakening merchant isolation.
Keep account access secure and know what to do if you think a session or email link was exposed.
Understand the billing information MemberConsole can show and where merchant-specific charge questions belong.
Read refund records correctly and know what happens after the merchant or payment system completes a refund.
Separate checkout errors from authoritative payment state and decide what to do next.
Review recurring purchase state while keeping merchant plan and cancellation rules clear.
How retailers and software merchants receive scoped credentials and keep them server-side.
Create server-authoritative checkout sessions and send customers into the correct merchant purchase flow.
Validate event authenticity, acknowledge deliveries quickly, and make every consumer safe to retry.
Use canonical MemberConsole records instead of making a copied merchant database the authority for commerce state.
Test the order lifecycle beyond the happy path before sending real customer traffic.
Update operational state without losing the relationship between merchant actions and the authoritative commerce record.
How one customer identity can connect purchases while each merchant remains inside its own authorization boundary.
Understand why commerce and security records may be retained and where privacy requests should be sent.
Send a useful security report without exposing payment credentials or unrelated customer information.
A reliable merchant integration starts with scope, server-authoritative checkout, signed events, and a clear security boundary.
Keep credentials server-side and inside the merchant scope provisioned for the integration.
Read guideCreate sessions from trusted backend context and let server logic resolve the commercial snapshot.
Read guideVerify signatures, expect retries, and make event consumers idempotent.
Read guideUnderstand tenant isolation, customer identity boundaries, and server-authoritative controls.
Read guideThe Resources hub combines merchant onboarding, integration guidance, testing, security, and customer support references in one place.
Those questions stay with the business you purchased from. Open your connected order to confirm the responsible merchant and the latest available purchase details.
Use MemberConsole support when the problem is with the platform itself rather than the product or service sold by a participating merchant.