Why you should know this
“Confirmed” sounds finished. In crypto remittance, it may mean only that a blockchain recorded a transfer. A receiving provider might still need to detect it, check information, convert it to PHP and credit the recipient.
The reverse can also happen: an app may say “processing” while no network transaction has been broadcast. Searching a block explorer then produces nothing, because the transfer is still inside the provider’s system.
Understanding these layers prevents panic, duplicate sends and fake-support scams. It also builds a market-mastery habit: never treat one data point as proof of the entire process.
One remittance, several records
A compliant crypto-enabled route can create at least three records:
- Provider record: the sender’s order, identity review, conversion and withdrawal instruction.
- Network record: the virtual-asset transfer and confirmations on a blockchain.
- Receiving and PHP-delivery record: asset detection, compliance review, conversion and bank/e-wallet/cash delivery.
Some providers keep the crypto movement entirely inside their own or partner systems, so the customer may never receive a public transaction hash. Others show one. Neither design alone proves that a service is safer or faster.
Track each layer separately. Do not assume the same status word has the same definition across companies.
Common status words, translated
Created or initiated
The user entered an instruction, but the provider may not have accepted funds or begun processing. Check whether payment, identity information or confirmation is still required.
Pending payment or funding
The order is waiting for the sender’s money. Sending an incorrect amount, using a different payer name or missing a deadline can stop progress. Use only the official instructions tied to the order.
Under review or verification required
The provider may need identity, source-of-funds, beneficiary, sanctions or transaction information. This is not automatically an accusation. Regulated providers perform risk-based checks.
Respond only through verified channels. Never send an OTP, password or seed phrase. Ask what document is required, why, how it will be protected and the official upload method.
Approved or processing
The provider accepted the instruction and is preparing the next step. “Processing” does not establish that a network transfer exists. Look for a transaction hash only if the service says it will provide one.
Broadcast or submitted to network
The two-ledger test
When a public network is involved, compare two facts:
- On-chain fact: What does the transaction hash show?
- Provider fact: What does the provider’s case or order record show?
Imagine the explorer says “confirmed,” while the app says “deposit not credited.” That narrows the issue to asset/network support, destination, memo/tag, provider detection or compliance—not network broadcast.
If the app says “processing” and there is no hash, the provider may not have broadcast anything yet. A blockchain explorer cannot solve an internal review.
When to wait and when to escalate
Read the provider’s current stated processing window and maintenance notice first. Escalate when the window is exceeded, the status contradicts verified records, sensitive information is demanded, the destination appears wrong or an unauthorized transfer is suspected.
Contact the provider through its official channel and keep the case ID. For BSP-supervised institutions, the BSP Consumer Assistance Mechanism is generally a second-level route after first raising the matter with the provider, subject to its scope and current rules. Law-enforcement or fraud reporting may also be appropriate for suspected crime.
Practice check — no money needed
Create a status timeline with separate columns for provider status and blockchain status. Decide what each record proves and what is still unknown.
The goal is not to memorize a slogan. If you can explain the route or decision, name the main limitation, and identify what evidence you would need before using real money, the lesson has done its job.
How this connects to market mastery
Trading systems also have layered states: order submitted, accepted, partially filled, filled, settled and withdrawable. Confusing them produces operational risk.
By learning to distinguish network finality from provider settlement and fiat delivery, you practice the same careful state analysis used in professional operations.
*Cryptocurrency and virtual asset transactions are highly volatile and irreversible, may result in significant losses, and do not guarantee returns; customers should trade only after understanding the risks involved.
