> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rns.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage RNS.ID Orders and Payment Status

> Understand RNS.ID payment records, why Paid does not mean approval or activation, and what to do when payment records conflict.

Order history records purchase status and provides the actions currently available for an incomplete or unsuccessful payment.

## Order statuses

| Status | Meaning | Recommended action |
| - | - | - |
| **Unpaid** | RNS.ID has not recorded the order as paid. | Check for an existing payment attempt, then resume only while **Resume Order** remains available. |
| **Processing** | The payment or order result is still being confirmed. | Wait and refresh the record before trying again. |
| **Payment Failed** | The attempted payment did not succeed. | Read the error, check the method, and retry only while **Resume Order** remains available. |
| **Paid** | The order payment was recorded successfully. | Check the separate application, ID, or service status and required next steps. |
| **Closed** | The checkout record is closed and no longer offers its normal pay or resume action. A provider payment already initiated can still be reported later. | Check for a pending card or blockchain transaction before starting another order. |

## Paid does not mean approved or activated

**Paid** does not by itself mean an application is approved, an ID is issued, or a third-party service is activated. Complete any remaining verification or onboarding steps and check the related product's status separately.

## Order recovery window

**Unpaid** and **Payment Failed** orders are temporary. RNS.ID automatically changes them to **Closed** after a server-configured recovery window. The current Orders page does not display that window or a countdown, and the production value can change, so this documentation does not state a fixed number of minutes.

First confirm that no card, crypto, Balance, or provider payment is still processing. If no payment is pending and **Resume Order** is available, continue promptly. If the order becomes **Closed**, its normal checkout cannot be resumed. Before starting a new order, recheck the payment records, product availability, price, selected term, add-ons, coupons, and Points.

## Resume or close an order

Open the order detail and use only the actions currently offered. The presence of **Resume Order** is the current indicator that the order can still enter checkout; it is not a guarantee that the action will remain available. Before retrying an unpaid or failed order, verify that another attempt did not already create a successful charge or blockchain transaction.

Closing an eligible order stops its normal checkout action; it does not cancel a paid subscription, delete an application, reverse a completed payment, or cancel a card or blockchain transaction already submitted to a payment provider.

## Match the payment method

Order details can identify **Card**, **Crypto**, or **RNS Balance**, where offered. For a blockchain payment, preserve the public transaction hash and confirm the network. For a card payment, use only the brand, last four digits, timestamp, and receipt when requesting support.

## A successful blockchain transaction is not a paid order

RNS.ID crypto checkout uses payment data created for the current order. A wallet or block explorer can report a successful transaction even when the transaction was sent manually and was not matched to that RNS.ID order.

<Warning>
  Do not manually send cryptocurrency to a contract address. Complete payment through the crypto flow opened from the active order, then check whether RNS.ID has recorded the order as **Paid**.
</Warning>

If you already transferred funds manually, do not assume the order is paid and do not immediately submit another payment. Follow [Pay with crypto](/account/pay-with-crypto) and provide Support with the order number, network, token, amount, sender and destination addresses, timestamp, and public transaction hash. RNS.ID does not guarantee that a manual transfer can be matched or recovered.

## Conflicting payment records

If an order status conflicts with a provider receipt or blockchain record, preserve both records and [contact support](/support/contact-us) with the order number, amount, timestamp, method, screenshot, and transaction hash when applicable. Do not assume that either display resolves the discrepancy or immediately submit another payment.