Payment destinations

A destination tells a wallet where and how a payment can be made. It is payment-critical data and receives stronger validation and safety handling than ordinary profile metadata.

Destination fields

{
  "chain": "base",
  "asset": "USDC",
  "address": "0xRecipient…",
  "token_contract": "0xUsdcContract…",
  "network_identifier": "eip155:8453",
  "minimum_amount": "1.00",
  "maximum_amount": "10000.00",
  "fixed_amount": "10.00",
  "expiration": "2026-12-31T00:00:00.000Z"
}

• chain, asset, and address are required.
• token_contract is required for token payments.
• network_identifier disambiguates networks, such as EIP-155 chain IDs.
• Optional memo, payment reference, amount limits, fixed amount, or expiration are payment constraints.

Safe update flow

1. Validate the address and asset combination.
2. Authorize the update as the controller.
3. Show update_pending and stop normal payment actions.
4. After activation, resolve again and display the new payable option.

The resolver never signs or sends funds. Wallets must show the final destination and network immediately before the user confirms payment.