[{"data":1,"prerenderedAt":140},["ShallowReactive",2],{"content-\u002Fchangelog\u002F2025-04-10-us-named-accounts":3},{"id":4,"title":5,"author":6,"body":7,"categories":6,"category":123,"categoryType":124,"date":125,"description":126,"extension":127,"faq":6,"howto":6,"isBlog":128,"isChangelog":129,"meta":130,"navigation":129,"path":135,"rawbody":136,"seo":137,"stem":138,"thumbnail":6,"__hash__":139},"content\u002Fchangelog\u002F2025-04-10-us-named-accounts.md","Named Virtual Accounts and API Pagination",null,{"type":8,"value":9,"toc":115},"minimark",[10,14,19,32,36,50,53,70,73,109],[11,12,13],"p",{},"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.",[15,16,18],"h2",{"id":17},"tldr","TL;DR",[20,21,22,26,29],"ul",{},[23,24,25],"li",{},"US named accounts",[23,27,28],{},"Terms of Service API (breaking changes)",[23,30,31],{},"Pagination (breaking changes)",[15,33,35],{"id":34},"named-virtual-accounts-powered-by-tier-1-bank-in-the-us","Named Virtual Accounts powered by Tier 1 Bank in the US",[11,37,38,39,43,44,49],{},"BlindPay can issue ",[40,41,42],"strong",{},"named"," virtual accounts backed by Tier 1 Bank in the US. This unlocks customer-facing account numbers that display your client's business or individual name instead of BlindPay. We are already onboarding beta testers—",[45,46,48],"a",{"href":47},"mailto:hello@blindpay.com","reach out to us"," if you want early access or pricing details.",[15,51,28],{"id":52},"terms-of-service-api-breaking-changes",[11,54,55,56,60,61,65,66,69],{},"For compliance reasons every customer must accept BlindPay’s terms of service before you can create payouts or payins on their behalf. Update your onboarding flow to capture the ",[57,58,59],"code",{},"tos_id"," returned by the ",[45,62,64],{"href":63},"\u002Fdocs\u002Fessentials\u002Fterms-of-service","Terms of Service endpoint"," and persist it when you create customers. All customers must complete this step by ",[40,67,68],{},"May 30"," to avoid disruptions.",[15,71,31],{"id":72},"pagination-breaking-changes",[11,74,75,76,79,80,83,84,87,88,91,92,95,96,99,100,104,105,108],{},"The ",[57,77,78],{},"\u002Fpayins"," and ",[57,81,82],{},"\u002Fpayouts"," endpoints now support cursor pagination with the ",[57,85,86],{},"limit",", ",[57,89,90],{},"starting_after",", and ",[57,93,94],{},"ending_before"," parameters. The legacy pagination response will be deprecated on ",[40,97,98],{},"June 30",". Review the new parameters in the ",[45,101,103],{"href":102},"\u002Fdocs\u002Fessentials\u002Fpayouts#create-a-payout","API reference"," and add the ",[57,106,107],{},"customer_id"," query filter where needed to segment results by customer.",[11,110,111,112,114],{},"We also added the first filter related to customers, so you can pass the ",[57,113,107],{}," on the query parameter as well.",{"title":116,"searchDepth":117,"depth":117,"links":118},"",2,[119,120,121,122],{"id":17,"depth":117,"text":18},{"id":34,"depth":117,"text":35},{"id":52,"depth":117,"text":28},{"id":72,"depth":117,"text":31},"Product Update","update","2025-04-10","Premium named virtual accounts powered by tier 1 banks displaying your client's business or individual name, mandatory terms of service acceptance workflow for all customers with compliance requirements, and cursor-based pagination across all core API endpoints with enhanced filtering capabilities.","md",false,true,{"excerpt":131},{"type":8,"value":132},[133],[11,134,13],{},"\u002Fchangelog\u002F2025-04-10-us-named-accounts","---\ntitle: Named Virtual Accounts and API Pagination\ndescription: Premium named virtual accounts powered by tier 1 banks displaying your client's business or individual name, mandatory terms of service acceptance workflow for all customers with compliance requirements, and cursor-based pagination across all core API endpoints with enhanced filtering capabilities.\ndate: 2025-04-10\ncategory: Product Update\ncategoryType: update\nisChangelog: true\n---\n\nBlindPay 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.\n\n\u003C!--more-->\n\n## TL;DR\n\n- US named accounts\n- Terms of Service API (breaking changes)\n- Pagination (breaking changes)\n\n## Named Virtual Accounts powered by Tier 1 Bank in the US\n\nBlindPay can issue **named** virtual accounts backed by Tier 1 Bank in the US. 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](mailto:hello@blindpay.com) if you want early access or pricing details.\n\n## Terms of Service API (breaking changes)\n\nFor compliance reasons every customer 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](\u002Fdocs\u002Fessentials\u002Fterms-of-service) and persist it when you create customers. All customers must complete this step by **May 30** to avoid disruptions.\n\n## Pagination (breaking changes)\n\nThe `\u002Fpayins` and `\u002Fpayouts` 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](\u002Fdocs\u002Fessentials\u002Fpayouts#create-a-payout) and add the `customer_id` query filter where needed to segment results by customer.\n\nWe also added the first filter related to customers, so you can pass the `customer_id` on the query parameter as well.\n",{"title":5,"description":126},"changelog\u002F2025-04-10-us-named-accounts","yvTxmNykkqsUH0Xo1nfNfXyI5usVaKGlYClK4vH8_JI",1785890525751]