Delaware LLC for RevenueCat Subscription App Management: 2026 complete setup guide

Why RevenueCat Subscription App Management requires a US LLC

RevenueCat Subscription App Management is part of the app store category. Non-resident founders typically need a US business entity to operate on this platform because of payment routing, KYC requirements, and tax reporting obligations. A Delaware LLC is the standard choice for this use case for the same reasons it dominates Delaware formation generally: case-law depth, US-counterparty recognition, and 6 Del. C. § 18-201 allowing non-resident ownership without restriction.

For RevenueCat Subscription App Management specifically: the platform's onboarding requires an EIN (the LLC's federal tax ID), a US bank account or compatible alternative, and identity verification of the entity beneficial owner. The 8-10 business day Delewarellc formation timeline produces all three: filed Certificate of Formation, EIN via Form SS-4, and applications submitted to 4-5 banks.

Payment routing for RevenueCat Subscription App Management

RevenueCat does not process payments directly; it manages subscription analytics across App Store and Google Play. Underlying payments routed via App Store / Play store payouts.

Banking fit for RevenueCat Subscription App Management

Mercury, Wise Business, or Payoneer for app-store payouts.

Delewarellc applies to 4-5 banks per customer (Mercury, Wise, Relay, Lili, Payoneer) so at least one approval clears the operational requirement. The country-by-country approval pattern is documented on the banking guide; the multi-bank framework is on the 4-Bank Application Strategy page.

Tax considerations for RevenueCat Subscription App Management

App store payouts handled per App Store / Play store taxation. Apple and Google withhold per W-8BEN-E.

Step-by-step setup for RevenueCat Subscription App Management

1. Form Delaware LLC, obtain EIN.
2. Set up App Store and Google Play developer accounts with LLC.
3. Connect RevenueCat for cross-platform subscription analytics.
4. Configure payment integrations.

Pitfalls to avoid on RevenueCat Subscription App Management

• RevenueCat is paid above free tier; budget per MAU.
• RevenueCat is analytics layer; underlying payment system is App Store / Play store.

Country-specific notes

Mobile app developers globally.

How RevenueCat Subscription App Management fits into the broader Delaware LLC structure

The Delaware LLC is the foundation; RevenueCat Subscription App Management is one of the platforms it operates on. Most non-resident bootstrap founders start with a single platform, then expand to multiple. The same Delaware LLC can hold accounts on Amazon Seller Central, Stripe, Shopify, and many other platforms simultaneously. The 4-5 bank applications submitted at formation cover the operational banking layer for any of these platforms.

The Year 1 cost to Delewarellc is $407 ($297 + $110 Delaware state fee). Year 2+ recurring is approximately $400-$900 per year depending on CPA fees and registered agent choice. RevenueCat Subscription App Managementoperational fees are separate and depend on the platform's own pricing model.

Does RevenueCat pay you, or does the money come from somewhere else?

This is the single most important thing to understand before you form a company for a RevenueCat app, because it changes which accounts you actually need. RevenueCat does not process payments and does not pay you. It is a subscription management and analytics layer that sits on top of the App Store and Google Play. When a user buys a subscription inside your app, Apple or Google collects the money, takes its store commission, and pays the remaining balance to the developer account that owns the app. RevenueCat reads that purchase data through the store APIs so you can see retention, churn, trial conversion, and revenue across both platforms in one dashboard. The cash itself never touches RevenueCat.

What this means in practice is that your Delaware LLC needs to be the account holder on Apple and Google, not on RevenueCat, for the money to land in a US business bank account. RevenueCat connects to your stores using API keys and shared secrets, so once your developer accounts are owned by the LLC, RevenueCat simply mirrors that ownership through read access. You can register your RevenueCat account under the LLC name for tidiness, but the payout chain runs Apple to bank and Google to bank. Treat RevenueCat as the measurement and entitlement engine, and treat the App Store and Google Play developer accounts as the entities that hold and disburse your revenue. Getting this distinction right up front saves you from looking for a payout setting inside RevenueCat that does not exist.

What does a non-US founder need from a Delaware LLC to run a RevenueCat app?

Because the real payers are Apple and Google, the documents your Delaware LLC needs are the ones those stores ask for, plus the basics every US company carries. You will need a federal EIN to open developer accounts and a US bank account, a US business bank account or fintech account to receive store payouts, and a completed W-8BEN-E if the LLC is owned by a non-resident and treated as a foreign person for US tax. The W-8BEN-E is what tells Apple and Google that the beneficial owner is outside the United States, which controls how much, if any, US tax they withhold on your payouts. Without it, a store may apply a default backup withholding rate that is far higher than your treaty rate.

The EIN is free directly from the IRS using Form SS-4, and for a non-resident applicant without an SSN it typically arrives in about 8 to 10 business days by fax or mail. You do not need to pay a third party for the number itself. Here is the short list of what to assemble before you ever open a store account:

• Delaware certificate of formation and your LLC's legal name.
• Federal EIN confirmation letter (CP 575 or 147C).
• A US business bank or fintech account that accepts ACH and wire from Apple and Google.
• A signed W-8BEN-E for the LLC if the owner is a non-resident, or a W-9 if the owner is a US person.
• A US address for the developer account, which can be your registered agent or a business mail address.

Which banks connect cleanly to App Store and Google Play payouts behind RevenueCat?

The record for this platform points to Mercury, Wise Business, or Payoneer for app-store payouts, and that lines up with how Apple and Google actually pay. Mercury is a popular choice for non-resident-owned Delaware LLCs because it is built for startups, opens fully online with an EIN and formation documents, and gives you USD account and routing numbers that Apple and Google can pay by ACH. Wise Business is strong when you want to hold and convert multiple currencies, which matters because Google Play often pays in the currency of the developer's registered region, and Wise lets you receive in USD and move funds home at the mid-market exchange rate with a transparent fee.

Payoneer is the third option named in the record and is useful when a founder's home country has limited support at the other two, since Payoneer reaches a wide set of countries and integrates with marketplace payouts. Relay and Lili are also common US business banking choices for Delaware LLCs and can receive ACH payouts the same way, though they are not the ones called out for this platform. Whichever you pick, confirm two things before you wire your store accounts to it: that the account is in the LLC's exact legal name so Apple and Google can match the payee, and that it accepts USD ACH credits without holding or rejecting business transfers from large technology companies. A name mismatch between the bank and the store developer account is one of the most common reasons a first payout stalls.

What US tax forms will Apple and Google issue, and what do they mean for a non-resident?

Since RevenueCat is not the payer, you will not receive a tax form from RevenueCat. The forms come from the stores. Apple and Google both collect a W-8BEN-E from foreign developers and withhold US tax based on it, applying any reduced rate available under a tax treaty between the United States and your country of residence. At year end, US-source income paid to a foreign person is generally reported on Form 1042-S, which shows the gross amount paid and the US tax withheld. For a non-resident owner of a single-member Delaware LLC, this is the form that documents what was withheld so you can reconcile it on a US filing or claim a foreign tax credit at home.

If your LLC were instead owned by a US person, the relevant document would be a 1099-K style report of gross transaction volume rather than a 1042-S. The practical point for the typical reader here, a founder outside the United States, is that a correctly filed W-8BEN-E can lower or eliminate the withholding on your app revenue, and the 1042-S is your proof of what happened. Apple in particular distinguishes between US sales and rest-of-world sales for withholding purposes, so the form you see may only reflect the US portion of your revenue. Keep every 1042-S and your filed W-8BEN-E together, because they support the federal filings a foreign-owned LLC must make regardless of whether any tax was due.

How do you actually connect a RevenueCat app to a Delaware LLC, step by step?

The order of operations matters because each store account depends on the one before it. The record lays out the spine of the process: form the Delaware LLC and obtain the EIN, set up App Store and Google Play developer accounts under the LLC, connect RevenueCat for cross-platform subscription analytics, then configure the payment integrations. The reason you form the company and get the EIN first is that both Apple and Google ask for a legal business entity and a tax identification number when you enroll an organization account, and you cannot complete enrollment cleanly without them. Once the LLC exists and has its EIN, you open the bank account so payouts have somewhere to land.

With the company, EIN, and bank ready, the connection sequence looks like this:

• Enroll the Apple Developer Program as an organization using the LLC name and EIN, and obtain a D-U-N-S number for the entity if Apple requests one.
• Register a Google Play Developer account under the same LLC and verify the business details.
• Enter your bank and tax information in App Store Connect and Google Play Console, including the W-8BEN-E.
• Create a RevenueCat project and add your apps, then paste the App Store and Play store API keys and shared secrets so RevenueCat can read purchase events.
• Define products and entitlements in RevenueCat that map to the subscriptions you created in each store.

What does RevenueCat cost, and how does that fit a non-resident budget?

The record is clear that RevenueCat is paid above its free tier and that you should budget per monthly active user, so plan for the analytics layer as a recurring software cost rather than a flat fee. The free tier covers smaller apps, and once your tracked revenue or active users cross the threshold the platform charges based on usage. For a founder modeling a launch, the safe approach is to treat RevenueCat pricing as a percentage of the revenue it manages above the free allowance, and to revisit it as your subscriber base grows. The record does not state a specific dollar figure, so size it against your own projected active users rather than a guess.

Stack that against the costs of the company itself, which are fixed and knowable. Forming the Delaware LLC through this service is $110, and our one-time setup is $297. Delaware charges a flat $300 annual franchise tax for an LLC, due June 1 each year, which is a fixed line item unrelated to how much your app earns. The EIN is free from the IRS. The larger variable costs are the store commissions Apple and Google deduct before they pay you, which sit outside both RevenueCat and your LLC. When you total these, the company overhead is small and predictable, the store commission is the big slice, and RevenueCat is a usage-based tool you can keep on the free tier until your subscriber count justifies upgrading.

Which countries can run this, and what causes store accounts to get rejected?

The record describes the audience simply as mobile app developers globally, and that is accurate because RevenueCat itself imposes no country restriction. The gating factors are the App Store and Google Play developer programs, not RevenueCat. Apple and Google both accept organization accounts from a wide range of countries, but the country you can register from and the payout currency you receive depend on the store's supported regions. Forming a Delaware LLC sidesteps a lot of this by giving you a US entity, a US EIN, and a US bank account, which together let you enroll as a US-based organization regardless of where you personally live.

Rejections usually trace back to mismatched or incomplete identity and payout data rather than RevenueCat. Common causes include:

• A developer account name that does not match the LLC name on the bank account, so a payout cannot be matched.
• A missing or expired W-8BEN-E, which triggers higher default withholding or a payout hold.
• An incomplete D-U-N-S record or unverified business address during Apple organization enrollment.
• Tax interview fields left blank in App Store Connect or Google Play Console.
• A bank account that rejects or holds inbound business ACH from large technology companies.

Why does the LLC own the developer accounts instead of RevenueCat?

It helps to picture the ownership graph. The Delaware LLC is the legal entity at the top. It owns the Apple Developer organization account and the Google Play Developer account, and those are the accounts that hold your app listings and receive money. RevenueCat connects sideways into both stores using API keys, reading subscription events so it can report entitlements, trials, and revenue. So the LLC is the owner and payee, the stores are the cashiers, and RevenueCat is the dashboard. Nothing about your money flow runs through RevenueCat, which is exactly why you register the LLC with Apple and Google rather than expecting RevenueCat to be where you enter banking details.

This structure has a practical benefit for a non-resident founder. Because the LLC owns the store accounts, you can change who manages the app, add team members, or even sell the business by transferring the entity, without disturbing the payment relationships. RevenueCat keys can be rotated or revoked at any time because they only grant read access to purchase data, so your subscription analytics layer is decoupled from your revenue. If you ever migrate off RevenueCat to another analytics provider, your App Store and Google Play accounts and their payout settings stay exactly where they are. Keeping the company as the durable owner and treating RevenueCat as a swappable tool is the cleanest way to run this over the long term.

How does App Store and Google Play withholding affect what actually reaches your bank?

Two deductions stand between a subscriber's payment and your bank balance, and neither is RevenueCat. The first is the store commission, which Apple and Google take from every transaction before they calculate your payout. The second is US tax withholding on the portion of your revenue treated as US-source income, which is set by your W-8BEN-E and any applicable treaty. For a non-resident-owned LLC, the W-8BEN-E is what lets the stores apply your treaty rate instead of a flat default, so filing it correctly is the lever that most directly increases what reaches your account.

The record notes that Apple and Google withhold per W-8BEN-E, which is the form you submit during each store's tax interview. Apple generally separates US sales from rest-of-world sales, applying US withholding only to the US portion, while sales to users in other countries are handled under those countries' rules. Google Play similarly runs a tax interview and applies withholding based on the documentation you provide. The result is that your reported RevenueCat revenue, which is gross, will be larger than the cash that lands in your bank, because store commission and any withholding come out along the way. When you reconcile, compare the gross figure in RevenueCat against the net payouts in App Store Connect and Google Play Console and the withholding shown on any 1042-S, so you always know where each slice went.

What US filings does a foreign-owned Delaware LLC owe even with all revenue from the stores?

Running your revenue through Apple and Google does not remove your federal filing duties. A Delaware LLC owned by a single non-resident is, by default, a disregarded entity that is also foreign-owned, which triggers a specific annual filing: Form 5472 paired with a pro forma Form 1120. This applies even if the LLC owes no US income tax, because the filing reports transactions between the foreign owner and the US company rather than profit. The penalty for failing to file Form 5472 is $25,000, so this is the one deadline a non-resident app founder cannot afford to overlook, regardless of how the store handled withholding.

Separately, Delaware charges its flat $300 annual franchise tax for the LLC, due June 1 each year, which is an entity fee and not an income tax. One administrative burden you can set aside is beneficial ownership reporting: under the FinCEN interim final rule issued March 26 2025, US-formed entities such as a Delaware LLC are exempt from BOI reporting, so a domestic LLC owned by a foreign founder does not file a beneficial ownership report. Keep your 1042-S forms, your filed W-8BEN-E, and your store payout statements organized through the year, because the federal 5472 and 1120 filing draws on the same records that document how Apple and Google paid your RevenueCat-managed app.

How should you map RevenueCat products to your store subscriptions and your LLC accounting?

RevenueCat works by mapping the in-app products you create in the App Store and Google Play to entitlements your app checks at runtime. For your LLC accounting to stay clean, set up that mapping so every paying entitlement traces back to a specific store product and therefore a specific payout line. When you define products and offerings in RevenueCat, name them in a way that matches the product identifiers in App Store Connect and Google Play Console, so that when you reconcile a month you can line up RevenueCat's revenue report against the two stores' payout reports without guessing which subscription drove which dollar.

This discipline pays off at tax time and at bank reconciliation. Because the LLC receives two separate payout streams, one from Apple and one from Google, your bookkeeping should record each store as its own income source, with RevenueCat serving as the cross-platform total that should roughly equal the sum of both before commission and withholding. Keep these records aligned:

• RevenueCat gross revenue by product, used as your top-line subscription figure.
• App Store Connect net payouts, after Apple commission and any US withholding.
• Google Play Console net payouts, after Google commission and any withholding.
• Bank deposits in the LLC account, matched to each store payout cycle.
• 1042-S forms, tying reported withholding back to the gross US-source revenue.