How to Check Whether an International Bank Transfer Was Already Initiated

EXPAT BANKING

Bankeaz | Expats Team

11/21/20267 min read

Blog > Expat Banking > How to Check Whether an International Bank Transfer Was Already Initiated

How to Check Whether an International Bank Transfer Was Already Initiated

EXPAT BANKING

BANKEAZ | Expats Team
11/21/2026 - 4 min read

A confirmation screen appears after you schedule a payment overseas. Hours later, your recipient says that nothing has arrived. Before pressing “send” again, you need to answer a narrower question: was the original international bank transfer actually initiated, or was its instruction merely saved?

Those events are different. A bank may store a draft, accept a payment order, debit the funding account, release a payment to its network, and eventually report delivery. None of these stages should be inferred from a single ambiguous status label. This guide shows how to check the first transfer, establish the evidence you have, and decide what to ask next.

Review drafts, scheduled payments and outstanding approvals before assuming that the transfer was sent.

Find the last completed step

> Identify the last confirmed action in your banking app

Open the original banking app or provider account through a trusted route and locate the transaction history, scheduled payments, pending approvals and saved drafts. Search using the payment amount, destination currency, beneficiary, and the date you attempted to send it. A missing entry in one list is not proof that no instruction exists; another queue or account may hold it.

Compare the exact wording displayed. “Draft” generally means information was saved; “awaiting approval” means an additional authorization may be outstanding; “scheduled” can mean the order is set for future execution. “Submitted” or “accepted” may establish that the provider received the order, but not that its payment network has processed it. Labels are provider-specific, so open the status explanation rather than guessing.

Check for missed authentication steps such as a biometric prompt, one-time approval, security challenge or second signatory. For business payments, the creator of an order may not be the person authorized to release it. In banking for expats, switching devices, numbers or jurisdictions can also complicate authentication; review notifications securely and never share approval codes.

Write down the last status you can actually prove, including its timestamp and time zone. If the app has only a loading spinner or an error after confirmation, do not immediately repeat the action: check the transaction history and contact the provider first.

Record what each status proves and what it does not.

Match status to action

> Reconcile the payment order, debit and confirmation

Next, compare three separate records: the payment instruction, movements on the funding account, and any bank-issued confirmation. A payment order shows what you asked the institution to do. A debit shows that funds moved or were reserved on your side. A release confirmation may show that a payment was submitted for processing. These records are not interchangeable.

Locate the requested execution date, booking date and value date if available. If money appears as a pending card charge or an account hold, that is not necessarily a settled bank-transfer debit. If a transfer debit appears, check whether the bank later reversed or returned it. A returned debit may not appear beside the original instruction.

Save the original reference, recipient name, destination account identifier, amount, currency and any confirmation identifier. If your provider generated a receipt, identify whether it confirms order acceptance, execution or recipient availability; the US consumer remittance guidance illustrates why transfer receipts and the promised availability date matter.

For example, a €1,200 order entered on Friday at 18:30 might appear as accepted on Friday but scheduled for processing on Monday. This does not, by itself, mean the bank sent funds on Friday. Checking cut-off times helps explain the difference between the entry time and the operational processing date.

Keep the original reference, instruction, debit and bank-issued receipt together.

Build an evidence file

> Ask the bank whether the payment was released

If the app and account statement do not settle the question, contact the sending bank or provider using its official support channel. Ask a question that requires an operational answer: “Has this payment order been received and authorized, and has it been executed or released to the payment network?” Supply the original transaction reference and the minimum details needed for authentication.

Ask the bank to distinguish the following stages: draft or incomplete order; accepted but awaiting funding, verification or approval; queued for a future processing date; executed and released; rejected or cancelled; or returned after release. Request the execution date and time, the payment rail used, and the bank-issued evidence available for that stage.

For a SWIFT payment, the bank may provide a Unique End-to-end Transaction Reference (UETR). Swift explains the role of the UETR in associating interbank payment messages with one transfer. However, a UETR on its own is an identifier, not independent proof that the beneficiary has been credited. Ask the institution for the latest trace or status report rather than relying on the presence of an identifier alone.

Not all international payments use SWIFT. Local clearing arrangements, regional schemes and specialist providers may use different references and enquiry procedures. Cross-border banking requires checking the actual route, not assuming that one tracking system applies to every payment.

Request confirmation of authorization, execution, release time and rail.

Ask the sending bank precisely

> Cross-check the receiving side without confusing stages

If the sender’s institution confirms release, ask the beneficiary to review their actual account activity and incoming-payment notices. Share only the information reasonably required for identification: amount, currency, approximate date, sender name and relevant payment reference. Do not send passwords, one-time codes or full statements through an untrusted channel.

The recipient should ask their bank whether it has received an incoming payment, whether the amount is awaiting posting or screening, and whether further beneficiary information is needed. A payment can reach the receiving institution without yet being visible as an available balance. Conversely, a sender-facing “completed” label may describe the sending provider’s part rather than the beneficiary’s credit.

For supported SWIFT payments, some banks offer status tracking based on the UETR; Santander’s corporate payment tracker explanation describes how the same identifier can follow a payment. Tracking coverage and the meaning of “completed” differ by service. For other routes, the receiving institution may need its own incoming-payment enquiry.

When funds have been credited, verify the destination account and credited currency, not simply a notification. In diaspora banking and recurring family-support payments, multiple similar transfers can arrive close together; matching dates, references and amounts prevents one transfer from being mistaken for another.

Check incoming transfers without treating one bank’s “completed” status as final receipt.

Confirm with the recipient

> Use an evidence-based decision before resending

Create a short decision record with four fields: last verified stage, source of evidence, timestamp and next responsible party. Examples include “pending authorization—bank app—Tuesday 10:14—sender must approve” or “released—sending bank support—Wednesday 09:05—recipient bank to check incoming payment.” This prevents conversations from restarting with vague descriptions.

If the original order was never submitted or was definitively cancelled before execution, the provider can explain whether a fresh instruction is appropriate. If it is queued, pending review, executed or simply untraceable in the app, ask the provider to clarify or investigate before sending again. Even if a transfer seems late, initiating a replacement may create a second valid payment.

For a rent, tuition or supplier deadline, tell the recipient the verified stage and share an appropriate confirmation, while explaining explicitly that initiation is not proof of receipt. Agree in writing on how any duplicate or late payment would be handled. Where available, request a formal trace, cancellation assessment or recall, but do not assume cancellation is guaranteed after release.

Keep the evidence securely until the outcome is resolved. The same approach can help people managing international banking across different institutions, navigating banking beyond borders while travelling, or dealing with money problems abroad when a transfer status is unclear. The objective is to avoid acting on an assumption when the first payment may already exist.

Use the latest confirmed stage and responsible institution before resending.

Avoid a second payment by mistake

______________________________________________________________________________________________________________________________________________________

> Key Takeaways

✓ Search drafts, scheduled orders, pending approvals and transaction history.

✓ Distinguish order acceptance from execution, release and recipient credit.

✓ Keep the transfer reference, debit, timestamp and bank-issued receipt together.

✓ Ask the sending bank whether the payment was released and on which rail.

✓ Check receiving-bank evidence separately; do not rely on ambiguous “completed” labels.

✓ Investigate the first payment before authorizing any replacement.

Bankeaz is developing international financial solutions.
Designed for people managing money across countries.
Availability and eligibility depend on supported jurisdictions and future rollout.

Understanding payment verification across borders

> Conclusion

To verify whether an international transfer was initiated, begin with the payment-order history and outstanding approvals, compare the account debit with bank-issued evidence, and ask the sending institution whether the order was actually released. Then check the receiving side separately and document the latest confirmed stage before considering a replacement.

A clearer record can reduce duplicate payments, unnecessary enquiries and missed deadlines. Still, international banking depends on separate institutions, operating calendars and payment networks, so even careful verification cannot remove every delay or visibility gap.

> Related reads

Why Bank Transfers Have No Clear Status

Discover why international bank transfers often lack clear tracking information, making it difficult to know where your money is.

→ Read article

Why Your Transfer Stays “Pending” for Days

Understand why international transfers can remain pending for days due to banking checks, processing times, and intermediary institutions.

→ Read article

How to Check Banking Cut-Off Times Before Sending an International Transfer

Learn how to check banking cut-off times to anticipate processing delays and better plan your international transfers.

→ Read article

How to Use Payment References to Avoid Transfer Delays

Learn how to use accurate payment references to help banks identify transactions and reduce international transfer delays.

→ Read article

______________________________________________________________________________________________________________________________________________________

by BANKEAZ

On demand banking services for all

Bankeaz | App LogoBankeaz | App Logo

______________________________________________________________________________________________________________________________________________________

Learn more about Expat Banking

Bankeaz - A young man recommends Bankeaz App to his friend.

Global lives deserve simpler banking.

Bankeaz | Card & Bankeaz app
Bankeaz | Card & Bankeaz app
Bankeaz | App Store
Bankeaz | App Store
Bankeaz | Google Play
Bankeaz | Google Play

Download the BANKEAZ app for a 100% mobile banking experience. Available on iOS and Android - public testing by invitation.

Legal documents

Disclaimer

Bankeaz is designed for people living between countries. Availability may vary depending on the user’s jurisdiction of residence.

The Bankeaz app is developed by Arcadia, a company currently being incorporated in Switzerland.

Bankeaz does not provide banking services in its own name. Financial services are provided by licensed and regulated partner institutions, in accordance with applicable laws and regulations.

Copyright © 2026 - Arcadia | Bankeaz - All rights reserved

Social Media
____________________

LinkedIn ↗

Youtube ↗

Facebook ↗

X (formerly Twitter) ↗

Instagram ↗

Address
____________________

Bankeaz | Offices location
Bankeaz | Offices location
Bankeaz | Phone
Bankeaz | Phone
Bankeaz | LogoBankeaz | Logo

__________________________________________________________________________________________________________________________________________________

Bankeaz | Back to TopBankeaz | Back to Top

(- - -) - - - - - - - - - -

Zurich - CH

__________________________________________________________________________________________________________________________________________________

Help
____________________

System Status

FAQs

___________________________________________________________________________________________________________________________________________________

__________________________________________________________________________________________________________________________________________________