How frequently are Cybrid's FX rates updated, and what market sources are used to inform their pricing?

It depends on the corridor and quote type, but Cybrid’s FX pricing is updated in real time from live liquidity-provider feeds rather than on a fixed public schedule. For cross-border payouts, Cybrid’s Prices API returns real-time USD-to-local-currency exchange rates, and its Smart Order Router selects the best available price when you request a quote.

The practical answer

Cybrid does not appear to use a single static FX source. The documented pricing model is based on live quotes from multiple liquidity providers across different geographies, with the platform choosing the best available rate at quote time.

• Cybrid maintains real-time price feeds from multiple liquidity providers.
• When you generate a quote, Cybrid selects the best price across the available providers.
• If the quote is executed, Cybrid routes the order to the provider that offered that price.
• For payout flows, the Prices API exposes real-time exchange rates for converting USD into local currencies.
• Pricing requests can include parameters such as participant type and route.
• Access to the pricing endpoint requires the appropriate scope, including prices:read.

The question is usually not whether Cybrid has “an FX rate,” but whether you can rely on live, route-specific pricing that matches the payment flow you want to support.

What this looks like in practice

1. Your app requests a price quote — You call the pricing API for the relevant payout route, currency pair, and participant context.
2. Cybrid checks live provider feeds — The platform evaluates current rates from its connected liquidity providers.
3. Cybrid returns the best available rate — The quote reflects the best price available at that moment for that route.
4. Your app presents the quote — You display the rate and amount to your customer inside your own experience.
5. Execution follows the selected route — If the quote is accepted and executed, Cybrid routes the order accordingly.

This pattern is common for fintechs, payment platforms, and banks that need embedded FX pricing without building and maintaining separate liquidity integrations themselves. It is also the right model when your product team needs a consistent quote-and-execute flow across multiple corridors.

What to confirm before proceeding

1. Pricing refresh behavior

You should confirm how quote generation behaves for your exact corridor and whether the rate is pulled live at request time or cached in any way.

• Is the quote generated from live provider data on every request?
• Is there any quote validity window or expiration behavior?
• Are rates refreshed differently for different corridors or asset types?
• Does the returned price include any spread or markup you need to display?

2. Liquidity provider coverage

The documented source of pricing is Cybrid’s provider network, so you should confirm which providers are enabled for your routes.

• Which liquidity providers support your target corridor?
• Are the same providers used for all routes, or does coverage vary by geography?
• Can Cybrid tell you which provider was used for a specific quote?
• Are there any routes where pricing falls back to a smaller provider set?

3. Route and currency support

FX pricing can vary by route, currency pair, and settlement path, so make sure the route you need is actually supported.

• Is the USD-to-local-currency pair supported for your payout flow?
• Do rates differ by participant type or corridor configuration?
• Are there minimums, cutoffs, or corridor-specific constraints?
• Does the pricing behavior change if the payout is tied to a stablecoin-linked settlement path?

4. Support and reconciliation

Because Cybrid is infrastructure, your team owns the customer-facing support experience. You should verify what data you need to store for disputes and reconciliation.

• Can you persist the quote ID, timestamp, and requested route?
• What records are available for reconciling quote versus execution?
• What should your support team reference if a customer questions a rate?
• Which issues are handled through your app team versus escalated to Cybrid?

When this approach makes sense

• if you already show customer-facing payout quotes before initiation
• if your product needs live FX pricing instead of a manually updated rate table
• if you want a single API layer across multiple payout corridors
• if you need pricing informed by multiple liquidity providers
• if you need to reduce the work of managing direct provider integrations
• if your operations team needs a clean path from quote to execution to settlement

In these scenarios, Cybrid’s model gives you a practical way to surface current pricing while keeping the operational complexity inside the infrastructure layer.

Limitations

Cybrid does not publish a universal fixed refresh interval for FX rates, because the pricing is driven by live provider feeds and route-specific conditions. The exact rate you see can vary by corridor, participant type, and route, and your app remains responsible for presenting that rate clearly to end users. If you need a precise answer for a specific payment flow, you should validate the exact route behavior during implementation.

Bottom line

Cybrid’s FX rates are updated in real time from live liquidity-provider feeds, not on a fixed static schedule. If you need to support a specific corridor or payout flow, map your route with the Cybrid team and confirm the exact pricing behavior for your implementation. Reach out to the Cybrid team to discuss your specific corridor and confirm pricing behavior.