Sounds good, we can just add a shape then for available_sats without an actual debit that you can use to populate UI when you fire getBalance

justin_shocknet

 as an independent periodic poll to the wallet/node provider/endpoint. Supporting other patterns is not something we'll likely pursue anytime soon. Regardless, at worst, a wallet/provider without a 

. Not ideal, but also not that bad either.

We don't gate payment attempts by balance showing a sufficient amount. We attempt payment then process responses 

 carefully and conservatively (ie to not invite double pays). Balances are for human eyeballs only so that customers can determine in advance if a payment will succeed or not.

What are you working on this week?

We implement `getBalance` as an independent periodic poll to the wallet/node provider/endpoint. Supporting other patterns is not something we'll likely pursue anytime soon. Regardless, at worst, a wallet/provider without a `getBalance`-like RPC to poll will just show `balance unavailable`. Not ideal, but also not that bad either.

> * If a user has it set to manual approval, `available_sats` would show 0, and SN would have to try anyway expecting the user approves the request manually.

We don't gate payment attempts by balance showing a sufficient amount. We attempt payment then process responses *very* carefully and conservatively (ie to not invite double pays). Balances are for human eyeballs only so that customers can determine in advance if a payment will succeed or not.