Skip to content
Go Back

Per-account partner fees, micro-deposits, and amount-based fee timing on virtual accounts

Bernardo Simonassi
Bernardo Simonassi
•

Virtual accounts get three upgrades: partner fees can now be set per account instead of one setting for the whole instance, deposits of any size are processed (micro-deposits included), and BlindPay fees are charged on your invoice or at transaction time depending on the deposit amount.

TL;DR

  • New partner_fee_id field on virtual account create and update: pin a partner fee to one account, overriding the instance-wide default
  • Every deposit now creates a payin, including $0.01 account-verification micro-deposits; at least $0.01 always reaches the linked wallet
  • BlindPay fees on deposits below $100.00 accrue to your monthly invoice (billing_fee_amount); deposits of $100.00 and above are charged at transaction time (transaction_fee_amount)

Partner fees per virtual account

Until now, virtual accounts supported a single partner fee for the entire instance: one fee configuration flagged for virtual accounts applied to every account's deposits. You can now pin a fee to each account individually.

Pass partner_fee_id when creating a virtual account, or set it later with the update endpoint:

Bash
curl --request POST \
  --url https://api.blindpay.com/v1/instances/in_000000000000/customers/re_000000000000/virtual-accounts \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "banking_partner": "cfsb",
    "token": "USDC",
    "blockchain_wallet_id": "bw_000000000000",
    "partner_fee_id": "pf_000000000000"
  }'

How the two levels interact:

  • A fee pinned to an account overrides the instance-wide default for that account's deposits.
  • Accounts without a pin keep using the instance-wide default (the fee configuration created with virtual_account_set: true), so existing setups keep working unchanged.
  • Updating an account with partner_fee_id: null clears the pin and falls back to the default.
  • Deleting a fee configuration automatically unpins it from any accounts referencing it; those accounts revert to the default.

The dashboard's virtual account create dialog and edit pane both gained a partner fee selector.

Micro-deposits are now collected

Deposits below $5.00 into a virtual account used to be ignored. Every deposit of any size now creates a payin, including the $0.01 account-verification micro-deposits sent by services like Plaid and Square, and always delivers at least $0.01 of stablecoin to the linked wallet.

Because fees can exceed a small deposit, partner fee collection is now partial rather than all-or-nothing: the fee collects as much as the deposit can bear while preserving the $0.01 delivery floor. A $5.00 fee on a $5.00 deposit collects $4.99; a micro-deposit collects nothing.

When BlindPay fees are charged

BlindPay fees on virtual account deposits now follow an amount-based rule:

Deposit amountWhen the BlindPay fee is chargedField on the payin
Below $100.00End of the billing cycle, on your monthly invoicebilling_fee_amount
$100.00 or moreAt the time of the transaction, deducted from the delivered amounttransaction_fee_amount

This keeps small deposits from being consumed by fees at transaction time while charging larger deposits immediately. Instances configured for end-of-month billing keep accruing every fee to billing_fee_amount, regardless of amount.

What you need to do

Nothing is required. Existing virtual accounts keep their behavior: the instance-wide partner fee still applies to accounts without a pin, and fee totals are unchanged, only the timing of when small-deposit fees are charged moves to the monthly invoice. If you reconcile payins, read both billing_fee_amount and transaction_fee_amount rather than assuming one of them.

To adopt per-account fees, create additional fee configurations and pass partner_fee_id on virtual account create or update.

Learn more

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.