news 2026-03-18 6 min read multiflow newsroom

multiflow open-sources the iframe rate calculator

3-minute scan
  • The iframe rate calculator multiflow ships to operators is now MIT-licensed and available on GitHub.
  • Any operator can fork it, embed it on their own site, and customize vertical lists, volume tiers, and theming.
  • No multiflow attribution is required in the open-source version; there is no hidden telemetry.
  • Contributions are welcomed — the internal multiflow version will continue to merge improvements upstream.
On this page

    multiflow today open-sourced its iframe rate calculator under the MIT license, making the widget available to any operator — not just multiflow customers — who wants to embed a payments rate-quote tool on their own site. The repository includes the full frontend, a Node.js reference backend, worked examples, and theming documentation.

    "We had a choice," said a multiflow engineering lead. "Keep the calculator as a customer-only feature, or ship it under MIT and let the whole operator community benefit. The calculator is not the product — the underwriting relationships, the acquirer stack, and the orchestration layer are the product. The calculator is just a nice front-end, and the operator ecosystem is better off if anyone can use it."

    The decision aligns with a broader pattern multiflow has followed since launch: calculators, templates, and reference documents are free. The commercial offering is the actual orchestration layer. Operators who want to use multiflow's calculator without ever opening a multiflow account can now do so legally, with no attribution or backlink requirement.

    What's in the repository

    The open-source release includes everything needed to run the calculator from scratch:

    • Frontend widget. Single-file iframe with responsive CSS and the same three-input flow (vertical, volume, ticket size) multiflow ships to operators.
    • Reference backend. Node.js server returning the rate quote based on configurable interchange assumptions. Operators plug in their own interchange cost structure.
    • Theming docs. Full CSS override guide plus a small set of pre-built themes (dark, light, neutral, brand-matched).
    • Vertical configuration. YAML file defining rate-card logic per vertical. Forks can add or remove verticals without touching code.
    • Compliance mode. Optional regulatory disclosure text for CA/NY, matching multiflow's internal compliance mode.
    • Tests. 146 unit tests covering rate logic, edge cases, and theming.

    What the open-source version does NOT include

    Three things stay inside multiflow's customer-only product: (1) the live interchange feed that drives multiflow's internal quotes — the open-source version uses a published interchange table that operators update manually; (2) the short-lived token auth system that binds the widget to an operator portal; (3) the direct-to-underwriting lead routing that pushes completed quotes into multiflow's underwriting pipeline. Operators running the open-source version get the frontend and the math; they do not get the underwriting layer.

    That distinction is intentional. The front-end calculator is a commodity; the underwriting is not.

    Why MIT, not something stricter

    multiflow picked MIT specifically because it is the most permissive commonly-used open-source license. Operators can fork the repository, white-label the widget, embed it on commercial sites, and never once mention multiflow. There is no copyleft obligation to share modifications back, no attribution requirement, and no use restriction.

    "We thought about Apache or BSD," said the engineering lead. "MIT is shorter, more widely understood, and operators don't need to lawyer-read it. That's the right call for a front-end widget."

    Contribution model

    multiflow will continue to maintain the canonical upstream repository and will merge contributions via standard pull request flow. The internal multiflow version — which is a superset of the open-source version — will continue to be developed, and improvements that are appropriate to share back (accessibility, performance, bug fixes, new verticals) will be merged upstream on a monthly cadence.

    Operators who find bugs, want new verticals supported, or want to contribute a new theme can open an issue or PR on the public repository. The repository includes a contribution guide and a code of conduct.

    Comparison to existing operator-facing calculators

    The calculator joins multiflow's existing collection of operator tools, including:

    The iframe rate calculator is the first of multiflow's tools to be formally open-sourced. If adoption goes well — measured by fork count, issue quality, and operator feedback — multiflow will move the other calculators to MIT in phases through 2026.

    Who should use the open-source version

    Three operator profiles:

    1. Non-multiflow operators who want a functional rate-quote tool on their own site and are willing to maintain their own interchange feed.
    2. Agencies and consultancies that build operator sites for clients and want a reusable calculator component.
    3. Payments-adjacent tool builders who want to embed rate-quote functionality in a larger product (CRM, finance dashboard, etc).

    About multiflow

    multiflow is the operator-first payment orchestration layer for multi-brand e-commerce portfolios. Built for operators running 3-42 brands, multiflow consolidates acquirer relationships, descriptor management, reserve negotiation, and reconciliation into a single operator-facing surface. Pricing is volume-tiered, 5.5-7.5% per transaction plus a one-time setup fee, with interchange passed through. The iframe rate calculator is now MIT-licensed and available on GitHub; the commercial multiflow offering is at the pricing page.

    Found this useful? Share it X LinkedIn Reddit HN Email

    FAQ

    What license is the calculator under?
    MIT. Fully permissive, no attribution required, no use restrictions.
    Can I use it commercially without being a multiflow customer?
    Yes, that is explicitly allowed. No backlink, no attribution, no commercial restriction.
    Does the open-source version include multiflow's underwriting pipeline?
    No. The open-source version is front-end + reference backend only. The underwriting pipeline stays inside multiflow's commercial product.
    Will other multiflow calculators be open-sourced?
    Yes, in phases through 2026 if adoption of this one goes well.

    Running multiple brands?
    multiflow was built for this.

    The Operator Briefing

    Twice-monthly. No fluff.

    Processor shutdowns, reserve-hold playbooks, reconciliation lessons, and the merchant-account decisions that save operators six-figure years. Delivered to your inbox — never spam.

    No spam. Unsubscribe in one click.

    We use essential cookies · Privacy