test_fixture_money_mode: Test service nodes run on Control Mode only
The reserved test service nodes (the addresses listed by GET /owner/v1/test-fixtures, and every address in their reserved range) stand in for payees during testing. They run only on Control Mode budgets (funding: "none"), where no money moves. Three places answer this code:
- Opening a stream (
POST /owner/v1/budgets/{id}/streams) to a reserved test address on a stablecoin or credit card budget. The open is refused before anything is allocated;paramisserviceNode. - Running a fixture delivery (
POST /owner/v1/test-fixtures/streams/{id}/run) on a stream of a money-mode budget. Nothing is metered. - Creating a top-up session (
POST /owner/v1/topups) whosepayeeServiceNodeis a reserved test address. Nothing is created;paramispayeeServiceNode. A deployment without the credit card rail answerstopup_card_mode_absentfirst.
The multi-tenant hosted tier answers the same way: the front door passes the request to the account's core.
What to do
- Open the budget with
funding: "none"to use the test service nodes. - Use a real payee service node on stablecoin and credit card budgets.
- See test agents and payees.
On the wire
HTTP 409, error type state_error.
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "test_fixture_money_mode",
"message": "test service nodes run only on Control Mode budgets (funding: none)",
"param": "serviceNode",
"doc_url": "…/developers/testing.md#test-fixture-money-mode",
"fix": "test service nodes run only on Control Mode budgets (funding: none)"
}
}
On the top-up route doc_url points at the top-up guide. See all error codes.