Skip to main content
Rise B2B API is designed for seamless integration with Web3 wallets and smart contract standards. This guide covers wallet integration and EIP-712 typed data signing for secure blockchain operations using the official Rise SDK.

Secure

EIP-712 typed data signing for enhanced security

Efficient

Gas-optimized transactions with structured data

Compatible

Works with MetaMask, WalletConnect, and other wallets

User-Friendly

Human-readable messages in wallet interfaces

SDK Installation

First, install the Rise SDK:

Supported Wallets

Rise B2B API supports all major Web3 wallets:

MetaMask

Most popular Ethereum wallet

WalletConnect

Multi-wallet connection protocol

Coinbase Wallet

Coinbase’s Web3 wallet

Rainbow

Beautiful mobile wallet

Trust Wallet

Binance’s mobile wallet

Any EIP-1193

Compatible with any EIP-1193 wallet

Getting Started

Initialize the SDK

EIP-712 Typed Data Signing

Many Rise operations (payments, team management, invites) require EIP-712 typed data signing for enhanced security and gas efficiency. The SDK handles this automatically for most operations.

What is EIP-712 Typed Data?

EIP-712 is a standard for typed data signing that provides:
  • Human-readable messages in wallet interfaces
  • Type safety to prevent signature replay attacks
  • Gas efficiency compared to raw message signing
  • Better security through structured data validation

Automatic Typed Data Signing

The SDK automatically handles typed data signing for most operations:
What the SDK does automatically:
  1. Generates typed data for EIP-712 signing
  2. Signs the typed data using your private key
  3. Submits the signed transaction to the Rise API
  4. Handles authentication and JWT token management
  5. Provides error handling and retry logic

Manual Typed Data Signing

For more control over the signing process, you can handle the signing manually:
What the manual flow provides:
  1. Custom signing logic - You control when and how to sign
  2. Typed data inspection - You can examine the data before signing
  3. Signature verification - You can verify the signature before submission
  4. Error handling control - Custom error handling for each step
  5. Integration flexibility - Easier integration with existing signing workflows

When to Use Typed Data Signing

Typed data signing is required for the following Rise operations:

Payments

Creating and executing payments

Team Management

Adding/removing team members

Invites

Sending team invitations

Settings

Updating team settings

Permissions

Managing role permissions

Withdrawals

Processing withdrawals

Complete Integration Example

Here’s a complete example showing how to integrate Web3 operations with Rise API using the SDK:

Security Best Practices

Private Keys

  • Never store private keys in client-side code
  • Use environment variables for server-side operations
  • Consider hardware wallets for high-value transactions

Verification

  • Always verify signatures before submitting
  • Check contract addresses and chain IDs
  • Validate typed data structure

Environment

  • Use HTTPS for all API communications
  • Implement proper error handling
  • Log security events for auditing

Timing

  • Respect expiration times in typed data
  • Implement retry logic for failed transactions
  • Monitor transaction status

Error Handling

The SDK provides comprehensive error handling:
Common Web3 errors:

Testing Web3 Integration

For testing, use the staging environment:

Environment Configuration

For the complete list of API URLs for each environment, see our Environments page.

Next Steps

Authentication Guide

Learn how to authenticate with Rise using the SDK

Payment Integration

Complete payment flow with typed data

Team Management

Managing teams with Web3

Invites Integration

User onboarding flow
Need help? Check out our Payment Integration Guide for a complete example of typed data signing in action.