Transaction statuses
Each transaction has one of these statuses. The dashboard shows the label, and the CSV export uses the code name. The status reflects the most recent event for that transaction; refunds and disputes update the existing row rather than inserting a sibling.
| Status | In the dashboard | Meaning |
|---|---|---|
succeeded | Paid | Payment completed. Money is in your account (net of provider fees). |
pending | Awaiting | Payment is in flight. Common with async payment methods (ACH, some crypto rails) where confirmation takes minutes to hours. |
failed | Failed | Payment did not complete: card declined, expired auth, hard rejection. No money moved. |
partial | Partial | Buyer paid less than invoiced (common when a crypto buyer sends a network-fee-reduced amount). On NOWPayments the row's amount stays the full invoiced price, and metadata.actuallyPaid holds the coin amount that arrived. On a self-hosted coin the row's amount is the value of what arrived. |
refunded | Refunded | Money has been returned to the buyer, fully or partially. Refunds can happen days or weeks after the original payment. |
disputed | Disputed | The buyer (or their bank) opened a dispute or chargeback. Check the provider's interface for the response window. On a Stripe dispute, the row's metadata.reason carries Stripe's classification verbatim. |
pending_manual | Awaiting mail | A pay-by-mail transaction is awaiting your physical confirmation. See the Pay by mail page. |
manual_canceled | Canceled | You chose Cancel payment on a pending pay-by-mail row before the buyer's payment arrived. |
manual_expired | Expired | A pending pay-by-mail row sat for 30 days without confirmation and auto-expired. |
manual_revoked | Reversed | You confirmed receipt of a pay-by-mail payment but later undid the confirmation (e.g., the payment turned out to be invalid). The row moves from succeeded back to this terminal state. |
Refunds, disputes, partial payments
Coin Moebius listens for these provider events and updates the original transaction row in the dashboard. Specifically:
- Refunds: Stripe's
charge.refundedevent (full or partial refunds, includingamount_refundedso partial refunds show the slice that was returned). The row's status flips torefunded, theamountreflects the refunded amount, andmetadata.originalChargeId/metadata.originalAmountcarry the original payment context. NOWPayments'refundedIPN also flips the row torefunded, and itsamountstays the invoiced price. On a cart order, a partial refund leaves the row paid and shows the refunded amount under it. - Disputes (chargebacks): Stripe's
charge.dispute.createdevent. The row's status flips todisputed. The provider's stated reason passes through tometadata.reasonverbatim, you can render it in your own UI however you choose. - Partial payments: NOWPayments'
partially_paidIPN. The row's status flips topartial. Theamountstays the invoiced price, andmetadata.actuallyPaidis the coin amount that arrived.
These events are surfaced in the dashboard and via the /status endpoint. Set up a small polling job (see the next section) or check the dashboard. If you need your own backend to react automatically, point your provider's own webhook at your server, the same way you would without us.