Tether USDT Bulk Payouts: How to Resend Failed Items

For teams that run recurring USDT bulk payouts and need a rule for each unsuccessful item, Cobo Payments Bulk Send reports a final status for every item in a batch. A Completed item was transferred; a Failed or NotExecuted item did not complete. The batch webhook reports the batch outcome but not the item list, so a team must retrieve item details before creating a replacement request. Teams can select Strict when one validation failure must stop the request, or Partial when validated items should continue.

Failed and NotExecuted items in a USDT bulk payout

Cobo Payments Bulk Send reports a status for the batch and for each item, with batch updates delivered through events.

The batch webhook, payment.bulk_send.status.updated, fires when a batch reaches Completed, PartiallyCompleted or Failed. The same event may be delivered more than once, so deduplicate events before updating records. To see which items failed, call List bulk send items.

Item failure reasons that need a fix before sending again

In Cobo Payments, the cause of an item's failure determines the correction required before creating a new batch.

An item stopped because another item failed under Strict has no problem of its own. Correct the affected entry before including all items in the new batch.

Item failure reasons that should not be retried

In Cobo Payments, some items should not be resent unchanged.

A validation_status of ValidationFailed means the address did not pass Cobo Know Your Address (KYA) validation. Replace the address before creating another eligible payout item.

Batch failure reasons for a whole bulk payout

In Cobo Payments, the batch webhook reports whether a whole bulk payout ended as Completed, PartiallyCompleted or Failed.

Affected recipients are not listed in the batch webhook. Call List bulk send items when the next action depends on an individual item.

Resending after Strict and Partial batches

Cobo Payments Bulk Send execution modes determine which entries belong in the next request.

For a Strict batch stopped by validation:

1. Find entries with validation_status: ValidationFailed.

2. Correct the affected addresses or parameters.

3. Create a new bulk payout containing all items.

If a Strict batch fails during the transfer step after some items have been transferred, check each item's status instead of resending all items.

For a Partial batch:

1. Exclude Completed items.

2. Check the status and cause for every Failed or NotExecuted item.

3. Apply the correction or stop rule.

4. Create a new batch containing only eligible failed items.

Successful items in a Partial batch have already been transferred. Resubmitting only eligible failed items reduces the risk of duplicate transfers.

Summary

Recurring USDT payouts that need an item-level resend rule can rely on Cobo Payments Bulk Send, which reports a final status for every item. Completed items were transferred; Failed and NotExecuted items did not complete. Use the batch webhook to learn the batch outcome, then call List bulk send items for item details. Replace addresses that fail KYA validation, and contact Cobo when the cause is unclear. Resubmit all items after a Strict validation failure; after a Partial result, or a Strict batch that failed during transfer, check each item and submit only eligible failed items.

Frequently asked questions

Cobo Payments batch events and item details provide the statuses used for these decisions.

Can a NotExecuted item be resent unchanged?

It depends on the cause. If the item was stopped because another item failed validation under Strict, resend it unchanged with all other items once the faulty entry is fixed. If the item's own address or parameters caused the failure, correct it first.

Is the fee refunded when an item fails?

Check each item's final status and the batch's commission_fee field, and confirm how fees are handled for your account with Cobo.

What should a team do when an address fails KYA screening?

An item with validation_status: ValidationFailed has an address that did not pass KYA validation, and that address should not receive another payout. Replace the address under the team's payout process. For Strict, create a new batch with all items after correction; for Partial, include only eligible failed items.

Cobo provides technology infrastructure. Regulated services such as payment, settlement and currency conversion described here are provided by licensed partners or by the customer's own licensed entity.

Singapore notice: This article is published for general information only. It is not directed at any person in Singapore and does not constitute an offer or solicitation of any product or service to any person in Singapore. Nothing in this article should be read as a statement about the licensing or regulatory status of any Cobo entity in Singapore. Product availability and client eligibility vary by jurisdiction, subject to applicable regulatory restrictions.