Pending, Partially Paid, or Expired: What a Crypto Payment Status Means

Use the invoice to decide what happens next

A customer says they paid, but the order still shows Awaiting payment or Processing. Start with the current invoice and its recorded amount. A wallet screenshot, transaction submission or return to your website does not establish that the order meets its payment requirements. Ulasend distinguishes payment progress from verified completion. Review hosted checkout.

These states help your team decide whether to wait, investigate or fulfill. Keep the invoice connected to the original order so a payment question does not become a search across unrelated transactions.

Pending and Processing: keep the order open

The pending invoice state appears as Awaiting payment. It means the invoice has not reached a completed payment result. If the customer has already sent funds, confirm the invoice reference and collect the transaction details before suggesting another payment.

Processing corresponds to confirmation or settlement still being checked. A detected source transfer may need further processing before verified USDC delivery. Neither a detected-payment event nor a confirming event authorizes fulfillment. The first notification can also be a paid event, so an integration must not require every intermediate step to arrive. See Ulasend's event definitions.

Partially paid: verify the shortfall before requesting more

Partially paid means verified funds have not met the invoice's required minimum. For an illustrative exact-payment invoice requiring 100 USDC, a verified 99 USDC receipt remains short. A positive crypto underpayment tolerance can change the acceptance minimum, but the rule saved on that invoice controls the result. Changing your settings later does not change the original requirement. Read the payment-amount rules.

Check the recorded settlement and any sending, conversion or network costs. Do not automatically ask the customer to send the difference to the same address. A completed provider route may not accept a second transfer. Review the case and arrange the next payment instructions before the customer sends more.

Expired or Cancelled: stop using the old instructions

Expired means the payment window has closed; Cancelled means the request was cancelled. If the customer has not paid, prepare a fresh checkout as appropriate and make clear which request replaces the old one. Do not tell them to send to an expired address because it remains visible in their wallet history.

If funds were already sent, keep that invoice and transaction record for reconciliation. A verified late arrival can require review. Expiry does not prove that no funds moved or that a refund has happened. See how checkout handles late payments.

Needs attention: resolve the review before fulfilling

Needs attention means a payment requires review, including in some late-arrival cases. Keep fulfillment on hold, review the available payment details and follow any requested next steps. An exact-payment shortfall cannot be waived simply by accepting a manual review. Review payment events and fulfillment conditions.

Paid: match the payment to the order

Before fulfillment, check the current paid result, order reference and actual amount against the requirement you intended to accept. An overpaid invoice can also display Paid; use its recorded allocation rather than assuming every extra token becomes merchant credit. For integrations, verify the webhook signature, fetch the current invoice, check live payment evidence and fulfill each order once. Follow Ulasend's fulfillment checks.

Record that decision with the order. Customer payment completion and withdrawal eligibility are separate: a paid invoice does not by itself establish that a payout is ready. Check your available balance, destination approval and applicable account requirements when arranging cash-out. Review receiving and payout setup.