Skip to main content
Try Cobo WaaS Skill in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster ๐Ÿš€
WaaS 2.0 defines a range of transaction statuses and sub-statuses to reflect different processing stages. This page provides a complete list of statuses and describes the actions you can perform based on each status.

โ€‹
Status reference table

โ€‹
Deposits

The table below provides an overview of transaction statuses and sub-statuses relevant to deposits in the WaaS 2.0 service.
StatusSub-StatusDescription
PendingScreeningPendingScreeningAppCheckThe transaction is under review by the Screening app.
PendingCoboKYTCheckThe transaction is pending Coboโ€™s KYT check.
ConfirmingPendingBlockConfirmationsThe transaction is awaiting the required number of confirmations.
CompletedN/AThe transaction is completed and funds are available.
RejectedRejectedByCoboKYTThe transaction was rejected by Cobo KYT.
RejectedByScreeningAppThe transaction was rejected by the Screening app.

โ€‹
Withdrawals

The table below provides an overview of transaction statuses and sub-statuses relevant to withdrawals in the WaaS 2.0 service.
StatusSub-StatusDescription
SubmittedN/AThe transaction is submitted.
PendingScreeningPendingTravelRuleCheckThe transaction is undergoing a Travel Rule check.
PendingTravelRuleInfoThe transaction is awaiting users to provide information related to the Travel Rule.
PendingScreeningAppCheckThe transaction is under review by the Screening app.
PendingCoboKYTCheckThe transaction is pending Coboโ€™s KYT check.
PendingAuthorizationPendingDoubleCheckThe transaction is pending a double check.
PendingSpenderCheckThe transaction is pending a spender check.
PendingRiskControlCheckThe transaction is pending for a Risk Control check.
PendingApproverCheckThe transaction is pending approval from the approver.
PendingCoboCheckThe transaction is pending an internal check by Cobo.
PendingSignatureQueueThe transaction is queued to be processed by Cobo Portal.
PendingWaitSignerThe transaction is waiting for a signer to sign it in Cobo Guard.
InsufficientBalanceThe transaction cannot proceed due to insufficient balance. Please deposit required tokens or cancel the transaction.
InsufficientBalanceFundLockedThe transaction cannot proceed because the available balance is currently locked. Please wait until the balance is unlocked.
PendingSystemProcessingThe transaction has been submitted and is awaiting processing by the blockchain system.
SystemProcessingOngoingThe blockchain system is currently processing the transaction.
BuiltThe transaction has been built but not signed yet.
PendingSignerApprovalThe transaction is pending approval from the signer.
PendingApprovalStartThe transaction approval is waiting to be started.
PendingSignerProcessingThe transaction is currently being signed.
SignatureVerificationSuccessThe transactionโ€™s signature has been successfully verified.
BroadcastingFailedBroadcastingThe transaction failed to be broadcast to the blockchain network.
ConfirmingRevertingThe transaction is being reverted due to failure on the blockchain.
PendingBlockConfirmations The transaction is awaiting the required number of confirmations.
CompletedN/AThe transaction is completed.
FailedFailedBySignerThe transaction failed during the signing process.
FailedOnChainThe transaction failed on the blockchain.
ReplacedByNewTransactionThe transaction has been replaced by a new transaction through the Replace-By-Fee (RBF) mechanism.
SignatureVerificationFailedThe transactionโ€™s signature failed verification.
FailedSignerTimeoutThe transaction failed due to signature timeout.
ReOrgedThe transaction failed due to a blockchain reorganization.
RejectedRejectedWhiteListThe transaction was rejected because the IP address of the initiator was not in the whitelist.
RejectedKYTThe transaction was rejected because it failed Know Your Transaction (KYT) compliance checks.
RejectedRiskControlCheckThe transaction was rejected because it failed the risk control check.
RejectedSpenderAuthThe transaction was rejected by the spender.
RejectedApproverAuthThe transaction was rejected by the approver.
RejectedDoubleCheckThe transaction was rejected because it failed a double check.
RejectedbyMobileCosignerThe transaction was rejected by a mobile cosigner.
RejectedCoboCheckThe transaction was rejected because it failed the internal check by Cobo.
RejectedByScreeningAppThe transaction was rejected because it failed the screening check by the Screening app.
RejectedTravelRuleDueToUnsupportedTokenThe transaction was rejected because the token was not supported by the Travel Rule.
RejectedTravelRuleThe transaction was rejected because it failed to comply with the Travel Rule.
RejectedTravelRuleDueToComplianceThe transaction was rejected because it failed the cross-check of the Travel Rule.
RejectedTransactionPolicyThe transaction was rejected due to it failed the transaction policies.
RejectedBySignerThe transaction was rejected by the signer.
CanceledBySpenderThe transaction was canceled by a spender.
CanceledByAPIThe transaction was canceled by a Cancel transaction operation.
OnchainRejectionThe transaction was rejected from being added to the blockchain.
RejectedByCoboThe transaction was rejected by Cobo possibly due to unmet compliance or risk control requirements. You can contact our support team for more details.
PendingN/AThe transaction is waiting to be included in a block.

โ€‹
Status details

The PendingAuthorization status aggregates both manual approval steps and internal automated checks. Manual steps include PendingApproverCheck, PendingSpenderCheck, and PendingDoubleCheck. Automated checks include PendingRiskControlCheck and PendingCoboCheck. A transaction in PendingAuthorization does not necessarily require a person to act, because it may be undergoing automated risk-control or compliance checks.
After a transaction is approved, it enters the PendingSignature status and must be signed by the MPC signer group within a limited signing window. If signing does not complete within this window, the transaction automatically fails and moves to the Failed status with the sub-status FailedSignerTimeout. To find out why a transaction failed, check the sub_status field returned by List all transactions or Get transaction information. If you encounter FailedSignerTimeout, the transaction is in a terminal Failed state and cannot be resumed. Submit a new transaction of the same type to try again: use Transfer token for token transfers, Call smart contract for contract calls, or Sign message for message signing.
A transaction in the Confirming status with the sub-status PendingBlockConfirmations is waiting for the required number of block confirmations on its chain. This is a normal part of processing and does not mean the transaction is stuck. The required number of confirmations and the expected confirmation time vary by chain.

โ€‹
Available actions

You can perform the following actions based on the transaction status:
  • Cancel a transaction if its status is one of the following:
    • Submitted
    • PendingScreening
    • PendingAuthorization
    • PendingSignature (Only when the sub-status is Queue, InsufficientBalance, InsufficientBalanceFundLocked, PendingSignerApproval, PendingSystemProcessing, or Built)
  • Resend a transaction if its status is Failed.
  • Speed up or drop a transaction if its status is Broadcasting.
For details on how a replaced transactionโ€™s status changes, see RBF (Replace-By-Fee) transaction lifecycle. For more details, refer to Manage transactions.