EMpulse › Products › Rail Health Index
Rail Health Index: which payment methods work today
Which payment methods in a country work today and how reliably: cards, bank transfers, instant transfers, e-wallets, mobile money, cash, crypto and direct local rails, each with a status (healthy / degraded / outage), a health index against its own norm, availability through the day and a supply class — for pay-ins and payouts.
Payment companies and online businesses entering emerging markets, gambling and forex operators routing deposits, payout and treasury teams choosing the rail for today, developers building routing logic.
Pro $290/month · all plans · free level without a key · API docs
Payment rails on 2026-10-24 (public view, one day behind)
328 status changes in the last 30 days (the incidents feed is on Pro). Statuses: healthy · degraded (three hours below the rail's norm) · outage (six hours without attempts at usual traffic).
Free and Pro
Free
$0
- daily status per method class
- free currencies
- one day behind
- 100 requests a day
Get a free key
Pro
$290/month
- every active currency, today
- health index, availability, supply
- hourly status
- history and the incidents feed
- MCP tool get_rail_health
- 10 000 requests a day
Get Pro
All products in one plan: see pricing. Series delivered to each key may contain insignificant individual differences (see the license terms).
API and MCP
Without a key (free level): GET https://api.empulse.ai/v1/rails/{CUR}. With your key in X-API-Key the same call answers at your plan's level.
curl https://api.empulse.ai/v1/rails/AED
curl -H "X-API-Key: YOUR_KEY" https://api.empulse.ai/v1/rails/AED
AI assistants and agents: tool get_rail_health(currency) on the EMpulse MCP server https://api.empulse.ai/mcp.
Example response (free level)
{
"product": "rail-health",
"source": "EMpulse Rail Health Index",
"as_of": "2026-10-24",
"plan": "free",
"currency": "AED",
"country": "United Arab Emirates",
"day": "2026-10-24",
"summary": {
"pay_ins": null,
"payouts": null
},
"rails": [
{
"method": "bank_transfer",
"direction": "out",
"status": "no_data",
"status_since": "2026-09-29T23:00+00:00",
"confidence": "limited"
}
],
"citation": {
"text": "The EMpulse Rail Health Index has no status for payment rails in United Arab Emirates on 2026-10-24.",
"url": "https://empulse.ai/products/rail-health",
"source": "EMpulse Rail Health Index"
}
}
How to cite
The EMpulse Rail Health Index has no status for payment rails in United Arab Emirates on 2026-10-24.
Cite as "EMpulse Rail Health Index" and link this page (https://empulse.ai/products/rail-health). Every API and MCP answer carries a ready citation. Not investment advice.
Sources and licences
- EMpulse payment-rail market data (transaction-based component, by country and method class) — class A: EMpulse data
Methodology
Rail Health Index
- Class = currency × direction (pay-ins / payouts) × method class:
card, bank_transfer, fast_transfer,
wallet, mobile_money, cash, crypto, direct (direct integrations with local rails), other.
Attempts with no method selected are not a rail and are left out.
- Success rate of a day = successful attempts / attempts, published only through the index: a day with
fewer attempts than the minimum is
insufficient (null). The 7-day rate smooths it; the baseline is the
median of the daily rates over the previous 90 days (at least 7 days with a value).
- health_index = 7-day rate / baseline × 100, capped at 100. 100 means the rail performs at its own norm;
below 80 is a degradation. The index is relative: a rail that always converts 60 % reads 100 while it stays at
60 %.
- availability = the share of the day's hours in which the rail accepted at least one attempt.
- supply =
ample / scarce / none from the number of funded, open counterparties on the rail per hour.
- status follows hourly rules: three consecutive hours with a success rate below 80 % of the baseline →
degraded (three good hours → healthy); six consecutive hours without attempts at hours that usually carry
traffic → outage (the first hour with attempts ends it); a class without a baseline yet → no_data.
status_since is the hour the current status began; every change is an incident (/v1/rails/incidents) and
an item of kind rail in the EM FX Events feed.
- confidence:
high / medium / limited from the breadth of the market data behind the class
(attempts and businesses of the last 7 days); the numbers themselves are not published.
- Days are UTC. The current day is recomputed with every data load; the status of a day is its last hour's.
General index methodology: /methodology. Related: unmet-demand · usdt-liquidity.