From: Matt Corallo Date: Mon, 5 Jun 2023 18:21:19 +0000 (+0000) Subject: Remove spurious docs which imply you cannot retry a failed payment X-Git-Tag: v0.0.116-alpha1~20^2~1 X-Git-Url: http://git.bitcoin.ninja/?a=commitdiff_plain;h=632c0d22b5bc6c430cbf34cb283d94d2ffdde9d2;p=rust-lightning Remove spurious docs which imply you cannot retry a failed payment If a payment (fully) fails, users are free to retry it, its only once a payment succeeds that a user must never retry it. --- diff --git a/lightning-invoice/src/payment.rs b/lightning-invoice/src/payment.rs index 7abfbe4bf..14702986a 100644 --- a/lightning-invoice/src/payment.rs +++ b/lightning-invoice/src/payment.rs @@ -28,8 +28,8 @@ use core::time::Duration; /// Pays the given [`Invoice`], retrying if needed based on [`Retry`]. /// /// [`Invoice::payment_hash`] is used as the [`PaymentId`], which ensures idempotency as long -/// as the payment is still pending. Once the payment completes or fails, you must ensure that -/// a second payment with the same [`PaymentHash`] is never sent. +/// as the payment is still pending. If the payment succeeds, you must ensure that a second payment +/// with the same [`PaymentHash`] is never sent. /// /// If you wish to use a different payment idempotency token, see [`pay_invoice_with_id`]. pub fn pay_invoice( @@ -82,8 +82,8 @@ where /// [`Retry`]. /// /// [`Invoice::payment_hash`] is used as the [`PaymentId`], which ensures idempotency as long -/// as the payment is still pending. Once the payment completes or fails, you must ensure that -/// a second payment with the same [`PaymentHash`] is never sent. +/// as the payment is still pending. If the payment succeeds, you must ensure that a second payment +/// with the same [`PaymentHash`] is never sent. /// /// If you wish to use a different payment idempotency token, see /// [`pay_zero_value_invoice_with_id`].