Spend limits to Spend Permissions (#8)

youssefea · web-flow · commit fa8c452cb0b3 · 2025-06-17T11:16:21.000-04:00
* change spend permisions

* add changes
diff --git a/_pages/builderkits/onchainkit/paymaster/errors.mdx b/_pages/builderkits/onchainkit/paymaster/errors.mdx
@@ -27,9 +27,9 @@ Below are a list of common error codes returned by the Paymaster.
 
 | Message                                                       | Description                                                       |
 | :------------------------------------------------------------ | :---------------------------------------------------------------- |
-| rejected due to max per user op spend limit exceeded          | UserOperation cost too large - configure Per UserOperation limit. |
-| rejected due to max monthly org spend limit                   | over max monthly spend - contact us to increase your limit.       |
-| rejected due to max global usd spend limit reached            | over configured max total USD - adjust your policy.               |
+| rejected due to max per user op Spend Permission exceeded          | UserOperation cost too large - configure Per UserOperation limit. |
+| rejected due to max monthly org Spend Permission                   | over max monthly spend - contact us to increase your limit.       |
+| rejected due to max global usd Spend Permission reached            | over configured max total USD - adjust your policy.               |
 | rejected due to maximum per address transaction count reached | per sender address maximum number of txn sponsored reached.       |
 | rejected due to maximum per address sponsorship reached       | per sender address maximum USD sponsorship reached.               |
 | attestation not found for address                             | sender address does not have required attestation.                |
diff --git a/_pages/builderkits/onchainkit/paymaster/gasless-transactions-with-paymaster.mdx b/_pages/builderkits/onchainkit/paymaster/gasless-transactions-with-paymaster.mdx
@@ -645,7 +645,7 @@ You should eventually encounter an error similar to this:
 ```json
 {
   "code": -32001,
-  "message": "request denied - rejected due to max global usd spend limit reached"
+  "message": "request denied - rejected due to max global usd Spend Permission reached"
 }
 ```
 
diff --git a/_pages/cookbook/account-abstraction/gasless-transactions-with-paymaster.mdx b/_pages/cookbook/account-abstraction/gasless-transactions-with-paymaster.mdx
@@ -294,7 +294,7 @@ async function sendTransaction(client, recipientAddress) {
    ```json
    {
      "code": -32001,
-     "message": "request denied - rejected due to max global usd spend limit reached"
+     "message": "request denied - rejected due to max global usd Spend Permission reached"
    }
    ```
    You’ve hit the **global** limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.
diff --git a/_pages/identity/smart-wallet/guides/sub-accounts/index.mdx b/_pages/identity/smart-wallet/guides/sub-accounts/index.mdx
@@ -45,6 +45,6 @@ If you want to skip ahead and just get the final code, you can find it here:
 2. [Using Sub Accounts](/identity/smart-wallet/guides/sub-accounts/using-sub-accounts) - Explore how to interact with Sub Accounts in your application. This guide demonstrates:
 
    - Signing messages with Sub Accounts using `useSignMessage`
-   - Sending transactions with spend limits using `useSendTransaction`
+   - Sending transactions with Spend Permissions using `useSendTransaction`
    - Building a complete interface for wallet connection and transactions
    - Understanding transaction limitations based on spend permissions
diff --git a/_pages/identity/smart-wallet/guides/sub-accounts/setup.mdx b/_pages/identity/smart-wallet/guides/sub-accounts/setup.mdx
@@ -123,7 +123,7 @@ Let's break down the key preference parameters:
 - `keysUrl`: Points to the development environment for Smart Wallet testing
 - `options: 'smartWalletOnly'`: Ensures only Smart Wallet mode is used
 - `enableAutoSubAccounts: true`: When set to true, automatically creates a Sub Account at connection
-- `defaultSpendLimits`: Configures Spend Limits for Sub Account for a network (eg. Base Sepolia `84532`), including:
+- `defaultSpendLimits`: Configures Spend Permissions for Sub Account for a network (eg. Base Sepolia `84532`), including:
 
   - Token address (In this case, `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` represents the native ETH)
   - Allowance WEI amount (in Hex)
diff --git a/_pages/use-cases/go-gasless.mdx b/_pages/use-cases/go-gasless.mdx
@@ -332,7 +332,7 @@ To confirm that your spend policies are correctly in place, try running the scri
    ```json
    {
      "code": -32001,
-     "message": "request denied - rejected due to max global usd spend limit reached"
+     "message": "request denied - rejected due to max global usd Spend Permission reached"
    }
    ```
    You’ve hit the **global** limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.
diff --git a/docs/cookbook/go-gasless.mdx b/docs/cookbook/go-gasless.mdx
@@ -340,7 +340,7 @@ To confirm that your spend policies are correctly in place, try running the scri
    ```json
    {
      "code": -32001,
-     "message": "request denied - rejected due to max global usd spend limit reached"
+     "message": "request denied - rejected due to max global usd Spend Permission reached"
    }
    ```
    You’ve hit the **global** limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.
diff --git a/docs/docs.json b/docs/docs.json
@@ -208,7 +208,7 @@
                     "group": "Optional Features",
                     "pages": [
                       "smart-wallet/concepts/features/optional/gas-free-transactions",
-                      "smart-wallet/concepts/features/optional/spend-limits",
+                      "smart-wallet/concepts/features/optional/spend-permissions",
                       "smart-wallet/concepts/features/optional/batch-operations",
                       "smart-wallet/concepts/features/optional/custom-gas-tokens",
                       "smart-wallet/concepts/features/optional/sub-accounts"
@@ -245,7 +245,7 @@
                   "smart-wallet/guides/sub-accounts/using-sub-accounts"
                 ]
               },
-              "smart-wallet/guides/spend-limits"
+              "smart-wallet/guides/spend-permissions"
             ]
           },
           {
@@ -298,13 +298,13 @@
                 ]
               },
               {
-                "group": "Spend Limits",
+                "group": "Spend Permissions",
                 "pages": [
                   "smart-wallet/technical-reference/spend-permissions/spendpermissionmanager",
                   "smart-wallet/technical-reference/spend-permissions/coinbase-fetchpermissions"
                 ]
               },
-              "smart-wallet/technical-reference/sdk/sub-account-reference"
+              "smart-wallet/technical-reference/sub-account-reference"
             ]
           },
           {
diff --git a/docs/learn/onchain-app-development/account-abstraction/gasless-transactions-with-paymaster.mdx b/docs/learn/onchain-app-development/account-abstraction/gasless-transactions-with-paymaster.mdx
@@ -291,7 +291,7 @@ async function sendTransaction(client, recipientAddress) {
    ```json
    {
      "code": -32001,
-     "message": "request denied - rejected due to max global usd spend limit reached"
+     "message": "request denied - rejected due to max global usd Spend Permission reached"
    }
    ```
    You’ve hit the **global** limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.
diff --git a/docs/llms-full.txt b/docs/llms-full.txt
@@ -4694,7 +4694,7 @@ If you repeatedly run transactions and eventually see:
 
 Copy{
      "code": -32001,
-     "message": "request denied - rejected due to max global usd spend limit reached"
+     "message": "request denied - rejected due to max global usd Spend Permission reached"
 }
 ```
 
diff --git a/docs/onchainkit/paymaster/errors.mdx b/docs/onchainkit/paymaster/errors.mdx
@@ -26,9 +26,9 @@ Below are a list of common error codes returned by the Paymaster.
 
 | Message                                                       | Description                                                       |
 | :------------------------------------------------------------ | :---------------------------------------------------------------- |
-| rejected due to max per user op spend limit exceeded          | UserOperation cost too large - configure Per UserOperation limit. |
-| rejected due to max monthly org spend limit                   | over max monthly spend - contact us to increase your limit.       |
-| rejected due to max global usd spend limit reached            | over configured max total USD - adjust your policy.               |
+| rejected due to max per user op Spend Permission exceeded          | UserOperation cost too large - configure Per UserOperation limit. |
+| rejected due to max monthly org Spend Permission                   | over max monthly spend - contact us to increase your limit.       |
+| rejected due to max global usd Spend Permission reached            | over configured max total USD - adjust your policy.               |
 | rejected due to maximum per address transaction count reached | per sender address maximum number of txn sponsored reached.       |
 | rejected due to maximum per address sponsorship reached       | per sender address maximum USD sponsorship reached.               |
 | attestation not found for address                             | sender address does not have required attestation.                |
diff --git a/docs/onchainkit/paymaster/gasless-transactions-with-paymaster.mdx b/docs/onchainkit/paymaster/gasless-transactions-with-paymaster.mdx
@@ -654,7 +654,7 @@ You should eventually encounter an error similar to this:
 ```json
 {
   "code": -32001,
-  "message": "request denied - rejected due to max global usd spend limit reached"
+  "message": "request denied - rejected due to max global usd Spend Permission reached"
 }
 ```
 
diff --git a/docs/smart-wallet/concepts/features/optional/spend-permissions.mdx b/docs/smart-wallet/concepts/features/optional/spend-permissions.mdx
@@ -1,19 +1,19 @@
 ---
-title: "Spend Limits"
+title: "Spend Permissions"
 ---
 
-Spend Limits enable third-party signers to spend assets (native and ERC-20 tokens) from users' wallets. Once granted, spend limits allow you to move your users' assets without any further signatures, unlocking use cases like subscriptions & trading bots. The reduced signing friction can also be leveraged to enhance UX for high-frequency use cases such as onchain games.
+Spend Permissions enable third-party signers to spend assets (native and ERC-20 tokens) from users' wallets. Once granted, Spend Permissions allow you to move your users' assets without any further signatures, unlocking use cases like subscriptions & trading bots. The reduced signing friction can also be leveraged to enhance UX for high-frequency use cases such as onchain games.
 
-Differences between Spend Limits and ERC-20 permits:
+Differences between Spend Permissions and ERC-20 permits:
 
-- Spend Limits **supports all ERC-20 assets**, whereas permits only support ERC-20s that implement the permit standard
-- Spend Limits **enable spending native tokens**
-- Spend Limits offers granular **controls for recurrence**
+- Spend Permissions **supports all ERC-20 assets**, whereas permits only support ERC-20s that implement the permit standard
+- Spend Permissions **enable spending native tokens**
+- Spend Permissions offers granular **controls for recurrence**
 - The logic that controls asset movements is **implemented in the user's wallet**, not the asset contract
 
 ## The `SpendPermission` details
 
-A spend limit is defined by the following parameters
+A Spend Permission is defined by the following parameters
 
 ```solidity
 struct SpendPermission {
@@ -29,7 +29,7 @@ struct SpendPermission {
 }
 ```
 
-Spend limits are managed by a single manager contract, the `SpendLimitManager`, which tracks the approval/revocation
+Spend Permissions are managed by a single manager contract, the `SpendLimitManager`, which tracks the approval/revocation
 statuses of all limits and enforces accurate spending limits and accounting.
 
 ## Approving
@@ -51,14 +51,14 @@ If the parameters of the new spend permission are identical to the revoked permi
 
 ## Cycle accounting
 
-Spend Limits offers granular controls for recurrence (e.g. 10 USDC / month).
+Spend Permissions offers granular controls for recurrence (e.g. 10 USDC / month).
 As the third-party signer spends user assets, the `SpendPermissionManager` contract tracks cumulative spend and enforces the per-period
 allowance. If there are multiple periods defined during the valid lifespan of the spend permission, the cumulative usage resets to 0
 at the beginning of the next period, allowing the spender to once again spend up to the allowance.
 
 This behavior is parameterized by the `start`, `end`, `period` and `allowance` properties of the permission.
 
-Note that spend limits can be used for non-recurring allowances, either indefinite or with expiry, by setting
+Note that Spend Permissions can be used for non-recurring allowances, either indefinite or with expiry, by setting
 a period duration that spans the entire range between start and end.
 
 A comprehensive example of spend permission accounting can be found [here](https://github.com/coinbase/spend-permissions/blob/main/docs/SpendPermissionAccounting.md).
diff --git a/docs/smart-wallet/concepts/what-is-smart-wallet.mdx b/docs/smart-wallet/concepts/what-is-smart-wallet.mdx
@@ -16,4 +16,4 @@ Smart Wallet combines the best features of a wallet and an app specific account:
 - [Get Free Sponsored Transactions](/smart-wallet/concepts/base-gasless-campaign): Use Paymaster to sponsor transactions and get qualified for up to $15k in gas credits;
 - [Support Sub Accounts](/smart-wallet/guides/sub-accounts): Improve user experience with embedded accounts controlled by their Smart Wallet,
   eliminating the need for users to sign a transaction for every onchain action.
-- [Support Spend Permissions](/smart-wallet/guides/spend-limits): Enable third-party signers to spend user assets
+- [Support Spend Permissions](/smart-wallet/guides/spend-permissions): Enable third-party signers to spend user assets
diff --git a/docs/smart-wallet/guides/spend-permissions.mdx b/docs/smart-wallet/guides/spend-permissions.mdx
@@ -11,7 +11,7 @@ Once granted, Spend Permissions
 allow developers to move users'
 assets without any further signatures, unlocking use cases like subscriptions & trading bots.
 
-The following is a technical guide to build with Spend Permissions. If you want to learn more about high level details of this feature, check out the [Spend Permissions feature page](/smart-wallet/concepts/features/optional/spend-limits).
+The following is a technical guide to build with Spend Permissions. If you want to learn more about high level details of this feature, check out the [Spend Permissions feature page](/smart-wallet/concepts/features/optional/spend-permissions).
 
 ## Let's build!
 
diff --git a/docs/smart-wallet/guides/sub-accounts.mdx b/docs/smart-wallet/guides/sub-accounts.mdx
@@ -14,7 +14,7 @@ To support using Smart Wallet with user experiences that require more developer
 
 Sub Accounts allow you to provision wallet accounts that are directly embedded in your application for your users. You can control when a Sub Account is created for your user, and can interact with them just as you would with another wallet via the wallet provider, or other popular web3 libraries like OnchainKit, wagmi, viem, etc.
 
-These Sub Accounts are linked to the end user's Smart wallet through an onchain relationship. When combined with our [Spend Permission feature](/smart-wallet/guides/spend-limits), this creates a powerful foundation for provisioning and funding app accounts, securely, while giving you, the developer, ample control over building the user experience that makes the most sense for your application.
+These Sub Accounts are linked to the end user's Smart wallet through an onchain relationship. When combined with our [Spend Permission feature](/smart-wallet/guides/spend-permissions), this creates a powerful foundation for provisioning and funding app accounts, securely, while giving you, the developer, ample control over building the user experience that makes the most sense for your application.
 
 If you would like to see a live demo of Sub Accounts in action, check out our [Sub Accounts Demo](https://sub-account-demo.com).
 
@@ -44,6 +44,6 @@ If you want to skip ahead and just get the final code, you can find it here:
 2. [Using Sub Accounts](/smart-wallet/guides/sub-accounts/using-sub-accounts) - Explore how to interact with Sub Accounts in your application. This guide demonstrates:
 
    - Signing messages with Sub Accounts using `useSignMessage`
-   - Sending transactions with spend limits using `useSendTransaction`
+   - Sending transactions with Spend Permissions using `useSendTransaction`
    - Building a complete interface for wallet connection and transactions
    - Understanding transaction limitations based on spend permissions
diff --git a/docs/smart-wallet/guides/sub-accounts/add-sub-accounts-to-onchainkit-minikit.mdx b/docs/smart-wallet/guides/sub-accounts/add-sub-accounts-to-onchainkit-minikit.mdx
@@ -130,7 +130,7 @@ Let's break down the key preference parameters:
 - `keysUrl`: Points to the development environment for Smart Wallet testing
 - `options: 'smartWalletOnly'`: Ensures only Smart Wallet mode is used
 - `enableAutoSubAccounts: true`: When set to true, automatically creates a Sub Account at connection
-- `defaultSpendLimits`: Configures Spend Limits for Sub Account for a network (eg. Base Sepolia `84532`), including:
+- `defaultSpendLimits`: Configures Spend Permissions for Sub Account for a network (eg. Base Sepolia `84532`), including:
 
   - Token address (In this case, `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` represents the native ETH)
   - Allowance WEI amount (in Hex)
diff --git a/docs/smart-wallet/guides/sub-accounts/index.mdx b/docs/smart-wallet/guides/sub-accounts/index.mdx
@@ -15,7 +15,7 @@ To support using Smart Wallet with user experiences that require more developer
 
 Sub Accounts allow you to provision wallet accounts that are directly embedded in your application for your users. You can control when a Sub Account is created for your user, and can interact with them just as you would with another wallet via the wallet provider, or other popular web3 libraries like OnchainKit, wagmi, viem, etc.
 
-These Sub Accounts are linked to the end user's Smart wallet through an onchain relationship. When combined with our [Spend Limits feature](/identity/smart-wallet/guides/spend-limits), this creates a powerful foundation for provisioning and funding app accounts, securely, while giving you, the developer, ample control over building the user experience that makes the most sense for your application.
+These Sub Accounts are linked to the end user's Smart wallet through an onchain relationship. When combined with our [Spend Permissions feature](/identity/smart-wallet/guides/spend-permissions), this creates a powerful foundation for provisioning and funding app accounts, securely, while giving you, the developer, ample control over building the user experience that makes the most sense for your application.
 
 If you would like to see a live demo of Sub Accounts in action, check out our [Sub Accounts Demo](https://sub-account-demo.com).
 
@@ -30,7 +30,7 @@ and it cannot be used on other applications on separate domains.
 In this guide, we'll set up a basic React app using NextJS and Wagmi that:
 
 - Lets users log in with their Smart Wallet
-- Creates a Sub Account scoped to the app with the a Spend Limit included in the configuration
+- Creates a Sub Account scoped to the app with the a Spend Permission included in the configuration
 - Uses the Sub Account to perform popup-less transactions
 
 ### Skip ahead
@@ -45,15 +45,15 @@ If you want to skip ahead and just get the final code, you can find it here:
 
    - Creating a new NextJS+Wagmi project
    - Configuring Smart Wallet with development environment settings
-   - Setting up Spend Limits for native ETH
+   - Setting up Spend Permissions for native ETH
    - Creating a basic wallet connection interface
 
 2. [Using Sub Accounts](/identity/smart-wallet/guides/sub-accounts/using-sub-accounts) - Explore how to interact with Sub Accounts in your application. This guide demonstrates:
 
    - Signing messages with Sub Accounts using `useSignMessage`
-   - Sending transactions with spend limits using `useSendTransaction`
+   - Sending transactions with Spend Permissions using `useSendTransaction`
    - Building a complete interface for wallet connection and transactions
-   - Understanding transaction limitations based on Spend Limits
+   - Understanding transaction limitations based on Spend Permissions
 
 3. [Using Sub Accounts with OnchainKit](/identity/smart-wallet/guides/sub-accounts/add-sub-accounts-to-onchainkit-minikit) - Learn how to use Sub Accounts with OnchainKit. This guide demonstrates:
 
diff --git a/docs/smart-wallet/guides/sub-accounts/setup.mdx b/docs/smart-wallet/guides/sub-accounts/setup.mdx
@@ -117,7 +117,7 @@ Let's break down the key preference parameters:
 - `keysUrl`: Points to the development environment for Smart Wallet testing
 - `options: 'smartWalletOnly'`: Ensures only Smart Wallet mode is used
 - `enableAutoSubAccounts: true`: When set to true, automatically creates a Sub Account at connection
-- `defaultSpendLimits`: Configures Spend Limits for Sub Account for a network (eg. Base Sepolia `84532`), including:
+- `defaultSpendLimits`: Configures Spend Permissions for Sub Account for a network (eg. Base Sepolia `84532`), including:
 
   - Token address (In this case, `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` represents the native ETH)
   - Allowance WEI amount (in Hex)
diff --git a/docs/smart-wallet/guides/sub-accounts/sub-accounts-with-privy.mdx b/docs/smart-wallet/guides/sub-accounts/sub-accounts-with-privy.mdx
diff --git a/docs/smart-wallet/guides/sub-accounts/using-sub-accounts.mdx b/docs/smart-wallet/guides/sub-accounts/using-sub-accounts.mdx
diff --git a/docs/smart-wallet/quickstart.mdx b/docs/smart-wallet/quickstart.mdx
diff --git a/docs/smart-wallet/technical-reference/sub-account-reference.mdx b/docs/smart-wallet/technical-reference/sub-account-reference.mdx

Original file line number	Diff line number	Diff line change
`@@ -645,7 +645,7 @@ You should eventually encounter an error similar to this:`
`645`	`645`	```json
`646`	`646`	`{`
`647`	`647`	`"code": -32001,`
`648`		`- "message": "request denied - rejected due to max global usd spend limit reached"`
	`648`	`+ "message": "request denied - rejected due to max global usd Spend Permission reached"`
`649`	`649`	`}`
`650`	`650`	```
`651`	`651`
Original file line number	Diff line number	Diff line change
`@@ -294,7 +294,7 @@ async function sendTransaction(client, recipientAddress) {`
`294`	`294`	```json
`295`	`295`	`{`
`296`	`296`	`"code": -32001,`
`297`		`- "message": "request denied - rejected due to max global usd spend limit reached"`
	`297`	`+ "message": "request denied - rejected due to max global usd Spend Permission reached"`
`298`	`298`	`}`
`299`	`299`	```
`300`	`300`	`You’ve hit the global limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.`
Original file line number	Diff line number	Diff line change
`@@ -332,7 +332,7 @@ To confirm that your spend policies are correctly in place, try running the scri`
`332`	`332`	```json
`333`	`333`	`{`
`334`	`334`	`"code": -32001,`
`335`		`- "message": "request denied - rejected due to max global usd spend limit reached"`
	`335`	`+ "message": "request denied - rejected due to max global usd Spend Permission reached"`
`336`	`336`	`}`
`337`	`337`	```
`338`	`338`	`You’ve hit the global limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.`
Original file line number	Diff line number	Diff line change
`@@ -340,7 +340,7 @@ To confirm that your spend policies are correctly in place, try running the scri`
`340`	`340`	```json
`341`	`341`	`{`
`342`	`342`	`"code": -32001,`
`343`		`- "message": "request denied - rejected due to max global usd spend limit reached"`
	`343`	`+ "message": "request denied - rejected due to max global usd Spend Permission reached"`
`344`	`344`	`}`
`345`	`345`	```
`346`	`346`	`You’ve hit the global limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.`
Original file line number	Diff line number	Diff line change
`@@ -208,7 +208,7 @@`
`208`	`208`	`"group": "Optional Features",`
`209`	`209`	`"pages": [`
`210`	`210`	`"smart-wallet/concepts/features/optional/gas-free-transactions",`
`211`		`- "smart-wallet/concepts/features/optional/spend-limits",`
	`211`	`+ "smart-wallet/concepts/features/optional/spend-permissions",`
`212`	`212`	`"smart-wallet/concepts/features/optional/batch-operations",`
`213`	`213`	`"smart-wallet/concepts/features/optional/custom-gas-tokens",`
`214`	`214`	`"smart-wallet/concepts/features/optional/sub-accounts"`
`@@ -245,7 +245,7 @@`
`245`	`245`	`"smart-wallet/guides/sub-accounts/using-sub-accounts"`
`246`	`246`	`]`
`247`	`247`	`},`
`248`		`- "smart-wallet/guides/spend-limits"`
	`248`	`+ "smart-wallet/guides/spend-permissions"`
`249`	`249`	`]`
`250`	`250`	`},`
`251`	`251`	`{`
`@@ -298,13 +298,13 @@`
`298`	`298`	`]`
`299`	`299`	`},`
`300`	`300`	`{`
`301`		`- "group": "Spend Limits",`
	`301`	`+ "group": "Spend Permissions",`
`302`	`302`	`"pages": [`
`303`	`303`	`"smart-wallet/technical-reference/spend-permissions/spendpermissionmanager",`
`304`	`304`	`"smart-wallet/technical-reference/spend-permissions/coinbase-fetchpermissions"`
`305`	`305`	`]`
`306`	`306`	`},`
`307`		`- "smart-wallet/technical-reference/sdk/sub-account-reference"`
	`307`	`+ "smart-wallet/technical-reference/sub-account-reference"`
`308`	`308`	`]`
`309`	`309`	`},`
`310`	`310`	`{`
Original file line number	Diff line number	Diff line change
`@@ -291,7 +291,7 @@ async function sendTransaction(client, recipientAddress) {`
`291`	`291`	```json
`292`	`292`	`{`
`293`	`293`	`"code": -32001,`
`294`		`- "message": "request denied - rejected due to max global usd spend limit reached"`
	`294`	`+ "message": "request denied - rejected due to max global usd Spend Permission reached"`
`295`	`295`	`}`
`296`	`296`	```
`297`	`297`	`You’ve hit the global limit of sponsored gas. Increase it in the CDP dashboard and wait a few minutes for changes to take effect.`
Original file line number	Diff line number	Diff line change
`@@ -4694,7 +4694,7 @@ If you repeatedly run transactions and eventually see:`
`4694`	`4694`
`4695`	`4695`	`Copy{`
`4696`	`4696`	`"code": -32001,`
`4697`		`- "message": "request denied - rejected due to max global usd spend limit reached"`
	`4697`	`+ "message": "request denied - rejected due to max global usd Spend Permission reached"`
`4698`	`4698`	`}`
`4699`	`4699`	```
`4700`	`4700`