Address and identity stack: PO boxes, virtual addresses, KYC handling

running multiple business entities means you need multiple addresses. not just any addresses, a clean, functional stack where mail actually arrives, KYC verifications pass, and nothing cross-contaminates between entities. this sounds straightforward until you try to open a second Stripe account, register a new LLC, or onboard to a marketplace and realize your home address is already attached to three other things you’d rather not surface.

this tutorial is for operators running multiple stores, agencies, holding companies, or accounts, whether that’s two entities or twenty. it’s not about fraud. every address here should correspond to a real business entity, opened in your name or a co-founder’s. what we’re building is the infrastructure to keep those entities clean, separated, and able to pass the identity checks that every payment processor and platform will throw at you. if you’re also farming airdrops or running DeFi wallets across entities, the same address hygiene logic applies, and airdropfarming.org’s blog covers the wallet side in more depth.

by the end you’ll have a working system: a defined address per entity, mail routed digitally, KYC documents mapped to the right entity, and a repeatable process for spinning up new addresses without creating a mess.

what you need

registered business entities (at least one LLC or equivalent per address tier you want)
USPS account (free) for PO box rental
virtual mailbox account: iPostal1, Anytime Mailbox, or Traveling Mailbox (from $9.99/month)
registered agent service: Northwest Registered Agent or Registered Agents Inc (~$50-$125/year per state)
government-issued ID per person acting as KYC principal, driver’s license + passport recommended
EIN letters for each US entity (IRS CP 575 or 147C)
spreadsheet or Notion database to track address-to-entity mappings
browser profile tool (optional but useful): Multilogin or AdsPower, for managing platform accounts cleanly. see antidetectreview.org/blog for a breakdown of which tools actually work

estimated monthly cost for a 5-entity setup: $80-$200 depending on mailbox tier and registered agent choice.

step by step

step 1: map your entity structure before buying anything

open a spreadsheet. columns: entity name, state of registration, registered agent address, mailing address (PO box or virtual), platform accounts attached to this entity, KYC principal (the human whose ID is used).

do this before spending a dollar. buying addresses without mapping them to entities first creates a mess that’s expensive to unwind. if you have three LLCs and four addresses, you’ll forget which address is on which bank account within two weeks.

expected output: a complete row per entity, even if half the columns are blank stubs you’ll fill in later.

if it breaks: you realize you have entities but no clear KYC principal for some of them. fix this now by deciding whether you’ll use your own ID or bring in a co-founder/director who can provide theirs.

step 2: rent USPS PO boxes for mail-sensitive entities

a USPS PO box costs $19-$75 per six months depending on box size and location. you rent at any post office in person with two forms of ID. you get a street address format (e.g. 123 Main St #456) in most locations, not just a “PO Box 456” format, which matters for forms that reject PO Box inputs.

use PO boxes for entities where you want a physical, government-connected address that won’t disappear if a startup fails. they’re stable, cheap, and USPS is a federal service, so the address is hard to dispute.

one PO box per entity. don’t share boxes across entities. the point is clean separation.

expected output: a physical address for each entity that receives mail and has a unique box number.

if it breaks: your local post office doesn’t offer street-format addresses. check USPS’s “Street Addressing” eligibility tool on their site, or switch to a virtual mailbox for that entity (step 3).

step 3: set up virtual mailboxes for remote-friendly entities

virtual mailboxes scan and email you your mail. you log in, see a digital image of each envelope, and decide to open/scan, shred, or forward. useful for entities where you never need to physically visit.

providers i’ve used: - iPostal1: from $9.99/month, 1,800+ locations including UPS Store addresses - Anytime Mailbox: from $9.99/month, clean UI, good for volume - Traveling Mailbox: $15/month, good customer support

pick an address in a state that makes sense for the entity. if your LLC is Delaware-registered but operating in Texas, a Texas virtual mailbox address is reasonable for correspondence. don’t pick a state at random.

expected output: a digital mailbox with a unique street address, accessible via web or app, with mail scans arriving within one business day.

if it breaks: the address is rejected by a platform because it’s flagged as a virtual mailbox. some platforms (Shopify Payments, Stripe) cross-reference addresses against known virtual mailbox databases. in that case, use a PO box (step 2) or a registered agent address (step 4) instead.

step 4: assign a registered agent per state

if your entity is registered in a state (say Wyoming or Delaware), that state requires a registered agent with a physical in-state address to receive legal documents. this is a legal requirement, not optional.

northwest registered agent is $125/year and includes a real street address, instant document scanning, and compliance alerts. registered agents inc is around $50/year for similar features. i’ve used northwest and found their scanning reliable.

don’t use your home address or a shared virtual mailbox as your registered agent address. registered agent addresses are public record in most states, so using your home means your home address is on the state’s business database.

expected output: a registered agent address per state per entity, appearing on your articles of incorporation and state records.

if it breaks: you forgot to update the registered agent when renewing, and the state sends lapse notices. set a calendar reminder 60 days before your registered agent renewal date.

step 5: build your address-to-entity map completely

go back to your spreadsheet. fill in every column for every entity. it should now look like:

entity	state	registered agent	mailing address	KYC principal	platforms
Apex LLC	WY	Northwest RA	iPostal1 Dallas	Xavier Fok	Shopify, Stripe
Ridge Media LLC	DE	Northwest RA	USPS PO Box 112	Jane Co-founder	Amazon, PayPal

this becomes your source of truth. when you open a new account, check the map first. never assign an address to an account that doesn’t match what’s in this table.

expected output: a complete mapping you can hand to an accountant or co-founder without explanation.

if it breaks: you realize some entities share addresses. separate them before running KYC on those platforms. platform KYC systems look for address collisions.

step 6: prepare KYC document packages per entity

KYC, or know-your-customer, is what every payment processor and regulated platform runs when you open an account. FinCEN’s beneficial ownership rules now require disclosure of real beneficial owners for most US entities, so there’s no legitimate way to hide who owns what. work with that, not against it.

per entity, prepare a folder with: - government-issued ID of the KYC principal (passport preferred, driver’s license as backup) - EIN confirmation letter (IRS CP 575 or request a 147C by calling 1-800-829-4933) - articles of incorporation or certificate of formation - operating agreement showing ownership percentages - proof of address for the business (utility bill at the mailing address, or bank statement)

a common mistake: using a virtual mailbox address as proof of address but not having any statements mailed there. get at least one bill or bank statement sent to each address before you run KYC on a major platform.

expected output: a ready KYC folder per entity, organized so you can upload documents quickly when a platform asks.

if it breaks: the platform rejects a virtual mailbox address as proof of business address. use the registered agent address or a PO box instead, and get a bank statement sent there.

step 7: run KYC submissions strategically

don’t run KYC for five entities in one afternoon on the same platform. space submissions out. if you’re opening five Stripe accounts across five entities, do one per week. this avoids triggering velocity flags in the platform’s fraud detection.

for each submission: use the entity’s dedicated browser profile (or at minimum, a clean browser session with no other entity’s cookies present). log in with the entity’s dedicated email. upload documents from the KYC folder you prepared in step 6.

for platforms using third-party KYC vendors (Persona, Stripe Identity, Onfido), the verification is usually automated. have good lighting if a selfie is required. document photos should be flat, no glare, full corners visible.

expected output: approved KYC status per entity per platform, each tied to the correct address and documents.

if it breaks: a KYC submission is rejected without clear reason. contact support with reference to your EIN letter and articles of incorporation. automated rejections are often reversible with a human review request.

step 8: document and version your stack

every time you add an entity, a new address, or a new platform, update the spreadsheet. add the date. if an address changes (registered agent switches, mailbox provider shuts down), note the old and new address and update every platform account that used the old one.

treat this like infrastructure, not a one-time setup.

common pitfalls

reusing addresses across entities. this is the most common mistake. one address shared between two LLCs on the same payment platform will eventually trigger a review. keep addresses 1:1 with entities.

not receiving mail before KYC. virtual mailbox addresses that have received zero mail are harder to verify. open the account and forward one piece of mail there before running KYC.

confusing registered agent address with mailing address. your registered agent address is for legal service. your mailing address is for correspondence. they can be different. keep them tracked separately.

using expired IDs for KYC. platforms check document expiry dates automatically. a passport expiring in 60 days will fail some KYC systems. use your most current document.

forgetting to update platforms when addresses change. if your registered agent or mailbox address changes, every bank, payment processor, and marketplace tied to that entity needs to be updated. set a task when you change any address.

scaling this

10 entities: the spreadsheet system works fine. one virtual mailbox account can handle multiple addresses through sub-plans on providers like iPostal1.

100 entities: you need a database, not a spreadsheet. Notion with linked databases, or Airtable, works well. you’ll also need a consistent naming convention for entities, folders, and email aliases. consider a dedicated registered agent that offers volume pricing.

1000 entities: at this scale you’re looking at operational overhead that warrants dedicated staff. you’ll also be hitting the attention thresholds of platform trust and safety teams. the setup principles don’t change but the review and renewal processes need to be systematized with automated reminders and audit logs. this is also the scale where entity structure becomes a serious legal and tax question, which needs a business attorney. this is not legal advice.

where to go next

Multi-entity banking setup for operators covers how to open business bank accounts for each entity without triggering SAR flags
Business registration stack for multi-account operators walks through choosing between Wyoming, Delaware, and New Mexico for LLC registration costs and privacy
Back to the blog index for the full tutorial library

Written by Xavier Fok

disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-05-19.