I. Introduction

Digital banking and electronic fund transfers have become ordinary parts of Philippine commercial life. Salary payments, family remittances, business collections, online purchases, loan payments, and supplier settlements are now often completed through bank apps, e-wallets, InstaPay, PESONet, QR Ph, or other electronic channels.

A common and stressful problem arises when the sender receives a confirmation that the transfer was “successful,” but the recipient does not receive the funds. The sender may have a screenshot, transaction reference number, debit confirmation, SMS notice, or email receipt. Yet the recipient’s account shows no credit.

This situation raises practical and legal questions:

Is the sender still liable to pay? Is the bank responsible? Can the recipient demand payment again? What evidence is needed? Can the issue become a criminal case? What remedies are available under Philippine law and regulation?

This article discusses the Philippine legal context of a bank transfer that appears successful on the sender’s side but is not received by the intended recipient.

This is general legal information, not a substitute for advice from a Philippine lawyer who can review the documents, bank records, and surrounding facts.

II. Understanding the Problem

A “successful” sender confirmation does not always mean that the recipient has already received usable funds.

In electronic banking, several events may happen separately:

The sender’s bank debits the sender’s account.
The sender’s bank accepts the transfer instruction.
The payment network processes the transaction.
The recipient’s bank receives the instruction.
The recipient’s bank posts the credit.
The recipient can actually use or withdraw the money.

A confirmation from the sender’s app may prove that the sender’s bank accepted or processed the instruction. It may not always prove that the recipient’s bank has finally credited the account.

This distinction matters because legal responsibility may depend on whether the transfer was actually completed, reversed, placed on hold, rejected, credited to the wrong account, or delayed due to technical, compliance, or account-related issues.

III. Common Causes of Non-Receipt

1. Delayed Posting

Some transfers are not instantaneous. InstaPay is generally designed for near-real-time transfers, while PESONet is batch-based and may post later depending on cut-off times and banking days. Transfers made on weekends, holidays, or after cut-off may be credited on the next banking day.

2. Incorrect Account Details

The sender may have entered the wrong account number, bank, account name, mobile number, QR code, or e-wallet identifier. If the receiving institution credits the account number provided, recovery may become difficult, especially if the wrong recipient has withdrawn or transferred the funds.

3. Name Mismatch or Validation Issues

Some institutions may hold, reject, or review transfers when the account name, number, or other details do not match expected records.

4. Receiving Bank System Issue

The sender’s bank may have processed the debit, but the recipient’s bank may have experienced downtime, reconciliation delay, posting error, or internal system failure.

5. Payment Network Issue

The problem may lie between banks, particularly if a third-party clearing or switching system is involved.

6. Compliance, AML, or Fraud Hold

Banks are required to observe anti-money laundering, fraud monitoring, sanctions screening, and know-your-customer obligations. Transactions may be held, reviewed, or temporarily restricted if flagged.

7. Reversal Pending

The transaction may have failed after the sender was debited, with the amount scheduled for return. The sender may see a “successful” or “processing” status before the final reversal appears.

8. Recipient Account Problem

The recipient’s account may be closed, dormant, restricted, frozen, incorrect, over limit, under review, or otherwise unable to receive funds.

9. Screenshot or Confirmation Fraud

In some cases, the sender’s proof may be fake, altered, outdated, or from a different transaction. This is common in online selling disputes and private payment arrangements.

IV. Legal Nature of a Bank Transfer in the Philippines

A bank transfer can involve several legal relationships:

1. Sender and Recipient

The sender may be paying a debt, purchase price, rent, loan, remittance, settlement, donation, or other obligation. The legal issue between them is usually whether payment has been made.

Under Philippine civil law principles, payment extinguishes an obligation only when it is properly made. If the creditor or intended recipient did not actually receive the money, the sender may still have to prove that valid payment occurred.

2. Sender and Sender’s Bank

The sender has a contractual relationship with the bank. The bank is expected to follow lawful instructions, observe reasonable diligence, and process transactions according to applicable terms, banking rules, and regulations.

3. Recipient and Recipient’s Bank

The recipient’s bank may be responsible for properly crediting incoming funds, subject to account status, banking rules, and verification.

4. Banks and Payment System Operators

Interbank transfers may involve payment systems, clearing houses, or switching networks. Operational responsibility may be allocated among the participating institutions under rules not always visible to consumers.

V. Has Payment Been Legally Made?

The central question is often this:

Does a sender’s successful transfer confirmation prove payment to the recipient?

The answer depends on the facts.

A sender confirmation is strong evidence that the sender initiated and may have completed a transaction from the sender’s side. But it is not always conclusive proof that the intended recipient received the funds.

In ordinary obligations, payment generally requires delivery of the thing or amount due to the creditor or to someone authorized to receive it. If the intended recipient’s account was never credited, the sender may still need additional proof that the funds were actually transferred to the correct destination.

Practical Rule

For private disputes, the safest position is:

A screenshot alone is not enough. The sender should obtain official bank confirmation showing the destination account, amount, date, time, reference number, and final transaction status.

The recipient, meanwhile, should obtain account records or bank certification showing non-receipt.

VI. Burden of Proof

In a dispute, the party asserting payment generally carries the burden of proving it.

If the sender claims, “I already paid,” the sender should prove actual payment. Evidence may include:

Official bank receipt or transaction advice;
Transaction reference number;
Sender’s bank statement showing debit;
Confirmation from sender’s bank;
Proof that the account number used belongs to the recipient;
Proof that the transfer was not reversed;
Written confirmation from the recipient’s bank, if obtainable;
Email or ticket response from the bank;
Screenshots, preferably supported by official records.

The recipient may prove non-receipt through:

Bank statement for the relevant period;
Transaction history;
Bank certification of no credit received;
Customer service ticket;
Screenshots from the banking app;
Written communication immediately notifying the sender of non-receipt.

In litigation, screenshots are generally better treated as supporting evidence, not the whole case.

VII. Duties of Banks in Electronic Transfers

Philippine banks are expected to exercise high standards of diligence because banking is impressed with public interest. A bank is not merely an ordinary business; it handles money entrusted by the public.

In electronic fund transfer issues, banks are generally expected to:

Provide accessible complaint channels;
Investigate disputed transactions;
Trace the transaction using the reference number;
Coordinate with the receiving bank or payment network;
Provide a clear response;
Reverse funds when appropriate;
Protect customers from unauthorized or erroneous transactions;
Observe consumer protection requirements;
Maintain adequate electronic banking controls.

A bank’s liability will depend on where the failure occurred, whether it followed the customer’s instruction correctly, whether the customer supplied wrong details, whether there was negligence, and whether regulatory standards were breached.

VIII. Role of the Bangko Sentral ng Pilipinas

The Bangko Sentral ng Pilipinas regulates banks, electronic money issuers, operators of payment systems, and other supervised financial institutions. It also provides a consumer assistance mechanism for complaints against BSP-supervised institutions.

A customer who has already complained to the bank but remains unsatisfied may escalate the matter to the BSP consumer assistance channels. Before doing so, the customer should usually have:

Filed a formal complaint with the bank;
Obtained a reference or ticket number;
Allowed the bank reasonable time to investigate;
Kept copies of all correspondence;
Prepared supporting documents.

The BSP may require the financial institution to respond, explain, or resolve the complaint according to applicable rules. The BSP process is not the same as a court case, but it can be useful in compelling institutional attention and documentation.

IX. What the Sender Should Do Immediately

A sender who has been debited but whose recipient has not received funds should act quickly.

1. Verify the Transfer Details

Check:

Recipient bank name;
Account number;
Account name;
Amount;
Date and time;
Transfer channel;
Reference number;
Fees;
Final transaction status;
Whether the transaction was reversed.

2. Contact the Sender’s Bank

Ask for a formal trace or investigation. Use precise language:

“Please trace this fund transfer. My account was debited, and the app shows successful, but the recipient has not received the funds. Please confirm whether the transaction was successfully credited, rejected, pending, or reversed.”

Request a ticket number.

3. Ask for Written Confirmation

A written bank response is more useful than a verbal hotline statement. Ask the bank to confirm:

Whether the transaction was completed;
Whether funds reached the receiving bank;
Whether a reversal is pending;
Expected resolution time;
Whether coordination with the receiving bank has been initiated.

4. Notify the Recipient

Send the recipient the transaction reference number and ask them to check with their bank.

5. Do Not Send a Duplicate Payment Prematurely

If the sender sends a second payment and the first later posts, there may be overpayment. The parties should agree in writing how to treat any duplicate credit.

X. What the Recipient Should Do Immediately

A recipient who has not received the transfer should also act quickly.

1. Check the Correct Account

Confirm that the account details given to the sender were correct. If the recipient supplied the wrong account number, the legal analysis may change.

2. Check Pending or Recent Transactions

Some banking apps show delayed credits only after refresh, statement generation, or batch posting.

3. Contact the Receiving Bank

Ask whether an incoming transfer with the sender’s details, amount, date, and reference number is pending, rejected, or under review.

4. Obtain Proof of Non-Receipt

This may include:

Transaction history;
Account statement;
Written bank response;
Certification from the bank, if available.

5. Communicate in Writing

The recipient should notify the sender in writing:

“As of [date and time], the amount has not been credited to my account. I have checked my account and contacted my bank. Please coordinate with your bank for tracing.”

Written communication helps prevent later disputes about delay, bad faith, or silence.

XI. If the Transfer Went to the Wrong Account

This is one of the most difficult situations.

If the sender entered the wrong account number and the money was credited to another person, recovery may require cooperation from the banks and the unintended recipient. Banks are often constrained by privacy and banking secrecy rules. They may not simply disclose the identity or account details of the wrong recipient to the sender.

Possible remedies include:

Requesting the sender’s bank to initiate a recovery request;
Requesting the receiving bank to contact the unintended recipient;
Asking for voluntary return;
Filing a civil action for recovery if the recipient is identified;
Considering criminal remedies if the unintended recipient knowingly keeps or uses money that clearly does not belong to them.

However, if the sender caused the error by entering incorrect details, the bank may deny liability if it processed the transaction according to the instructions given.

XII. Civil Liability Between Sender and Recipient

A. If the Sender Owed Money to the Recipient

Suppose a buyer owes a seller ₱20,000 and claims to have paid by bank transfer. The seller says no funds were received.

The buyer must prove payment. If the buyer only has a screenshot but no final confirmation of credit, the seller may still demand payment. However, fairness may require both parties to cooperate in tracing before accusing each other of non-payment or fraud.

If the bank later confirms that the transfer was credited to the correct account, the seller may no longer demand payment. If the transfer failed and was reversed to the buyer, the buyer remains liable to pay.

B. If the Recipient Gave Wrong Details

If the recipient gave an incorrect account number or wrong QR code, the sender may argue that the loss was caused by the recipient’s own mistake. The issue then becomes whether the sender followed the payment instructions exactly.

C. If the Sender Entered Wrong Details

If the sender mistyped the account number or selected the wrong bank, the sender may remain liable to the intended recipient. The sender may separately pursue recovery from the unintended recipient.

D. If the Bank Was at Fault

If the sender and recipient both provided correct information and the bank or payment system caused the loss or unreasonable delay, the responsible institution may be liable depending on proof of negligence, breach of contract, or regulatory violation.

XIII. Possible Causes of Action

Depending on the facts, possible civil claims may include:

1. Collection of Sum of Money

The recipient may sue the sender if the underlying obligation remains unpaid.

2. Breach of Contract

A customer may sue a bank if the bank failed to perform its contractual obligations under the deposit account, electronic banking terms, or transfer service.

3. Damages for Negligence

A party may claim damages if a bank or person failed to exercise the required diligence and caused loss.

4. Unjust Enrichment or Solutio Indebiti

If funds are mistakenly credited to a person who has no right to them, that person may be required to return the amount. Under civil law principles, no one should unjustly enrich themselves at another’s expense.

5. Specific Recovery or Restitution

The owner of funds may seek recovery from the person who wrongfully received or retained them.

6. Consumer Complaint

A bank customer may pursue a consumer complaint through the bank’s internal complaint process and, if unresolved, through the BSP’s consumer assistance mechanism.

XIV. Can It Be a Criminal Case?

Not every failed or delayed bank transfer is a crime. Many are technical, operational, or civil in nature.

However, criminal issues may arise in certain situations.

1. Fake Transfer Proof

If a person creates or uses a fake bank transfer screenshot to make another person release goods, provide services, or acknowledge payment, this may potentially involve estafa, falsification, cybercrime-related offenses, or other fraud-related liability depending on the facts.

2. Intentional Non-Payment

Mere failure to pay a debt is generally not automatically a crime. But if there was deceit at the beginning, such as pretending to pay through a fake confirmation, criminal liability may be considered.

3. Wrong Recipient Keeping the Money

If a person receives money by mistake and knowingly keeps, withdraws, or spends it despite being informed that it belongs to another, civil liability is clear, and criminal implications may be considered depending on circumstances.

4. Unauthorized Transfer

If the sender did not authorize the transfer and the account was hacked or compromised, the matter may involve cybercrime, fraud, identity theft, phishing, or unauthorized access issues.

XV. Evidence Checklist

For the sender:

Screenshot of successful transfer;
Official transaction receipt;
Reference number;
Bank statement showing debit;
Account details entered;
Recipient’s payment instructions;
Bank complaint ticket;
Written bank replies;
Proof of no reversal;
Communications with recipient.

For the recipient:

Bank statement showing no credit;
Transaction history;
Written bank response;
Account details previously given to sender;
Communications with sender;
Demand letter, if any;
Proof of goods/services released or obligation involved.

For both parties:

Date and time of transfer;
Amount;
Platform used;
Transaction channel;
Cut-off rules, if relevant;
Names and account identifiers;
All SMS/email/app notifications;
Screenshots with visible timestamp;
Any later reversal or delayed posting.

XVI. Demand Letters

A demand letter may be useful when informal coordination fails.

A. Demand Letter from Recipient to Sender

The recipient may demand payment if the funds were not received and the sender cannot prove final credit.

The letter should state:

The obligation owed;
Amount due;
Alleged transfer details;
Non-receipt;
Request for official bank proof;
Deadline to pay or resolve;
Reservation of rights.

B. Demand Letter from Sender to Bank

The sender may demand investigation and reversal or confirmation.

The letter should state:

Account details;
Transaction reference number;
Amount;
Date and time;
Recipient details;
Proof of debit;
Recipient’s claim of non-receipt;
Request for written findings;
Request for reversal or completion.

C. Demand Letter to Wrong Recipient

If the wrong recipient is identified, the letter should demand return of funds and warn that retention of mistakenly received money may give rise to legal action.

XVII. Sample Notice from Sender to Bank

Subject: Request for Trace and Resolution of Bank Transfer Not Received

I am requesting an urgent trace and investigation of a fund transfer made from my account on [date] at approximately [time] in the amount of ₱[amount]. The transaction reference number is [reference number].

My account was debited and the transaction appeared successful on my banking application. However, the intended recipient, [recipient name], maintains that the funds have not been credited to the recipient account.

Please confirm in writing whether the transfer was successfully credited, rejected, pending, reversed, or placed on hold. If the transaction was not completed, please reverse the amount to my account immediately. If further coordination with the receiving bank or payment network is required, please provide the applicable ticket or case number and expected resolution timeline.

I reserve all rights and remedies under applicable law and banking regulations.

XVIII. Sample Notice from Recipient to Sender

Subject: Notice of Non-Receipt of Bank Transfer

This is to inform you that, as of [date and time], the amount of ₱[amount] allegedly transferred on [date] has not been credited to my account.

Please coordinate with your bank using the transaction reference number and request a formal trace. Kindly provide official confirmation from your bank showing that the funds were actually credited to the correct account, or otherwise complete payment through an agreed method.

This notice is made without prejudice to my rights and remedies.

XIX. Bank Secrecy and Privacy Issues

A common frustration is that banks may refuse to disclose details about another account. Philippine banking secrecy and data privacy principles can limit what banks may reveal to customers.

For example, if funds were transferred to a wrong account, the bank may not freely disclose the account holder’s name, address, or transaction history to the sender. The bank may instead communicate internally with the receiving institution or contact the unintended recipient directly.

This does not mean the sender has no remedy. It means recovery may require formal bank processes, regulatory complaint, subpoena, court order, or law enforcement involvement in appropriate cases.

XX. Time Is Important

Delays can make recovery harder. If funds were wrongly credited, the unintended recipient may withdraw or transfer them. If fraud is involved, accounts may be emptied quickly.

A party should report the issue immediately to:

Sender’s bank;
Recipient’s bank;
E-wallet provider, if applicable;
Platform or marketplace, if involved;
BSP consumer assistance, if unresolved;
Law enforcement or cybercrime authorities, if fraud or unauthorized access is suspected.

XXI. Practical Settlement Between Sender and Recipient

Where both parties are acting in good faith, the best approach is usually cooperative.

They may agree that:

The sender will file a trace request immediately;
The recipient will obtain proof of non-receipt;
Neither party will accuse the other of fraud without evidence;
The sender will pay again only if the first transfer is reversed or confirmed failed;
If duplicate credit occurs, the recipient will return the excess immediately;
All communications will be in writing.

This avoids unnecessary escalation while preserving each party’s rights.

XXII. Special Considerations for Online Sellers

Online sellers often face fake payment screenshots. A seller should avoid releasing goods based solely on a screenshot unless the relationship is trusted or the risk is acceptable.

Best practices:

Confirm actual credit in the seller’s own account;
Use official app notifications, not only buyer screenshots;
Check account balance and transaction history;
Beware of edited screenshots;
Match amount, name, date, and reference number;
Do not rely on “floating” explanations indefinitely;
Use escrow or platform-protected payment systems for higher-value transactions.

For sellers, the safest commercial rule is:

No confirmed credit, no release of goods.

XXIII. Special Considerations for Employers, Businesses, and Payroll

If a company sends salary, commission, or supplier payment and the recipient does not receive it, the business should not rely only on batch confirmation. It should check bank reports, rejected items, account validation, and returned transactions.

For payroll, delayed or failed credit can create labor and employee-relations issues. Employers should act promptly, document the investigation, and pay the employee through an alternative method if the original transaction failed.

For supplier payments, the contract may specify when payment is deemed made. Some contracts treat payment as made upon debit, while others require actual receipt or cleared funds.

XXIV. Special Considerations for Loans and Debt Payments

If a borrower claims to have paid a lender by bank transfer, the borrower should retain official proof. If the lender does not receive funds, the borrower may still be treated as unpaid until actual credit or valid tender of payment is proven.

If delay causes penalties or interest, the dispute may turn on:

Whether the borrower used the correct payment channel;
Whether the lender gave correct details;
Whether the bank caused the delay;
Whether the borrower notified the lender promptly;
Whether the contract defines payment date as transfer initiation, debit date, or credit date.

XXV. When to Escalate

Escalation may be appropriate when:

The bank gives no clear response;
The amount is substantial;
More than a reasonable processing period has passed;
The recipient denies receipt despite bank confirmation;
The sender’s proof appears fake;
The transfer went to a wrong account;
There is suspected fraud, hacking, or phishing;
The bank refuses to issue written findings;
The transaction remains unresolved after formal complaint.

Escalation options include:

Bank branch or official customer care;
Bank complaint management unit;
BSP consumer assistance;
Barangay conciliation, if applicable between individuals in the same city or municipality;
Small claims court, if the claim qualifies;
Regular civil action;
Criminal complaint, if facts support fraud or cybercrime;
Legal demand letter through counsel.

XXVI. Small Claims Court

For money claims within the jurisdictional threshold of small claims procedure, a party may consider filing a small claims case. This can be useful for unpaid obligations, wrongfully retained funds, or reimbursement claims.

Small claims procedure is designed to be simpler and faster than ordinary civil litigation, and lawyers are generally not allowed to appear for the parties during hearings. However, legal advice before filing can still be valuable.

A claimant should prepare:

Contract, invoice, receipt, chat messages, or proof of obligation;
Transfer records;
Bank statements;
Demand letter;
Proof of non-payment or non-receipt;
Identity and address of defendant;
Computation of claim.

XXVII. Barangay Conciliation

If the dispute is between individuals who live in the same city or municipality, barangay conciliation may be required before filing certain court cases. This depends on the residence of the parties, nature of the dispute, and applicable exceptions.

For online transactions between parties in different cities, barangay conciliation may not apply. When in doubt, consult the barangay or a lawyer before filing.

XXVIII. Liability of the Wrong Recipient

If money is accidentally credited to a person who is not entitled to it, that person should not treat it as free money.

The wrong recipient should:

Avoid withdrawing or spending the funds;
Notify the bank;
Cooperate in reversal;
Keep records of communications.

A person who knowingly keeps money transferred by mistake may face civil liability to return it, plus possible damages. Depending on conduct, criminal issues may also arise.

XXIX. Liability of the Sender

The sender may be liable if:

The sender never actually transferred the money;
The sender used fake proof;
The sender transferred to the wrong account due to own error;
The transfer failed and was reversed;
The sender refuses to cooperate in tracing;
The underlying obligation remains unpaid.

The sender may not be liable, or liability may be reduced, if:

The recipient gave wrong account details;
The recipient’s bank received and credited the funds;
The recipient actually received the money but denies it;
The bank or payment system caused the failure despite correct sender action;
The contract treats payment as completed upon sender debit or transfer initiation.

XXX. Liability of the Recipient

The recipient may be liable if:

The recipient actually received the money but falsely denies it;
The recipient gave wrong account details;
The recipient refuses to return duplicate payment;
The recipient receives both original and replacement payment and keeps both;
The recipient acts in bad faith.

The recipient is usually justified in withholding acknowledgment of payment until actual credit is confirmed.

XXXI. Liability of the Bank

A bank may be liable if it:

Debited funds but failed to process the transfer properly;
Failed to reverse a failed transaction within a reasonable time;
Credited funds to an account despite clear mismatch or internal error;
Failed to investigate a complaint properly;
Gave misleading confirmation;
Ignored consumer protection obligations;
Failed to maintain adequate system controls;
Acted negligently or in bad faith.

But a bank may have defenses if:

It followed the exact account details entered by the customer;
The customer authorized the transaction;
The issue was caused by wrong information supplied by the sender or recipient;
The transaction is still within normal processing time;
The transfer was subject to compliance review;
Terms and conditions allocate certain risks to the customer, subject to law and regulation.

XXXII. What Counts as “Successful”?

The word “successful” can be misleading. A transaction may be successful in one sense but incomplete in another.

Possible meanings:

Successfully submitted;
Successfully debited;
Successfully accepted by sender’s bank;
Successfully transmitted to network;
Successfully received by receiving bank;
Successfully credited to recipient;
Successfully completed and final.

When dealing with a dispute, ask the bank to clarify exactly what “successful” means in its records.

The strongest form of confirmation is one showing that the funds were credited to the intended receiving account and not reversed.

XXXIII. Recommended Language When Talking to Banks

Avoid vague statements like:

“My transfer is missing.”

Use precise language:

“Please confirm the final status of this transaction: whether it was credited to the receiving account, rejected, reversed, pending, or under investigation.”

Ask for:

Final status;
Receiving institution response;
Trace result;
Reversal status;
Reason for delay;
Expected resolution;
Written certification or email.

XXXIV. Red Flags of Fake Transfer Confirmation

Be cautious when:

The screenshot has inconsistent fonts or spacing;
The reference number is hidden;
The sender refuses to show transaction details;
The sender pressures immediate release of goods;
The name or amount does not match;
The transaction time is suspicious;
The sender says “it will reflect later” but cannot provide official proof;
The sender uses a different account name;
The screenshot lacks bank branding or transaction ID;
The supposed confirmation is only a photo, not an in-app share or email.

For high-value transactions, insist on actual credit or verifiable official confirmation.

XXXV. Data Privacy Considerations

Parties should avoid publicly posting another person’s account number, full name, mobile number, address, or transaction details. Public shaming on social media may create separate legal risks, including defamation, data privacy complaints, or harassment allegations.

Communicate privately first. Escalate formally through banks, regulators, lawyers, or authorities when needed.

XXXVI. Best Practices to Prevent the Problem

For senders:

Double-check account number and bank;
Send a small test amount for first-time recipients;
Save official receipts;
Use QR Ph where available to reduce typing errors;
Avoid transferring under time pressure;
Confirm recipient details in writing;
Use remarks or notes identifying purpose;
Keep sufficient balance for fees;
Monitor for reversal.

For recipients:

Provide account details in copyable text;
Avoid screenshots that can be misread;
Confirm exact bank name and account number;
Notify sender immediately if not received;
Do not release goods until credit is confirmed;
Keep records of all payments.

For businesses:

Use validated payment channels;
Reconcile daily;
Maintain written payment policies;
Train staff to detect fake confirmations;
Use official receipts only after confirmed credit;
Maintain escalation contacts with banks.

XXXVII. Key Legal Takeaways

A sender’s successful confirmation is evidence, but not always conclusive proof of receipt.
Payment disputes depend on proof of actual credit, correct details, and final transaction status.
The party claiming payment generally must prove payment.
The sender should immediately request a bank trace.
The recipient should obtain proof of non-receipt.
If the transfer went to the wrong account, recovery may be difficult but not impossible.
Banks must investigate and handle consumer complaints properly.
BSP escalation may be available after the bank complaint process.
Fake transfer proof can create criminal liability.
The safest commercial practice is to treat payment as complete only when funds are actually credited, unless the contract says otherwise.

XXXVIII. Conclusion

A bank transfer marked “successful” on the sender’s side but not received by the recipient is not a simple matter of who is telling the truth. It may involve delayed posting, bank error, wrong account details, failed clearing, compliance holds, system issues, or fraud.

In the Philippine context, the practical and legal solution begins with documentation. The sender should prove the debit and request a formal trace. The recipient should prove non-receipt. Both should preserve written communications. If unresolved, the matter may be escalated to the bank’s complaint unit, the BSP, barangay proceedings, small claims court, civil court, or law enforcement, depending on the facts.

The most important rule is this:

Do not rely on screenshots alone. Obtain official bank records and written confirmation of the transaction’s final status.