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

It depends, but Cybrid usually handles per-transaction charge changes through contract configuration and invoice-level credits, not through an automatic refund on every individual transaction. If a charge needs to be adjusted, the usual path is a billing or commercial review, then a credit, reduced invoice, or fee schedule change.

---

The practical answer

Cybrid’s fee handling is contract-driven, so the first question is what kind of charge you are talking about and where it is recorded.

• Cybrid trade fees are configured by the Cybrid team and can be billed in basis points or fixed amounts.
• Cybrid and partner fees can both appear in the fee field of POST /api/quotes and POST /api/trades responses.
• If you need to charge your own spread, you can pass a fees array in POST /api/quotes.
• Monthly invoices can include accumulated trade fees, ACH and wire fees, KYC/KYB fees, gas fees, and other platform service costs.
• When fee revenue exceeds costs, the invoice can be reduced or credited; when costs exceed revenue, the partner is invoiced for the net amount.
• Billing questions are handled through Cybrid finance, not through a consumer-style self-serve refund flow.

The more useful question is not “Can Cybrid refund a charge?” but “Which fee type is this, where does it settle, and does the correction belong in configuration, reconciliation, or the monthly invoice?”

---

What this looks like in practice

1. Agree the fee schedule — your contract defines which transactions are billable, how the charges are calculated, and who owns them.
2. Generate the quote or transaction — the API returns the fee so you can store it in your ledger and internal records.
3. Execute and accumulate — charges flow into monthly billing along with the rest of your platform costs.
4. Review exceptions — if a charge was applied in error or needs a commercial waiver, Cybrid finance can review it and apply a credit or reduced invoice.
5. Reconcile internally — your team handles end-user support and communication, because Cybrid supports the app owner, not your app’s customers.

This is the typical pattern for fintechs, payment platforms, and banks that need predictable billing and a clean audit trail without turning every exception into a one-off manual process.

---

What to confirm before proceeding

1. Fee type and ownership

Start by identifying exactly what charge you want to adjust.

• Is it a Cybrid platform fee, your partner fee, or a third-party rail or network cost?
• Is the fee calculated as basis points or as a fixed amount?
• Does the fee appear in the quote or trade response, the invoice, or both?
• Is it charged only on successful transactions, or on every attempted transaction?

2. Adjustment mechanism

You need to know how a correction is actually applied.

• If the charge is wrong, is the correction a credit, a reduced invoice, or a fee schedule update?
• Who approves waivers or exceptions on your account?
• Is there a cutoff before monthly invoicing closes?
• Are refunds possible, or are adjustments limited to invoice-level credits?

3. Settlement and reversal constraints

Some charges are easier to correct than others.

• Has the underlying rail or network cost already been incurred?
• Is the transaction final on the payment rail?
• Can the original charge be reversed, or only netted later?
• Are partial reversals supported in the corridor you care about?

4. Operational workflow

Make sure the billing process fits your support model.

• Who on your side files and tracks the billing issue?
• What evidence is required to support an adjustment?
• How will the correction appear in reconciliation and reporting?
• Which Cybrid team handles finance questions and billing review?

---

When this approach makes sense

• if you already have negotiated commercial terms and need them enforced consistently
• if your product needs invoice-level credits or reduced invoices instead of real-time refunds
• if you need fee data in quote and trade responses for reconciliation
• if you operate across corridors where external rail costs make after-the-fact reversals limited
• if your operations team can manage end-user support and billing escalation in your own application

In these scenarios, Cybrid gives you a clearer way to bill, reconcile, and correct charges without treating every fee like a reversible card authorization.

---

Limitations

Cybrid does not advertise a consumer-style refund workflow for every per-transaction charge. Fees are contract-driven, some are tied to external rails or network activity, and once that underlying activity has occurred the available remedy may be limited to a credit or reduced invoice rather than a direct reversal. Cybrid also does not handle end-user support, so your team remains responsible for customer-facing communication.

---

Bottom line

Cybrid can adjust per-transaction charges, but usually through contract configuration and invoice-level correction rather than an automatic refund on each transaction. If you need to know exactly which fees are waivable in your setup, map the fee type, settlement state, and billing path with the Cybrid team to confirm the right implementation. Map your fee model with the Cybrid team to confirm which charges can be credited, reduced, or waived, and get a demo to see this in action.