destination_ownership: The proof is not signed by the destination address
A payee registered a stablecoin payout destination (POST /payee/v1/destinations with rail: "usdc"), and the proof does not verify as a signature by that destination address over the message dynamo-payout-destination-v2, the deployment's audience (GET /payee/v1/audience), the payee's serviceNode and the address (each on its own line). A proof over the earlier text without the audience, or naming another deployment or tenant, is refused the same way. Nothing was registered (fail closed).
What to do
- Sign the destination message with the key of the destination address itself, not the serviceNode key (unless the two are the same address).
- Put this deployment's audience on the second line:
GET /payee/v1/audienceanswers it. - Send the 65-byte signature as
proof, together with the sameaddress.
On the wire
HTTP 422.
{
"error": "invalid_proof",
"reason": "destination_ownership",
"detail": "the proof is not a signature by the destination address (fail closed)"
}
See getting paid as a payee and all error codes.