ESCROW_RECEIVER_TRUSTLINE_MISSING

A role that receives escrow funds has no trustline for the escrow token.

422 Validation Error · request validation · v2 deploy, update and multi-release manage-milestones

Example

{
  "type": "https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/escrow-receiver-trustline-missing",
  "title": "Validation Error",
  "status": 422,
  "code": "ESCROW_RECEIVER_TRUSTLINE_MISSING",
  "detail": "Every role that can receive escrow funds must hold a trustline for the escrow token — roles.receiver (G…): no trustline for the escrow token.",
  "instance": "/escrow/single-release/v2/deploy",
  "traceId": "…",
  "extensions": {
    "trustline": "C…",
    "missing": [
      { "address": "G…", "roles": ["roles.receiver"], "reason": "trustline-missing" }
    ]
  }
}

When it happens

Before building the transaction, the API checks that every address that can receive funds from the escrow can hold the escrow token. Roles that never receive funds (approvers, service providers, release signers, dispute resolvers, admin, observers) are not checked.

Endpoint	Addresses checked
Single-release deploy, update	roles.receiver, plus roles.platform when platformFee > 0
Multi-release deploy	every milestones[].receiver, plus roles.platform when platformFee > 0
Multi-release update	roles.platform when platformFee > 0
Multi-release manage-milestones	every newMilestones[].receiver

extensions.missing lists each failing address, the roles it plays, and a reason:

• trustline-missing — the account exists but has no trustline for the escrow token.

• account-missing — the account does not exist on this network.

How to fix it

For account-missing, fund the account with XLM first. Then add a trustline to the escrow asset (for example USDC) on the same network, and retry.