From 9c7b641a3e3f93e2d332a24adfcc49eda0235af2 Mon Sep 17 00:00:00 2001
From: 413x5 <159362274+413x5@users.noreply.github.com>
Date: Sun, 8 Dec 2024 17:03:56 +0100
Subject: [PATCH] Update sc-payments.md

Broken link
---
 docs/developers/developer-reference/sc-payments.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/developers/developer-reference/sc-payments.md b/docs/developers/developer-reference/sc-payments.md
index 879c605e9..23f73ecb4 100644
--- a/docs/developers/developer-reference/sc-payments.md
+++ b/docs/developers/developer-reference/sc-payments.md
@@ -87,4 +87,4 @@ Additional restrictions on the incoming tokens can be imposed in the body of the
 
 ## Sending payments
 
-We have seen how contracts can accommodate receiving tokens. Sending them is, in principle, even more straightforward, as it only involves specializing the `Payment` generic of the transaction using specific methods, or better said, attaching a payload to a regular transaction. Read more about payments [here](../../developers/transactions/tx-payment).
\ No newline at end of file
+We have seen how contracts can accommodate receiving tokens. Sending them is, in principle, even more straightforward, as it only involves specializing the `Payment` generic of the transaction using specific methods, or better said, attaching a payload to a regular transaction. Read more about payments [here](../transactions/tx-payment.md).