Missing Japan PSA authorization freezes Google Play payouts worldwide
If you sell into Japan from abroad, or from Japan to users abroad, Google must collect Payment Services Act (PSA) authorization for Google to act as your payment-collection agent. Miss the 1 December 2026 deadline and the how-to places a global disbursement block—not a Japan-only hold—with no payouts from any region until consent is completed. ISA disclosures for sales into Japan run on a separate clock. W-8, bank-beneficiary, and trader-status tasks do not substitute for PSA consent.
If you sell into Japan from abroad, or from Japan to users abroad, Google must collect a Payment Services Act (PSA) authorization for Google to act as your payment-collection agent. Miss the deadline, and the hold is not limited to Japan earnings. The how-to is explicit: a miss places a global disbursement block, with no payouts from any region until the consent is completed.
The official 29 October 2026 policy announcement states: "If you sell into or out of Japan, you must complete authorization by December 1st, 2026, or your payments will be held globally." That is the public announcement clock. The how-to, How to verify as a developer selling into or out of Japan, also says to "complete the authorization by the deadline stated in your invitation." If the invitation shows a different date, verify it from that invitation. This article does not invent a rule for which text overrides the other.
This is paperwork with a payout-hold penalty, not a store-listing copy change, and not a W-8, bank-name, or trader-status task. None of those substitutes for this consent.
Who has to complete PSA authorization
The how-to lists two groups:
- Developers located outside Japan selling to users in Japan
- Developers based in Japan selling to users outside Japan
It adds, in parentheses, that PSA "Does not apply to domestic sales within Japan." A FAQ on the same page says these laws "apply based on where your customers are, not just where your business is physically located," and that PSA applies to sales into and out of Japan.
The public pages do not say that every Google Play developer must complete this authorization, and they do not say that the absence of an invitation proves you are out of scope. This article does not invent a revenue threshold. If Japan is in your distribution, or you are Japan-based and selling abroad, check email, Play Console, and Payments Center now.
A global block, not a Japan-only hold
The how-to FAQ asks what happens if you do not complete the requirements. For PSA: "If you miss the deadline, a global disbursement block will be placed on your account. You will not receive any payouts from any region globally until you complete the consent." The same page also says that if authorization is not completed on time, "Google will place a global hold on all your earnings across all regions until it is completed."
That wording is not a freeze of Japan earnings only, and it is not the same event as a declined W-8, a bank-beneficiary mismatch, or a trader-status problem. Those holds can look similar in Payments Center; they are fixed by different forms. See Google Play payment holds, W-8 and bank mismatches and Play trader status in three steps. The 29 October announcement also reminds developers to declare trader status, on a later clock; that form does not replace PSA consent. The Policy Deadlines table, as fetched on 2026-11-12, has no Japan / PSA / 1 December 2026 row — do not look for this clock there.
ISA is a second requirement, with a different clock
Beside PSA consent — "Authorizing Google to act as your payment collection agent" — the how-to describes a separate Installment Sales Act (ISA) disclosure for "any global developer who sells into Japan." Do not merge the two. For new sellers, "Your global payouts will be blocked the moment you earn money from a buyer in Japan for the first time if you haven't completed the disclosure." For existing sellers, the page grants "a temporary grace period" with no immediate block and "recurring reminders," and it does not state how many days that period lasts.
Existing sellers are notified "immediately upon the policy launch"; new sellers after their first Japan sale. PSA's announcement clock remains 1 December 2026 (and the date in your invitation). ISA's trigger is first Japan sale, or that grace period. Treat them as two forms.
What to do this week
- Decide whether PSA applies under the who-must language above. If you sell into Japan, or from Japan to users abroad, look now — do not wait for a second reminder.
- Check email, Play Console, and Payments Center for the invitation. Open the Authorization page and select Continue. The how-to says PSA status updates immediately after you provide consent.
- If you sell into Japan, complete the ISA disclosure when you are notified. A W-8, bank, or trader-status task will not cover it.
- If the invitation date and 1 December 2026 differ, record both, complete the earlier one, and keep the official email.
If you answer "Yes" to a legal-history question
ISA asks two mandatory Yes/No questions about legal history over the last five years: the Act on Specified Commercial Transactions, and the Consumer Contract Act. If either answer is Yes, the explanation must include all five official elements: the exact date of the judgment or administrative action; what happened; people involved; where it occurred; and the steps taken to prevent it from happening again.
The most common issue, the page says, is a Yes without all five details. Read the feedback email, update, and resubmit. A Yes is not an automatic ban. The FAQ answers "Can I still do business on Google Play if I answer 'Yes' to a legal disclosure?" with: "Yes. Having a past administrative action or judgment does not automatically ban you from Google Play. However, you must provide complete, truthful details about the event and prove your remediation efforts to pass the verification review." ISA submissions are manually reviewed; the page does not say how many days that takes. If a later check finds that you answered No when you should have answered Yes, or that you provided false information, Google will restart the verification process.
If a global hold has already started
Complete the missing PSA consent first; the status updates immediately after consent. If the block is tied to an incomplete ISA disclosure, submit all five details and wait for the manual review. Do not open a second Payments profile or developer account to route around the hold — that usually creates a linked problem rather than a payout. Once review is complete, the how-to says you will receive a confirmation email, and "If your payouts were blocked due to missing information, the global block will be lifted."
What this article is not
It is not a W-8 or bank-documentation payout hold, and it is not the trader-status declaration. It does not recap the other items on the 29 October announcement (restricted permissions, eligibility-discount disclosures, AppFunctions). Those have their own dates on the Policy Deadlines table.
Not legal advice. Quotes are from Google Play's and Google Payments Center's public help pages as fetched on 2026-11-12. Check the current pages, and any invitation or official email on your account, before you act.
If a global payout hold has already started and the Payments Center wording is unclear, KappS can help you match it to the official PSA / ISA text before you file or resubmit.
Sources
- Policy announcement: October 29, 2026 https://support.google.com/googleplay/android-developer/answer/18100766?hl=en
- How to verify as a developer selling into or out of Japan https://support.google.com/paymentscenter/answer/17595997?hl=en
- Policy Deadlines https://support.google.com/googleplay/android-developer/table/12921780?hl=en
- Trader status declaration (anti-mix only) https://support.google.com/googleplay/android-developer/answer/17594752?hl=en