How frequently does Cybrid update or review its per-transaction pricing and what notice is given before changes?

It depends on your contract, and Cybrid does not publish a single fixed cadence for reviewing or changing per-transaction pricing. Exact rates live in your contract fee schedule, and the notice you receive before a change is governed by the commercial terms you agree to with Cybrid.

The practical answer

Cybrid pricing is contract-based, so the review cycle and change notice are not one-size-fits-all. In practice, the right place to look is your fee schedule and the pricing language in your agreement, not a public rate card.

• Per-transaction pricing can vary by rail, product type, and volume.
• Typical costs vary by contract, but exact rates are specified in your fee schedule.
• The Cybrid team configures trade fees.
• Trade and quote responses include fee fields that reflect the configured pricing.
• If you charge your own spread or fixed fee, you can pass a fees array in POST /api/quotes, subject to the product rules.
• Billing questions are handled through Cybrid finance, and fee line items appear on your invoice.

The more useful question is usually not “How often does Cybrid change prices?” but “Where is the fee defined, who can change it, and what notice is required before the new rate applies?”

What this looks like in practice

1. You agree on the fee schedule
   Rail-by-rail pricing is set in the commercial agreement before launch.

2. Cybrid configures the platform fees
   The Cybrid team applies the agreed pricing to your account.

3. Your app submits transactions and receives fee data
   Quotes and trades return fee information, and your own system can layer on any approved partner fee.

4. Any pricing change is handled as a contract change
   Revised rates and their effective date are confirmed through the commercial process before they are applied.

5. Invoices reflect the agreed pricing
   Your finance team reconciles invoice line items against the rate card and transaction volume.

This pattern is common for fintechs, payment platforms, and banks that need pricing tied to a contractual relationship rather than a public, self-serve fee table.

What to confirm before proceeding

1. Rate card scope

You need to know exactly which products and rails the pricing covers.

• Which rails are priced separately, such as ACH, RTP/FedNow, wire, or stablecoin-related flows
• Whether pricing differs by corridor, transaction type, or volume tier
• Whether successful, failed, returned, or reversed transactions are billed differently
• Where the authoritative fee schedule is stored

2. Change notice and effective date

This is the core question behind your pricing review process.

• Is there a fixed advance-notice period for pricing changes?
• How is notice delivered, such as amendment, email, or account contact
• Who at Cybrid is authorized to approve a pricing change?
• Can existing rates be grandfathered until a specified date?

3. Billing and reconciliation

Pricing only works operationally if invoicing is clear.

• Are fees billed monthly or on another cadence?
• Are charges shown per transaction or as aggregated line items?
• How are disputes or billing corrections handled?
• Which contact should your finance team use for billing questions?

4. Custom fees and margin control

If you add your own pricing on top of Cybrid, confirm how that is represented.

• Can you add fixed or spread-based fees to a quote?
• Are there limits on how many custom fees can be included?
• Do custom fees appear in the total fee shown by the API?
• Where does your internal revenue recognition or ledger logic sit relative to Cybrid’s fee data?

When this approach makes sense

• if you need rail-specific pricing instead of a single flat fee
• if your unit economics depend on exact per-transaction costs
• if you already have a contract and want to confirm the operational terms
• if you plan to layer your own spread or fixed fee on top of Cybrid
• if you need invoice line items that your finance team can reconcile cleanly
• if your volumes may change and you want to understand tiered pricing

This is the right model when pricing needs to be documented, configurable, and tied to your commercial agreement. It gives you predictability, but only if you confirm the change process up front.

Limitations

Cybrid’s public documentation confirms that pricing is tiered, that exact rates are set in the contract fee schedule, and that typical costs vary by contract. It does not state a universal review frequency or a standard notice window for all customers, so you should not assume a monthly, quarterly, or annual cycle unless your agreement says so. In other words, the cadence and notice period are commercial terms, not a fixed platform rule.

Bottom line

Per-transaction pricing is contract-driven, and there is no published universal update cadence or notice window. Confirm the current fee schedule, the change-notice language, and any rail-specific exceptions with Cybrid before you finalize your margins.

Map your fee schedule with the Cybrid team and get a demo to see how pricing is applied in practice.