Coins.ph users in the Philippines can no longer receive InstaPay or PESONet bank transfers after the Bangko Sentral ng Pilipinas partially suspended the payment-network access of the platform’s e-money operator, tightening one of the country’s most-used crypto on-ramps.
## What the BSP order does
According to BitPinas, Philippine Payments Management Inc. notified financial institutions through PPMI Advisory No. 2026-0929-029, which ordered immediate implementation of BSP Monetary Board Resolution No. 839. The restriction applies to DCPay Philippines, the entity that operates Coins.ph’s electronic-money and peso payment business.
Under the advisory, transfers from external bank accounts or e-wallets into affected Coins.ph peso wallets are rejected when routed through InstaPay or PESONet. The restriction covers incoming person-to-person transfers, incoming InstaPay QR credit transfers, and DCPay’s participation in the InstaPay for Business pilot.
The order is partial by design. DCPay remains authorized to originate outgoing transfers, meaning users can still send funds from Coins.ph wallets to Philippine bank accounts and other e-wallets. Its person-to-merchant QRPh participation is also intact, so existing balances can still be spent at QRPh-enabled merchants.
## How Coins.ph responded
Coins.ph initially went further than the directive itself, temporarily pausing all peso cash movements — including cash-outs — while making the technical adjustments needed to implement the inbound restriction. The company said it expected outbound transfers to resume by 11 a.m. Philippine time on Sept. 30.
By Oct. 1, the platform’s status page showed regular cash-outs, InstaPay cash-outs and PESONet cash-outs as operational. Bank cash-ins remain blocked: both InstaPay and PESONet cash-in services are listed as under maintenance, and the active InstaPay cash-in incident has been labeled “Investigating” since 1 p.m. Philippine time on Sept. 29, with no resolution notice posted.
The rest of the platform — mobile app, website, spot exchange, peer-to-peer transfers and major blockchain network deposits and withdrawals — is listed as operational.
## Why crypto trading still works
The regulatory action targets DCPay’s e-money license, not the exchange’s virtual asset authorization. The BSP’s latest public VASP list, dated May 31, 2026, shows Betur Inc., doing business as Coins.ph, as an active non-bank virtual asset service provider. Betur handles crypto trading, digital-asset wallets and custody.
The practical link is the peso wallet. Customers who relied on InstaPay or PESONet transfers to fund their accounts cannot use those rails to add pesos before buying crypto, even though the trading engine itself is untouched. Crypto deposits and withdrawals across Bitcoin, Ethereum, XRP, Tron, Solana, BNB Smart Chain and other networks remain available.
The license distinction has grown more relevant as Philippine regulators deepen supervision of digital-asset businesses. Under stricter BSP rules for virtual assets, VASPs must conduct stronger screening of listed tokens and maintain ongoing monitoring and delisting procedures.
## The QRPh wrinkle
The restriction separates receiving money from paying merchants: a user cannot receive an affected inbound transfer into DCPay, but funds already in the wallet can still be spent at eligible merchants. That preserves one of Coins.ph’s most significant product wins of 2026 — QRPh stablecoin payments, launched earlier in the year, which let customers pay with pesos, USDT or USDC at checkout across nearly 700,000 QRPh-enabled merchants, with crypto converted to pesos during the payment process.
## Why it matters beyond one exchange
Coins.ph is among the Philippines’ longest-running crypto platforms and one of its most widely used fintech apps, serving a market where remittances and mobile wallets dominate financial life. A partial suspension of its bank-transfer rails — even one that spares crypto services — reduces the fiat on-ramp capacity of the entire local ecosystem, at least temporarily.
The BSP has not publicly detailed the reasons behind Monetary Board Resolution No. 839, and Coins.ph has not announced a timeline for restoring inbound transfers. Users holding peso balances can still withdraw them, and users holding crypto can still move it on-chain or trade it. Affected customers looking to fund accounts still have a few workarounds, including crypto deposits from external wallets and any non-bank cash-in channels unaffected by the advisory, but each adds friction and cost to what was previously a one-tap transfer.
For now, the episode is a reminder of how centralized the decentralized on-ramp still is: a single advisory from the national payments body can shut off the banking pipes to one of the country’s largest crypto platforms overnight, while the blockchains underneath keep running without noticing.
GCrypto route works but the spread eats like 1.5 percent. Still cheaper than watching your balance sit frozen during an investigation.
the gcash to gcrypto detour works but yeah that spread stings. holding off transfers until dcpay says something official
same, holding off until dcpay posts something official. guessing which workaround survives the next advisory is its own tax on your time
waited hours on a pesonet cash-in before i found the advisory on twitter. a push notification from coins wouldve been nice
incoming instapay and pesonet cut off but outgoing still works, so its a choke on new money coming in. rough timing for php crypto users
BSP blocked the InstaPay and PESONet cash-ins but left QRPh and the whole crypto side running. They left the VASP license alone too. reads like pressure, not a shutdown
outgoing transfers still work so anyone with balance can route through another wallet and re-fund. annoying, survivable
agreed on pressure not shutdown. bsp kept outgoing rails open which means they want dcpay to fix reporting, not exit. october is gonna be loud
thats the optimistic read. vasp license staying alive is hope but resolution 839 gives zero timeline, weeks can mean anything
been using coins.ph since 2019. workaround for now is cash in via gcash to gcrypto then send, annoying but the crypto rails being unaffected helps
gcash to gcrypto works but check the limits, anything above 50k a day needs multiple hops. fine for small amounts, painful for a business
^ good tip. resolution 839 is partial by design, bsp clearly wants compliance fixes from dcpay, not a shutdown. expect this to get resolved in weeks
instapay cash-in incident marked investigating since sept 29, no update since. status page doing heavy lifting as usual
investigating since sept 29 and still nothing by oct 2, classic. at least qrph merchants keep the lights on for small sellers
investigating since sept 29 is corporate for they dont know either. at least the vasp license is untouched, thats the real signal
person to merchant qrph still live, so merchants are fine. its the bank transfer crowd that got hit. hope they publish what triggered this
know several ppl who cashed out via qrph merchants no problem. the panic was 90% people not reading which rails got cut
PPMI advisory went out same day banks had to implement it. zero transition window for remittance senders, that part is the real story here
zero transition window is right. my tita sent a remittance through instapay that same morning and it just bounced, no explanation. at least tell people which rails are dead