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

# Corridor status

> Read the availability of BUY, SELL and PAY, supported formats and status freshness.

This page records the scope and limitations of BUY, SELL and PAY. A dedicated status view is being prepared for the app's **More** menu, with a reason and last review time for each product and corridor. The corridor and local rail names follow the provider catalog; the status also considers the product rollout and documented restrictions.

## Read the status

* **Live:** the product is enabled for the corridor, with no operational incident recorded in the current review. Availability still depends on a merchant, a valid quote and your account's requirements.
* **Degraded:** an operational problem is recorded for the product and corridor. Read the reason and affected scope.
* **Paused:** the product is not offered, disabled by policy or suspended by the operator. Existing operations still need status tracking and support.
* **Unknown:** the review is missing, expired or unreachable. A last reported state is not current health evidence.

**Alpha** and **pilot** describe rollout maturity. A product can be live during an alpha or pilot rollout; those labels alone do not indicate a service incident. Supported formats and their limitations are listed separately from operational status.

The app's available-merchant count is separate. Zero merchants can be a temporary liquidity condition. A supported format or a quote does not confirm that a bank received a payment.

## Nigeria

BUY and SELL use the **NIP transfer** rail under the alpha rollout. Availability still depends on a partner, a valid quote and the account's current limits.

PAY supports **NQR and SPD** payment formats. Availability follows the same partner, quote and account checks. Confirm the recipient and exact bill amount in the app before approving payment.

## Brazil and QR PAY

Brazil PAY accepts **static Pix QR only**. Confirm that the merchant can provide one **before sending ZEC**. Dynamic Pix is blocked; its rejection after scanning cannot undo an earlier ZEC conversion.

Each PAY corridor has supported formats and specific limitations. A recognised QR may rely on an external order or contain an opaque amount. Confirm the merchant and exact bill amount; never infer that a QR is unpaid, unexpired or supported by every bank just because it can be read. See [Pay with QR](https://docs.0xramp.app/pay-with-qr.md) for the order of steps and recovery limits.

## Evidence and updates

A status review records enabled products, supported formats and current incidents. It does not certify every bank or device. [Live activity methodology](https://docs.0xramp.app/metrics-methodology.md) explains how historical settlements are counted; those totals do not establish universal present-day coverage.

**0xramp maintainers** own status updates. They review the page at least weekly and after reported incidents. Each review expires within seven days. A new timestamp must follow an actual review, not merely a page refresh.

For an incident, maintainers identify the affected product and corridor, publish its reason and scope, and pause new operations when necessary while preserving tracking and support for existing payments. Restoration follows a correction and validation of the affected scenario. The public page and its update time are then checked again. Report a problem through [support](https://docs.0xramp.app/contact.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.