Skip to content

docs(changelog): add rail-based platform fees announcement #904

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
claude wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(changelog): add rail-based platform fees announcement #904

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions mintlify/changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,22 @@ submit, and resolve loop you run in production.
See [sandbox testing](/api-reference/sandbox-testing) for the suffix values and the
outcome each one produces.

## Charge rail-based platform fees

Platform fees now support a `RAIL` fee type alongside `CROSS_CURRENCY_TRANSACTION`, so
you can charge your customers per-rail when their payments settle over ACH, RTP, FedNow,
or wire.

- Set a standing rail fee with `feeConfigs` on `PATCH /config`鈥攕pecify the rail,
direction (`OUT`), and originator (`GRID` or `EXTERNAL`).
- Both fee types can apply to the same transaction鈥攆or example, a cross-currency payment
that goes out over ACH. Your platform receives the sum of all applied fees.
- Rail fees are keyed by `(feeType, rail, direction, originator)`, so you can set
different fees for different rails.

See [Assessing fees](/payouts-and-b2b/payment-flow/assessing-fees) for configuration
examples and how the fees are calculated.

</Update>

<Update label="August 2026">
Expand Down
Loading