We implement a `getBalance` function for each send side wallet that supports balance fetching. Ideally we'd be able to use the `ndebit` string to get a clink balance as an independent request. If it's a field on the debit response, it probably wouldn't make much sense for us because we'd have to cache it clientside and it'd be stale until money was sent again.

To each wallet we are also adding (when supported):

1. a `checkInvoice` function for receive side to record if an invoice we generated was paid
2. a `checkPayment` function for send side to gather the preimage/status for an invoice we attempted to pay

So as-is:

- lack of `getBalance` reports balance as unavailable
- lack of `checkInvoice` warns that we don't know if the invoice was paid
- lack of `checkPayment`, assuming we missed the preimage of the send response and did not get a definite `fail` response, warns that payment status is unknown to us and could be complete/inflight

So far works pretty darn well,

![](https://m.stacker.news/146090)

Removed my primal wallet and using Shocknet🤘

@Car brought to my attention the new wallet ui... sounds like if we add remaining budget/balance to clink debit responses you could use it as a web wallet from SN? Or would you need it as a info query separate from an operation? 

Would be a good spec extension I was marinading on anyway, just don't want to complicate handling for sdk users, let me know what you're thinking is on it...

justin_shocknet

External wallet plumbing where the goal is:

What are you working on this week?

External wallet plumbing where the goal is:

1. make our best effort to surface invoice receive status
2. enable sending