403
merchants.not_activemerchantsThis merchant's live keys do not work yet
Returned by the implementation; no specification rule declares it yet.
The partner surface's live gate. A live key is refused with 403 unless the merchant is active (or suspended — a suspended merchant can still read its own history). A test key always works, in every status, from the merchant's first minute and before any KYC at all.
Why the API refuses
this merchant is not active, so its live API keys do not work yet
What to do
- Keep building against test mode. This is not something the integration can route around, and nothing about the integration changes when it lifts.
GET /merchants/mereports where onboarding has got to:draftandsubmittedmean documents are outstanding,in_reviewmeans we are looking at them,sandboxmeans the review passed and we have not yet cleared the account for live,approvedmeans live mode still has to be requested — seemerchants.not_ready_for_livefor the three conditions — andsuspendedcarries asuspension_reason.- If you are seeing this in a deployment you expected to be live, check the key prefix before anything else: this is the error a
pg_live_key gets, and finding a live key in a staging deployment is worth knowing about for its own sake.