For my client, I have set up a custom BTC payment solution using BTCPay Server. The wallets I have configured in BTCPay Server produce only bech32 (
bc1xxx) addresses for payments (cheapest transaction fees).
My client (who ordered the solution) has asked me how many of his customers would be unable to send a payment to a bech32 address?
His concern is that his clients will be unable to pay their invoices in BTC because their wallets will be unable to send payments to the bech32 addresses.
As I can see it, I can go back to my client with one of the following two answers:
- Nearly all (
??%) of wallets can send to bech32 including all\most commercial wallet providers so you don't need to worry, or
- This is a problem and instead of bech32 addresses I need to set up a payment wallet that supports legacy addresses (either
Could someone please tell me whether I can reassure him that the solution is fine as is, or whether I need to add legacy address support into it?