GITBOOK-168: chore: update supported currencies and wallets

Author: MantisClone

docs/README.md

@@ -2,21 +2,12 @@
 description: >-
   Request Network is a protocol for creating payment requests and reconciling
   payments.
-layout:
-  title:
-    visible: true
-  description:
-    visible: true
-  tableOfContents:
-    visible: true
-  outline:
-    visible: true
-  pagination:
-    visible: false
 ---
 
 # Request Network Docs
 
+
+
 {% hint style="info" %}
 **Talk to an expert**
 

docs/SUMMARY.md

@@ -9,7 +9,7 @@
 * [Crypto-to-fiat Payments](request-network-api/crypto-to-fiat-payments.md)
 * [Batch Payments](request-network-api/batch-payments.md)
 * [Recurring payments](request-network-api/recurring-payments.md)
-* [Currencies](request-network-api/currencies.md)
+* [Supported Chains and Currencies](request-network-api/supported-chains-and-currencies.md)
 * [EasyInvoice: API Demo App](request-network-api/easyinvoice-api-demo-app.md)
 * [API Portal: Manage API Keys and Webhooks](request-network-api/api-portal-manage-api-keys-and-webhooks.md)
 * [Full API Reference](https://api.request.network/open-api)

docs/advanced/protocol-overview/private-requests-using-encryption.md

@@ -1,17 +1,3 @@
----
-layout:
-  title:
-    visible: true
-  description:
-    visible: true
-  tableOfContents:
-    visible: true
-  outline:
-    visible: true
-  pagination:
-    visible: true
----
-
 # Private Requests using Encryption
 
 The Request Network protocol persists request contents on IPFS. When privacy is required, the SDK supports the creation and subsequent reading of encrypted requests.

docs/advanced/request-network-sdk/sdk-demo-apps/components/invoice-dashboard.md

@@ -1,16 +1,5 @@
 ---
 description: A dashboard for viewing and paying invoices in Request Network
-layout:
-  title:
-    visible: true
-  description:
-    visible: true
-  tableOfContents:
-    visible: true
-  outline:
-    visible: true
-  pagination:
-    visible: true
 ---
 
 # Invoice Dashboard

docs/request-network-api/create-and-pay-requests.md

@@ -26,8 +26,11 @@ At its core, the Request Network API empowers you to:
     * **Gradual payment plans:** Allow users to pay large invoices in smaller chunks.
     * **Risk mitigation:** Test with small amounts before completing large payments.
 
-    The API automatically tracks payment progress, showing `partially_paid` status until the request is fully paid, and prevents overpayment by capping amounts to the remaining balance.\
+    The API automatically tracks payment progress, showing `partially_paid` status until the request is fully paid, and prevents overpayment by capping amounts to the remaining balance.
 
+### Supported Chains and Currencies
+
+See [#request-network-api-supported-currencies](supported-chains-and-currencies.md#request-network-api-supported-currencies "mention")
 
 {% openapi-operation spec="request-api" path="/v2/request" method="post" %}
 [OpenAPI request-api](https://api.request.network/open-api/openapi.json)
@@ -96,3 +99,4 @@ sequenceDiagram
     Request Network API->>App: POST <webhook url> {"payment.confirmed", requestId, paymentReference, request scan link, timestamp}
     App-->>User: Payment Complete
 ```
+

docs/request-network-api/crosschain-payments.md

@@ -20,16 +20,20 @@ Crosschain payments allow users to pay a request using a stablecoin from a diffe
 * **Time-Saving:** Payers don't need to swap or bridge tokens manually.
 * **Simplified UX:** Payment settlement requires only 1 or 2 signatures from the Payer.
 
-## Supported Networks
+## Crosschain Payments Supported Chains and Currencies
+
+For Crosschain (and Samechain) Payments, the Request Network API supports 12 stablecoins: USDC/USDT/DAI on 4 chains (Ethereum, Arbitrum One, Base, OP Mainnet).
+
+### Crosschain Payments Supported Chains
 
 Crosschain payments are supported on the following blockchain networks:
 
-* Base
-* Optimism
-* Arbitrum
 * Ethereum
+* Arbitrum One
+* Base
+* OP Mainnet
 
-## Supported Stablecoins
+### Crosschain Payments Supported Currencies
 
 {% hint style="warning" %}
 **Warning:** Crosschain payments work only with mainnet funds (real money). Test networks are not supported.
@@ -99,7 +103,7 @@ The API may return samechain routes if the payer address has supported currencie
 * No native token (ETH, etc..) needed for gas
 
 {% openapi-operation spec="request-api" path="/v2/request/{requestId}/routes" method="get" %}
-[Broken link](broken-reference)
+[OpenAPI request-api](https://api.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 ### 3. Getting payment calldata
@@ -111,7 +115,7 @@ If the selected route is a crosschain payment, the [#get-v2-request-requestid-pa
 If the selected route is a direct payment, the [#get-v2-request-requestid-pay](crosschain-payments.md#get-v2-request-requestid-pay "mention") returns an unsigned payment calldata. It may also return an approval calldata. For direct payments, this endpoint IS approval aware - it will omit the approval calldata if sufficient approval has already been granted.
 
 {% openapi-operation spec="request-api" path="/v2/request/{requestId}/pay" method="get" %}
-[Broken link](broken-reference)
+[OpenAPI request-api](https://api.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 ### 4. Signing the payment intent
@@ -189,7 +193,7 @@ const signedData = {
 Finally, the signed payment intent (and possibly the signed approval permit) are sent back to execute the crosschain payment via the [#post-v2-request-payment-intents-paymentintentid](crosschain-payments.md#post-v2-request-payment-intents-paymentintentid "mention") endpoint. It will handle all the necessary steps to complete the payment. A `payment.complete` event will be sent to the platform's webhooks when the payment is completed.
 
 {% openapi-operation spec="request-api" path="/v2/request/payment-intents/{paymentIntentId}" method="post" %}
-[Broken link](broken-reference)
+[OpenAPI request-api](https://api.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 ## Custom fee configuration

docs/request-network-api/crypto-to-fiat-payments.md

@@ -52,6 +52,10 @@ Production access includes:
 * Live bank account validation
 * Fiat deposits to real bank accounts
 
+### Crypto-to-fiat Supported Chains and Currencies
+
+For Crypto-to-fiat Payments, the Request Network API supports USDC on Ethereum, Polygon, Arbitrum One, and Sepolia.
+
 ## Understanding `clientUserId`
 
 Many `/payer` endpoints in the Request Network API require a `clientUserId` as a path parameter. This value is an **arbitrary identifier** chosen by your platform to represent a user (the payer) in your own system.
@@ -124,15 +128,15 @@ sequenceDiagram
 * `PATCH /payer/{clientUserId}`: Update agreement status after signature.
 
 {% openapi-operation spec="request-api-staging" path="/v2/payer" method="post" %}
-[Broken link](broken-reference)
+[OpenAPI request-api-staging](https://api.stage.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 {% openapi-operation spec="request-api-staging" path="/v2/payer/{clientUserId}" method="get" %}
-[Broken link](broken-reference)
+[OpenAPI request-api-staging](https://api.stage.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 {% openapi-operation spec="request-api-staging" path="/v2/payer/{clientUserId}" method="patch" %}
-[Broken link](broken-reference)
+[OpenAPI request-api-staging](https://api.stage.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 ## Setting Up a Crypto-to-Fiat Request (Payee Flow)
@@ -197,15 +201,15 @@ This approach ensures a smooth, compliant, and user-friendly experience, even if
 * `POST /v2/request` with `isCryptoToFiatAllowed = true`: Create a new crypto-to-fiat request 
 
 {% openapi-operation spec="request-api-staging" path="/v2/payer/{clientUserId}/payment-details" method="post" %}
-[Broken link](broken-reference)
+[OpenAPI request-api-staging](https://api.stage.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 {% openapi-operation spec="request-api-staging" path="/v2/payer/{clientUserId}/payment-details" method="get" %}
-[Broken link](broken-reference)
+[OpenAPI request-api-staging](https://api.stage.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 {% openapi-operation spec="request-api-staging" path="/v2/request" method="post" %}
-[Broken link](broken-reference)
+[OpenAPI request-api-staging](https://api.stage.request.network/open-api/openapi.json)
 {% endopenapi-operation %}
 
 ## Paying a Crypto-to-Fiat Request

docs/request-network-api/currencies.md

@@ -16,6 +16,10 @@ Discover how your app can have its own EasyInvoice features - [book a call](http
 
 ## Key Features
 
+### Overall Supported Currencies and Chains
+
+15 stablecoins: USDC/USDT/DAI on 5 chains (Ethereum, Polygon, Arbitrum One, Base, OP Mainnet) + 4 testnet tokens on Sepolia + USD fiat for Conversion and Crypto-to-fiat payments.
+
 ### **Invoice Creation**
 
 * **Invoice Creation**: A simple form to create invoices.
@@ -36,23 +40,31 @@ Discover how your app can have its own EasyInvoice features - [book a call](http
 
 * **Invoice Payment:**
   * View invoice details and initiate payment using transaction calldata provided by the Request Network API.
-  * Compatible with 50+ different crypto wallets.
+  * Compatible with 80+ different crypto wallets via Reown AppKit
 * **Real-time Updates**: The app receives webhooks from the Request Network API to update the invoice status in real-time.
 
 <figure><img src="../.gitbook/assets/Screenshot from 2025-02-14 01-01-00 (2).png" alt=""><figcaption><p>EasyInvoice Invoice Payment Page</p></figcaption></figure>
 
-<figure><img src="../.gitbook/assets/image (1) (3).png" alt=""><figcaption><p>EasyInvoice supports 50+ wallets via Reown AppKit</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (1) (3).png" alt=""><figcaption><p>EasyInvoice supports 80+ wallets via Reown AppKit</p></figcaption></figure>
 
 ### Invoice Crosschain Payment
 
 <figure><img src="../.gitbook/assets/Screenshot 2025-04-01 at 4.07.30 PM.png" alt=""><figcaption></figcaption></figure>
 
 {% embed url="https://youtu.be/OpAd3Xzu8zU" %}
 
+#### Crosschain Payment Supported Currencies
+
+For Crosschain (and Samechain) Payments, EasyInvoice supports 12 stablecoins: USDC/USDT/DAI on 4 chains (Ethereum, Arbitrum One, Base, OP Mainnet)
+
 ### Crypto-to-fiat Payment
 
 {% embed url="https://youtu.be/1Y7QIi6oZoU" %}
 
+#### Crypto-to-fiat Payment Supported Currencies
+
+For Crypto-to-fiat Payments, EasyInvoice supports USDC on Sepolia.
+
 ### Batch Pay Invoices
 
 {% embed url="https://youtu.be/BsbENNP00AI" %}

docs/request-network-api/easyinvoice-api-demo-app.md

@@ -0,0 +1,95 @@
+---
+description: The Request Network API supports 500+ currencies across 10 EVM chains.
+---
+
+# Supported Chains and Currencies
+
+{% hint style="info" %}
+**Talk to an expert**
+
+Discover how Request Network API can enhance your app's features - [book a call](https://calendly.com/mariana-rn/request-network-demo-docs) with us.
+{% endhint %}
+
+## Request Network API Supported Chains and Currencies
+
+Overall, the Request Network API supports 500+ currencies across 10 EVM chains.
+
+### ERC20, Native, and Conversion Payments Supported Chains
+
+10 EVM Chains:
+
+* Ethereum
+* Arbitrum One
+* OP Mainnet
+* Base
+* Polygon
+* BSC
+* Avalanche
+* Fantom
+* zkSync Era
+* Sepolia
+
+### ERC20 and Native Payments Supported Currencies
+
+For ERC20 and Native Payments, the Request Network API supports 500+ tokens, mostly on Ethereum. See [request-network-token-list.md](../general/request-network-token-list.md "mention") for the full list.
+
+{% hint style="info" %}
+The [request-network-token-list.md](../general/request-network-token-list.md "mention") is a _super set_, which contains some currencies on non-supported chains. Cross-reference with the [#request-network-api-supported-chains](supported-chains-and-currencies.md#request-network-api-supported-chains "mention") 
+{% endhint %}
+
+### Conversion Payments Supported Currencies
+
+For Conversion Payments, the Request Network API supports the following _invoice_ currencies:
+
+* USD
+* EUR
+* CNY
+* GBP
+* JPY
+
+For Conversion Payments, the Request Network API supports the following _payment_ currencies:
+
+* USDC
+* USDT
+* DAI
+* FAU on Sepolia
+
+### Crosschain Payments Supported Currencies
+
+See [#crosschain-payments-supported-chains-and-currencies](crosschain-payments.md#crosschain-payments-supported-chains-and-currencies "mention")
+
+### Crypto-to-fiat Payments Supported Currencies
+
+See [#crypto-to-fiat-supported-chains-and-currencies](crypto-to-fiat-payments.md#crypto-to-fiat-supported-chains-and-currencies "mention")
+
+## Currencies API Endpoint
+
+The currencies API endpoints provide access to the complete Request Network token list, enabling you to discover and filter available tokens across multiple blockchain networks. 
+
+## Key Features
+
+* **Payment Request Integration**: Get the exact currency IDs needed for creating payment requests
+* **Payment Integration**: Get accurate token information for payment processing
+* **Currency Validation**: Verify supported tokens before creating payment requests
+* **Multi-Chain Support**: Access tokens across Ethereum, Polygon, Arbitrum, and more
+* **Developer-Friendly**: Simple filtering options for easy integration
+
+## Currency Information Structure
+
+Each token in the response includes:
+
+* **id**: Unique Request Network token identifier (e.g., `USDC-mainnet`)
+* **name**: Human-readable token name (e.g., `USD Coin`)
+* **symbol**: Token symbol (e.g., `USDC`)
+* **decimals**: Number of decimal places for the token
+* **address**: Contract address on the specified network
+* **network**: Blockchain network name
+* **type**: Token type (`ERC20`, `ETH`, etc.)
+* **hash**: Contract address hash
+* **chainId**: Blockchain chain ID
+
+## Endpoints
+
+{% openapi-operation spec="request-api" path="/v2/currencies" method="get" %}
+[OpenAPI request-api](https://api.request.network/open-api/openapi.json)
+{% endopenapi-operation %}