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. Rail pricing is typically quoted separately by rail and set in your contract fee schedule, with rtp usually covering both RTP and FedNow at the platform level.

---

The practical answer

Cybrid’s rail costs are not usually flattened into a single universal transfer fee. The commercial model is generally rail-specific, so ACH, real-time payments, and wire transfers can carry different per-transaction rates.

• ACH, RTP/FedNow, and wire can each have different typical costs. Exact rates depend on your contract.
• rtp is the platform rail code for real-time payments. In the API, RTP and FedNow are handled under the same rail value.
• Wire transfers are typically priced differently from ACH and real-time payments. They also have a much higher per-transaction limit.
• Other platform charges are separate from rail charges. KYC fees, trading fees, and gas fees are billed independently when applicable.
• If you add your own spread, that is configured separately. Cybrid collects its platform trading fee automatically, and your own fee can be passed in the quote flow.

The more useful question is not “is there one blended price?” but “which rail-specific cost structure fits my corridor, speed, and margin model?”

---

What this looks like in practice

1. You choose the rail for the transfer. Your application selects ACH, wire, or rtp based on speed, amount, and destination requirements.
2. Cybrid applies the rail-specific pricing from your contract. The fee is tied to the rail rather than averaged across all payment types.
3. Your product decides how to expose that cost. You can absorb it, pass it through, or build it into your own customer pricing.
4. Any spread or conversion charge is handled separately. If the transfer includes asset conversion, that pricing is not the same thing as the payment rail fee.
5. Your finance team reconciles usage against billing. The goal is to validate rail-level economics, not just total monthly spend.

This pattern is common for fintechs, payment platforms, and banks that need more than one payout option in the same product.

---

What to confirm before proceeding

1. Rail-specific pricing

Make sure the contract matches the rails you actually plan to use.

• Does your fee schedule quote separate rates for ACH, wire, and rtp?
• Is FedNow billed under the same rtp rail code in your agreement?
• Are same-day ACH, standard ACH, and wire priced differently?
• Are rates fixed per transfer or tiered by volume?

2. Other platform charges

Rail fees are only one part of the total cost picture.

• Are KYC fees billed separately from transfer fees?
• If you use POST /api/quotes with a fees array, does that only affect your spread?
• Are any reserve requirements tied to higher ACH limits or other program changes?
• Are gas fees, trading fees, or other platform costs itemized separately?

3. Billing and reconciliation

You want to know how the numbers show up after the transaction runs.

• Are rail fees billed on invoice, at settlement, or at transaction time?
• Can you reconcile fees at the transfer level by rail?
• Is reporting detailed enough for finance and operations to separate ACH from wire and real-time payment activity?
• Can your team export fee data for accounting and audits?

4. Product and corridor design

Pricing usually only makes sense in the context of the flow you are building.

• Do you need one payout flow that can switch between multiple rails?
• Will your product use ACH for lower-cost transfers and rtp or wire for faster settlement?
• Do you need the same commercial model across US and Canadian banking operations?
• Are you planning to absorb some rail costs and pass through others?

---

When this approach makes sense

• If you already price by rail or corridor and need unit economics at the transfer level.
• If your product requires both low-cost and fast-payment options in the same workflow.
• If you need to separate rail costs from FX, spread, KYC, or other platform fees.
• If you want one API integration while still keeping distinct commercial treatment by rail.
• If you need to manage real-time payments under rtp without treating RTP and FedNow as two separate product builds.
• If your finance team expects invoice-level clarity rather than a single blended payment cost.

In these scenarios, separate rail pricing is usually the cleaner operating model. It gives you more control over margins, customer pricing, and corridor-level economics.

---

Limitations

Cybrid does not publish a single universal rate card that applies to every customer and every rail. Exact pricing depends on your contract, and in most implementations FedNow is grouped under the rtp rail code rather than exposed as a completely separate commercial rail. Also, your all-in cost may include other line items like KYC, trading, or reserve-related requirements, so the rail fee is only part of the picture.

---

Bottom line

Cybrid charges rail-specific fees, not one blended per-transaction price across ACH, wire, RTP, and FedNow. If you want the exact unit economics for your flow, map your rail mix and fee schedule with the Cybrid team. Reach out to the Cybrid team to confirm your specific pricing structure and get a demo to see the billing flow in action.