MB Wallet Developers

Environments

Keep test and live integrations strictly separated.

The Checkout API uses a different base URL for each deployment environment. Keys, data, and webhook endpoints stay within their assigned environment and mode.

API base URLs

Use the staging API while you build and test your integration.

EnvironmentPurposeBase URL
StagingPrivate integration testinghttps://stg-checkout-api.mbwallet.dev
ProductionLive merchant trafficPublished at launch

The base URL is not a documentation page. A request to / may return 404; call a documented API path instead.

For example, create a staging checkout session at:

https://stg-checkout-api.mbwallet.dev/v1/checkout_sessions

Staging data and keys are not valid in production. Never point automated tests at production.

Webhook destinations

Your webhook URL belongs to your service, not MB Wallet. Register a separate public HTTPS callback URL for each environment and mode.

EnvironmentExample webhook destination
Staginghttps://staging.merchant.example/webhooks/mbwallet
Productionhttps://merchant.example/webhooks/mbwallet

MB Wallet sends events to the registered destination. It does not receive partner webhooks at the Checkout API base URL.

On this page