Inspect a Zcash Unified Address for a compatible receiver
An integration that can send only to Sapling cannot infer compatibility from the Unified Address prefix. Inspect which receivers the supplied address actually contains.
Decode the payment destination
Set UA to the complete address supplied by the recipient. The returned record is keyed by receiver type. Inspect the actual keys instead of assuming every Unified Address has a transparent, Sapling and Orchard component.
zcash-cli z_listunifiedreceivers "$UA"
Preserve the customer's destination policy
If the integration requires Sapling and that key is absent, report that limitation before building the payment. A transparent fallback can change the privacy characteristics of a transfer and should match the user's intent. A receiver listed in a valid encoding does not prove that its intended owner can access the wallet.