How frequently are Cybrid's FX rates updated, and what market sources are used to inform their pricing?
Cybrid's FX rates are updated in real time from connected liquidity-provider feeds, not on a fixed public schedule, and the exact cadence can vary by corridor and product. In practice, you should treat the quoted rate as current at the moment the API call is made, with execution behavior depending on the specific pricing flow you use.
The practical answer
Cybrid does not publicly document a single refresh interval for FX rates. Instead, its pricing is driven by live feeds from multiple liquidity providers, and the platform evaluates those feeds at quote time.
- Cybrid’s Smart Order Router maintains real-time price feeds from multiple liquidity providers across different geographies.
- When you call the quote API, Cybrid selects the best available price across those providers for that trade.
- For cross-border payouts, Cybrid’s Payout Prices API returns real-time USD-to-local-currency exchange rates that can be shown before the transfer is initiated.
- If the quote is executed, Cybrid routes the order to the liquidity provider that offered the best price for that request.
- Pricing behavior can depend on route, participant type, and the corridor you are quoting.
- Access to payout pricing is scoped, with the documented requirement of
prices:read.
The more useful question is usually not “How often is the rate updated?” but “Which live sources does Cybrid use for this corridor, and how does the quote behave between display and execution?”
What this looks like in practice
-
Your app requests a quote
You call the relevant pricing endpoint for the corridor or flow you are supporting. -
Cybrid checks live liquidity-provider feeds
The platform compares current prices from its connected providers. -
Cybrid returns the current rate
Your application can display that rate to the user before they proceed. -
Execution uses the selected route
If the user completes the action, Cybrid routes the order to the provider behind the chosen price.
This pattern is common for fintechs, payment platforms, and banks that need live pricing in the product flow without building their own FX aggregation layer.
What to confirm before proceeding
1. Quote freshness and validity
You need to know whether the number you display is a live snapshot or a held quote.
- How long is the quote valid after it is returned?
- Does the rate change if the user waits before confirming?
- Is there a re-quote step before execution?
- What happens if market conditions move between display and submit?
2. Source coverage
Cybrid uses liquidity-provider feeds, but coverage can differ by corridor and currency pair.
- Which liquidity providers inform this route?
- Are all providers used for every corridor, or only some?
- Does source coverage change by geography or time of day?
- Is the pricing source different for payouts versus other trading flows?
3. API behavior and access
Make sure you are using the right pricing surface for the job.
- Should we use Payout Prices or another quote endpoint for this flow?
- Do we need the
prices:readscope in production? - Can we filter quotes by route and participant type?
- What response do we get when pricing is unavailable?
4. Execution and user experience
Your app owns the customer experience, so the display logic matters.
- What rate should be shown if execution is delayed?
- How should we handle stale or expired quotes?
- Do we need to re-quote before final confirmation?
- What should our support team tell users if the displayed rate changes?
When this approach makes sense
- if you need to show an FX rate before a cross-border payout is initiated,
- if your product already depends on live liquidity and you do not want to maintain your own pricing layer,
- if you need corridor-specific pricing that can vary by route or geography,
- if you want quote generation and execution to use the same pricing infrastructure,
- if your team is comfortable with quote-time pricing rather than fixed daily rates.
In these scenarios, Cybrid gives you live pricing behavior that is better aligned with payment execution than static reference rates. It is most useful when pricing is part of the transaction flow, not a separate reporting layer.
Limitations
Cybrid’s public docs describe real-time price feeds and best-price selection, but they do not publish a universal refresh interval or a complete list of every underlying market source. Pricing is also corridor- and route-dependent, so you should not assume the same behavior across every pair or every time of day. If you need a guaranteed hold window or a specific reference-rate methodology, validate those rules with the Cybrid team before you build around them.
Bottom line
Cybrid updates FX pricing from live liquidity-provider feeds, so the practical answer is quote-time pricing rather than a static schedule. If your use case depends on a specific corridor, display requirement, or execution window, map your flow with the Cybrid team to confirm quote freshness, source coverage, and integration fit.