Stackup Documentation

website·Indexed 33 days ago

https://docs.stackup.fi/

Guides and API references for managing organization crypto operations, including smart account management, team permissions, banking integrations, and treasury operations. Features documentation on the Batch Transaction API, Forwarding Address API, and the implementation of ERC-4337 and passkeys for secure, non-custodial onchain operations.

Tokens
11K
Snippets
31
Records
103
Agent score
66%

What's inside Stackup

  1. Overview of Stackup Forwarding Addresses

    Forwarding addresses provide a way to generate unique, deterministic proxy addresses for end-users. When an end-user sends funds to a forwarding address, the system notifies the customer via webhook or API and automatically sweeps the funds to the associated Stackup wallet. This enables payment attribution for transfers coming from non-Stackup interfaces (e.g., Centralized Exchanges).
  2. Overview of Batch Transaction API

    The Batch Transaction API enables the queuing of multiple blockchain actions for approval before execution. This is designed for automating payment runs, managing treasury operations, and creating complex transaction sequences. Note that this API only queues transactions for approval in the Stackup dashboard; it does not submit them directly to the blockchain. Prerequisites include an API token and a Stackup wallet address.
  3. Overview of ERC-4337 Account Abstraction

    ERC-4337 is a standard that enables 'smart accounts' on Ethereum and similar blockchains through account abstraction. Unlike traditional accounts (which are simple public/private key pairs), ERC-4337 allows smart contracts to act as accounts. This removes several traditional blockchain limitations, such as the requirement to pay gas fees exclusively in the native token (e.g., ETH), the necessity of a cryptographic signature for every transaction, and the permanent loss of funds if private keys are lost.
  4. Overview of Passkey authentication at Stackup

    Stackup utilizes passkeys based on the WebAuthn API and asymmetric key cryptography to provide a passwordless authentication environment. This approach eliminates credential stuffing and phishing attacks because private key material is never sent to or stored by Stackup; the platform only stores a reference to the public key. Passkeys are used for both web platform login and signing smart contract transactions.
  5. How Stackup verifies passkey signatures on-chain

    Stackup links the passkey's public key to the user's smart account. Transactions signed by the passkey are verified natively on-chain using a P-256 verifier contract or precompile. This architecture ensures the account remains non-custodial and reduces the need for intermediaries compared to MPC wallets.
  6. Understand Stackup's free features and gas fee coverage

    Stackup is free to use, and the platform covers gas fees for the following activities:

    • Access Control: Setting up and managing role-based permissions and team transaction capabilities.
    • Sends: Sending tokens via the platform.
  7. Use Smart Accounts for programmable wallet logic

    A smart account is a smart contract purpose-built to function as a wallet. Unlike EOAs, smart accounts allow developers to programmatically define validation and execution logic via the EVM. This enables:

    • Custom Validation: Implementation of multi-sigs, passkeys, timed sessions, and granular spending limits (covering both Authentication—who can sign, and Authorization—what they can do).
    • Atomic Batching: Combining multiple onchain actions into a single transaction.
    • Gas Abstraction: Flexibility in how gas fees are paid for transactions.
  8. Understand Stackup's two-tiered permission system

    Stackup implements a two-tiered permission system that separates access control into two distinct levels: Organization roles and Wallet roles. This allows for granular control over who can manage the organization versus who can interact with specific wallets.
  9. Forwarding Address Smart Contract Architecture

    Each forwarding address is an ERC-1167 minimal proxy contract. The system automatically deploys the proxy and calls the sweep function to transfer the maximum balance of a specified token to the initialized receiver. Both deployment and sweeping are permissionless.
    interface IForwardingAddress {
        function receiver() external view returns (address);
        function initialize(address payable aReceiver) external;
        
        // A zero address for the input will sweep native ETH
        function sweep(address token) external;
    }
  10. Understand how yield works in Stackup

    Stackup offers yields through the use of vaults. Each vault is a smart contract that deposits user funds into a DeFi protocol to generate yield. The Annual Percentage Yield (APY) associated with these vaults is a variable rate.
  11. Understand Stackup's Two-Tiered Permission System

    Stackup utilizes a two-tiered permission system where organization-level roles and wallet-level roles are independent. A user's role in the organization does not dictate their permissions within a specific wallet; for example, an organization 'Member' can still be an 'Admin' of a specific wallet.
  12. Understand and use Proxy Addresses for automated ACH transfers

    A proxy address (also known as a Liquidation Address) is a permanent, chain-specific blockchain address that creates an automated pathway to liquidate crypto assets (such as USDC) into a connected bank account via ACH transfer. Funds sent to a proxy address are automatically routed to the destination bank account. Stackup does not take custody of funds during this process; the service is powered by the partner Bridge.