Chore: update docs links (#982)

ElliotFriend · web-flow · commit ef848b027d9c · 2025-12-09T09:13:40.000-08:00
### What

Change Links to the developer documentation. Also went through other
links to the docs site, and updated old links to new locations, where
necessary.

### Why

I moved some of the platform docs around (with redirects), and wanted to
update the source links, as well.
diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 [![Swagger Documentation](https://img.shields.io/badge/docs-swagger-blue?logo=swagger)](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/stellar/stellar-docs/refs/heads/main/openapi/stellar-disbursement-platform/bundled.yaml)
 [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/stellar/stellar-disbursement-platform-backend)
-[![Stellar Docs](https://img.shields.io/badge/docs-stellar.org-blue?logo=stellar)](https://developers.stellar.org/platforms/stellar-disbursement-platform)
+[![Stellar Docs](https://img.shields.io/badge/docs-stellar.org-blue?logo=stellar)](https://developers.stellar.org/docs/platforms/stellar-disbursement-platform)
 [![CI](https://img.shields.io/github/check-runs/stellar/stellar-disbursement-platform-backend/develop?logo=github&label=CI)](https://github.com/stellar/stellar-disbursement-platform-backend/actions/workflows/docker_image_public_release.yml)
 [![Go Report Card](https://goreportcard.com/badge/github.com/stellar/stellar-disbursement-platform-backend)](https://goreportcard.com/report/github.com/stellar/stellar-disbursement-platform-backend)
 [![GitHub](https://img.shields.io/github/license/stellar/stellar-disbursement-platform-backend)](https://github.com/stellar/stellar-disbursement-platform-backend/blob/main/LICENSE)
@@ -25,8 +25,8 @@
   - [State Transitions](#state-transitions)
 
 > [!NOTE]
-> If you are using version 1.x.x, we highly recommend upgrading to version 2.x.x to benefit from the latest features, routine fixes, and security patches. 
-> For detailed instructions on how to upgrade, please refer to [the upgrade guide](https://developers.stellar.org/network/stellar-disbursement-platform/admin-guide/single-tenant-to-multi-tenant-migration).
+> If you are using version 1.x.x, we highly recommend upgrading to version 2.x.x to benefit from the latest features, routine fixes, and security patches.
+> For detailed instructions on how to upgrade, please refer to [the upgrade guide](https://developers.stellar.org/docs/platforms/stellar-disbursement-platform/admin-guide/single-tenant-to-multi-tenant-migration).
 
 ## Introduction
 
@@ -47,7 +47,7 @@ stellar-disbursement-platform --help
 
 ## Quick Start
 
-### Docker Compose 
+### Docker Compose
 
 To quickly test the SDP using preconfigured values, use the startup wizard.
 
@@ -57,7 +57,7 @@ make setup
 
 For more information about launching and configuring the SDP, see the [Quick Start Guide](./dev/README.md).
 
-### Helm 
+### Helm
 
 To deploy the SDP using Helm, see the [Helm Chart](./helmchart/sdp/README.md).
 
@@ -178,7 +178,7 @@ The SEP10/SEP24 implementation can be configured using the following environment
 SEP10_SIGNING_PUBLIC_KEY=G...  # Public key for SEP10 signing
 SEP10_SIGNING_PRIVATE_KEY=S... # Private key for SEP10 signing
 
-# SEP24 Configuration  
+# SEP24 Configuration
 SEP24_JWT_SECRET=jwt_secret_... # JWT secret for SEP24 tokens
 ```
 
@@ -190,7 +190,7 @@ The following environment variables are required for SEP10/SEP24 functionality:
 
 **Required Variables:**
 - `SEP10_SIGNING_PUBLIC_KEY` - Public key for SEP10 challenge signing
-- `SEP10_SIGNING_PRIVATE_KEY` - Private key for SEP10 challenge signing  
+- `SEP10_SIGNING_PRIVATE_KEY` - Private key for SEP10 challenge signing
 - `SEP24_JWT_SECRET` - JWT secret for SEP24 token signing
 
 **Optional Variables:**
@@ -207,9 +207,9 @@ The SDP Core service include several components started using a single command.
 stellar-disbursement-platform serve --help
 ```
 
-#### Admin API 
+#### Admin API
 
-The Admin API is the component responsible for managing tenants of the SDP. It runs by default on port 8003 and is used to provision new tenants and manage existing tenants. 
+The Admin API is the component responsible for managing tenants of the SDP. It runs by default on port 8003 and is used to provision new tenants and manage existing tenants.
 
 #### Dashboard API
 
@@ -273,7 +273,7 @@ TWILIO_WHATSAPP_RECEIVER_OTP_TEMPLATE_SID=HXxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 - WhatsApp requires pre-approved message templates for all business-initiated conversations
 - Template variables are automatically populated by the SDP based on the message type
 - All templates must be approved by WhatsApp before they can be used in production
-- For detailed setup instructions, refer to the [Twilio WhatsApp API documentation](https://www.twilio.com/docs/whatsapp/api) 
+- For detailed setup instructions, refer to the [Twilio WhatsApp API documentation](https://www.twilio.com/docs/whatsapp/api)
 
 #### Wallet Registration UI
 
@@ -308,7 +308,7 @@ In future iterations of the project, the Transaction Submission Service will pro
 
 To manage the migrations of the database, use the `db` subcommand.
 
-#### 
+####
 
 ```sh
 stellar-disbursement-platform db --help
@@ -322,7 +322,7 @@ stellar-disbursement-platform db --help
 stellar-disbursement-platform db admin migrate up
 ```
 
-The tables below are used to manage tenants and their configurations. 
+The tables below are used to manage tenants and their configurations.
 
 ![admin schema](./docs/images/admin_db_schema.png)
 
@@ -371,8 +371,8 @@ The SDP uses Background jobs to handle asynchronous tasks.
 
 **1. Jobs**
 
-> [!NOTE]  
-> Certain jobs are not listed here because they cannot be configured and are necessary to the functioning of the SDP. 
+> [!NOTE]
+> Certain jobs are not listed here because they cannot be configured and are necessary to the functioning of the SDP.
 
 * `send_receiver_wallets_invitation_job`: This job is used to send disbursement invites to recipients. Its interval is configured through the `SCHEDULER_RECEIVER_INVITATION_JOB_SECONDS` environment variable.
 * `payment_to_submitter_job`: This job is used to submit payments from Core to the TSS. Its interval is configured through the `SCHEDULER_PAYMENT_JOB_SECONDS` environment variable.
diff --git a/cloudformation/eks/README.md b/cloudformation/eks/README.md
@@ -41,7 +41,7 @@ This guide walks through deploying the Stellar Disbursement Platform (SDP) infra
   - Creates EKS cluster and node group
   - Sets up IAM roles and security groups
   - Configures IRSA (IAM Roles for Service Accounts)
-  - Sets up permissions for pods to access secrets stored in AWS Secrets Manager 
+  - Sets up permissions for pods to access secrets stored in AWS Secrets Manager
 
 After the CloudFormation stacks are deployed, additional Kubernetes resources are installed via Helm charts to complete the setup. The SDP expects secrets to be available as Kubernetes secrets, but how those secrets are synchronized (whether through ExternalSecrets, direct creation, or other means) is left to the deployer's preference.
 
@@ -82,7 +82,7 @@ aws cloudformation create-stack \
 ```
 
 ## 3. Keys Stack Deployment
-For testnet, you can auto-generate Stellar secrets using the following command: 
+For testnet, you can auto-generate Stellar secrets using the following command:
 
 ```bash
 aws cloudformation create-stack \
@@ -107,7 +107,7 @@ aws cloudformation create-stack \
     ParameterKey=ChannelAccountEncryptionPassphrase,ParameterValue=your-channel-encryption-passphrase \
     ParameterKey=DistributionAccountEncryptionPassphrase,ParameterValue=your-distribution-encryption-passphrase
 ```
-for a description of these parameters, please see: [Configuring the SDP](https://developers.stellar.org/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp)
+for a description of these parameters, please see: [Configuring the SDP](https://developers.stellar.org/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp)
 
 ## 4. EKS Cluster Deployment
 Deploy the EKS cluster:
@@ -374,7 +374,7 @@ aws cloudformation delete-stack --stack-name ${STACK_NAME_PREFIX}-network --regi
 ## Additional Information
 
 ### Stellar Disbursement Platform Domain Structure
-The SDP platform uses two base-level domains for multi-tenant frontend and backend access. For example, lets say your hosted public domain is `api.example.org`. Then, you could configure a subdomain called `api.example.org` as the base-level domain for api access and `dashboard.example.org` as the front-end dashboard base-level domain.   If you then added a tenant (eg `ridedash`) to the SDP, the api and dashboard URLs for them would be `ridedash.api.example.org` and `ridedash.dashboard.example.org` respectively.  you can see this example in the helm-example-values file.   
+The SDP platform uses two base-level domains for multi-tenant frontend and backend access. For example, lets say your hosted public domain is `api.example.org`. Then, you could configure a subdomain called `api.example.org` as the base-level domain for api access and `dashboard.example.org` as the front-end dashboard base-level domain.   If you then added a tenant (eg `ridedash`) to the SDP, the api and dashboard URLs for them would be `ridedash.api.example.org` and `ridedash.dashboard.example.org` respectively.  you can see this example in the helm-example-values file.
 
 ## Example Helm Values configuration
 The following illustrates the example configuration for backend (api) and frontend (dashboard) base domains for the public domain `example.org`. Note, these domains must have a wild-card certificate.
@@ -392,7 +392,7 @@ dashboard:
 
 The following illustrates the kubernetes configurations that result from the above helm values.
 ```bash
-kubectl -n sdp get ingress              
+kubectl -n sdp get ingress
 NAME            CLASS            HOSTS                                           ADDRESS                                                                         PORTS     AGE
 sdp             ingress-public   api.example.org,*.api.example.org               a3ca0226bd4494ffb808a64476ddfc4f-66bf685869e3cc2e.elb.us-west-2.amazonaws.com   80, 443   9s
 sdp-ap          ingress-public   ap-api.example.org                              a3ca0226bd4494ffb808a64476ddfc4f-66bf685869e3cc2e.elb.us-west-2.amazonaws.com   80, 443   9s
@@ -514,4 +514,4 @@ kubectl describe pods -n sdp
 ```bash
 aws secretsmanager list-secrets \
   --filters Key=name-prefix,Values=/sdp/${ENVIRONMENT}
-```
+```
diff --git a/dev/README.md b/dev/README.md
@@ -11,8 +11,15 @@
     - [Update local DNS](#update-local-dns)
     - [Set up local HTTPS (optional)](#set-up-local-https-optional)
     - [Automated Stellar Account Creation and .env Configuration](#automated-stellar-account-creation-and-env-configuration)
-    - [Start/Stop Local Environment](#startstop-local-environment)
+    - [Start Local Environment](#start-local-environment)
+      - [Option 1: Using the Setup Wizard (Recommended)](#option-1-using-the-setup-wizard-recommended)
+      - [Option 2: Using Docker Compose Directly](#option-2-using-docker-compose-directly)
+      - [Option 3: Running Locally with Go (Development)](#option-3-running-locally-with-go-development)
+  - [Mainnet Deployment](#mainnet-deployment)
+    - [Mainnet Configuration](#mainnet-configuration)
+    - [Mainnet Startup](#mainnet-startup)
     - [Login to the SDP and send a Disbursement](#login-to-the-sdp-and-send-a-disbursement)
+    - [SEP10/SEP24 Endpoints](#sep10sep24-endpoints)
     - [Receive Payment to Digital Wallet (Deposit Flow)](#receive-payment-to-digital-wallet-deposit-flow)
   - [Additional Development Environment Details](#additional-development-environment-details)
     - [Stellar Accounts and .env File](#stellar-accounts-and-env-file)
@@ -25,8 +32,8 @@
       - [Start Prometheus and Grafana containers](#start-prometheus-and-grafana-containers)
       - [Load the SDP Grafana Dashboard](#load-the-sdp-grafana-dashboard)
   - [Troubleshooting](#troubleshooting)
-    - [Sample Tenant Management Postman collection](#sample-tenant-management-postman-collection)
-    - [Distribution account out of funds](#distribution-account-out-of-funds)
+      - [Sample Tenant Management Postman collection](#sample-tenant-management-postman-collection)
+      - [Distribution account out of funds](#distribution-account-out-of-funds)
 
 ## Introduction
 
@@ -151,7 +158,7 @@ go run main.go serve \
 
 You can also run the TSS by using the `tss` command instead of `serve`.
 
-```sh 
+```sh
 go run main.go tss \
   --env-file ./dev/.env.https-testnet \
   --database-url "postgres://postgres@localhost:5432/sdp_mtn?sslmode=disable"
@@ -212,10 +219,10 @@ make setup
 
 ### Login to the SDP and send a Disbursement
 
-> [!NOTE]  
+> [!NOTE]
 > In the following section, we will assume you're using the `bluecorp` tenant that was provisioned when you started the stack.
 
-The startup prints Login information for each tenant.  
+The startup prints Login information for each tenant.
 ```
 🎉🎉🎉🎉 SUCCESS! 🎉🎉🎉🎉
 Login URLs for each tenant:
@@ -275,7 +282,7 @@ The SDP now provides native SEP10 and SEP24 endpoints for wallet integration:
 - `POST /auth` - Validate challenge and receive JWT token
 
 **SEP24 Interactive Deposit Endpoints:**
-- `GET /sep24/info` - Get supported assets and capabilities  
+- `GET /sep24/info` - Get supported assets and capabilities
 - `POST /sep24/transactions/deposit/interactive` - Initiate interactive deposit
 - `GET /sep24/transactions` - Get transaction status
 
@@ -298,11 +305,11 @@ Now deposit the disbursement payment into the digital wallet using the SEP-24 de
    <img src="images/demo_wallet1.png" alt="Demo Wallet" width="40%">
 
 6. In the `Select action` dropdown, select `SEP-24 Deposit` and then click the `Start` button.
-   
+
    <img src="images/sep24_deposit1.png" alt="SEP-24 Deposit" width="40%">
 
 7.  In the new window, enter the phone number `+13163955627` from the disbursement CSV payment.
-    
+
     <img src="images/sep24_deposit2.png" alt="Enter Phone Number" width="40%">
 
 8. To verify the payment, enter the passcode and date of birth. You can use `000000` passcode or find the actual passcode in the `sdp-api` container logs.
@@ -325,7 +332,7 @@ You need to create and configure two Stellar accounts to use the SDP. You can ei
 
 **Option 1: Manually Create and Configure Accounts**
 
-1. Create and fund a Distribution account that will be used for sending funds to receivers. Follow the instructions [here](https://developers.stellar.org/docs/stellar-disbursement-platform/getting-started#create-and-fund-a-distribution-account).
+1. Create and fund a Distribution account that will be used for sending funds to receivers. Follow the instructions [here](https://developers.stellar.org/docs/platforms/stellar-disbursement-platform/getting-started#create-and-fund-a-distribution-account).
 2. Create a SEP-10 account for authentication. It can be created the same way as the distribution account but it doesn't need to be funded.
 3. Create a `.env` file in the `dev` directory by copying the [env.example](.backup/.env.example) file:
    ```sh
diff --git a/helmchart/sdp/templates/NOTES.txt b/helmchart/sdp/templates/NOTES.txt
@@ -95,7 +95,7 @@ Your release is named {{ .Release.Name }} and deployed to namespace {{ .Release.
 6. Create your first tenant:
    If you don't have a tenant yet, you'll need to create one to start using the SDP.
    Tenant provisioning is documented at:
-   https://developers.stellar.org/platforms/stellar-disbursement-platform/admin-guide/tenant-provisioning
+   https://developers.stellar.org/docs/platforms/stellar-disbursement-platform/admin-guide/tenant-provisioning
 
    To calculate the auth header for the admin API, run:
 
@@ -111,4 +111,4 @@ Your release is named {{ .Release.Name }} and deployed to namespace {{ .Release.
    # Use this value in your API requests as:
    # curl -H "Authorization: $AUTH_HEADER" ...
 
-For more information and configuration options, please refer to the README.md file.
+For more information and configuration options, please refer to the README.md file.
diff --git a/internal/transactionsubmission/README.md b/internal/transactionsubmission/README.md
diff --git a/internal/transactionsubmission/store/transactions_test.go b/internal/transactionsubmission/store/transactions_test.go
