pay now

[ichthus1604]

No description provided.

[adamPetho]

Cannot build the TX.

System.ArgumentOutOfRangeException: Cannot be less than 1 sat/vByte. (Parameter 'feeRate')
Actual value was 0 Sat/B.

Fix coming soon.

[adamPetho]

Note for the future:
WW cannot rebuild the invoice, if we close the app beforehand.

[adamPetho]

When the payment is done and confirmed, the invoice disappers from the chat after some time.

[soosr]

This is ready from a UI point of view, @adamPetho will fix the remaining business part.

As of now, this solution cannot handle if an invoice is received for the second time, will fix it in a separate PR.

[adamPetho]

I think the business part is more or less finished, too.

• If we don't have enough balance to pay for the order, we show an error dialog. (not sure what else we can do)
• If we have enough balance, the transaction is built with fee target: 2 block and broadcasted right away.

Edge case:

• If the fee is bigger than the amount we want to send an exception is thrown from TxBuilder.
  There is a safety check for this. Not sure what to do in this scenario.
  The minimum amount will be 1000$ for a concierge request, so this edge case shouldn't happen in real scenarios.

  Should we let as it is?

@soosr do you know scenarios that I missed or scenarios that the business logic can't handle right now?
Or what is the "remaining business part" I should fix in this PR?