
Your app is making sales on Google Play. So when does Google send the money, and which Nigerian bank account can receive it?
Google supports USD wire payouts for eligible Nigerian merchants, with a $100 minimum payout balance. But a US dollar account isn't automatically eligible, especially if it doesn't match the merchant profile's country requirements. Here's how to set up the receiving account, avoid rejected bank details and check a missing payout.
Match the bank account to the profile
Look at the merchant profile country, legal payee and payout currency before you ask your bank for instructions. The receiving institution should confirm that it can accept an incoming USD international wire from Google for that beneficiary. Ask for current beneficiary details and any intermediary instructions required for that route.

Copy the fields from the institution's instructions into the corresponding form fields. A routing number for domestic US ACH cannot substitute for a SWIFT/BIC.
What to check | What a useful answer looks like |
|---|---|
Merchant country | The country on the Play Console payments profile |
Bank country and rail | A bank in the required jurisdiction that confirms incoming USD wire support |
Beneficiary | Exact name on bank records and the relevant merchant profile |
Charges | Receiving fee, possible intermediary deductions and any conversion charges |
Follow-up | A support channel and the reference needed to locate an incoming transfer |
The international bank details guide shows how to identify the fields for each rail. If you are comparing account types, use the virtual USD account checklist to distinguish the bank location from the currency and the payer rules.

How to add a payout bank account in Google Play Console
Sign in to Play Console and open Settings → Payments settings.
Under How you get paid, choose the payment-method option.
Select Add Payment Method and enter the bank details requested for your merchant profile.
Confirm that the bank's country, beneficiary and account currency meet Google's requirements.
Complete any required verification and check the account for payment holds before your first payout.
For a Nigerian merchant using Google's USD wire route, confirm with the bank that it can receive international USD wires. A domestic US ACH routing number is not an alternative to the destination Google requires.
Google Play revenue and freelance development income follow different payment rules. Your Play Console payout needs an eligible merchant bank account. For direct payments from international development clients, explore walllet's receiving options.
Explore walllet for developer client payments
Budget for the payout cycle
Google says it generally pays eligible activity around the 15th of the following month. The USD wire route has a US$100 minimum earned balance at payout. Refunds and chargebacks affect the balance, and the receiving bank may take additional time to credit the transfer. Order processing and payouts

How much can receiving a Google Play wire cost?
Google states that receiving-bank and intermediary charges can vary, potentially from $0 to $50 or more. Your bank determines the actual fees. If a $120 payout incurs a $20 receiving charge, a significant part of that month's proceeds disappears before you can use it.
Compare the remittance amount against the final bank credit, especially when your monthly app revenue is close to the $100 payout minimum.
For example, if a developer's eligible balance is $85 at the payout cutoff, there is no reason to start an international wire investigation. First establish that the threshold was met and a payment was actually issued. If Play shows an issued payment, move on to the transfer reference and bank-side checks. The distinction matters when you need to pay a contractor out of the proceeds.
Two worked examples for a first Google Play wire
You have two sets of bank details. Your Nigerian USD account provides international wire instructions. A second account provides a US ACH routing number. Ask the Nigerian bank to verify its current incoming instructions and whether it can credit a Google merchant payment in USD. Then check whether Play Console accepts the bank country and the fields provided. Do not take the ACH routing number from the second account and add it to the first account's beneficiary instructions. That would describe neither receiving account accurately. If the bank says a correspondent is required and the form does not show an appropriate field, ask Google and the bank how to handle that requirement before submitting details.

Your eligible payout is $180, but the account credits $168. These numbers are illustrative. First check that Google's remittance amount actually was $180 after any platform adjustments. Compare the bank's credit currency and transaction advice. The difference could involve bank fees, conversion, or an amount that never left the platform. A screenshot of gross app revenue cannot tell you which. Ask the bank for the breakdown and reconcile each deduction once. For future estimates, use only charges you can identify or clearly label a range.
Give finance a receiving record it can reuse
Store the merchant profile name, the date the bank confirmed its instructions and the authorized person who can update the destination. Keep account numbers in an appropriate restricted record, separate from the spreadsheet the entire team can see. Record the next expected cycle without treating the date as a bank guarantee. Assign one person to check the payment form and another, if available, to verify the fields against the bank record. That small check is especially useful after changing your legal entity, bank or payout contact.
If your team also bills clients for development services, put that work in a separate cash-flow column. Your client contract can have a different payer, route and due date than the store payout. Keeping those obligations separate helps you spot whether a late payment is a Play settlement issue or an overdue client invoice.
Building apps for clients as well as selling them?
Keep your Google Play payouts separate from contract payments. See how walllet helps eligible developers receive, hold and spend international income.
Explore walllet.com receiving options for separate client payments.
Find the bottleneck before replacing the bank account
No payout issued. Read the profile notices and check the payable balance, verification and any hold. Confirm the reporting month. Gross sales, estimated earnings and a payout confirmation refer to different points in the process.
Payout issued but not credited. Save the amount, currency, payment date, beneficiary and Google's reference. Ask the receiving bank to confirm it can locate an inbound USD wire using those details. If it cannot, ask which reference the sender needs to provide. Use the payment evidence checklist to organize the exchange.
Transfer returned. Get the return reason from the institution that can see it. Correct the underlying mismatch before updating anything. An invalid beneficiary and a receiving institution that cannot accept that payment require different fixes. Google Play payout FAQs

Keep platform payouts and client income separate
Your app sales can use the bank route required by Play Console while your US or European clients use a different approved payment route. Keep a record for each payer. The US, UK and EU client payment guide covers the second workflow. The walllet receiving-account guide explains how to verify currency and beneficiary details for eligible walllet accounts. Confirm platform acceptance independently before entering any fintech-issued details in Play Console.