I. Overview

Unauthorized merchant deductions from an e-wallet occur when money is debited from a user’s digital wallet without the user’s valid consent, authorization, or lawful obligation. In the Philippines, this issue commonly involves e-wallets, mobile payment apps, QR payments, subscriptions, online merchants, in-app purchases, linked cards, payment gateways, and digital marketplaces.

The legal issue may appear simple: “Money was deducted without permission.” But legally, the correct remedy depends on what actually happened.

The deduction may be:

a true unauthorized transaction;
a merchant billing error;
a duplicate charge;
a delayed posting of a prior authorized purchase;
a recurring subscription the user forgot or did not understand;
a scam or phishing incident;
an account takeover;
a mistaken debit by the payment provider;
a charge authorized by a linked app, card, or platform;
a disputed but technically authorized transaction.

The proper legal response may involve customer service escalation, reversal request, chargeback or dispute process, complaint to the e-wallet provider, complaint to the merchant, report to the Bangko Sentral ng Pilipinas, complaint to consumer protection authorities, data privacy complaint, cybercrime complaint, or civil/criminal action depending on the facts.

The most important first step is to classify the deduction correctly.

II. What Is an E-Wallet?

An e-wallet is a digital account that stores electronic money or enables electronic payment transactions. It may be used for:

sending and receiving money;
paying merchants;
scanning QR codes;
paying bills;
buying prepaid load;
online shopping;
in-app purchases;
subscriptions;
remittances;
cash-in and cash-out;
linking bank accounts, debit cards, or credit cards;
receiving refunds or incentives.

Philippine e-wallets are generally part of the regulated financial technology ecosystem. They may be operated by electronic money issuers, payment service providers, banks, or non-bank financial institutions subject to regulatory obligations.

Because e-wallets hold monetary value and process payments, unauthorized deductions may raise issues involving financial regulation, contract, consumer protection, cybercrime, data privacy, fraud, and civil liability.

III. Meaning of Unauthorized Merchant Deduction

An unauthorized merchant deduction is a debit from an e-wallet balance made in favor of a merchant, biller, app, online platform, subscription provider, or payment gateway without the user’s valid authorization.

Examples include:

a merchant charges the e-wallet even though the user did not buy anything;
a QR payment goes through twice;
a subscription renews without proper notice or consent;
an app deducts money after a free trial without clear authorization;
a merchant uses saved payment credentials without permission;
a payment gateway processes a charge that the user did not approve;
a scammer obtains OTP or login credentials and pays a merchant;
an account is hacked and used for purchases;
a transaction appears under a merchant name unknown to the user;
a user cancels an order but the merchant still deducts or keeps the payment;
a merchant deducts a higher amount than the amount displayed;
an e-wallet auto-debit arrangement continues after cancellation.

The legal remedy depends on whether the transaction was truly unauthorized or whether the dispute is about performance, refund, cancellation, defective goods, or misunderstanding of terms.

IV. Common Scenarios

A. Duplicate deduction

The user pays once, but the e-wallet shows two deductions. This may be a technical error, duplicate merchant capture, payment gateway issue, or delayed reversal problem.

B. Failed transaction but amount deducted

The payment fails at the merchant side, but the e-wallet balance is reduced. The merchant says payment was not received, while the e-wallet says the transaction was successful or pending.

C. Unknown merchant name

The transaction history shows a merchant name the user does not recognize. Sometimes the merchant name is the legal name or payment gateway name, not the store’s trade name. Sometimes it indicates fraud.

D. Subscription renewal

The user signs up for a trial, app, streaming service, game, dating app, cloud service, antivirus, or digital membership. Later, money is deducted automatically. The dispute is whether the user validly authorized recurring billing and whether cancellation was available and honored.

E. Unauthorized in-app purchase

Children, relatives, or third parties may use the phone or account to purchase game credits, coins, skins, or digital content. The issue becomes whether the e-wallet account holder authorized access or failed to secure the account.

F. Phishing or account takeover

The user receives a fake link, fake verification request, fake customer support message, or fake merchant checkout page. The scammer obtains OTP, MPIN, password, or device access, then makes merchant payments.

G. QR code manipulation

A QR code is replaced, tampered with, or misdirected. The user thinks payment is going to one merchant, but funds go to another account or merchant.

H. Merchant overcharging

The displayed price is ₱500, but the e-wallet is charged ₱5,000. This may be billing error, fraud, or merchant misconduct.

I. Auto-debit after cancellation

The user cancels a subscription or merchant authorization, but deductions continue.

J. Unauthorized linked account deduction

The e-wallet is linked to a card, bank account, app store, ride-hailing app, food delivery app, shopping app, or gaming platform. A merchant deduction occurs through that linked authorization.

V. Legal Characterization of the Problem

An unauthorized merchant deduction may be legally characterized in different ways.

A. Payment dispute

This is the most common category. The user disputes the transaction through the e-wallet provider or merchant. The issue may be resolved by refund, reversal, or correction.

B. Consumer complaint

If the merchant failed to deliver goods, refused a refund, misrepresented charges, or imposed hidden fees, the issue may involve consumer protection.

C. Financial services complaint

If the e-wallet provider failed to handle the dispute properly, failed to reverse an unauthorized transaction, or ignored the user’s complaint, the matter may be escalated as a financial consumer protection issue.

D. Cybercrime or fraud

If the deduction resulted from phishing, hacking, identity theft, fake merchant pages, malware, or unauthorized access, the issue may involve cybercrime.

E. Data privacy incident

If personal data, account credentials, transaction details, or identity documents were misused or leaked, data privacy issues may arise.

F. Civil claim for sum of money or damages

If the responsible party is identifiable and refuses to refund, the user may have a civil claim.

G. Criminal complaint

If deceit, theft, unauthorized access, identity misuse, or falsification is involved, a criminal complaint may be appropriate.

VI. First Legal Question: Was There Valid Authorization?

The central issue is authorization. A transaction may be considered unauthorized if the account holder did not consent to it and did not validly approve it.

However, the user’s consent may be disputed. The e-wallet provider or merchant may argue that the transaction was authorized because:

the correct MPIN was entered;
OTP was used;
biometric authentication was completed;
the device was recognized;
the user previously linked the merchant;
the user accepted recurring billing terms;
the user saved payment credentials;
the user’s account login was used;
the transaction came from the user’s registered device;
the merchant has proof of order or delivery.

The user may respond that:

credentials were stolen through phishing;
OTP was obtained by deception;
the transaction was processed without confirmation;
the amount was different from what was authorized;
recurring billing was not clearly disclosed;
cancellation was ignored;
the merchant used saved credentials beyond consent;
the transaction occurred after account compromise;
the e-wallet failed to implement adequate security or dispute handling.

The legal and factual dispute often turns on evidence.

VII. Second Legal Question: Who Is Responsible?

Responsibility may fall on one or more parties:

The merchant If the merchant overcharged, duplicated billing, refused refund, or processed unauthorized payment.
The e-wallet provider If the provider failed to secure the account, process dispute, reverse unauthorized transaction, or handle complaints properly.
The payment gateway If the transaction was processed through an intermediary that caused duplicate or erroneous debit.
The user If the user disclosed OTP, MPIN, password, or negligently allowed access.
A scammer or third party If the account was compromised or credentials were stolen.
An app or platform If the deduction arose from an app store, subscription, game, or digital service.

In many cases, the e-wallet provider initially blames the merchant, while the merchant blames the wallet or gateway. The user should pursue both the merchant and e-wallet provider until the transaction path is clarified.

VIII. Evidence to Preserve Immediately

Evidence is critical. The user should preserve the following:

screenshot of the transaction history;
transaction reference number;
merchant name as shown in the app;
amount deducted;
date and time;
wallet balance before and after deduction, if available;
SMS, email, or push notification;
receipt or lack of receipt;
order number, if any;
checkout page screenshots;
QR code used, if any;
merchant invoice;
cancellation confirmation, if subscription-related;
conversation with merchant support;
conversation with e-wallet support;
proof that no goods or services were received;
proof that the user was elsewhere or did not transact;
device login alerts;
OTP messages;
phishing messages or suspicious links;
screenshots of fake pages or scam chats;
bank/card statements if linked account was used;
complaint ticket numbers;
refund request records.

The user should avoid deleting messages, uninstalling apps, factory-resetting the phone, or closing the wallet account before evidence is preserved.

IX. Immediate Practical Steps

Step 1: Stop further loss

If the deduction appears unauthorized, the user should immediately:

change the e-wallet password or MPIN;
unlink cards and bank accounts;
remove saved merchants;
disable auto-debit if possible;
log out all devices;
revoke app permissions;
enable stronger authentication;
block suspicious numbers;
avoid clicking suspicious links;
contact the e-wallet provider to freeze or secure the account.

Step 2: Report to the e-wallet provider

Report the transaction immediately through official channels. Provide the reference number, amount, merchant name, date, and reason for dispute.

Step 3: Contact the merchant

If the merchant is identifiable, ask for transaction details and refund or reversal. Request confirmation whether the merchant received the payment.

Step 4: Document all communications

Keep screenshots of ticket numbers, chat replies, emails, and call logs.

Step 5: Escalate if unresolved

If the provider or merchant does not resolve the issue, escalate through internal complaint channels, regulatory complaint mechanisms, and legal remedies.

X. Internal Dispute With the E-Wallet Provider

Most e-wallets have formal complaint and dispute processes. The user should file a transaction dispute as soon as possible.

The dispute should state:

“I did not authorize this merchant deduction.”
“The transaction reference number is ______.”
“The amount is ₱______.”
“The transaction occurred on ______ at ______.”
“The merchant shown is ______.”
“I did not receive goods or services.”
“I request immediate investigation, reversal, and preservation of transaction logs.”

If phishing or account takeover is suspected, state:

“My account may have been compromised.”
“I request account security review and transaction hold.”
“Please preserve login records, device information, and merchant settlement details.”

The user should ask for:

formal dispute ticket number;
expected resolution period;
name of merchant or payment gateway;
transaction status;
whether the merchant has claimed settlement;
reason for refusal if reversal is denied;
copy or summary of authorization basis;
escalation to fraud or chargeback team.

XI. Merchant Complaint

The merchant may be directly liable if it received funds without valid basis.

The complaint to the merchant should request:

confirmation whether the merchant received the payment;
order or invoice associated with the payment;
identity of account or order that used the wallet;
reason for deduction;
refund or voiding of charge;
cancellation of recurring billing;
deletion of saved payment authorization;
written confirmation of reversal.

If the merchant claims it did not receive payment, the user should ask the e-wallet provider for proof of settlement or reversal status. If the e-wallet says the transaction succeeded and the merchant says it did not, the dispute may involve the payment gateway or reconciliation process.

XII. Recurring Billing and Subscriptions

Unauthorized merchant deductions often arise from recurring billing. The user may have clicked a free trial, accepted terms, or authorized automatic renewal without fully realizing it.

Recurring billing is more defensible when:

the user clearly agreed to recurring payments;
the price and renewal date were disclosed;
cancellation method was available;
reminder or notice was provided when required;
the user did not cancel before renewal;
the charge matches the agreed amount.

Recurring billing is more vulnerable to challenge when:

consent was hidden or unclear;
the user was charged after cancellation;
the amount changed without notice;
cancellation was difficult or impossible;
the merchant continued billing after account closure;
the merchant disguised the transaction;
the user never created an account with the merchant.

The user should immediately cancel the subscription, screenshot the cancellation, request refund, and remove the merchant authorization from the e-wallet or linked platform.

XIII. One-Time Merchant Payment Disputes

For one-time purchases, disputes may involve:

wrong amount charged;
duplicate charge;
payment made but order not confirmed;
order cancelled but no refund;
merchant did not deliver goods;
merchant delivered wrong or defective goods;
merchant denies receiving payment;
merchant used saved credentials without consent.

The remedy may involve refund, replacement, reversal, complaint to platform, consumer complaint, or civil action.

XIV. QR Payment Disputes

QR payments create special evidentiary issues. The user should preserve:

screenshot or photo of QR code;
merchant name shown before confirmation;
amount entered or displayed;
confirmation screen;
transaction receipt;
merchant’s acknowledgment or denial;
location of transaction;
CCTV or store receipt, if applicable.

If the QR code was tampered with or replaced, the matter may involve fraud. If the user scanned the wrong QR code, liability may be disputed.

XV. Linked Card or Bank Account Deductions

If the e-wallet is funded by a linked bank account or card, the deduction may trigger multiple dispute routes:

e-wallet dispute;
bank dispute;
card chargeback;
merchant refund;
payment gateway complaint.

The user should determine where the funds were ultimately deducted:

from the e-wallet balance;
from a linked debit card;
from a linked credit card;
from a linked bank account;
from an auto cash-in arrangement.

A credit card transaction may have chargeback remedies. A wallet balance deduction may follow wallet provider dispute procedures. A bank transfer may require bank fraud reporting.

XVI. Chargeback and Reversal

The term “chargeback” is commonly used for card transactions, while “reversal” or “refund” may be used for e-wallet transactions.

Possible outcomes include:

immediate reversal;
temporary credit;
merchant refund;
transaction voiding;
chargeback investigation;
denial due to alleged authorization;
partial refund;
account freeze pending investigation.

The user should ask whether the transaction is still pending or already settled. Pending transactions may be easier to void. Settled transactions may require merchant cooperation or formal dispute review.

XVII. E-Wallet Provider’s Duties

An e-wallet provider is expected to maintain secure systems, process transactions accurately, provide customer support, handle complaints, maintain records, and comply with financial consumer protection standards.

Potential provider failures include:

failure to investigate unauthorized transaction;
unreasonable delay;
failure to provide ticket or written decision;
failure to secure account after report;
failure to reverse obvious duplicate debit;
failure to preserve transaction logs;
misleading customer service replies;
blaming merchant without investigation;
refusing to explain denial;
inadequate fraud detection;
allowing suspicious merchant deductions;
failure to honor complaint escalation procedures.

A user’s strongest regulatory complaint often focuses not only on the lost amount, but also on the provider’s failure to properly handle the dispute.

XVIII. Merchant’s Duties

A merchant accepting e-wallet payments should process only authorized charges, issue receipts, deliver goods or services, honor refunds when required, and avoid deceptive billing.

Potential merchant misconduct includes:

unauthorized charging;
duplicate billing;
hidden subscription renewal;
refusal to refund cancelled order;
charging a different amount;
misrepresentation of price;
failure to deliver;
use of misleading checkout design;
failure to disclose recurring billing;
continuing auto-debit after cancellation;
processing payment under an unrelated name;
using customer credentials without authority.

If the merchant is a regulated business, franchise, marketplace seller, or app provider, additional complaint channels may exist.

XIX. Cybercrime Issues

Cybercrime may be involved when the deduction resulted from:

phishing;
hacked e-wallet account;
unauthorized access;
fake merchant website;
fake checkout page;
malware;
SIM swap;
OTP theft;
identity theft;
social engineering;
fake customer support;
QR code tampering;
account takeover;
fraudulent digital payment.

Possible offenses may include computer-related fraud, identity theft, illegal access, misuse of devices, estafa through electronic means, and related crimes depending on the facts.

A cybercrime complaint should include:

wallet transaction details;
phishing links;
screenshots of scam messages;
phone numbers used;
merchant account details;
receiving account information;
device alerts;
OTP messages;
support tickets;
timeline;
proof of loss.

XX. Phishing and OTP Issues

Many unauthorized deductions happen because scammers trick users into giving OTPs, passwords, MPINs, or login links.

A difficult legal question arises: who bears the loss when the user was deceived into providing credentials?

The e-wallet provider may argue that the transaction was authenticated using the correct credentials. The user may argue that the transaction was unauthorized because consent was obtained through fraud and the provider’s security measures were inadequate.

Factors that may matter include:

whether the user disclosed OTP or MPIN;
whether the provider gave clear warnings;
whether the transaction was unusual;
whether device binding was bypassed;
whether the merchant was suspicious;
whether the provider acted promptly after report;
whether the user reported immediately;
whether the provider could have stopped settlement;
whether there were prior fraud alerts.

Even where user error is alleged, the provider may still have complaint-handling obligations.

XXI. SIM Swap and Device Compromise

If the unauthorized deduction followed loss of signal, SIM replacement, device theft, or account takeover, the user should preserve evidence of:

SIM signal loss;
telecom complaint;
unauthorized SIM replacement;
device theft report;
login alerts;
password reset messages;
OTP messages;
unfamiliar device logins;
unauthorized email access.

The user should report to both the telecom provider and e-wallet provider. SIM swap incidents can involve identity theft and cybercrime.

XXII. Data Privacy Issues

Unauthorized merchant deductions may involve unauthorized processing or misuse of personal data.

Data privacy concerns may arise if:

the merchant stored payment credentials without consent;
the e-wallet shared data improperly;
personal information was leaked;
a scammer used personal details to bypass verification;
identity documents were misused;
transaction records were disclosed to third parties;
customer support demanded excessive personal information through insecure channels.

A data privacy complaint may be appropriate where the issue involves unauthorized collection, use, disclosure, or compromise of personal data.

However, not every unauthorized deduction is automatically a data privacy violation. The privacy issue must be connected to improper processing or breach of personal information.

XXIII. Consumer Protection Issues

If the unauthorized deduction arises from merchant conduct, consumer protection principles may apply.

Examples:

misleading price display;
hidden fees;
undisclosed subscription;
refusal to honor cancellation;
defective goods;
non-delivery after payment;
deceptive sales practice;
unfair refund policy;
misleading checkout page;
false advertising.

A consumer complaint may be useful when the dispute is primarily with a merchant over goods or services, not account hacking.

XXIV. Civil Remedies

The user may have civil remedies against the merchant, scammer, e-wallet provider, or other responsible party.

Possible civil claims include:

sum of money;
refund;
damages for breach of contract;
unjust enrichment;
quasi-delict or negligence;
moral damages in proper cases;
exemplary damages in proper cases;
attorney’s fees and litigation expenses.

Civil action is more practical when:

the responsible party is known;
the amount is significant;
evidence is strong;
the defendant is within reach of Philippine jurisdiction;
administrative remedies failed;
the claim is not too small compared with litigation cost.

XXV. Small Claims

For straightforward refund or collection disputes within the applicable threshold, small claims may be an option. It may be useful against a merchant that refuses to refund a clearly unauthorized or erroneous deduction.

Small claims may be less suitable when:

the defendant is unknown;
the case involves hacking;
the merchant is foreign;
complex digital forensic evidence is needed;
criminal fraud is involved;
the issue requires injunction or data disclosure;
the e-wallet provider’s regulatory obligations are central.

Still, for a simple unpaid refund against a local merchant, small claims may be practical.

XXVI. Criminal Remedies

A criminal complaint may be appropriate if there is deceit, unauthorized access, identity theft, falsification, or fraudulent taking.

Possible criminal theories include:

estafa;
theft in some factual scenarios;
computer-related fraud;
identity theft;
illegal access;
falsification;
use of falsified documents;
unjust vexation or harassment if threats are involved;
other cybercrime-related offenses.

Criminal complaints require evidence of criminal intent and the identity of the offender. A mere unresolved refund dispute is not always criminal.

XXVII. Administrative and Regulatory Complaints

If the e-wallet provider fails to resolve the dispute, the user may escalate through financial consumer protection complaint channels.

The regulatory complaint should include:

complainant’s name and contact details;
e-wallet account number or registered mobile number;
transaction reference number;
merchant name;
amount;
date and time;
summary of dispute;
proof of unauthorized nature;
complaint ticket numbers;
provider’s responses;
requested relief.

The complaint should be concise, factual, and supported by documents. Regulators generally expect that the user first attempted to resolve the matter directly with the provider.

XXVIII. Complaint Against the Merchant

If the merchant is the main wrongdoer, the user may file complaints through:

merchant’s internal complaint process;
marketplace platform;
app store;
payment gateway;
consumer protection office;
industry regulator, if the merchant is regulated;
civil court;
law enforcement, if fraud is involved.

The merchant complaint should ask for both refund and written explanation.

XXIX. If the Merchant Is Unknown

Sometimes the transaction history shows only a vague code, payment gateway, aggregator, or unfamiliar merchant name.

The user should ask the e-wallet provider for:

merchant legal name;
merchant ID;
transaction route;
payment gateway involved;
settlement status;
order reference;
registered merchant contact information;
basis of authorization.

If the provider refuses to provide details for privacy or security reasons, the user may still request that the provider investigate and reverse the unauthorized debit.

XXX. If the Provider Says “Transaction Was Successful”

A successful transaction is not necessarily an authorized transaction. It only means the payment system processed it.

The user should respond:

“I dispute the authorization, not merely the technical success.”
“Please provide the basis for treating the transaction as authorized.”
“Please identify the merchant and transaction purpose.”
“Please preserve authentication and device logs.”
“Please escalate to fraud investigation.”

A provider cannot resolve an unauthorized transaction complaint merely by saying the payment went through.

XXXI. If the Merchant Says “No Payment Received”

If the merchant denies receiving payment but the wallet shows deduction, the user should request:

transaction trace;
reconciliation result;
settlement status;
reversal timeline;
payment gateway reference;
proof whether funds were captured or only authorized;
written certification from merchant if payment was not received.

The e-wallet provider and merchant should reconcile the transaction. The user should not be trapped between them indefinitely.

XXXII. If the Provider Denies Refund Because OTP Was Used

If OTP was used, the provider may claim the transaction was authenticated. But the user can still raise issues if the OTP was obtained through fraud, the transaction was suspicious, or security controls failed.

The user should provide:

phishing messages;
fake links;
timestamps of OTP messages;
proof of immediate report;
device compromise evidence;
unfamiliar login alerts;
unusual transaction pattern.

The legal and practical outcome may depend on whether the provider finds account compromise and whether the user violated security reminders.

XXXIII. If the User Shared OTP or MPIN

Sharing OTP, MPIN, password, or login credentials weakens the user’s claim. Providers repeatedly warn users not to share these details.

However, even if the user was deceived, there may still be remedies against the scammer or fraudulent merchant. The user may also challenge the provider if the provider failed to act after timely notice or allowed suspicious transactions despite red flags.

The user should be truthful. False denial of sharing credentials may damage credibility.

XXXIV. If a Family Member Made the Transaction

If a child, spouse, sibling, helper, friend, or family member used the phone or account to make a purchase, the e-wallet provider may treat the transaction as authorized if it came from the user’s device and credentials.

The remedy may be against the merchant if refund rules allow cancellation, or against the family member privately. If the user voluntarily gave access to the device, the provider may deny liability.

However, if a child made in-app purchases through unclear design or without parental consent, refund policies of the app store or merchant may help.

XXXV. If the Phone Was Stolen

If the phone was stolen and merchant deductions followed, the user should immediately:

report to the e-wallet provider;
request account freeze;
report to telecom provider for SIM blocking;
change email and wallet credentials;
file police report;
preserve proof of theft;
identify unauthorized transactions after theft;
request reversal.

Timeliness matters. Delayed reporting may weaken the claim.

XXXVI. If the Deduction Is From a Scam Merchant

Some merchants exist only to receive stolen or unauthorized e-wallet payments. Signs include:

no real website;
fake Facebook page;
no business address;
payment to personal account;
pressure to pay quickly;
refusal to issue receipt;
disappearing after payment;
inconsistent merchant name;
fake customer service;
newly created page;
copied branding.

The remedy is likely fraud reporting, payment dispute, and complaint to platform or payment provider.

XXXVII. Demand Letter

A demand letter may be useful when the merchant or provider refuses to refund.

A demand letter should state:

the transaction details;
why the deduction was unauthorized or erroneous;
the amount demanded;
evidence attached;
prior complaint ticket numbers;
demand for refund within a reasonable period;
request for written explanation if denied;
reservation of rights.

The demand should be professional. It should not contain threats of violence, defamatory accusations, or exaggerated claims.

XXXVIII. Sample Demand Letter to Merchant

A demand may read:

I am formally disputing the deduction of ₱_____ from my e-wallet on _____ under transaction reference number _____. I did not authorize this transaction, did not receive goods or services corresponding to it, and request immediate reversal or refund. Please provide the order record, authorization basis, and settlement details if you claim the transaction is valid. If no valid authorization exists, please process the refund immediately.

This should be adjusted to the facts.

XXXIX. Sample Complaint to E-Wallet Provider

A complaint may read:

I am disputing an unauthorized merchant deduction from my e-wallet. The transaction occurred on _____ at _____ in the amount of ₱_____ under reference number _____. The merchant shown is _____. I did not authorize this payment and did not receive any goods or services. Please freeze any further merchant debits, investigate the transaction, preserve authentication and device logs, identify the merchant or payment gateway, and reverse the amount. My complaint ticket numbers are _____.

If phishing is involved, add:

I may have been targeted by phishing or account compromise. Attached are screenshots of suspicious messages and links. I reported the matter immediately upon discovery.

XL. Complaint-Affidavit for Cybercrime or Fraud

A complaint-affidavit should include:

complainant’s identity;
e-wallet account details;
description of unauthorized deduction;
date, time, and amount;
merchant or recipient details;
how the transaction was discovered;
whether phishing or hacking occurred;
what credentials, if any, were compromised;
immediate reports made;
loss suffered;
evidence attached;
names or account details of suspects, if known.

The affidavit should be chronological and factual.

XLI. Importance of Timely Reporting

Timely reporting is crucial because:

pending transactions may still be reversible;
merchant settlement may not yet be final;
fraud accounts may still contain funds;
logs may be preserved;
providers may impose dispute deadlines;
delayed reports create doubt;
scammers move money quickly.

A user should report immediately after discovering the deduction.

XLII. Time Limits

Different remedies have different time limits:

e-wallet dispute deadlines may be set by provider rules;
card chargeback deadlines may be short;
consumer complaints may have practical timing requirements;
criminal prescription periods vary by offense;
civil claims have limitation periods;
evidence retention periods may be limited.

The safest approach is to act promptly and document every step.

XLIII. User’s Duties

E-wallet users have responsibilities, including:

keeping passwords, MPINs, and OTPs confidential;
securing devices;
using official apps only;
avoiding suspicious links;
monitoring transaction history;
reporting unauthorized transactions promptly;
updating contact information;
using strong authentication;
not allowing others to use the account;
reading subscription and auto-debit terms;
keeping evidence.

Failure to follow security obligations may affect refund eligibility.

XLIV. Provider’s Common Defenses

The e-wallet provider may deny liability by arguing:

transaction was authenticated;
OTP or MPIN was correctly entered;
user disclosed credentials;
transaction came from registered device;
merchant fulfilled the order;
user has a recurring billing authorization;
report was filed too late;
user violated terms of service;
deduction was a valid fee or charge;
merchant already received settlement;
refund must come from merchant.

The user should respond with evidence showing lack of consent, fraud, cancellation, duplicate charge, non-delivery, or provider failure.

XLV. Merchant’s Common Defenses

The merchant may argue:

user placed the order;
goods or services were delivered;
digital goods are non-refundable;
subscription was not cancelled;
user accepted terms;
payment was processed by gateway;
refund must be handled by wallet;
transaction was made by someone with access to the user’s device;
charge is valid.

The user should request proof: order record, delivery confirmation, IP/device data if available, account used, subscription agreement, and cancellation records.

XLVI. Proving Non-Receipt of Goods or Services

If the dispute involves non-delivery, evidence may include:

absence of order confirmation;
merchant admission;
delivery tracking;
chat messages;
cancellation email;
refund request;
screenshots of account showing no purchase;
app store purchase history;
merchant account history;
witness statements.

The issue may be consumer refund rather than unauthorized deduction if the user authorized payment but did not receive the product.

XLVII. Unauthorized Deduction Versus Refund Dispute

It is important to distinguish these two:

Unauthorized deduction

The user says: “I did not authorize this transaction at all.”

Refund dispute

The user says: “I authorized payment, but the merchant failed to deliver or should refund me.”

Both may justify relief, but they use different arguments and evidence.

Calling every dispute “unauthorized” may weaken credibility if the record shows the user did authorize payment. Be accurate.

XLVIII. Civil Liability for Negligence

Negligence may be alleged against a provider or merchant if they failed to exercise reasonable care.

Examples:

weak security controls;
allowing suspicious repeated charges;
failure to block known fraudulent merchant;
failure to act after user reported compromise;
failure to reverse duplicate charge;
failure to maintain proper transaction records;
poor complaint handling;
failure to secure stored payment credentials.

Negligence claims require proof of duty, breach, causation, and damage.

XLIX. Unjust Enrichment

If a merchant received money without lawful basis, unjust enrichment may apply. The principle is that no person should unjustly enrich themselves at another’s expense.

This may be useful where:

the merchant received payment but no order exists;
duplicate payment was received;
subscription continued after cancellation;
refund was promised but withheld;
the merchant cannot justify the charge.

The remedy is usually return of the amount and, in proper cases, damages.

L. Moral and Exemplary Damages

Moral damages may be claimed in proper cases where the user suffered anxiety, embarrassment, mental anguish, or serious inconvenience due to bad faith, fraud, or unlawful conduct. Exemplary damages may be considered where the defendant acted in a wanton, fraudulent, oppressive, or malevolent manner.

However, damages must be supported by facts. Minor inconvenience alone may not justify large claims.

LI. Attorney’s Fees and Costs

Attorney’s fees may be recoverable in certain cases, especially where the claimant was compelled to litigate due to the other party’s unjustified refusal to pay. However, courts do not award attorney’s fees automatically. They must be justified.

For small amounts, practical resolution through provider dispute or regulatory complaint may be better than litigation.

LII. If the Amount Is Small

If the unauthorized deduction is small, the most practical route is usually:

immediate provider dispute;
merchant refund request;
internal escalation;
regulatory complaint if unresolved;
small claims only if the responsible merchant is identifiable and the amount justifies the effort.

For small losses from phishing, the user may still report to help identify patterns and prevent further fraud.

LIII. If the Amount Is Large

For large unauthorized deductions, the user should:

secure account immediately;
report to provider and request freeze;
file written complaint;
report to bank/card issuer if linked;
preserve device and messages;
consider police or cybercrime report;
consult counsel;
send demand letter;
escalate to regulators;
consider civil or criminal action.

Large losses require stronger documentation and faster action.

LIV. If Multiple Users Are Affected

If many users experienced unauthorized deductions from the same merchant, this strengthens the case. Affected users should preserve their own evidence and may file separate or coordinated complaints.

Patterns may show:

merchant system abuse;
fraudulent scheme;
payment gateway issue;
platform security weakness;
deceptive subscription practice;
mass phishing campaign.

However, public posts should be carefully worded to avoid defamation issues.

LV. Defamation Risk When Posting Online

Users often post accusations against merchants or e-wallets after unauthorized deductions. Caution is needed.

A risky statement:

“This merchant is a thief and this e-wallet steals money.”

A safer statement:

“I am disputing a ₱_____ deduction from my e-wallet on ____ under transaction reference _____. I have requested investigation and refund. Others should monitor their accounts and report similar transactions through official channels.”

State facts, not insults. Avoid posting personal information of employees, agents, or suspected scammers.

LVI. Privacy and Security After the Incident

After an unauthorized deduction, the user should:

change e-wallet MPIN/password;
change email password;
change passwords of linked merchant accounts;
unlink cards and bank accounts;
remove saved payment methods;
review active subscriptions;
review authorized devices;
check transaction limits;
enable biometrics or stronger authentication;
update SIM security;
avoid public Wi-Fi for financial transactions;
install only official apps;
monitor accounts for further deductions.

If identity documents were exposed, monitor for identity theft.

LVII. Preventive Measures

To reduce risk:

Do not share OTP, MPIN, password, or recovery codes.
Use official apps and websites only.
Do not click payment links from unknown messages.
Check merchant name and amount before confirming.
Avoid saving payment credentials with unknown merchants.
Review subscriptions monthly.
Use transaction notifications.
Set transaction limits where possible.
Keep screenshots of cancellations.
Avoid lending your phone or account.
Report suspicious merchants.
Update apps and device security.

LVIII. Practical Legal Strategy

A strong strategy follows this sequence:

Secure the account.
Preserve evidence.
File an immediate dispute with the e-wallet provider.
Contact the merchant for explanation and refund.
Request transaction trace and basis of authorization.
Escalate internally if unresolved.
File a regulatory complaint against the e-wallet provider if complaint handling fails.
File a consumer complaint against the merchant if the dispute concerns goods, services, or unfair billing.
File a cybercrime or fraud complaint if there was phishing, hacking, identity theft, or scam activity.
Consider civil action or small claims if the responsible party is known and the amount justifies it.

LIX. Sample Evidence Checklist

Prepare a folder containing:

transaction screenshot;
transaction reference number;
merchant name;
amount;
date and time;
e-wallet complaint ticket;
merchant complaint ticket;
all chat transcripts;
emails;
SMS alerts;
OTP messages;
suspicious links;
screenshots of checkout page;
cancellation confirmation;
proof of non-delivery;
bank or card statement if linked;
police or cybercrime report, if filed;
timeline of events.

This evidence folder is useful for the provider, merchant, regulator, lawyer, police, or court.

LX. Sample Timeline

A useful timeline may look like this:

April 1, 9:10 AM: Received notification of ₱3,500 deduction from e-wallet.
April 1, 9:15 AM: Checked transaction history; merchant shown as “ABC Merchant.”
April 1, 9:20 AM: Confirmed I did not transact with ABC Merchant.
April 1, 9:30 AM: Changed MPIN and unlinked cards.
April 1, 9:45 AM: Reported to e-wallet provider; ticket no. 12345.
April 1, 10:30 AM: Emailed merchant requesting refund and transaction details.
April 2: Merchant denied order exists.
April 3: E-wallet stated transaction was successful but did not provide authorization basis.
April 5: Filed escalation complaint with supporting documents.

A clean timeline makes the case easier to understand.

LXI. Sample Legal Theories by Scenario

Scenario 1: Duplicate merchant deduction

Likely remedy: reversal/refund through e-wallet and merchant. Legal theory: payment error, unjust enrichment, breach of merchant obligations.

Scenario 2: Subscription after cancellation

Likely remedy: merchant refund, cancellation confirmation, consumer complaint. Legal theory: unauthorized recurring billing, unfair practice, breach of cancellation terms.

Scenario 3: Unknown merchant deduction after phishing

Likely remedy: account freeze, e-wallet dispute, cybercrime report. Legal theory: computer-related fraud, identity theft, unauthorized transaction.

Scenario 4: Merchant charged higher amount

Likely remedy: partial refund or reversal. Legal theory: overcharging, misrepresentation, unjust enrichment.

Scenario 5: Payment deducted but merchant says failed

Likely remedy: reconciliation between e-wallet, gateway, and merchant. Legal theory: payment processing error.

Scenario 6: Child made in-app purchases

Likely remedy: app store refund request, parental controls. Legal theory: refund policy and lack of valid consent, depending on facts.

LXII. When to Consult a Lawyer

Legal advice is especially useful when:

the amount is substantial;
the provider denies liability;
the merchant refuses refund;
phishing or hacking caused large losses;
personal data was compromised;
the user is accused of authorizing the transaction;
the provider refuses to disclose transaction details;
the user wants to sue;
criminal complaint is being prepared;
multiple victims are involved;
the transaction affects business funds.

A lawyer can help prepare demand letters, complaint-affidavits, evidence packets, and regulatory complaints.

LXIII. Conclusion

Unauthorized merchant deductions from an e-wallet in the Philippines can involve payment error, merchant misconduct, subscription abuse, phishing, account takeover, cybercrime, data privacy issues, or consumer protection violations. The correct remedy depends on whether the transaction was truly unauthorized, whether the merchant received funds, whether the user’s credentials were compromised, whether recurring billing was valid, and whether the e-wallet provider handled the complaint properly.

The user should act quickly: secure the account, preserve evidence, dispute the transaction, contact the merchant, escalate to the e-wallet provider, and file regulatory, consumer, cybercrime, civil, or criminal complaints where appropriate. The strongest cases are built on clear documentation: transaction reference numbers, timestamps, merchant details, screenshots, support tickets, cancellation records, and proof of non-authorization.

An e-wallet deduction is not automatically valid simply because the system processed it. At the same time, not every unwanted charge is legally unauthorized if the user previously consented to payment or recurring billing. The decisive issues are consent, authorization, transaction records, security, merchant conduct, provider response, and evidence.