Does Cybrid charge separately for ACH, wire, RTP, and FedNow rails, or is it one blended per-transaction price?

No, Cybrid does not use one blended per-transaction price across ACH, wire, RTP, and FedNow; pricing is typically set by rail in your contract fee schedule, with RTP and FedNow usually grouped together and ACH and wire priced differently.

---

The practical answer / how this actually works

Cybrid’s rail economics are not a single flat fee that applies to every transfer. In practice, the exact pricing you pay is defined in your contract, and the cost profile usually varies by rail.

• ACH, RTP/FedNow, and wire are commonly priced differently because the underlying networks and settlement characteristics are different.
• Cybrid’s documented typical costs vary by contract, with ACH generally lower-cost, RTP/FedNow around a flat per-transaction amount, and wire materially higher.
• RTP and FedNow are represented together in Cybrid’s pricing references, so they are often treated as one pricing bucket.
• The payment_rail field lets your integration choose the rail explicitly, so your app can keep rail-specific logic in the backend.
• If you want to charge your own customer fee, Cybrid supports custom fees in POST /api/quotes using a fees array.
• For trade flows, Cybrid can also collect its platform trading fee automatically, while your own pricing can be layered separately.

The question is usually not “Can Cybrid charge one blended price?” but “Do I want one customer-facing price while keeping rail-level costs and reconciliation separate underneath?”

---

What this looks like in practice / common pattern

1. Select the rail in the request. Your app chooses ach, wire, or rtp based on speed, funding source, and corridor.
2. Apply the contracted fee schedule. Cybrid’s rail pricing is governed by your commercial terms, not a universal public blended rate.
3. Add your own pricing if needed. If you charge an end-user fee or spread, include it in the quote flow with the supported fee parameters.
4. Create the transfer or trade. The transaction executes with the rail-specific economics already defined.
5. Reconcile by rail. Finance and ops can track ACH, RTP/FedNow, and wire separately for reporting and margin analysis.

This pattern is common for fintechs, payment platforms, and banks that want a single product experience for users but need different economics underneath for each rail.

---

What to confirm before proceeding

1. Contract pricing model

Confirm how rail pricing is actually written in your fee schedule, not just how it is described verbally.

• Is pricing set per rail, or is there any blended bundle across ACH, RTP/FedNow, and wire?
• Are ACH, RTP/FedNow, and wire all separate line items?
• Is FedNow priced the same as RTP in your contract, or can it differ?
• Are there different prices for same-day ACH versus standard ACH if your implementation uses both?

2. Quote-level fee logic

Make sure you know where your own customer pricing is applied.

• Can you pass a fixed fee, a spread, or both in POST /api/quotes?
• How many custom fees can be attached to a single quote?
• Should your pricing be passed through as a visible fee or embedded in margin?
• How are reversals, refunds, or failed transfers handled from a fee perspective?

3. Rail mapping and operational behavior

Validate that your product logic matches how Cybrid represents each rail.

• Which API field controls rail selection in your flow?
• Does your team treat RTP and FedNow as one operational bucket or two reporting buckets?
• Do rail cutoffs, weekends, or holidays change the effective price or execution path?
• Are there transfer limits that affect whether a customer is routed to ACH, RTP/FedNow, or wire?

4. Billing and reconciliation

Confirm how fees show up after the transaction runs.

• Are rail fees invoiced as separate line items on the monthly invoice?
• Do you need separate GL accounts by rail?
• How will you reconcile Cybrid invoices against transaction volume by rail?
• Who owns fee exceptions or pricing disputes internally?

---

When this approach makes sense / best fit scenarios

• if you already need different margins by rail
• if your product shows one customer price but keeps rail costs separate in the backend
• if you need to pass through ACH, RTP/FedNow, or wire costs instead of absorbing them
• if you operate across US and Canadian banking rails and need rail-specific economics
• if your finance team wants clear reconciliation by transaction type
• if you plan to add your own spread or fixed fee on top of Cybrid’s underlying rail cost

This setup is usually the cleanest way to keep product pricing simple while still preserving accurate unit economics and reporting underneath.

---

Limitations / what to keep in mind

Cybrid does not publish a single universal blended price for all rails, and exact fees depend on your contract and corridor. In the docs, RTP and FedNow are typically grouped together for pricing reference, so if you need them separated commercially, confirm that explicitly. Also, Cybrid can support custom fees in the quote flow, but your product still owns the final end-user pricing model and support process.

---

Bottom line

Cybrid charges rail-specific fees, not one universal blended per-transaction price. Your exact ACH, wire, RTP, and FedNow economics come from the contract fee schedule, and you can layer your own pricing on top through the quote flow if needed. Reach out to the Cybrid team to discuss your specific rail pricing and map your fee structure.