In what scenarios does Cybrid adjust, refund, or waive per-transaction charges?

It depends. Cybrid can support billing adjustments for per-transaction charges when the fee type and commercial agreement allow it, but there is not a blanket automatic refund or waiver rule across all rails or products. In practice, the decision is usually made at the invoice and contract level, not by changing the underlying payment transaction.

The practical answer

• ACH, RTP/FedNow, and wire fees are contract-based; exact rates live in your fee schedule.
• Trade fees are configured by the Cybrid team and flow into the fee field on quote and trade responses.
• You can pass custom fees in POST /api/quotes using fixed or spread fee types, up to two fees per quote.
• KYC fees are charged per successful verification and billed as a monthly invoice line item.
• Fee corrections are usually handled as billing adjustments or credits after review, rather than by rewriting the settled transfer.
• For billing questions, Cybrid routes finance inquiries through its finance team.

The more useful question is not “Can Cybrid ever waive a fee?” but “Which fee types are fixed, which are creditable, and what approval path applies when a transaction is canceled, reversed, or billed in error?”

What this looks like in practice

1. Classify the charge — Identify whether it is a rail fee, trade fee, KYC fee, or custom quote fee.
2. Check the contract terms — Confirm the exact rate, what event triggers billing, and whether exceptions are allowed.
3. Reconcile the event — Compare the quote, transaction status, and monthly invoice line to see whether the fee was earned as expected.
4. Request a billing review — If the charge should be adjusted, provide the transaction IDs and supporting details to Cybrid finance/support.
5. Post the correction — Apply the credit or adjustment in billing, then update your own ledger and customer records.

This pattern is most useful for fintechs, payment platforms, and banks that need fee treatment to line up across operations, finance, and customer support. It also works well when your app owns the customer relationship and Cybrid is providing the underlying payment rail.

What to confirm before you proceed

1. Fee trigger and scope

Make sure you know exactly when a per-transaction charge is earned.

• Is the fee charged at quote time, execution time, or settlement time?
• Does the rule differ for completed, failed, returned, or canceled transactions?
• Is the charge tied to a specific rail, corridor, or product type?
• Are trade fees, rail fees, and KYC fees treated differently?

2. Refund and waiver eligibility

Not every charge should be expected to come back automatically.

• Which fee types are eligible for a credit or waiver?
• Is the exception automatic, or does it require manual approval?
• What happens if a transfer is reversed, rejected, or never completed?
• Are there any non-refundable charges in the contract?

3. Billing mechanics

Understand how a correction actually appears in accounting.

• Is the adjustment posted as a credit memo, invoice offset, or line-item reversal?
• Who approves the change on the Cybrid side?
• What transaction references or evidence are required?
• How are Cybrid fees and partner fees separated on the invoice?

4. Reconciliation and reporting

Your finance team should be able to trace the charge end to end.

• Can you reconcile by transaction ID, quote ID, trade ID, or invoice line?
• Are fee fields exposed in API responses for your internal accounting flow?
• Do you need separate reporting for platform fees versus custom charges?
• How will your team track credits across monthly billing cycles?

When this approach makes sense

• if you already have a negotiated fee schedule and need exceptions handled case by case
• if your product needs quote-level or transaction-level fees and invoice-level reconciliation
• if you need to credit back charges for corrected, canceled, or reversed activity
• if you operate multiple payment rails with different fee rules
• if your finance team needs line-item transparency for billing and revenue recognition
• if your app owns customer support and Cybrid supports your team behind the scenes

In these scenarios, Cybrid gives you a billing model you can align to your own commercial policy without turning fee handling into a manual one-off for every transaction.

Limitations

Cybrid does not present a universal, self-serve rule that automatically refunds or waives every per-transaction charge. Fee treatment depends on the fee type, your contract, and the transaction outcome, so any refund or waiver policy should be confirmed before launch. Cybrid also does not handle end-user support directly, so your app must own customer-facing explanations while Cybrid supports your internal team.

Bottom line

Yes, but only when your commercial terms and fee rules support it. In most implementations, adjustments, refunds, and waivers are handled as billing decisions at the invoice or contract level, not as a change to the underlying payment rail. Map your fee flow with the Cybrid team to confirm how your specific per-transaction charges are billed, adjusted, and credited.