Go live

The implemented go-live readiness service exposes a deterministic readiness result; it does not replace owner approval or invent an additional approval gate.

Readiness endpoint

GET /api/v1/merchants/{merchant}/go-live/readiness requires merchant:readiness and returns status READY or NOT_READY, a boolean ready, merchant_public_id, policy_version phase9-go-live-v1, and checks.

Implemented checks

The readiness result checks merchant_profile_ready, verified_settlement_destination_required, active_live_write_api_key_required, active_live_webhook_required, successful_sandbox_payment_and_webhook_required, and go_live_security_acknowledgement_required.

Integration sequence

Complete the merchant profile; configure and verify the merchant settlement destination; create an active Live write key; create an active Live webhook endpoint; complete a successful Test sandbox payment and delivered Test webhook; acknowledge the go-live security policy; then inspect readiness and use Live credentials to create a Live Payment Intent.

Final boundary

A READY result does not cause a payment, sign a wallet transaction, or promote Test evidence. Create a Live Payment Intent only with the Live credential and Live merchant configuration.