An Airtm payment marked pending is a status, not a complete diagnosis. The word may appear at a paying platform, in the payout service or at the receiving provider. Before changing settings or opening several tickets, establish which system is displaying it and what has already happened. That distinction makes a support request shorter and more useful.
The three clocks
- Earnings clock. When did the payer approve the work and mark the payout as released?
- Transfer clock. When did the payout service acknowledge the payment or provide a transaction reference?
- Receiving clock. When did the destination first show the deposit, review or credit?
Write the time zone beside each timestamp. “Yesterday evening” can mean different dates to two support teams, while a copied timestamp preserves the sequence. If a stage has no evidence, mark it unknown rather than filling the gap with an assumption. A payer’s completed-work screen is not necessarily evidence of a released payment.
Check the setup state once
Airtm’s US setup documentation says enterprise payouts can remain pending when the preferred payout method has not been configured. That is one documented explanation, not proof that every delay has the same cause. Check the method’s status inside the authenticated account and record what it says. Official US setup reference.
Airtm’s separate migration note concerns the transition from the earlier model and the requirement to clear a preexisting balance. Its dated transition instructions should not be read as a fresh deadline for every new user. If an older account remains in an unexpected state, refer to the notice when asking support how that account should proceed. Read the migration notice.
Send a compact evidence packet
A useful ticket identifies the paying platform, the amount and asset, the date and time, the status shown at each stage, and the relevant transaction reference. Add a short sentence describing what you expected and what is different. A concise sequence is easier to investigate than a folder of unlabelled screenshots.
Illustrative ticket structure: “The payer marked this payout released at [time and zone]. My payout method shows [status]. The receiving service shows [status or no entry]. The payment reference is [reference]. Please confirm which stage needs action.”
Use the provider’s authenticated support channel. Redact unrelated account balances and personal data from screenshots, and never include a password, authentication code or wallet recovery phrase. An editorial website cannot inspect the account or release a payment; our role is to help organize the question, not to receive the evidence.
Avoid creating a second problem
Do not request a duplicate payment merely because the first is not visible at the destination. Likewise, repeatedly replacing receiving details can make it harder to determine which instructions applied when the original payout was initiated. Ask the responsible service to clarify the existing payment before attempting a corrective transaction.
Once resolved, keep the final explanation with the payout record. If the issue was incompatible destination instructions, revisit the asset-network-memo checklist. If it was an account-security concern, use the support-channel checks before responding to any new message.