The way to fix this is two Kind: 0 metadata fields: - One for primary Bolt12 wallet addresss. - One for secondary Bolt 12 wallet address. The primary can be fully sovereign self custody destination such as Phoenix wallet, and the secondary is a fallback custodial wallet for async such as CoinOS. Destination wallets can expose their received zaps via API; I'm pretty sure the CoinOS API can already do this. Bolt 12 is instant and reliable. It's supported by a bunch of KYC and non KYC wallets. Strike springs to mind. It's not like this is a new idea.

UX Design | BOLT 12

UX ideas for integrating BOLT 12 into your bitcoin lightning application.