Does Cybrid offer the ability to lock in an FX rate at the time of transaction, and how is that guaranteed?

Yes, Cybrid can lock in an FX rate at transaction time for supported quote-based payout flows, and the guarantee comes from executing the transaction against a time-limited quote with the rate, fees, and amounts fixed for that window. If the quote expires or the transaction changes, the rate is no longer guaranteed and you need to refresh pricing.

---

The practical answer

Cybrid’s pricing and quote flow is designed to give you a firm, executable FX rate before the payment is initiated.

• Cybrid’s Payout Prices API provides real-time USD-to-local-currency pricing for cross-border payouts.
• The quote includes the exchange rate, fees, and amounts, so you can present an all-in payout value before execution.
• The quote is time-limited, which is what makes the FX lock practical rather than just indicative.
• If the transaction is executed within the quote window, the quoted rate is the rate used for that transaction.
• Pricing access is feature-enabled and may require the prices:read scope.
• Coverage and behavior can vary by corridor, route, and participant type, so the exact setup should be validated for your use case.

The more useful question is usually not “does Cybrid show an FX rate?” but “can my product create a transaction against that rate, keep the flow inside the validity window, and reconcile the final settlement cleanly?”

---

What this looks like in practice

1. Request a payout price or quote

   • Your system asks Cybrid for pricing for the specific corridor, amount, and route.

2. Show the locked amount in your app

   • You present the rate, fees, and final payout amount before the user approves the transfer.

3. Create the transaction against that quote

   • The transfer is submitted using the quoted pricing details, not a fresh spot price.

4. Execute within the validity window

   • If the transaction is processed before the quote expires, Cybrid honors the quoted FX rate.

5. Refresh if the quote changes

   • If the user takes too long, the payment details change, or the quote expires, you request a new price before continuing.

This pattern is common for fintechs, payment platforms, and banks that need a predictable send amount in local currency while keeping the payment logic in their own product.

---

What to confirm before proceeding

1. Quote validity and execution timing

You need to know exactly when the rate becomes binding and when it stops being valid.

• How long is the quote valid for this corridor and transaction type?
• Does the transaction have to be submitted against the same quote ID to preserve the rate?
• What happens if approval is delayed and the quote expires?
• Can any change to amount, beneficiary, or route invalidate the locked rate?

2. Corridor and route coverage

FX locking only matters if it is available where you plan to use it.

• Is payout pricing enabled for the currencies and countries you need?
• Does the route support the exact transfer method you want to use?
• Are there different pricing behaviors for payouts, transfers, or book transfers?
• Are any corridors excluded, restricted, or manually reviewed?

3. Settlement and funding mechanics

The quote is one part of the flow; you still need to understand what happens at settlement.

• At what point is the FX rate fixed relative to funding and execution?
• How is the quoted amount tied to the underlying settlement leg?
• What happens if the downstream payment rail settles later than expected?
• Which leg of the flow carries the operational risk if the transaction fails or reverses?

4. Pricing display and compliance

If you are surfacing the rate to end users, the display and compliance model needs to be clear.

• Which pricing fields can you show before payment initiation?
• Do you need to display fees separately from the FX rate?
• What KYC/KYB checks must complete before the quote can be executed?
• Is the pricing feature enabled in your environment and scoped correctly?

5. Exception handling and support

You should plan for expiry, failure, and reconciliation before going live.

• How will your app handle expired quotes or stale pricing?
• What transaction records tie the quote to the final settlement?
• What alerts or webhooks are available for failed execution?
• How will your support team explain rate changes or re-quotes to end users?

---

When this approach makes sense

• If you already show a final send amount before approval, and you want that amount to be executable.
• If your product requires FX certainty, not just an indicative market rate.
• If you need to reduce exposure between initiation and settlement, especially on cross-border payouts.
• If your corridor has meaningful rate movement, and small changes affect margin or user trust.
• If you want a traceable quote-to-settlement record, for operations and reconciliation.
• If your app owns end-user support, and you need deterministic pricing behavior your team can explain.

This works best when the quote is part of the payment itself, not just a display tool. It gives your users a clear amount and gives your operations team a fixed reference point for settlement.

---

Limitations

Cybrid does not make FX risk disappear, and it does not guarantee a rate indefinitely. The lock is tied to the supported quote flow, the validity window, and the specific corridor or route you are using. If the transaction is delayed, changed, or re-priced outside that window, the original rate no longer applies, and you should expect to request a new quote.

---

Bottom line

Yes, Cybrid can lock in an FX rate for supported transaction flows, and that lock is enforced through a time-limited quote executed within the valid window. If you need this in production, map your flow with the Cybrid team to confirm integration fit.