docs: fixes 3331 (#3350)

Author: melissahenderson

packages/documentation/astro.config.mjs

@@ -98,6 +98,10 @@ export default defineConfig({
                   label: 'Open Payments',
                   link: '/overview/concepts/open-payments'
                 },
+                {
+                  label: 'Payment pointers and wallet addresses',
+                  link: '/overview/concepts/payment-pointers'
+                },
                 {
                   label: 'Telemetry',
                   link: '/overview/concepts/telemetry'

packages/documentation/src/components/PageSidebar.astro

@@ -4,6 +4,7 @@ import Default from '@astrojs/starlight/components/PageSidebar.astro';
 
 const removeOverview = [
  'resources/glossary',
+ 'overview/concepts/payment-pointers',
 ]
 const noOverview = removeOverview.includes(Astro.props.slug);
 const toc = noOverview && Astro.props.toc !== undefined

packages/documentation/src/content/docs/overview/concepts/interledger.mdx

@@ -42,11 +42,13 @@ In the image below, the sender node (A) and the receiver node (C) share a common
 
 In reality, there can be multiple connectors between a sender node and a receiver node. As more nodes that support different assets peer with one another, the easier it becomes for payments to traverse the Interledger network.
 
-## Payment pointers
+## Payment pointer
 
-Rafiki assigns each of your customers’ accounts with a payment pointer. Payment pointers are a type of wallet address for accounts within the Interledger network. They’re similar to email addresses in that they’re used to determine which account to send a payment from and which account to deliver the payment to.
+A payment pointer is a type of wallet address that serves as an SPSP endpoint to facilitate sending and receiving ILP packets. Rafiki will assign each of your customers' accounts with a payment pointer.
 
-Every payment pointer serves as a Simple Payment Setup Protocol (SPSP) endpoint and must resolve to an HTTPS URL. Payment pointers can be written out using the `$` shorthand (for example, `$wallet.example.com/alice`) or as a URL (for example, `https://wallet.example.com/alice`).
+Payment pointers must resolve to an HTTPS URL and can be written out using the `$` shorthand (for example, `$wallet.example.com/alice`) or as a URL (for example, `https://wallet.example.com/alice`).
+
+See [Payment pointers and wallet addresses](/overview/concepts/payment-pointers) for more information.
 
 ## Simple Payment Setup Protocol (SPSP)
 

packages/documentation/src/content/docs/overview/concepts/payment-pointers.mdx

@@ -0,0 +1,55 @@
+---
+title: Payment pointers and wallet addresses
+---
+
+## Payment pointers
+
+A payment pointer is a standardized identifier for a payment account that supports Interledger payments. Each payment pointer must resolve to an HTTPS URL that serves as an [SPSP](/overview/concepts/interledger#simple-payment-setup-protocol-spsp) endpoint to facilitate sending and receiving ILP packets.
+
+You can determine whether a URL is a payment pointer by sending a `GET` request to the URL with an `accept: application/spsp4+json` header.
+
+```http title="Example request"
+curl --request GET \
+ --url https://wallet.example.com/alice/ \
+ --header 'accept: application/spsp4+json'
+```
+
+A response from an SPSP server means the URL is a payment pointer.
+
+```http title="Example response"
+{
+ "destination_account":"example.0.cloudnine.ind.alice.cdfa5e16-e759",
+ "shared_secret":"7h0s7EpQDqcgzqmX-mwrNHFHinPvJq8Jw",
+}
+```
+
+Payment pointers are often written out using the `$` shorthand. For example, `$wallet.example.com/alice`, which resolves to `https://wallet.example.com/alice/`.
+
+Rafiki assigns each of your customers' accounts with a payment pointer. This payment pointer is also a wallet address because Rafiki supports both Interledger and Open Payments.
+
+## Wallet addresses
+
+A wallet address is a secure, unique URL for a payment account that supports Open Payments. It acts as an entry point into the Open Payments APIs, facilitating interactions like sending and receiving payments.
+
+You can determine whether a URL is a wallet address by sending a `GET` request to the URL with an `accept: application/json` header.
+
+```http title="Example request"
+curl --request GET \
+ --url https://wallet.example.com/alice \
+ --header 'accept: application/json'
+```
+
+A valid response means the URL is a wallet address.
+
+```http title="Example response"
+{
+  "id": "https://wallet.example.com/alice",
+  "publicName": "Alice",
+  "assetCode": "USD",
+  "assetScale": 2,
+  "authServer": "https://auth.wallet.example.com",
+  "resourceServer": "https://wallet.example.com",
+}
+```
+
+Rafiki assigns each of your customers' accounts with a wallet address. This wallet address is also a payment pointer because Rafiki supports Open Payments and Interledger. See the integration requirements for [wallet addresses](/integration/requirements/wallet-addresses) for more information.