# Go live (/guides/go-live)

Prepare your Live configuration after the [CI/CD](/guides/operate/ci-cd/) checks and paid test pass. Live payments are not available yet. Business verification approval lets you configure resources and pricing in Live; it does not enable payment collection or payouts.

Test and live Resources are separate. recuut's **Promote** action copies a published revision to another environment and preserves its Resource key and public `rvk_…` revision key. The target has its own Resource, pricing, and transactions. Your merchant API key selects the environment in which that revision key is resolved.

The paid test and promotion are manual: the payer setup requires email authentication, a one-time code, and test-wallet funding, and promotion is performed in the recuut app.

## 1. Prove the paid test path

Deploy the checked artifact to the test environment with the test key and no live key, then [test a paid request](/guides/test-paid-request/). Direct HTTP and raw-revision applications also need `RECUUT_REVISION_KEY`.

The test passes when the unpaid request returns HTTP `402` with `PAYMENT-REQUIRED` and no protected result, the paid retry returns the protected response with `PAYMENT-RESPONSE`, and the saved transaction has `status: succeeded` and a non-null `receipt`. Approving a wallet prompt alone is not proof.

Do not load a live key into the test process.

## 2. Request business verification

An organization admin opens **Go live** in the recuut app and chooses **Request review** under **Business verification**. A recuut team member reviews the request manually. Keep using Test while the request is pending.

If the request is rejected, read **Reason for rejection**, address the feedback, then choose **Request another review**. Approval creates your Live environment. It does not require a wallet-provider signup.

## 3. Prepare the Live revision

From the published test revision, choose **Promote**, select the live environment, and review the contract plus **Pricing & access** result. Promotion preserves the public revision key, but creates an independent live Resource and revision. Confirm the live availability and Price before continuing.

After promotion, load only the live key and create a fresh live [contract snapshot](/guides/operate/ci-cd/#check-the-published-contract). Compare it with the reviewed test snapshot: the public revision key, resource key, and reporting rules must match; the environment-specific Resource ID will differ. If the live check cannot find the revision, verify the promotion result and live key.

Keep the same application artifact that passed the paid test. Review the Live contract and pricing now, but keep your running payment integration on Test until Live payments become available. Do not send real payer assets to verify this configuration.