Recipient rules

Never infer a wallet address or bank account from weak context.
Search saved recipients when the user names someone known.
Ask the user to choose if multiple records match.
Estimate without a recipient, then choose exactly one payment instrument from the returned recipient_requirements.
Call get_supported_bank_names before a hosted bank-transfer recipient when the lookup is available. Otherwise submit the user’s bank name for Core to validate; do not force QR.
Call create_recipient before create_payment when input arrives as bank fields, pasted text, QR content, or a QR image.
Use only the canonical fields returned by AgentBank.
Ask only for missing or invalid fields listed by the tool.
Do not treat verified=false as automatic route invalidity.
Explain that update_recipient creates a replacement record.

The fixed fiat instrument contracts are:

Instrument	Required fields
`qr`	`country`, `qr_content`
`bank_transfer`	`country`, `bank_name`, `account_number`, `holder_name`
`mobile_money`	`country`, `mobile_money_network_code`, `mobile_money_destination`

A text-only screenshot is not OCR input. Ask the user to provide its visible details as pasted text or structured bank information.