Named Virtual Accounts and API Pagination

Published on April 10, 2025.

BlindPay delivered the most-requested account features in April, including support for named virtual accounts, a revamped terms of service workflow, and cursor-based pagination across core endpoints.

TL;DR

  • US named accounts
  • Terms of Service API (breaking changes)
  • Pagination (breaking changes)

Named Virtual Accounts powered by JPMorgan Chase

BlindPay can issue named virtual accounts backed by JPMorgan Chase infrastructure. This unlocks customer-facing account numbers that display your client's business or individual name instead of BlindPay. We are already onboarding beta testers—reach out to us if you want early access or pricing details.

Terms of Service API (breaking changes)

For compliance reasons every receiver must accept BlindPay’s terms of service before you can create payouts or payins on their behalf. Update your onboarding flow to capture the tos_id returned by the Terms of Service endpoint and persist it when you create receivers. All receivers must complete this step by May 30 to avoid disruptions.

Pagination (breaking changes)

The /payins and /payouts endpoints now support cursor pagination with the limit, starting_after, and ending_before parameters. The legacy pagination response will be deprecated on June 30. Review the new parameters in the API reference and add the receiver_id query filter where needed to segment results by customer.

We also added the first filter related to receivers, so you can pass the receiver_id on the query parameter as well.