Closed joshr4 closed 2 months ago
For zaps in the mobile app today, we are generating an invoice, then paying it somehow, and the accounting API publishes the zap receipt upon payment. Should we generate an invoice for wavlake wallet zaps? or call on the /send
auth'd accounting API to do a wavlake wallet zap, and skip generating an invoice?
We should use the NWC payment flow for the mobile wallet, basically creating a new NWC connect string for the user when they link their Wavlake wallet.
I think we'll need to modify the accounting
/send
route to accept an optional zap request url param from the mobile app.When included, the accounting API should process the payment (will always be an internal wavlake payment - no support for keysends from the mobile app) and then publish the zap receipt. The mobile app will then listen for the zap receipt. cc @blastshielddown