From e2971923e5048a9c61a2e41b8916df30e36a1405 Mon Sep 17 00:00:00 2001 From: Ramkumar SG Date: Thu, 28 Jan 2021 17:23:53 -0800 Subject: [PATCH 1/2] Typo on payment failure Typo: When a receiving address is funded, and the payment meets any limitation, the payment fails. --- content/concepts/payment-types/direct-xrp-payments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/payment-types/direct-xrp-payments.md b/content/concepts/payment-types/direct-xrp-payments.md index 2beb7c6ce6..d767f6f2ba 100644 --- a/content/concepts/payment-types/direct-xrp-payments.md +++ b/content/concepts/payment-types/direct-xrp-payments.md @@ -52,7 +52,7 @@ From a relatively high level, the XRP Ledger's transaction processing engine app 2. It checks whether the receiving address is a funded account. - - If the receiving address is funded, it checks whether the receiving address has any limitations on receiving payments, such as [Deposit Authorization](depositauth.html) or [`RequireDest`](source-and-destination-tags.html#requiring-tags). If the payment does not meet any such limitations, the payment fails. + - If the receiving address is funded, it checks whether the receiving address has any limitations on receiving payments, such as [Deposit Authorization](depositauth.html) or [`RequireDest`](source-and-destination-tags.html#requiring-tags). If the payment meets any such limitations, the payment fails. - If the receiving address is not funded, it checks whether the payment would deliver enough XRP to meet the minimum [account reserve](reserves.html). If not, the payment fails. 3. It debits the sending account by an amount of XRP specified by the `Amount` field plus the XRP to be destroyed for the [transaction cost](transaction-cost.html) and credits the receiving account for the same amount. From 45ac16a68b41d3edb133ab6341fc16d37e3803a6 Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Mon, 8 Feb 2021 14:23:05 -0800 Subject: [PATCH 2/2] Clarify additional requirements for receiving payments --- content/concepts/payment-types/direct-xrp-payments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/payment-types/direct-xrp-payments.md b/content/concepts/payment-types/direct-xrp-payments.md index d767f6f2ba..1c691a6982 100644 --- a/content/concepts/payment-types/direct-xrp-payments.md +++ b/content/concepts/payment-types/direct-xrp-payments.md @@ -52,7 +52,7 @@ From a relatively high level, the XRP Ledger's transaction processing engine app 2. It checks whether the receiving address is a funded account. - - If the receiving address is funded, it checks whether the receiving address has any limitations on receiving payments, such as [Deposit Authorization](depositauth.html) or [`RequireDest`](source-and-destination-tags.html#requiring-tags). If the payment meets any such limitations, the payment fails. + - If the receiving address is funded, the engine checks any additional requirements for receiving payments, such as [Deposit Authorization](depositauth.html) or [`RequireDest`](source-and-destination-tags.html#requiring-tags). If the payment does not satisfy any of these additional requirements, the payment fails. - If the receiving address is not funded, it checks whether the payment would deliver enough XRP to meet the minimum [account reserve](reserves.html). If not, the payment fails. 3. It debits the sending account by an amount of XRP specified by the `Amount` field plus the XRP to be destroyed for the [transaction cost](transaction-cost.html) and credits the receiving account for the same amount.