When money does not appear where expected, it is tempting to describe the transfer as “missing.” That word, however, can cover several very different situations. A payment may still be pending, may have been rejected before execution, may have been returned or reversed, or may be marked complete even though the recipient has not identified it.
A useful complaint begins by defining the status rather than assuming the cause. This gives support a better chance to trace the transaction and creates a more reliable record if the matter later requires formal review.
Identify the Payment Rail and Visible Status
First establish what kind of transfer was attempted. The information needed for a SEPA payment can differ from the information needed for a card-based or crypto transfer. Blackcat’s overview of Blackcat transfers describes the transfer services available, while the current Terms and Conditions contain the contractual rules that should be checked for an individual case.
Record the exact status displayed in the app. Do not replace it with an interpretation. The following distinctions can help organise the first request:
| Visible situation | What it may mean at a high level | Evidence to retain |
| Pending | Processing or further review may not be complete | Time submitted, status screenshot and reference |
| Rejected or declined | The instruction may not have been accepted or executed | Error message and submitted details |
| Returned or reversed | Funds may have been sent back after an attempted transfer | Original and return transaction records |
| Completed but not received | The sending side may show completion while the recipient cannot identify the credit | Confirmation, beneficiary details and recipient records |
These descriptions are not findings about responsibility. Transfer chains can involve payment schemes, intermediary institutions, beneficiary institutions or blockchain networks. A complaint should state what is known and ask the provider to investigate what is not known.
Collect the Transfer Record
Before contacting support, gather the transaction reference, date, time, amount, currency and beneficiary information as entered. For a bank transfer, include the relevant IBAN and BIC in a secure and appropriately redacted form. For a crypto transfer, retain the asset, network, destination address and transaction hash if one exists. For a card-based transfer, note the card or network reference shown in the official record without exposing full card credentials.
If the recipient says the funds have not arrived, ask for a short written confirmation and, where appropriate, a statement covering the relevant period. The recipient should protect unrelated transactions and personal data.
Check whether the beneficiary information in the original instruction matches the intended destination. This is a factual check, not an admission that an error occurred.
Ask Focused Questions in the Support Request
A first message can be concise:
Please confirm the current status of transfer [reference], initiated on [date] for [amount and currency]. The app shows [status], while [specific issue]. Please advise whether any information is required from me and provide the next expected step.
Avoid opening several chats with slightly different descriptions. Multiple threads can make it harder to see what has already been reviewed. Keep the support reference, save each response and provide requested information through the approved secure channel.
Know the Difference Between Related Procedures
A complaint is not necessarily the same as a transfer recall, cancellation request, fraud report or correction request. Each may have different rules and possible outcomes.
For example, a customer who entered incorrect beneficiary details may need to ask whether a recall can be attempted. A customer who did not authorise a transfer should follow the provider’s urgent security and transaction-reporting instructions. A customer dissatisfied with how either request was handled may also have a complaint, but submitting a complaint does not automatically cancel or reverse the transaction.
The live Terms and Conditions should be reviewed for the relevant service before any deadline or remedy is assumed.
Escalate an Unresolved Issue as a Formal Complaint
If support does not resolve the concern, write a formal complaint that links back to the original ticket. State the transaction reference at the top, then provide a short chronology:
- When the instruction was submitted.
- What status appeared.
- When support was contacted.
- What information was provided.
- What replies were received.
- What specific issue remains unresolved.
Explain the effect factually. If a delayed transfer caused a documented fee or missed obligation, identify the amount and attach evidence. Do not inflate the impact or claim that every downstream loss must be reimbursed.
The requested resolution might be a trace, a written status explanation, correction of an error, confirmation of a return or review of the service handling. The appropriate outcome depends on the facts and applicable terms.
Use Current Complaint Details
As checked on 24 August 2026, Article 32 of Blackcat’s Terms and Conditions says complaints may be submitted in English through the official support portal, in writing to The Manager, Customer Issues at Papaya Ltd, or by email to complaints@papaya.eu. Customers should verify these channels on the live site before submission.
The terms currently say a response should be provided no later than 15 business days from receipt. If exceptional circumstances prevent a full response within that period, an interim reply may explain the delay and state a final-response date no later than 35 business days. Save proof of receipt and do not confuse business days with calendar days.
Assess the Answer and Next Route
Read the final response against the complaint. Does it identify the status, explain what was investigated and answer the requested questions? If the issue involves another institution, does the response explain what can be confirmed and what remains outside the provider’s control?
If the internal process does not resolve the dispute, Blackcat’s current terms refer eligible customers to Malta’s Office of the Arbiter for Financial Services. The OAFS tells consumers to complain to the provider first and publishes current guidance for taking a complaint further. Eligibility, deadlines, forms and contact details must be verified directly with the OAFS.
A well-prepared transfer complaint does not begin with a theory about where the money went. It begins with a precise status, a complete transaction record and a focused request for investigation. That approach helps separate a processing question from a formal service dispute and gives every reviewer the same reliable chronology.
This article is general information and not legal advice. Transaction rights and procedures depend on the current terms, payment rail and facts of the case.
