A Quppy transaction can be delayed, placed under review, returned or rejected because of payment-route rules, blockchain confirmations, incorrect details, security controls, transaction limits, provider availability, sanctions or AML/CFT checks, Travel Rule information, source-of-funds questions, or a technical incident. A pending or rejected status does not identify one specific cause, and Quppy may be legally unable to disclose every internal risk indicator.
Zuletzt geprüft am 2026-08-21
| Field | Visible value |
|---|---|
| Applies to | Fiat transfers, crypto deposits/withdrawals and exchanges |
| Possible outcomes | Pending, under review, returned, rejected, failed, cancelled or completed |
| Common cause groups | Technical, payment-route, blockchain, security, compliance, eligibility or provider |
| Does pending prove funds are lost? | No |
| Does rejection prove wrongdoing? | No |
| Guaranteed review time | No |
| Last reviewed | 2026-08-21 |
Status labels can differ by product and provider. In general:
| Status | General meaning |
|---|---|
| Pending | Submitted but not yet completed |
| Processing | Being handled by Quppy, a provider, payment rail or blockchain |
| Under review | Additional security or compliance assessment is taking place |
| Completed | The service recorded the operation as completed |
| Returned | Funds were sent back or are being sent back |
| Rejected | The transaction was not accepted for processing or completion |
| Failed | A technical, routing or validation failure prevented completion |
| Cancelled | The operation was cancelled before completion where cancellation was possible |
The status shown in the current Quppy interface and provider record prevails over this general explanation.
Possible reasons include:
Quppy does not guarantee that every payment described as “instant” at scheme level will complete instantly for every customer or transaction.
Possible reasons include:
A blockchain explorer showing “confirmed” does not automatically prove that a custodial provider has completed all crediting and compliance steps.
An exchange can be unavailable or rejected when:
The final executable rate, amount and applicable costs are those shown before confirmation, not an earlier indicative website value.
Depending on the review:
Provide only what is requested through an approved channel.
In some reviews, detailed disclosure could:
Support should still explain what action the user can take when disclosure is permitted, such as supplying a missing document or correcting transfer details.
Never post identity documents, account details, wallet addresses linked to your identity, or transaction evidence publicly.
Depending on the operation:
Crypto already sent on a blockchain usually cannot be cancelled or reversed by Quppy. A rejected credit for an unsupported deposit does not guarantee recovery.
Quppy does not publish one guaranteed time for every transaction review. Timing can depend on:
Support should not promise a deadline unless an approved service-specific SLA applies.
No. It means the operation is not yet recorded as completed. Check whether action is required and contact Support when appropriate.
No. Rejection can result from eligibility, technical, routing, limit, provider or compliance reasons.
A transfer already broadcast and confirmed on a blockchain normally cannot be cancelled or reversed.
Not until you know whether the first transaction will complete, fail or return. Repeating it can create a duplicate operation.
The provider may still require enough confirmations, network validation, Travel Rule information or compliance review.
Yes. Eligibility, provider checks, receiving-institution support and technical conditions can affect processing.
Not always. Some monitoring and legal-reporting details cannot be disclosed.
There is no universal guaranteed review time.
This article explains the current Quppy product and compliance configuration. The applicable Quppy and service-provider terms, country eligibility rules, privacy notices and information shown in the app prevail if they differ from this article.
A source-of-funds check helps Quppy or the applicable service provider understand where the fiat money or crypto used for a particular transaction or account activity came from and whether that origin is consistent with the customer profile and lawful use of the service. The check can be requested during onboarding or later and can require an explanation supported by documents or blockchain evidence.
The crypto Travel Rule is a regulatory requirement for crypto-asset service providers to collect, verify where required, transmit and retain information about the originator and beneficiary of a crypto transfer. In the European Union, Regulation (EU) 2023/1113 applies to covered crypto transfers from 30 December 2024. It can require Quppy’s applicable provider to ask who is sending or receiving crypto, which provider or self-hosted address is involved, and in some cases for evidence of wallet ownership or control.
Quppy or the applicable crypto-service provider may ask for information about an external wallet to identify the sender or beneficiary, determine whether the address is self-hosted or managed by another provider, comply with the Travel Rule, assess sanctions and AML/CFT risk, and confirm that the asset and network are supported. The request can apply to deposits and withdrawals and never requires you to disclose a private key or seed phrase.
A crypto transaction can remain pending because it is waiting for blockchain confirmations, the external platform has not completed processing, the applicable provider is processing it, or a security, compliance or Travel Rule review is required. “Pending” and “under review” are not the same as “failed.” Check the transaction status and evidence before contacting Support.
Wir verwenden Cookies, um die Nutzung unserer Website zu messen und unsere Werbung relevanter zu gestalten. Sie entscheiden, was wir verwenden dürfen. Cookie-Richtlinie