Introduction

In the Philippines, unauthorized credit card transactions connected with scams have become legally and practically complex. The old image of credit card fraud as simple physical card theft is no longer enough. Today, unauthorized charges may arise from phishing, vishing, spoofed bank calls, fake merchant sites, OTP theft, card-not-present fraud, account takeover, malware, social engineering, SIM-related compromise, fake refund schemes, QR or link scams, or deception involving installment conversion, cash advance, or merchant enrollment. In many cases, the cardholder does not realize immediately whether the transaction is legally “unauthorized,” merely “disputed,” or technically “authorized but fraudulently induced.”

That distinction matters. In Philippine legal context, not every bad transaction is treated the same way. A charge may be:

purely unauthorized, where the cardholder never consented at all;
induced by fraud, where the cardholder was tricked into disclosing credentials or approving something without understanding its true nature;
merchant-related, where the cardholder transacted with a deceptive seller;
bank-side security failure, where the issuer’s systems or controls are questioned;
partly attributable to cardholder negligence, depending on the facts and the contract.

The legal and remedial path depends on what actually happened, when the bank was notified, what the cardholder disclosed, what contractual terms say, what the evidence shows, and how Philippine consumer, banking, payments, cybercrime, and civil law principles apply.

This article explains the Philippine legal framework for disputing scam-related unauthorized credit card transactions, the difference between kinds of disputes, the immediate steps a cardholder should take, the role of the card issuer, the standards banks usually invoke, the effect of OTP and cardholder participation, documentation, procedural strategy, and the legal remedies available when a bank denies reversal.

I. Why scam-related credit card disputes are legally complicated

A scam-related charge is rarely just a billing problem. It may involve several overlapping legal relationships:

The cardholder and the issuing bank
The cardholder and the scammer or fake merchant
The issuing bank and the card network
The issuer and the acquiring bank or merchant
Potential criminal and cybercrime exposure
Consumer protection and financial regulation concerns

Because of this, a cardholder often faces several separate questions at once:

Is the charge really unauthorized?
Does the bank have to reverse it immediately?
Is the cardholder still liable while the dispute is under investigation?
What if the cardholder gave the OTP because of deception?
What if the card details were used online but the cardholder never physically lost the card?
What if the transaction involved a fake merchant website or online platform?
What evidence must be submitted?
Can the bank refuse because the OTP was entered?
Can the cardholder escalate to regulators or sue?

These are legal and evidentiary questions, not just customer service questions.

II. The most important threshold issue: what kind of transaction is being disputed?

Before discussing remedies, Philippine legal analysis should classify the transaction correctly. This is the single most important step.

A. Pure unauthorized transaction

This is the clearest case. The cardholder did not make, approve, authorize, or participate in the transaction, directly or indirectly.

Examples:

card details were stolen and used online;
cloned card used without knowledge;
charge appears from a merchant the cardholder never dealt with;
recurring charge appears from unknown source;
physical card was stolen and used without permission.

In these cases, the dispute is strongest when the cardholder promptly notified the bank and there is no evidence of cardholder participation.

B. Fraudulently induced transaction

This is harder. The cardholder may have clicked a link, read an OTP to a fake bank caller, entered card details on a scam website, or followed instructions under deception.

Examples:

cardholder was told a charge needed OTP reversal, but actually approved a transaction;
scammer impersonated the bank and obtained CVV/OTP;
cardholder entered details into a fake courier, e-wallet, or government page;
“refund” scam led to real charge authorization.

These cases are more contested because banks may argue the cardholder participated in the security step. But legally, fraudulent inducement does not automatically end the inquiry. Consent obtained through deception is not the same as informed authorization in every context.

C. Merchant dispute rather than pure fraud

Sometimes the cardholder willingly transacted with a seller but was scammed later.

Examples:

fake online store never delivers goods;
merchant double-charged;
service was misrepresented;
subscription was disguised;
promised refund never came.

Here, the dispute may involve chargeback rules, merchant misconduct, and proof of non-delivery, not just bank-side unauthorized use.

D. Account takeover or profile compromise

The cardholder’s app or online banking profile may have been hijacked, and the scammer then enrolled the card in a digital wallet, changed contact details, or pushed through transactions.

These cases raise additional issues about:

authentication controls;
device enrollment;
account recovery;
SIM compromise;
bank-side risk detection.

III. Philippine legal framework governing these disputes

Several areas of Philippine law and regulation may apply.

A. Civil Code

The Civil Code governs obligations, contracts, damages, fraud, negligence, good faith, abuse of rights, and liability arising from breach of contractual duty. The relationship between cardholder and issuer is contractual, but it is also regulated.

B. Banking and financial regulation

Banks and card issuers are subject to regulatory duties concerning consumer protection, prudential conduct, security controls, fair dealing, and complaint handling. Their discretion is not unlimited.

C. Consumer protection principles

Credit card users are financial consumers. Disclosure, fairness, complaint processing, and reasonable dispute resolution standards matter.

D. Electronic commerce and digital transaction principles

Because many scam transactions occur online, issues of electronic consent, authentication, and digital records become central.

E. Data privacy law

Where cardholder data is compromised, mishandled, or inadequately protected, data privacy considerations may arise, though not every fraud event automatically proves a privacy violation by the bank.

F. Cybercrime and criminal law

Phishing, spoofing, identity theft, online fraud, unauthorized access, and electronic deception may create criminal issues separate from the billing dispute.

G. Financial consumer protection regulation

Banks are generally expected to handle complaints fairly, explain decisions, and maintain adequate consumer assistance mechanisms.

The cardholder’s rights therefore come from both contract and regulation.

IV. Basic legal relationship between cardholder and issuer

A credit card is not just a payment tool; it is a continuing contractual relationship. The issuer generally extends credit subject to terms and conditions, while the cardholder undertakes to use the card according to the agreement.

From the issuer’s perspective, the cardholder usually agrees to:

safeguard the card and credentials;
promptly report loss, theft, or unauthorized use;
review statements;
dispute erroneous charges within the prescribed period;
avoid disclosing OTP, CVV, PIN, password, or security information to others.

From the cardholder’s perspective, the issuer usually undertakes to:

maintain billing accuracy;
process genuine disputes;
apply security measures;
investigate unauthorized charges;
communicate findings fairly;
reverse or correct charges when justified.

This contractual framework is important because most unauthorized transaction disputes turn on whether the issuer met its duty of care and whether the cardholder breached security obligations.

V. Immediate steps after discovering a scam-related unauthorized charge

From a legal and evidentiary standpoint, the earliest steps are often the most important.

1. Report the transaction to the issuer immediately

Prompt notice is critical. Delay weakens the cardholder’s position because banks often argue that earlier reporting could have prevented further charges.

2. Block or lock the card

If the issuer offers in-app card lock or hotlisting, the cardholder should do this at once.

3. Preserve all evidence

Take screenshots of:

SMS alerts;
app notifications;
email notices;
merchant names;
transaction reference numbers;
scam messages;
spoofed caller numbers;
fake websites;
OTP prompts;
chat logs.

4. Record the timeline

Prepare a written chronology:

when the suspicious call/text arrived;
what was said;
whether OTP was requested;
when the charge posted;
when the bank was called;
what the bank representative advised.

5. Change credentials where relevant

If the scam involved account compromise, passwords and related login security should be changed immediately.

6. File a formal dispute, not just a casual complaint

A phone call may alert the bank, but a written dispute is usually more legally useful.

These early steps affect the quality of the later claim.

VI. Why prompt reporting matters so much

Prompt reporting matters for three separate reasons.

A. Contractual notice requirements

Most issuers require cardholders to report unauthorized charges within a certain period after discovery or statement issuance. Missing the deadline does not always destroy the claim absolutely, but it creates serious problems.

B. Damage mitigation

Banks often argue that immediate notice could have prevented subsequent charges, digital wallet enrollment, or recurring fraud.

C. Good faith and credibility

A cardholder who notices a suspicious charge and immediately protests appears more credible than one who waits until payment becomes inconvenient.

Thus, even when the cardholder is emotionally overwhelmed, delay is dangerous.

VII. Writing the dispute properly

A strong written dispute should clearly state:

the cardholder’s full name;
masked card number;
disputed transaction amount;
merchant name as appearing in records;
transaction date and posting date;
statement that the charge was unauthorized or fraudulently induced;
concise account of what happened;
exact time the bank was first notified;
request for reversal, investigation, and temporary suspension of collection on the disputed amount;
request for written findings;
attached evidence list.

The dispute should avoid rambling accusations and focus on legal facts. The bank must understand exactly which charge is disputed and why.

VIII. Is the cardholder required to pay the disputed amount while the case is pending?

This is one of the most stressful practical questions.

The answer depends on the issuer’s procedures, the card terms, and how the dispute is provisionally handled. In practice, some banks may place the amount under investigation, temporarily credit it, or instruct the cardholder regarding the undisputed portion.

The cardholder should not assume either of these extremes:

that the entire bill can simply be ignored; or
that paying the disputed charge means admitting liability.

The safer legal approach is:

formally dispute in writing;
ask the issuer to identify what amount, if any, must be paid pending investigation;
pay undisputed charges on time if possible;
keep proof that the disputed amount was specifically contested.

Failure to handle the billing side carefully can lead to finance charges, delinquency reporting, or weakened leverage, even where the underlying fraud claim is valid.

IX. The effect of OTP disclosure: the hardest issue in scam disputes

In Philippine practice, one of the most difficult cases is where the cardholder disclosed or entered a one-time password because of a scam.

Banks often take the position that OTP use proves the transaction was authorized or at least that the cardholder breached security obligations. But the legal position is not always that simple.

A. Bank position

The issuer may say:

the OTP was sent to the registered number;
the transaction passed authentication;
the cardholder shared security credentials;
therefore the loss falls on the cardholder.

B. Cardholder counter-position

The cardholder may argue:

the OTP was obtained through impersonation, deception, or system manipulation;
the cardholder was tricked into authorizing something materially different from what was represented;
the issuer’s fraud detection should have flagged the pattern;
warnings were inadequate or transaction labeling was misleading;
the event was a scam-induced unauthorized charge, not genuine informed consent.

C. Legal significance

OTP disclosure weakens the cardholder’s case factually, but it does not automatically eliminate all remedies. The question becomes whether the issuer can treat any OTP-backed event as conclusively binding regardless of fraud context, or whether the surrounding circumstances show unfairness, inadequate controls, or deceptive authentication circumstances.

The answer is highly fact-specific.

X. When the cardholder clicked the scam link or entered card details on a fake website

Another common issue is whether the bank can deny reversal because the cardholder voluntarily typed the card number, expiry, or CVV into a fake merchant page.

Again, this usually weakens the case, but it does not end it automatically. The analysis may include:

Was the merchant obviously fake or deceptively disguised?
Did the page mimic a legitimate merchant or government service?
Did the issuer’s systems identify unusual merchant geography or spending pattern?
Was the transaction card-not-present but inconsistent with prior cardholder behavior?
Were there repeated attempts or small test charges before the larger fraud?
Did the bank send meaningful real-time alerts?

A scam victim may have been negligent, but negligence is not always total legal defeat. The bank still has regulatory and contractual duties of fair handling and reasonable security.

XI. Card-present versus card-not-present fraud

The nature of the transaction matters.

A. Card-present transactions

These usually involve physical card use at a terminal or ATM-like environment. If the cardholder had the card in possession and was elsewhere, the dispute may be easier factually.

B. Card-not-present transactions

These include online, app-based, phone, subscription, or digital wallet transactions. These are more difficult because:

physical possession is less relevant;
authentication may depend on OTP, stored credentials, tokenization, or merchant-side authorization;
banks often rely on digital logs.

Most scam-related cases today are card-not-present disputes, which is why digital evidence is central.

XII. Temporary reversal, chargeback, and investigation

In practice, a dispute may proceed in several stages.

A. Initial complaint intake

The issuer records the complaint and may block the card.

B. Provisional handling

The bank may or may not grant temporary credit while it investigates. This is often a matter of issuer policy and the chargeback posture.

C. Chargeback or network dispute process

If the matter is treated as a network dispute, the issuer may assert a chargeback against the merchant or acquiring side under card network rules.

D. Final issuer determination

The issuer decides whether to permanently reverse, partially reverse, or deny the dispute.

The cardholder should remember that internal bank investigation and network chargeback rules are not exactly the same thing. A bank’s contractual duties to the cardholder still matter even when the bank refers to “merchant proof” or network results.

XIII. Merchant proof and why banks often deny claims

Banks often deny unauthorized transaction disputes by citing “proof” such as:

successful OTP authentication;
IP/device data;
matching billing details;
3D Secure or equivalent authentication success;
merchant confirmation of completed service;
digital receipt or email address used;
prior cardholder transactions with the merchant;
non-reporting of the card as lost before the charge.

A cardholder should not be intimidated by generic denial language. The proper response is to ask:

What exact proof was relied upon?
Does it actually prove informed authorization?
Was the email address or device really mine?
What was the basis for concluding I consented?
Were there multiple scam markers the bank ignored?
Was the merchant itself fraudulent?
Was the OTP prompt accurately described to me?

The bank’s proof must logically answer the dispute, not merely sound technical.

XIV. Evidence the cardholder should preserve and submit

A strong dispute package may include:

written dispute letter;
screenshots of fraud alerts and SMS;
call logs showing scammer contact;
screenshot of spoofed number, if available;
screenshots of fake website or payment page;
scam chats or emails;
proof of immediate report to the bank;
affidavit narrating the incident;
police or cybercrime report, if made;
screenshots showing location at time of charge, where relevant;
proof the card remained in the cardholder’s possession;
transaction history showing abnormal spending pattern.

The goal is to show a coherent, credible fraud narrative supported by documents.

XV. Filing a police or cybercrime complaint: is it necessary?

It is often useful, though not always legally indispensable to the bank dispute itself.

A. Why it helps

A police or cybercrime report can:

memorialize the incident promptly;
support the seriousness and credibility of the claim;
assist if multiple victims exist;
create a record of spoofing, phishing, or identity theft.

B. What it does not automatically do

A police report does not automatically force the bank to reverse the charge. The issuer may still conduct its own inquiry.

C. Strategic value

Where the scam was clearly criminal and sophisticated, filing a complaint can strengthen the cardholder’s posture in later escalation.

In Philippine context, the absence of a police report is not always fatal, but having one can be helpful.

XVI. Bank denial letters: how to respond

If the issuer denies the dispute, the cardholder should not stop at the first refusal. A proper response should:

ask for the full factual basis of denial;
challenge any incorrect assumptions;
reiterate the scam timeline;
emphasize prompt reporting;
point out anomalies in the transaction pattern;
contest any claim that OTP equals informed consent in all circumstances;
request reconsideration and escalation to the bank’s consumer assistance mechanism.

A denial letter often uses broad formulaic statements. The cardholder should answer with specificity.

XVII. Internal escalation within the bank

Before external escalation, the cardholder should usually exhaust or at least substantially pursue the bank’s internal complaint channels.

This may include:

customer dispute unit;
fraud department;
credit card investigations unit;
bank consumer assistance desk;
formal written complaint channel;
executive escalation, where available.

The cardholder should keep:

ticket numbers;
email chains;
dates of calls;
names of officers spoken to;
copies of denial letters and responses.

A documented internal escalation record is very useful later.

XVIII. External escalation and regulatory complaint

If the issuer refuses reversal or handles the complaint unfairly, the cardholder may escalate to the appropriate financial regulatory and consumer complaint mechanisms.

In Philippine context, a bank’s refusal is not the final word. Regulatory escalation may become relevant where there is:

unreasonable denial;
failure to explain findings;
prolonged inaction;
unfair collection during a live dispute;
disregard of fraud indicators;
poor complaint handling;
opaque or abusive customer treatment.

The key legal theory in escalation is not merely “I was scammed,” but also “the issuer failed to handle my financial consumer complaint fairly and reasonably.”

XIX. Can the cardholder stop paying altogether once the bank is unreasonable?

This is risky. Even where the cardholder is morally certain the charge is fraudulent, complete nonpayment can create separate problems, including:

late fees;
finance charges;
delinquency tagging;
collection calls;
possible adverse credit reporting;
litigation risk for unpaid balances.

A more disciplined legal approach is to:

keep disputing formally;
segregate the disputed amount conceptually;
pay undisputed charges where possible;
preserve proof that the disputed portion was continuously contested;
object to finance charges on the disputed amount.

This preserves the cardholder’s credibility and reduces collateral damage.

XX. What if the transaction has already been converted to installment, loan, or cash advance?

Scam-related fraud sometimes appears not as a direct merchant charge but as:

installment conversion;
credit-to-cash transaction;
quasi-cash;
digital wallet cash-in;
money transfer funded by credit card;
balance conversion induced by scam instructions.

These are harder because the form of the transaction may look like a voluntary credit product. Still, the cardholder may dispute if the transaction arose from deception or account takeover. The bank may resist more strongly, however, because the event appears more “authorized” on its face.

The legal analysis then focuses on:

how the instruction was obtained;
whether authentication was compromised;
whether account takeover occurred;
whether fraud markers should have been detected;
whether disclosures were clear.

XXI. Cardholder negligence: how much does it matter?

Banks often rely heavily on alleged cardholder negligence, such as:

disclosing OTP;
sharing CVV;
clicking suspicious links;
using public Wi-Fi recklessly;
failing to report immediately;
storing card details insecurely.

Negligence matters, but it should not be treated mechanically. Philippine legal analysis may still ask:

Was the bank’s own security reasonable?
Were the fraud warnings clear and timely?
Did the issuer ignore abnormal transaction patterns?
Did the bank’s call/SMS branding make spoofing easier?
Was there misleading transaction labeling?
Was the cardholder’s conduct careless, or was the scam unusually sophisticated?

Negligence can reduce the practical strength of the cardholder’s claim, but it is not always a complete shield for the bank.

XXII. The special problem of spoofed bank calls and fake bank representatives

A very common Philippine scam pattern involves callers pretending to be from the bank. This raises a particularly sensitive issue because the fraud exploits trust in the bank’s identity.

A cardholder disputing such a case should emphasize:

the caller misrepresented themselves as bank personnel;
the wording used mirrored actual bank language or scripts;
the scam occurred in close sequence with real bank alerts or brand references;
the cardholder believed the communication related to account protection, not purchase authorization.

These facts matter because the issuer cannot always dismiss such cases as ordinary careless disclosure. The closer the scam mimics bank communications, the stronger the argument that the event involved sophisticated fraud rather than simple cardholder irresponsibility.

XXIII. Recurring charges and subscriptions triggered by scams

Sometimes the scam-related unauthorized transaction is not a one-time charge but a recurring subscription or stored-card billing arrangement.

In such cases, the cardholder should dispute:

the initial enrollment transaction;
all subsequent recurring charges;
any merchant authority or “free trial” claim;
failure of the issuer to block repeated suspicious debits after report.

Once the bank is notified, continued recurrence can strengthen the cardholder’s complaint if the issuer failed to take effective blocking measures.

XXIV. Liability allocation in merchant scams

Where the cardholder willingly entered a transaction with what turned out to be a fake seller, liability becomes more nuanced.

The cardholder may have stronger grounds if:

the merchant was nonexistent or clearly fraudulent;
goods were never delivered;
the merchant disappeared immediately after payment;
the charge descriptor concealed the real merchant;
the merchant charged vastly more than agreed.

These disputes are often framed as:

non-delivery;
misrepresentation;
invalid merchant processing;
unauthorized follow-up charges.

A scam merchant case may therefore support both a fraud dispute and a merchant/chargeback dispute.

XXV. Civil remedies if the bank still refuses reversal

If internal and regulatory channels do not resolve the matter, the cardholder may consider civil action, depending on the amount and facts.

Possible theories may include:

breach of contract;
damages for improper refusal to reverse unauthorized charges;
bad faith in complaint handling;
abuse of rights;
wrongful collection of a fraudulently disputed charge;
failure to exercise diligence required of banks.

Philippine law generally expects a high degree of diligence from banks because they are engaged in a business affected with public interest. That does not mean every fraud loss is automatically the bank’s responsibility, but it does mean banks cannot treat disputes casually or hide behind boilerplate.

A lawsuit, however, requires careful factual preparation and cost-benefit analysis.

XXVI. Criminal remedies against scammers and their limits

The cardholder may also pursue criminal complaints against the scammer or unknown persons involved, especially where there was:

phishing;
spoofing;
identity theft;
fraudulent online solicitation;
unauthorized access;
deceptive electronic communications.

But criminal action has limits:

the fraudster may be untraceable;
recovery may be difficult even if the crime is clear;
criminal process does not automatically reverse the credit card charge.

Thus, criminal remedy is important but should not substitute for aggressive card dispute handling.

XXVII. Data privacy and breach-related arguments

Some cardholders believe any unauthorized charge proves the bank leaked their data. That is not always true. Fraud can happen through merchant compromise, phishing, malware, social engineering, or device-level compromise without direct bank data leakage.

Still, privacy-related arguments may matter where there is reason to believe:

sensitive data was exposed due to inadequate controls;
the bank mishandled personal information;
verification changes were made without proper authentication;
contact details were altered in the system without adequate protection.

Such arguments are strongest when supported by concrete facts, not mere suspicion.

XXVIII. Common mistakes cardholders make

A. Waiting too long to report

Delay weakens both factual and contractual standing.

B. Making only verbal complaints

Phone calls without written confirmation are weak evidence later.

C. Failing to preserve screenshots and logs

Fraud evidence disappears quickly.

D. Paying nothing at all without clarifying the dispute status

This can create separate billing problems.

E. Admitting “I authorized it” when what happened was scam-induced deception

Language matters. The cardholder should describe the event accurately.

F. Arguing only emotionally

Banks respond to evidence, timelines, and specific dispute grounds.

G. Assuming OTP automatically defeats the case

It hurts the case, but the dispute may still be arguable depending on facts.

H. Ignoring escalation options after first denial

Many cardholders stop too early.

XXIX. Common arguments banks make, and how to analyze them

Argument 1: “The transaction was authenticated with OTP.”

Response: authentication is relevant, but the real question is whether it reflects informed authorization or scam-induced deception under circumstances that also raise questions about fraud controls.

Argument 2: “You disclosed your OTP, so the loss is yours.”

Response: disclosure may matter, but the issuer still must handle the case fairly, assess the surrounding scam circumstances, and explain why no bank-side control issue exists.

Argument 3: “Merchant proof shows successful delivery.”

Response: ask what exactly was delivered, to whom, and whether the merchant itself was fraudulent or the digital records were tied to the scammer.

Argument 4: “The card was not reported lost before the charge.”

Response: card-not-present fraud does not require physical loss of card.

Argument 5: “Our records show no system compromise.”

Response: the cardholder need not prove a bank-wide breach to dispute an unauthorized transaction.

A good dispute attacks conclusions, not just outcomes.

XXX. Practical legal framework for analyzing any scam-related unauthorized credit card transaction

A Philippine legal analysis should ask these questions in order:

1. What exactly happened?

Pure unauthorized use, phishing-induced approval, fake merchant, account takeover, or recurring fraud?

2. What did the cardholder actually do?

Did they do nothing, disclose OTP, enter data on a fake site, or willingly transact with a fake seller?

3. How fast was the bank notified?

Prompt notice greatly matters.

4. What security steps were used?

Card details only, OTP, app authentication, digital wallet tokenization, or other steps?

5. What evidence exists?

Texts, screenshots, call logs, bank reports, receipts, scam chats, email traces?

6. What is the legal theory?

Unauthorized charge, fraud-induced transaction, merchant non-delivery, unfair bank denial, bad faith collection?

7. What did the issuer say in writing?

The dispute should be answered at the level of the bank’s actual reasons.

8. What remedy is being pursued?

Charge reversal, finance charge removal, regulatory complaint, damages, criminal complaint, or all of these in proper sequence?

This framework prevents confusion and improves dispute strategy.

XXXI. Conclusion

In the Philippines, disputing a scam-related unauthorized credit card transaction requires more than simply telling the bank “I was scammed.” The legal strength of the dispute depends first on correctly classifying the transaction: whether it was purely unauthorized, fraudulently induced, merchant-related, or the product of account takeover. From there, the cardholder’s rights arise from a combination of contract, banking regulation, consumer protection, digital transaction law, and ordinary civil law principles. The bank is entitled to investigate, but it is not entitled to decide arbitrarily, rely on formulaic denial language, or ignore credible evidence of fraud.

The most important practical and legal steps are prompt reporting, written dispute submission, careful evidence preservation, disciplined handling of the billing account, and methodical escalation if the bank refuses reversal. OTP use, clicked links, or disclosed card details make the case harder, but they do not always end the matter. The real legal question is whether the transaction was truly authorized in an informed and voluntary sense, whether the bank acted with adequate diligence, and whether the issuer handled the financial consumer complaint fairly.

In the end, a scam-related credit card dispute is not won by outrage but by precision: a clear timeline, correct legal framing, documented fraud indicators, and persistent assertion of rights.

Final takeaway

In Philippine context, the right question is not only “Was I scammed?” but also “What kind of card transaction was this in law, what evidence shows it was unauthorized or fraudulently induced, and did the issuer meet its duty to investigate and treat my dispute fairly?”