Orders
Read canonical orders, update fulfillment, and create shipment records without losing the source of truth.
Developers
Build the customer experience. Let MemberConsole handle the commerce boundary.
Connect orders, payments, fulfillment, customer identity, signed events, and operational health through a server-side API designed to stay behind your product instead of taking it over.
Merchant integrationProduction model
Scoped API credentialYour server proves which merchant it represents
Canonical commerce stateOrders, payments, refunds, and subscriptions stay connected
Operational updatesFulfillment and shipment workflows stay in sync
Signed eventsDurable delivery for retry-safe downstream systems
Merchant api
One clean boundary for the work your systems actually need to do.
Merchant credentials carry explicit scopes and resolve merchant identity from trusted server authentication. Your frontend stays focused on the customer experience while sensitive commerce decisions stay on the backend.
Payments and refunds
Read payment and refund records and request eligible order refunds through your merchant-scoped backend.
Events and webhooks
Inspect ordered event history, replay deliveries, and keep downstream systems current with signed merchant events.
Integration health
See endpoint health, delivery alerts, pending outbox work, and operational signals from one place.
Authentication
Keep the key on your server and keep the model simple.
Your onboarding package includes the production API base URL and a merchant-scoped credential. Send it from your backend as a Bearer token so merchant scope, permissions, and operations remain easy to reason about.
Server-side onlyMerchant scopedExplicit scopesVersioned routes
Read merchant orders
GET /v1/merchant/orders?limit=25 Authorization: Bearer $MEMBERCONSOLE_SECRET_KEY Accept: application/json
Requires an active credential with the orders:read scope.
Current v1 surfaces
A focused API for real operational work.
The Merchant API centers on canonical records and downstream operations. Checkout remains server-authoritative, while fulfillment, refunds, events, and reconciliation stay connected to the same commerce model.
Orders and fulfillment
GET /ordersGET /orders/:orderPATCH /orders/:order/fulfillmentPOST /orders/:order/shipmentsMoney and subscriptions
GET /paymentsGET /refundsPOST /orders/:order/refundsGET /subscriptionsEvents and operations
GET /eventsGET /events/:eventPOST /events/:event/replayGET /webhook-endpointsPOST /webhook-endpoints/:id/testGET /integration-healthSigned webhooks
Know exactly which event you received before you act on it.
MemberConsole signs each delivery with HMAC-SHA256 over the timestamp and raw request body. Verify first, store the event ID, then hand longer work to your own queue or operational system.
MemberConsole-Event-IdMemberConsole-TimestampMemberConsole-SignatureMemberConsole-Version
Signature input
signed_payload = timestamp + "." + raw_request_body expected = HMAC_SHA256(webhook_secret, signed_payload) // Compare expected with the v1 signature value. // Store the event ID before applying side effects.
Retries are expected, so consumers should be safe when the same event arrives again.
Onboarding
A clear route from first conversation to production traffic.
Each step makes the merchant boundary, credentials, event delivery, and operational handoff explicit before customers depend on the integration.
Scope
Share the storefront, business, expected volume, countries, and systems you want to connect.
Provision
MemberConsole creates the merchant boundary, credential scopes, allowed surfaces, and webhook configuration.
Integrate
Connect your backend to the API, verify signed events, and map canonical identifiers into your systems.
Validate
Test authorization, retries, fulfillment, refunds, reconciliation, and recovery before normal production traffic.
Ready to connect a retail or software business?
Tell us what you sell, how checkout works today, and which systems need to stay in sync. We will route the right merchant onboarding path.