Skip to main content

Troubleshoot incoming and outgoing transfers

This guide helps partner support teams troubleshoot incoming and outgoing credit transfers for your users: what to collect, how to explain common statuses, when to wait, and when to contact Swan Support.

Key takeaways
  • Start every investigation by identifying direction (IN or OUT), transfer type, and the transfer's status.
  • If an outgoing transfer isn't visible at all, it wasn't registered. Your user needs to initiate it again.
  • Rejected outgoing transfers (instant, standard, and international) have no impact on the account balance: the funds never leave the account.
  • Rejected incoming transfers take up to three business days to return for SEPA transactions and up to 10 business days for international ones.
  • Your users can download a transaction confirmation statement for Booked SEPA, Instant SEPA, and International Credit Transfers.
  • Before Swan can trace a Booked outgoing transfer, you need written proof from the beneficiary's bank that the money wasn't received. An account statement isn't enough.

Who does what​

WhoWhat they do
DebtorSends the transfer and contacts their bank if the transfer is missing or rejected.
CreditorReceives the transfer and checks the account details or balance.
Swan SupportProcesses transfers and investigates cases with banking partners when you provide the required evidence.
You (Partner support team)Identify the transfer, explain the visible status, gather the required evidence, and contact Swan when needed.

Transfer types​

Credit transfers move funds from a debtor to a creditor. Troubleshooting depends on identifying the right type first.

Transfer typeWhat it's forWhat to know for support
Instant SEPA Credit TransferEUR transfer that processes immediately.Completes in around 10 seconds. Runs 24/7, including weekends and SEPA closing days. Investigate any Pending status.
SEPA Credit TransferEUR transfer within SEPA, sometimes called a regular transfer.Settles within three to five business days. Not processed on weekends or SEPA TARGET closing days.
Swan Internal Credit TransferTransfer between two Swan accounts.Almost as quick as instant. Both accounts are on Swan, so there's no external bank to chase. Funds set aside following an administrative or judicial seizure can also appear as a Swan Internal Credit Transfer because they're moved to Swan's internal seizure account.
International Credit TransferTransfer outside the SEPA zone, in a non-euro currency.Typically up to 10 days depending on destination and rail. Can't have the status Upcoming. Creates a separate fee transaction.
Instant transfer limit

Instant SEPA Credit Transfers have a maximum of €100,000 per transaction. Above that, your user needs to send a regular SEPA Credit Transfer instead. See SEPA Credit Transfers.


Permissions​

Check an account member's rights in Dashboard > Data > Account memberships, then open the membership and check General > rights:

  • canViewAccount: needed to see transfers.
  • canInitiatePayments: needed to send transfers.
  • canManageBeneficiaries: needed to add or edit saved beneficiaries.

Adding a beneficiary also requires your user to give consent, separately from consenting to the transfer itself.


Country coverage and currencies​

International Credit Transfers go to a limited set of countries, and each currency has to travel on a specific rail. SWIFT carries USD, EUR, and GBP only. Local rails carry local currencies, and your user needs the exact rail for the currency; Indonesian rupiah can only go on the Indonesian rail, for example.

Check current coverage in International Credit Transfers. If the country or currency isn't supported, Swan can't send or receive funds for that route.

Integration: transfer statuses

Ask your development team to surface transfer status and transaction details inside your own product using Swan's API, so your team can investigate without opening the Dashboard. See Credit transfers. They can also test transfer scenarios using the Event Simulator in Dashboard > Developers > Event Simulator.


Start every investigation​

Confirm your user is asking about a transfer that has already happened or should have happened. If they're asking how to create one, point them to your product's transfer flow instead.

1. Identify the transfer​

Ask your user for:

  • Debtor IBAN
  • Creditor IBAN
  • Amount and currency
  • Execution date
  • Transfer reference, transaction label, or end-to-end reference

Then find the transaction in Dashboard > Data > Transactions. The transaction detail page gives you the transaction ID, execution date, status, amount, debtor and creditor details, and any supporting documents.

For international transfers that aren't visible, direct your user to ask the sending institution for a SWIFT payment confirmation, usually called an MT103.

2. Classify the issue​

  1. Is it incoming (IN) or outgoing (OUT)?
  2. Which transfer type is it?
  3. Is there a transaction in the history? If so, what's its status?
  4. Is there a shareable reason in the transaction details?
Accounts still in verification

While account holder verification is in progress, the account's payment level is Limited and Swan automatically rejects some incoming transfers. See Limited account restrictions for current thresholds, and share Transfer restrictions during verification with your user.

3. Check for incidents​

Check status.swan.io for a known incident overlapping the transaction timing. If there is one, include that context when you contact Swan.


Quick triage​

DirectionTransfer typeStatus or visibilityWhat you do
OutgoingInstant SEPABooked, beneficiary says not receivedDirect your user to ask the beneficiary to check with their bank. Get written proof of non-receipt before contacting Swan.
OutgoingInstant SEPARejectedShare the reason shown in the Dashboard, unless it's compliance-related. If a fallback was used, the transfer continues as a regular SEPA Credit Transfer. Otherwise funds return automatically.
OutgoingInstant SEPAPendingUnusual for an instant transfer. Submit a Swan Support request with the transaction details.
OutgoingSEPABooked, beneficiary says not receivedWait three to five business days from submission. If it's still missing, get written proof of non-receipt.
OutgoingSEPA or InternationalPendingIf a review is indicated, wait. If a technical pending status persists past the next business day, submit a Swan Support request.
IncomingInstant SEPABookedConfirm the funds are available.
IncomingInstant SEPAPendingUnusual for an instant transfer. Submit a Swan Support request.
IncomingSEPANot visibleAsk your user for proof of transfer. If beneficiary details match and normal timelines have passed, the sender's bank needs to investigate.
IncomingInternationalNot visibleAsk your user for the MT103. Submit a Swan Support request if you still can't locate it.

Handle outgoing transfers​

For what each status means, see credit transfer statuses.

If an outgoing transfer is Booked but the beneficiary says they didn't receive it​

Applies to: SEPA, Instant SEPA, and International Credit Transfers. For Swan Internal transfers, check the receiving Swan account directly instead. There's no external bank involved.

A Booked outgoing transfer means Swan processed and submitted it.

  1. Confirm the transfer details with your user.
  2. Direct your user to ask the beneficiary to check with their financial institution.
  3. Give your user the transaction confirmation statement or end-to-end reference to pass on. See Give your user proof of a transfer.
  4. If the beneficiary's bank says it didn't receive the funds, direct your user to ask that bank for written proof.
  5. Submit a Swan Support request with that proof and the transaction details.

Normal processing times​

Allow the normal processing time before escalating:

  • SEPA Credit Transfer: between three to five business days
  • Instant SEPA Credit Transfer: around 10 seconds
  • International Credit Transfer: up to 10 business days

See Trace a transfer that wasn't received for the full procedure.

If an outgoing transfer is Rejected​

First, check the rejection reason. See the full list of rejection reason codes.

Don't disclose compliance reasons

If the transfer was rejected for compliance, tell your user that you don't have information about the rejection reason. Don't speculate or share internal compliance details. If the transfer was rejected for another reason, share only the reason shown in the Dashboard.

For rejected outgoing transfers:

  • The funds never leave the account, so there's nothing to return and no support request is needed.
  • If Instant SEPA fallback was activated, the transfer continues as a regular SEPA Credit Transfer and no action is needed. Two transactions appear in the history: the rejected instant transfer and the new regular one. This is expected and isn't a duplicate. See Fallback mode.
  • If there was no fallback, your user needs to resubmit once they've addressed the reason.
  • For instant transfers, retrying as a regular SEPA Credit Transfer can help, because regular transfers have fewer real-time constraints.
Exchange rate locks for one business day

Applies to: International Credit Transfers involving currency conversion.

The exchange rate is calculated when your user starts the transfer and locks for one business day. If your user doesn't consent within that time, the rate unlocks and Swan rejects the transfer. Your user needs to start a new transfer at the current rate.

Direct your user to Currency exchange and fees for International Credit Transfers, or to Consent and SMS issues if consent is what's failing.

If a transfer was rejected for insufficient funds but the balance looked sufficient​

Swan checks the account's Available balance immediately before executing, and rejects instantly if it's short. Available excludes amounts already committed, pending card authorizations, other upcoming transfers, and pending direct debits, so your user may be looking at a different number.

  1. Check the Available balance at the time of the rejection, not now.
  2. Look for other transactions competing for the same funds around that time.
  3. Explain the difference, and tell your user to resubmit once funds are available.

If your user reports an error or a feature that isn't working​

Applies to: All transfer types.

Errors when creating a transfer, adding a beneficiary, or setting up a standing order usually come from your product or your integration, not from a transfer that already exists. Don't troubleshoot these as a missing transfer.

  1. Ask what they were doing, what they saw, and when, including the exact error message and a screenshot.
  2. Check status.swan.io for an overlapping incident.
  3. Check the member's rights in Dashboard > Data > Account memberships. Adding beneficiaries needs canManageBeneficiaries; sending needs canInitiatePayments.
  4. Check that account holder verification is complete.
  5. If none of that explains it, pass the error message, timing, and account ID to your development team.
  6. If they confirm the error is coming from Swan's API, submit a Swan Support request with their findings.
Beneficiary and standing order management are part of your integration

Whether your users can add beneficiaries or manage standing orders depends on what your product exposes through Swan's API. If a capability is missing or broken for every user rather than one, it's an integration task for your development team, not a support request.

If your user wants to modify a submitted transfer​

Submitted transfers can't be edited.

  • If the transfer is Upcoming, cancel it and ask your user to resubmit with the correct details. See Cancel an upcoming transfer.
  • If it's Pending or Booked, modification isn't possible. Your user can request a recall. See Returns and recalls.

Handle incoming transfers​

If an incoming transfer is Booked​

The funds are available in the account. If your user can't see them, ask them to check they're looking at the correct account, and at History rather than Upcoming in Web Banking.

If an incoming transfer is Rejected​

  • Funds return automatically to the sender's account: within three business days for SEPA, up to 10 business days for International.
  • If the reason is compliance-related, don't share the detail.
  • The sender needs to correct the issue and resubmit.

If funds haven't returned after that time, submit a Swan Support request.

If an incoming SEPA transfer isn't visible​

  1. Confirm three to five business days have passed since the sender submitted it.
  2. Ask your user for proof of transfer from the sending institution.
  3. Check the beneficiary details on the proof against the Swan account details.
  4. If they don't match, direct your user to ask the sender to check with their bank and resubmit with the correct details.
  5. If the debtor's bank confirms that it credited the funds to the Swan account and the beneficiary details match, raise a Swan Support request with that confirmation and the transfer details. If the debtor's bank can't confirm that it credited the funds, direct the debtor to ask that bank to investigate.

If an incoming International transfer isn't visible​

  1. Confirm up to five business days have passed.
  2. Direct your user to ask the sender for a SWIFT payment confirmation (an MT103).
  3. Check the sending and beneficiary details against the account.
  4. Submit a Swan Support request with the MT103 and the transfer details.

If Swan and its providers can't locate the funds, the sending institution is often the only party that can trace the transfer through the network.

If your user receives an unexpected incoming transfer​

Check the transaction label, reference, and debtor details on the transaction detail page in Dashboard > Data > Transactions. If the label or reference is missing and you can't identify the source, submit a Swan Support request with the account ID and transaction details.

If your user needs to return funds received by mistake​

Submit a Swan Support request to return the funds to the sender. Your user needs to consent before Swan returns anything.

If the incoming amount is lower than expected​

Applies to: International Credit Transfers.

The credited amount can be lower than what the sender says they sent, for two reasons: Swan's processing and currency exchange fees, and intermediary banks deducting their own fees along the routing chain.

Direct your user to Currency exchange and fees for International Credit Transfers for the breakdown. If fees don't explain the difference, submit a Swan Support request.

For a SEPA transfer, fees aren't the explanation. Check for a partial payment or a second transaction instead.

Outgoing international transfers create two transactions

Every outgoing International Credit Transfer produces a transfer transaction and a separate fee transaction. Your user seeing two debits is expected, not a duplicate. You can filter fee transactions in Dashboard > Data > Transactions by the FeesIn and FeesOut types.


Give your user proof of a transfer​

Applies to: Incoming and outgoing SEPA, Instant SEPA, and International Credit Transfers with a Booked status.

Users might request a payment receipt or attestation for accounting purposes, or proof that an outgoing transfer was executed. Swan provides this as a transaction confirmation statement.

To download it:

  1. Go to Dashboard > Data > Transactions.
  2. Open the transfer.
  3. Select Transaction confirmation.

The option only appears for eligible Booked transfers. Transaction confirmation statements aren't available for transfers with another status, or for card payments, direct debits, and fee transactions.

A transaction confirmation statement confirms the transfer details and its Booked status. For an outgoing transfer, it provides proof of execution, but doesn't prove that the beneficiary received the funds.

If your user needs proof of reception, or another document that the statement doesn't provide, submit a Swan Support request. Include the transaction ID and explain what the document will be used for.

Integration: confirmation statements

Ask your development team to expose transaction confirmation statements in your product using Swan's API, so your users can download their own instead of asking you.


Trace a transfer that wasn't received​

Applies to: Booked SEPA, Instant SEPA, and International Credit Transfers.

Use this when an outgoing transfer is Booked but the beneficiary says they haven't received it.

  1. Give your user the transaction confirmation statement, including the end-to-end reference.
  2. Direct your user to ask the beneficiary to check with their financial institution using that reference.
  3. If the beneficiary's bank confirms non-receipt, direct your user to ask that bank for written proof.
  4. Once normal processing times are exceeded, submit a Swan Support request with that proof and the transaction details.
  5. Swan uses the evidence to investigate with its banking partners.
An account statement isn't enough

An account statement extract doesn't support a trace. Swan needs a document from the receiving institution confirming the money wasn't received.


Returns and recalls​

Returns and recalls are different things, and mixing them up sets the wrong expectations with your user.

What it isWho starts itTiming
ReturnAutomatic reversal by a bank that can't process the transfer: closed account, wrong BIC, or technical errorThe receiving bank, automaticallyFunds back within 3 business days
RecallA request to reverse a completed transfer, usually sent to the wrong IBANThe debtor, via their bankBeneficiary responds within 15 business days. Not guaranteed

Recalls work the same way for SEPA Credit Transfers and Instant SEPA Credit Transfers. Recalls also work for International Credit Transfers, but they take longer, require manual processing through intermediary banks, and the outcome can't be predicted.

Request a recall for an outgoing transfer​

  1. Ask your user for the transaction ID, the reason, and supporting evidence.
  2. Submit a Swan Support request with the recall details as early as possible. Recalls have a submission deadline: up to 13 months after settlement for unauthorized or fraudulent transfers, or 10 business days for technical or duplicate errors.
  3. Swan sends a recall request to the beneficiary's bank.
  4. The beneficiary's bank notifies the beneficiary, who decides whether to accept.
  5. If they accept, funds are credited back to your user's account. If they refuse or don't respond within 15 business days, the recall closes.

A separate recall transaction appears in the history. It doesn't replace the original.

Handle a recall request for an incoming transfer​

  1. Swan asks your user whether they accept the recall. We proactively contact you or your user when we receive any recall request for incoming transfer.
  2. Your user decides whether to accept or refuse.
  3. If they accept, Swan debits the funds and sends them to the debtor.
  4. If they refuse, the funds stay in the account and the response is automatically sent to the debtor's financial institution.
  5. If they don't respond within 15 business days, the recall closes, and the funds stay in the account.

Cancel an upcoming transfer​

Applies to: SEPA and Swan Internal Credit Transfers. Doesn't apply to: Instant SEPA and International Credit Transfers, which can't have the status Upcoming.

You can cancel a transfer yourself while it still has the status Upcoming. Once it's Booked, cancellation isn't available: use Returns and recalls instead.

  1. Go to Dashboard > Data > Transactions.
  2. Open the transfer and confirm its status is Upcoming.
  3. Select Cancel transaction.

The Cancel transaction button only appears while the transfer is eligible. If you can't see it, the transfer has moved out of Upcoming and you'll need to trace it or request a recall.

Upcoming transfers can't be edited. If your user needs different details, cancel and ask them to create a new transfer.

Cancel a standing order​

Canceling a standing order stops future executions. It doesn't reverse transfers already sent. If one has already gone out and needs reversing, cancel the standing order first, then follow Returns and recalls for the individual transfer.

Integration: self-serve cancellations

Ask your development team to build cancellation into your product using Swan's API, so your users can cancel their own Upcoming transfers and standing orders. See Cancel a credit transfer and Cancel a standing order.


Keep your user updated​

While Swan investigates:

  • Tell your user you're checking with Swan. When you raise the request, say how urgent it is so Swan can prioritize it.
  • Share any timeframe Swan gives you.
  • Update your user regularly, even when there's nothing new to report.
  • If you don't understand the answer you receive, ask Swan to clarify before replying to your user.

Contact Swan Support​

Submit a Swan Support request if:

  • You can't identify a transfer after collecting the required details.
  • An Instant SEPA transfer is stuck in Pending.
  • A SEPA or International transfer is stuck in a technical pending status past the next business day.
  • A transfer has been Pending for several business days with no communication.
  • A Booked outgoing transfer hasn't been received and you have written proof of non-receipt.
  • A rejected transfer hasn't returned after 3 business days.
  • Your user needs a recall, or needs to return funds received by mistake.
  • You can't explain the response you received from Swan.

Include in your request:

  • Account ID
  • Transaction ID, if available
  • Direction: incoming or outgoing
  • Transfer type
  • Status and status details, if visible
  • Debtor IBAN and creditor IBAN
  • Amount and currency
  • Execution date
  • Transfer reference or end-to-end reference
  • Proof of transfer or proof of non-receipt, depending on the case
  • Screenshots or incident context, if relevant

Share these articles with your users​

Help center content

You can also use these articles as a starting point for your own help center content, tailored to your product's terminology and your users' context.