Open a PHP Virtual Bank Account

The PHP is a managed float overseen by the Bangko Sentral ng Pilipinas (BSP), which actively uses reserves and policy tools to smooth excessive volatility. It's not a hard peg, so the rate does move against the USD - typically within a few percent annually under normal conditions, with sharper swings during global risk-off cycles. For most operating businesses, the practical concern isn't whether to hold PHP, but how long to hold it. If your PHP inflows fund local payroll or supplier costs in the Philippines, holding the balance is natural. If you ultimately need to convert to USD, EUR or another base currency, we recommend converting on a regular cadence rather than letting balances accumulate uncontrolled.

No. A Woalet PHP virtual account gives you local Philippine bank details under our regulated infrastructure, so you can invoice and collect in pesos without incorporating a domestic company, securing a Mayor's Permit, or maintaining a Philippine business address. This is the single biggest reason foreign SMEs, agencies, and platforms move off SWIFT or Wise personal accounts - they need to look local to the payer without taking on local incorporation, tax filings, or BIR registration overhead.

It depends on the rail the sender chooses. InstaPay credits in real time, 24/7, including weekends and holidays. PESONet handles larger amounts with no per-transaction ceiling but settles in batches, so a payment initiated in the morning typically reflects the same banking day, while late-cutoff transfers move to the next business day. We surface both options on your account so payers can choose the rail that fits the amount.

Yes. Outbound PHP payouts to any local bank or major e-wallet (GCash, Maya) are supported through the same InstaPay and PESONet rails. This is a common setup for agencies, SaaS companies, and remote-first teams paying Filipino developers, VAs, customer support, and BPO partners - you fund your account in USD, EUR, or stablecoin, hold a PHP balance, and disburse locally without each contractor incurring a SWIFT receiving fee or losing 3–5% on a personal remittance app.

There's no monthly maintenance fee for the account itself. You pay only on activity: a small inbound collection fee on incoming PHP, an FX spread on conversions, and a per-transfer cost on payouts. Unlike Airwallex or Tazapay's published rate cards with fixed markup, FX is negotiated based on your monthly volume - higher throughput moves you to tighter spreads. We're happy to share a written quote once we understand your expected flow.

You can hold PHP indefinitely or convert on demand into any of the 15+ currencies we support, including USDC and USDT. Most businesses fall into one of two patterns: convert immediately to lock in revenue at the booking rate (best when PHP is weakening or you don't have peso-denominated costs), or hold and convert in tranches (best when you have local payroll, supplier, or tax obligations in pesos). For larger amounts we can quote a custom rate per transaction rather than applying a standard spread.

Yes. You receive dedicated local PHP bank details - account number and partner bank name - that work natively on the payer's online banking interface, the same way any domestic Philippine account would. This matters because a lot of Philippine corporates, government suppliers, and platforms will only release payment to a local PHP account; they won't process SWIFT to a foreign beneficiary, and they often can't send to e-wallets for compliance reasons.

Holding a virtual PHP account doesn't, on its own, create a permanent establishment or income tax liability in the Philippines - you're transacting through our licensed infrastructure, not operating a local entity. However, the source of the income matters. Recent BIR and EY guidance clarifies that payments for services rendered to Philippine customers can be treated as Philippine-sourced under specific conditions, which may trigger withholding by the payer. We can't give tax advice, but we strongly recommend confirming your treatment with a Philippine tax counsel before high-volume invoicing - particularly if your client base is concentrated in Metro Manila enterprises or government-linked organizations.

Yes, indirectly. E-wallets in the Philippines interoperate with the banking system via InstaPay, so a GCash or Maya user can send pesos to your virtual account number as if it were any local bank. This is increasingly important for businesses with retail or freelance Filipino customers, where e-wallets have overtaken traditional bank apps as the default payment method.

Three practical differences. First, Wise and Payoneer give you a USD receiving account for "PHP" inflows that's actually converted on arrival - you don't get true local PHP holding or native InstaPay/PESONet credentials in your business name. Second, personal Philippine accounts impose retail-tier limits (typically ₱500K daily) and aren't designed for business invoicing or volume. Third, we negotiate FX per client rather than applying a fixed published spread, and we settle natively in USDC/USDT if you prefer stablecoin treasury - neither of which is on offer from those providers.

Typical onboarding is a few business days from KYC submission to receiving your live PHP account details, assuming clean documentation. Regulated industries or complex ownership structures may add review time. We schedule a short call upfront to scope your use case so the application goes through on the first pass rather than cycling through compliance follow-ups.