One of four products in one stack. The same page structure on all four, so comparing them is reading rather than hunting.
ForgeRails
The payment layer: deposits and withdrawals, provider routing, and stablecoin deposits that credit automatically.
What it removes.
The gap between a client sending money and being able to trade. It also removes the second ledger: there is no payments system holding one view of a balance while the platform holds another, and therefore no nightly reconciliation and no support conversation about which one is right.
Capabilities.
- 01
Stablecoin auto-deposit
A confirmed on-chain transfer credits tradable balance without anyone approving it. The client is trading, not waiting for your morning.
- 02
One ledger
Payments write to the balance the platform reads. There is no reconciliation because there is nothing to reconcile.
- 03
Provider routing
Multiple payment providers with rules per method, currency and region. A declining provider is routed around without a deployment.
- 04
Withdrawal approval
Configurable approval steps with a recorded trail of who authorised what. The rules are yours; the record is not editable.
The claim is one system. This is where it is either true or not.
How it connects to the rest of the stack.
Not "integrates with" — there is nothing between these to integrate. Each line below names what actually crosses, and what does not have to happen as a result.
- ForgeRails ForgeTerminal
- A credited deposit is margin immediately. The terminal is reading the ledger the payment wrote to, not a copy of it.
- ForgeRails ForgeQuote
- Margin calculations use the settled balance, so a deposit does not need a pass before it can support a position.
- ForgeRails ForgeCRM
- A withdrawal raised in the trader’s room carries its approval trail from request to settlement as one record.
Technical detail.
| Stablecoins | Auto-credit on confirmation. Supported chains — see missing items below. |
|---|---|
| Providers | Multiple concurrent, with routing rules per method and region. |
| Approvals | Configurable steps, immutable trail. |
| Custody | ForgeBroker does not hold client funds. See /trust/security. |
Interface.
No screenshots yet. Real interface captures and a short video are outstanding (brief §11). A stock mock-up would be the one thing this page cannot afford: the pitch is that the product exists, and a fabricated screenshot argues the opposite to anyone who looks closely. The demo environment is the honest substitute until the assets exist.
Questions that come up.
Not written yet. The brief asks for three or four questions that actually come up in sales calls. Those have to come from someone who has sat in them — inventing plausible-sounding questions would produce a section that answers nothing a real buyer asked.
5open items on this page
- Screenshots of the deposit and withdrawal flows, and a short interface video (brief §11).
- Which stablecoins and which chains are supported, with confirmation thresholds.
- The list of payment providers integrated today, by region.
- Settlement timings per method — and these are figures, so each needs its measurement definition before it can be published.
- FAQ — needs real sales-call questions.
Listed because a page that hides what it does not know is the thing this audience is checking for. Figures among these will each need their measurement definition before they can appear — see execution transparency.
See it before you decide.
ForgeRails is not sold separately. The demo gives you the whole stack, because that is the only way to check whether the connections above are real.