- Platform-level accounts: Hold pooled funds for your platform operations (rewards distribution, reconciliation, etc.)
- Customer accounts: Hold individual customer funds for their transactions
Internal accounts are automatically created when you onboard a customer, based
on your platform’s currency configuration. Platform-level internal accounts
are created when you configure your platform with supported currencies.
How internal accounts work
Internal accounts act as an intermediary holding account in the payment flow:- Deposit funds: You or your customers deposit money into internal accounts using bank transfers (ACH, wire, PIX, etc.) or crypto transfers
- Hold balance: Funds are held securely in the internal account until needed
- Send payments: You initiate transfers from internal accounts to external destinations
- Is denominated in a single currency (USD, EUR, etc.)
- Has a unique balance that you can query at any time
- Includes unique payment instructions for depositing funds
- Supports multiple funding methods depending on the currency
Retrieving internal accounts
List customer internal accounts
To retrieve all internal accounts for a specific customer, use the customer ID to filter the results:Request internal accounts for a customer
Response
Response
Filter by currency
You can filter internal accounts by currency to find accounts for specific denominations:List platform internal accounts
To retrieve platform-level internal accounts (not tied to individual customers), use the platform internal accounts endpoint:Platform internal accounts are useful for managing pooled funds, distributing
rewards, or handling platform-level operations.
Understanding funding payment instructions
Each internal account includesfundingPaymentInstructions
that tell your customers how to deposit funds. The structure varies by payment rail and currency:
US ACH or wire transfers
US ACH or wire transfers
For USD accounts, instructions include routing and account numbers:
Each internal account has unique banking details in the
bankAccountInfo
field, which ensures deposits are automatically credited to the correct
account.SEPA EUR transfers
SEPA EUR transfers
For EUR accounts, instructions use SEPA IBAN numbers:
Spark Stablecoin Funding
Spark Stablecoin Funding
For stablecoin accounts, instructions use Spark wallet addresses:
Checking account balances
The internal account balance reflects all deposits and withdrawals. The balance includes:- amount: The balance amount in the smallest currency unit (cents for USD, centavos for MXN/BRL, etc.)
- currency: Full currency details including code, name, symbol, and decimal places
Example balance check
Fetch the balance of an internal account
Response
Response
Always check the
decimals
field in the currency object to correctly convert
between display amounts and API amounts. For example, USD has 2 decimals, so
an amount of 50000 represents $500.00.Displaying funding instructions to customers
When customers need to deposit funds themselves, display the funding payment instructions in your application:1
Retrieve the internal account
Fetch the customer’s internal account for their desired currency using the API.
2
Extract payment instructions
Parse the
fundingPaymentInstructions
array and select the appropriate instructions based on your customer’s preferred payment method.3
Display instructions clearly
Show the payment details prominently in your UI:
- Account holder name
- Bank name and routing information (account/routing number, CLABE, PIX key, etc.)
- Reference code (if provided)
- Any additional notes from
instructionsNotes
The unique banking details in each internal account automatically route
deposits to the correct destination.
4
Monitor for deposits
Set up webhook listeners to receive notifications when deposits are credited to the internal account. The account balance will update automatically.
You’ll receive
ACCOUNT_STATUS
webhook events when the internal account balance changes.Best practices
Display complete funding instructions
Display complete funding instructions
Ensure your customers have all the information needed to make deposits. Consider implementing:
- Clear display of all banking details from
fundingPaymentInstructions
- Copy-to-clipboard functionality for account numbers and reference codes
- Email/SMS confirmations with complete deposit instructions
Monitor account balances proactively
Monitor account balances proactively
Set up monitoring to alert customers when their balance is low:
Handle multiple currencies efficiently
Handle multiple currencies efficiently
If your platform supports multiple currencies, organize internal accounts by currency in your UI:
Cache account data appropriately
Cache account data appropriately
Internal account details (especially funding instructions) rarely change, so you can cache them safely. However, always fetch fresh balance data before initiating transfers.
Using internal accounts for ramps
Internal accounts play a critical role in both on-ramp and off-ramp flows:For on-ramps (Fiat → Crypto)
Internal accounts are optional for on-ramp flows using just-in-time (JIT) funding:- JIT funding: Quotes provide payment instructions directly; funds flow through without requiring an internal account
- Pre-funded model: Deposit fiat to internal account first, then create and execute conversion quotes
Most on-ramp implementations use JIT funding to avoid holding customer
balances and simplify compliance.
For off-ramps (Crypto → Fiat)
Internal accounts are essential for off-ramp flows:- Deposit crypto: Transfer Bitcoin or stablecoins to the internal account
- Hold balance: Crypto balance is held securely until conversion
- Execute conversion: Create and execute quote to convert crypto to fiat and send to bank account
Off-ramps require pre-funded internal accounts with crypto balances. Grid
supports Fiat, BTC, and Stablecoin deposits.
Crypto funding for internal accounts
For off-ramp operations, fund internal accounts with cryptocurrency:Bitcoin (Lightning Network)
Internal accounts can receive Bitcoin via Lightning Network:- Spark address: Reusable address for multiple deposits
- Lightning invoice: Single-use invoice for specific amounts
Lightning Network transfers are typically instant and have minimal fees,
making them ideal for crypto deposits.
Stablecoins
Internal accounts can also receive stablecoins via Lightning Network or Spark:Stablecoins like USDB are 1:1 pegged to USD, offering price stability for
off-ramp balances while maintaining instant settlement via Lightning Network.
Multi-currency balances
Internal accounts support both fiat and crypto balances:Example: Account with USD and BTC
Always check the
decimals
field when working with balances. USD uses 2
decimals (cents), while BTC uses 8 decimals (satoshis).Monitoring account balance changes
Subscribe toACCOUNT_STATUS
webhooks to receive real-time balance updates:
Balance updates are triggered by: - Incoming deposits (fiat or crypto) - Quote
executions (funds debited) - Failed transaction reversals (funds credited
back)
Ramp-specific use cases
Pre-funding for off-ramps
Maintain crypto balances for instant fiat conversions:Platform treasury management
Use platform-level internal accounts for pooled liquidity:Platform internal accounts enable centralized treasury management for
high-volume ramp operations.
Best practices for ramps
Choose the right funding model
Choose the right funding model
- On-ramps: Use JIT funding to avoid holding customer fiat
- Off-ramps: Pre-fund with crypto for instant fiat conversions
- High volume: Consider platform-level accounts for pooled liquidity
Monitor crypto price exposure
Monitor crypto price exposure
Implement balance alerts
Implement balance alerts
Set up proactive notifications for low balances:
Next steps
- External Accounts - Configure destination accounts for conversions
- Plaid Integration - Connect bank accounts via Plaid
- Fiat-to-Crypto Conversion - Build conversion flows
- Webhooks - Handle real-time notifications
Related resources
- Platform Configuration - Configure supported currencies
- Sandbox Testing - Test funding and conversions safely
- API Reference - Complete API documentation