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

It depends: Cybrid’s per-transaction pricing is contract-based, and the review cadence and notice period before changes should be defined in your agreement and fee schedule. There isn’t a universal public calendar in the available documentation, so confirm those terms before you launch or renew.

The practical answer

• The available documentation does not state a fixed public cadence for per-transaction pricing reviews or a standard notice period.
• Per-transaction fees for fiat rails vary by contract, and the exact rates are defined in your fee schedule.
• Trading fees are configured by the Cybrid team and are typically expressed in basis points under your agreement.
• For quote-based trade flows, Cybrid can aggregate its fee and partner/custom fees in POST /api/quotes and POST /api/trades responses.
• Billing questions are handled through Cybrid finance, not through a public self-serve pricing portal.

The question is usually not “How often does Cybrid change prices?” but “Which fees are contract-controlled, and what written notice do I get before those terms change?”

What this looks like in practice

1. You agree on a fee schedule at onboarding. The schedule sets the per-transaction rate by product, rail, or corridor.
2. Cybrid configures the applicable fees. For trade flows, that can include platform fees and any partner fees reflected in quote or trade responses.
3. Your team reconciles invoices against the contract. Usage-based charges should match the agreed schedule and the way the product reports fees.
4. Any pricing change is handled commercially. The effective date and notice period should be documented in the amended fee schedule or contract addendum.

This is the typical pattern for fintechs, payment platforms, and banks that want stable payment infrastructure but still need clear unit economics and change control.

What to confirm before proceeding

1. Pricing scope and unit of charge

Get specific about which actions are billed and how the rate is applied.

• Which products have per-transaction pricing versus other billing models?
• Are charges applied per initiated transaction, per successful transaction, or per settled transaction?
• Are rates different for ACH, RTP/FedNow, wire, trade, or other rail types?
• Are fixed fees, spread fees, or both used in your corridor?

2. Review cadence and change control

This is where you validate whether pricing is reviewed on a schedule or only through contract changes.

• Is there a fixed review cadence for pricing, or is it only revisited at renewal or amendment?
• Who can propose and approve a rate change on Cybrid’s side?
• How much written notice is required before a change takes effect?
• Does the notice window vary by product or corridor?

3. Billing and reconciliation

You need to know how fees will show up in your finance workflow.

• Will invoices show itemized transaction-level charges, aggregated totals, or both?
• Can you reconcile invoice lines to API responses or ledger entries?
• How are reversals, refunds, retries, or failed transactions handled?
• Are custom fees added through quote requests billed separately or included in the same fee total?

4. Ownership and escalation

Make sure the right people own pricing questions before you go live.

• Which team handles billing questions and rate clarifications?
• Is finance@cybrid.xyz the right contact for commercial issues?
• Who confirms custom pricing configured in quote or trade flows?
• If you pass costs through to end users, which internal team owns the customer-facing notice?

When this approach makes sense

• if you already negotiate unit economics by rail, corridor, or product
• if your business needs per-transaction pricing that can change through contract amendments
• if you want to layer your own customer pricing on top of Cybrid’s infrastructure
• if you need fee data surfaced in quotes, trades, or invoices for reconciliation
• if you have an internal finance process that can manage pricing updates and effective dates
• if you prefer commercial control over a public self-serve rate card

This setup works well when the pricing model needs to track real transaction mix rather than stay fixed across every use case.

Limitations

Cybrid’s documentation does not define a universal public review frequency or default notice period for per-transaction pricing, so you should not assume those terms are the same across all products, corridors, or contracts. Exact rates, billing treatment, and change notice are commercial terms, and some fee behavior is configured by the Cybrid team rather than by self-service settings. Cybrid also does not interact with your end users, so any pass-through pricing notices are your team’s responsibility.

Bottom line

Cybrid’s per-transaction pricing is contract-driven, and the notice period before changes should be confirmed in your agreement. If pricing predictability matters to your launch or renewal plan, validate the fee schedule, billing workflow, and change-control terms with the Cybrid team. Map your fee schedule with the Cybrid team to confirm notice terms and get a demo to see how it works in your flow.