Advertiser and Payer Verification for Taiwan Ads (September 2026)
Ads targeting Taiwan must disclose an advertiser and a payer, and that verification now happens on the business portfolio and the ad account, not on the Page. The result no longer carries across accounts automatically, so in most cases every ad account you run Taiwan traffic from has to be verified separately.
The Page-level entry point is gone, and a verification no longer carries across accounts on its own. This covers which layer still verifies, what documents actually matter, why buying a pre-verified Page has stopped working, and how per-account verification changes your budget.
The short version:
- Taiwan ads must disclose an advertiser and a payer. This is a published Meta requirement, not a risk-control glitch.
- Verification happens on the business portfolio and the ad account. The Page is no longer the entry point.
- A verification no longer carries across accounts by itself — budget for verifying each ad account separately.
Point one can be checked against Meta's own documentation. Points two and three come from field reports by practitioners between August and September 2026. Each section below says which is which, because the two kinds of claim carry different weight and call for different responses.
1. Why Taiwan triggers verification
This is not a sign that something is wrong with your account. Meta's own page on advertiser and payer transparency lists the places where disclosure is required: the EU, Singapore, Taiwan, Australia and India. Target Taiwan and the requirement applies.
Two terms, because the interface wording changed:
| Term | In plain words | Note |
|---|---|---|
| Advertiser | Whose product or service the ad promotes | Called "beneficiary" before March 2026; same thing |
| Payer | Who actually pays for the ad | Usually the same entity as the advertiser |
If you run ads for clients, the official definition is explicit: the advertiser is your client, not you. That field gets filled in wrong constantly in agency setups, and wrong means rejected.
2. Which layer actually gets verified
Four layers come up in any discussion of this: the personal profile, the business portfolio (commonly called the BM), the ad account, and the Page. Separating documented behaviour from field reports matters here.
Documented: what gets verified is an entity — the advertiser and the payer — not an asset. Once verified, that entity appears in the dropdown when you build an ad. To run the verification you need at least partial admin access to the ad account (admin or advertiser level), and if the ad account sits inside a business portfolio, you must be in that portfolio too.
Field reports: since August 2026, starting Taiwan verification from a Page redirects into the business portfolio, so the Page entry point is effectively closed; over the same period, previously verified Pages have been lapsing. By early September the reports get sharper — for many people only ad-account-level verification still goes through.
So the working order is business portfolio → ad account. If you are still hunting for the button on the Page, the button is not there. If those layers are unfamiliar, read what a Business Manager is and how ad accounts work first.
3. Where "one verification per account" comes from
This is the section that costs money, so it gets the detail.
The old experience was that one verification covered new Pages and new accounts under the same profile. The current reports say otherwise: ad account A is verified, and ad account B in the same business portfolio still shows no advertiser to select.
Meta's documentation actually accounts for this. The stated condition for reusing someone's verification is that the account which completed it holds at least partial admin access on the ad account in question, and that you are inside the same business portfolio. In other words, reuse depends on the permission relationship, not on the fact that a verification exists somewhere. Inheritance used to look automatic because the old permission structures happened to satisfy the condition.
The practical conclusion: plan for every new ad account to need its own verification. That turns verification from a one-off cost into a per-account cost, which is a different line in the budget.
4. Why buying a pre-verified Page has stopped working
It was the standard workaround for a year. Three problems now stack up:
They lapse. Between late August and early September 2026 verified Pages and accounts lapsed in batches. You pay once for a status that expires with no guaranteed lifetime.
Running ads from one makes lapsing more likely. The consistent advice in practitioner circles is to keep a verified Page as a held asset and never run ads from it. That is a usage restriction, and it is not printed next to the price.
It does not solve section 3. A Page's verified status will not make the advertiser dropdown appear for a different ad account. You can buy one and still face per-account work.
We retired our own Taiwan region-verified Page product in September 2026 for exactly these three reasons. Selling something that lapses, carries a usage restriction and does not solve the core problem only generates support tickets later.
5. Documents and common failures
Rules first, field reports second.
| What you verify | Documented requirement | Where it goes wrong |
|---|---|---|
| An individual | Government-issued ID | Name and date of birth must match the account details |
| An organisation | Meta checks third-party databases first and asks for official company documents only when there is no match | Company name, registration number and address all have to agree |
Three things worth knowing from the field:
Review got slower. Two to three days was normal before July 2026. Since August, more than ten days still in review is a common report. Treat it as a risk, not a scheduled step, and never leave it until the day before launch.
The usual failure message is "we can't verify based on the information provided." It gives almost nothing away, but the reports point at inconsistent information rather than a wrong submission route. Resending the same set rarely helps.
No document type is a guaranteed pass. Local IDs, foreign IDs and company papers all have both successes and failures behind them. Anyone promising a specific document always works is selling you a story.
6. The order to do it in
- Check the deadline. Notices come in three flavours: no deadline, a deadline, and ads already paused. The third needs handling today; the first two can be scheduled.
- Decide who is being verified. Advertiser and payer are usually the same entity. If they differ, verify both. For agency work, the advertiser is the client.
- Fix the permissions first. The verifying account needs admin or advertiser level access on the target ad account, inside the same business portfolio. Skip this and everything after it is wasted.
- Submit from the business portfolio's verification entry. Not from the Page.
- Confirm the field appears at the ad level. You should be able to pick the advertiser from the dropdown, and specify a separate payer if they differ. If you cannot, the ad account still has no verified entity available.
- Set the defaults. Desktop Ads Manager has a default advertiser and payer setting under ad delivery preferences. Set it once and new ad sets inherit it.
7. How our verification service works
For anything Taiwan-related we now run verification as a service: 30 USDT per ad account.
Four steps:
- You grant our operator admin rights on the relevant ad account inside your own business portfolio.
- Our operator completes and submits the verification.
- We tell you when the result lands, and the advertiser and payer become selectable at the ad level.
- You remove the access.
A few things that decide whether the fee is worth it:
- Every asset stays yours. The verification lands on your business portfolio and your ad account. Nothing is handed over from outside, and once access is removed we cannot touch anything.
- No password is involved. What the job needs is access rights, not credentials.
- One per account. Three ad accounts means three jobs, because of section 3 — not because of how we price it.
- The decision is Meta's. We control submission quality and consistency of the details. We do not control the outcome or the timing.
- All Taiwan-related packages follow this model now. No more selling a pre-verified Page; the reasons are in section 4.
If you need a full set of assets plus verification, pick the account tier first in which account type fits, then handle verification as described here.
8. Four common misconceptions
"Verification only appears if the account is flagged." No. Taiwan is on the published list; a clean account targeting Taiwan gets asked too.
"Verify once and you are done." Not any more. It lapses, silently, and you usually find out when you try to launch something new.
"The right document gets you through." Consistency between details decides it far more often than the type of document.
"An agency doing this for you means faking something." The opposite. Falsified details get revoked later and drag the whole business portfolio down with them. The work here is getting the process and the consistency right.
Results disclosure: the process and timings described here reflect the situation in September 2026. Meta has changed this policy several times within the year, and your experience will vary with account history, market and the details you submit.
Sources (official pages, checked 2026-09-11). Anything marked as a field report comes from public practitioner discussion between August and September 2026 and from our own support tickets, not from these pages:
- About advertiser and payer transparency for ads — Meta Business Help Centre — facebook.com
- About advertiser verification for ad transparency — Meta Business Help Centre — facebook.com
- Verification requirements for advertisers — Meta Business Help Centre — facebook.com
- About business verification in Meta Business Suite — Meta Business Help Centre — facebook.com
FAQ
Is verification mandatory for Taiwan?
Yes. Meta lists Taiwan among the places where advertiser and payer disclosure is required, alongside the EU, Singapore, Australia and India. Without it the advertiser field never appears, ads fail to publish, and running ads can be paused.
Are "beneficiary" and "advertiser" the same thing?
Yes. Meta replaced the word "beneficiary" with "advertiser" in March 2026; the mechanism did not change. The payer is whoever actually pays for the ad, and in most cases both are the same entity.
Can a Page still be verified for Taiwan?
Since August 2026 practitioners report that the Page entry point redirects straight to the business portfolio, new Page verifications cannot be added, and older ones have been dropping. That is field reporting rather than an announcement, but enough people report it to treat as the current state.
I verified one ad account — why is the second one still blocked?
Meta's reuse condition is that the account which completed verification holds at least partial admin access (admin or advertiser level) on the ad account you want to use, and that you are in the same business portfolio. Without that permission relationship the verification does not travel.
The advertiser field does not appear when I build an ad. What now?
That usually means the ad account has no verified entity available to it yet. Go back to the verification entry in the business portfolio, complete it once, then check the ad level again.
What documents are needed?
An individual verifies with a government-issued ID. For an organisation, Meta first tries to match your details against third-party databases and only asks for official company documents when it cannot find a match.
How long does review take?
Meta promises nothing. Before July 2026 two to three days was common; since August plenty of people report more than ten days still in review. Treat the timing as a risk in your plan, not a fixed step.
"We can't verify based on the information provided" — is that a rejection?
It is the most common failure message, and it usually points at inconsistent information rather than a wrong submission method. Resubmitting the same set of details rarely changes anything.
Is buying a pre-verified Page still worth it?
Less every month. Verified Pages lapse, running ads from them makes lapsing more likely, and the status does not unlock other ad accounts. It can buy you a few weeks; it is not a strategy.
Does submitting for verification put the account at risk?
Verification only passes or fails; submitting does not get you banned. What does cause damage is falsified information, which is a policy problem rather than a review problem.
How is your verification service priced?
30 USDT per ad account. Because verification is now per account, three ad accounts means three of them.
What access do you need?
Admin rights on the relevant ad account inside your own business portfolio. Our operator completes the verification and the access can be removed afterwards. No password is ever needed.
Can a verification lapse after it passes?
Yes. A wave of verified Pages and accounts lapsed between late August and early September 2026. A lapse means verifying again, which is normal for this phase.
Is there a way around verification?
In practice there are two options: change the market you target, or verify each account one at a time. Anyone selling a third option is usually selling someone else's identity documents.
Want the parts this article talks about?
See Facebook ad assetsRead next
Running Facebook Ads: the complete path from nothing to your first live ad
The whole route on one page. From "where is Ads Manager" to "how do I
What Is BM in Facebook Ads? Business Manager, BM3 and BM50
BM is the container your ad assets live in, not the place you run ads
What is an ad account? How personal accounts, ad accounts, BMs and Pages relate
Four things get talked about interchangeably, but they are four separa
How Meta policy changes affect account survival
When accounts start dying in batches, it is usually not something you
Account types and when to use each one
Blank, aged, once-cleared, twice-cleared, cloned, ad account. Plenty o