Article facts
| Status | Core meaning |
|---|
| Available | Live for eligible users under stated conditions |
| Limited | Live only for specified capabilities, directions, networks or customer types |
| Coming soon | Planned but not live; no guaranteed launch date |
| Temporarily paused | Normally supported but currently not operational |
| Unavailable | Not offered under the current configuration |
| Not applicable | The service does not apply to the selected context |
| Last reviewed | 2026-08-21 |
Available
Meaning: The service is live for eligible users under the conditions shown.
Available does not mean:
- automatic approval;
- availability to every customer type;
- no verification;
- no limits or fees;
- every direction, network or use case is enabled;
- permanent availability.
Example:
USDC on Ethereum — Available in the EEA where supported for the user’s country and provider configuration.
Limited
Meaning: The service is operational only within a defined scope.
A limitation can concern:
- incoming versus outgoing;
- asset or network;
- customer type;
- provider;
- amount or limit;
- country;
- feature;
- temporary migration condition.
Example:
GBP functionality — Limited: selected GBP operations are supported, but incoming GBP transfers are not currently available.
Every Limited status should state the limitation in plain language.
Coming soon
Meaning: Quppy plans to introduce the service or feature, but it is not live.
Coming soon does not mean:
- a confirmed date;
- a guaranteed country;
- an approved provider;
- an open application;
- a live balance, transfer or card;
- the feature can be included in a transactional CTA or Offer schema.
Current roadmap examples include local European IBANs, local payment methods, USD support, Solana additions and Quppy cards.
Temporarily paused
Meaning: The service is normally supported in the selected configuration but is currently unavailable because of an operational, provider, payment-rail, security, network or regulatory event.
The page should show where possible:
- affected service;
- affected countries or users;
- start time;
- whether existing balances are affected;
- actions users must not take;
- next update time;
- status-page link.
Do not tell users to retry repeatedly when that could create duplicate payments.
Unavailable
Meaning: The service is not offered in the selected country, customer type or provider configuration.
Reasons can include:
- legal restriction;
- sanctions;
- provider coverage;
- unsupported payment route;
- asset restriction;
- product decision;
- customer ineligibility.
Example:
USDT — Unavailable through Quppy to users in the EEA.
Unavailable is different from Temporarily paused: it does not imply that the service normally exists in that configuration.
Not applicable
Meaning: The service or field does not logically apply to the selected context.
Examples:
- an EEA-only regulatory provider field on a non-EEA page;
- an incoming-payment direction for a service that supports exchange only;
- a blockchain network field for a fiat transfer;
- a Personal eligibility field on a Business-only product.
Not applicable should not be used to hide missing information that is actually unknown.
How should a complete status record look?
A status should be tied to enough context:
- Country
- Customer type
- Service
- Provider
- Currency or asset
- Payment rail or network
- Direction or capability
- Status
- Limitation
- Effective date
- Last reviewed
- Next review
For example:
- Region: EEA
- Customer type: Personal
- Service: Quppy Crypto
- Asset: USDT
- Capability: custody, receive, send and exchange
- Status: Unavailable
- Reason category: regional provider configuration
- Last reviewed: 2026-08-21
What is the difference between service status and account eligibility?
Service status describes the product in a market.
Account eligibility describes whether a particular user or company is approved.
A service can be Available in a country while one applicant is not eligible. Conversely, a user cannot be approved for a service marked Unavailable or Coming soon in that configuration.
What should I do before a transaction?
- Check the current service status.
- Read the limitation.
- Confirm the same function in Quppy.
- Verify provider, direction, asset and network.
- Review any fee, limit and warning.
- Do not use an old address or account detail after a status change.
- Contact Support if the account and published status conflict.
The latest in-product restriction and applicable terms prevail when they are more recent than a cached page.
How should status changes be communicated?
Material changes should include:
- old status;
- new status;
- effective date;
- users or markets affected;
- reason category where disclosure is permitted;
- required action;
- alternative service where available;
- link to updated terms or Help article;
- Last reviewed date.
The word Available should not remain in metadata or structured data after the visible status changes.