Mints a FRESH invoice every time. There is no get-or-create and there cannot be one: `/addresses` is idempotent on a reference you supply, but an invoice is amount-fixed and single-use, so the same trick does not apply. **A request that times out and is retried mints a SECOND invoice.** That is cheap rather than dangerous - an unpaid invoice expires on its own, and only one can ever be paid, because the credit is keyed on the payment hash. The cost is showing the wrong one to a payer, so prefer one mint per payment attempt over blind retries.

Pay a beneficiary in local currency

Prices and sends in ONE call. There is deliberately no quote endpoint: a quote locks a rate for five minutes, which is a courtesy to a person and a free option to a machine - poll quotes, execute the ones the market moved in your favour, let the rest lapse at no cost. Use `min_settlement_amount_minor` to bound what you accept instead. It is checked BEFORE anything is debited, so a refusal costs you nothing. `amount_minor` is what leaves your WALLET, in the asset's minor units. What the beneficiary receives depends on a rate that does not exist until we ask for it, which is why you state the side you are spending.