← Back to all sparks
M

Moov

FINANCE
Velocity6.3

Moov is filling in the payfac feature matrix, and now moves money on both US instant rails.

payments-infrastructureinstant-paymentsembedded-onboardingpayment-linksconnected-accountsapi-versioning
Current state
Moov ships every two to three weeks against a quarterly versioned API, with previews running ahead of each stable release. The recent work splits cleanly: acquiring features that merchants ask for by name — Google Pay, tipping presets, HSA/FSA/HRA card processing, credit card surcharging, user-defined amounts on payment links — and platform plumbing for the businesses embedding Moov, including resumable onboarding Drops, resolution links for failed verification, custom Dashboard roles, account connections with scoped visibility, and a client-side TypeScript SDK.
Where it's heading
Two arcs are running in parallel. The first is coverage: Moov is closing the gap on the payment methods and fee mechanics an established processor is expected to support, one release at a time, and instant payouts now reach both RTP and FedNow with the network chosen automatically. The second is that Moov is behaving less like an API and more like a platform its customers resell — connected accounts with scoped access, embeddable onboarding a merchant can resume and edit, fee-plan disclosure inside that flow. The API discipline underneath is unusually visible, with deprecations like taxAmount announced against a named version rather than dropped.
Prediction
The v2026.10.00 preview is already published, so expect it to stabilize in the autumn window and carry more of the amountDetails consolidation that started with tax and surcharge fees. Given FedNow eligibility is now checked at bank-link time, more work on instant-rail routing and its failure modes is the likeliest follow-on.

Recent moves

  1. 15d ago

    FedNow support, feePlanID in onboarding Drop & API v2026.10.00 preview

    ⚡ SPARK

    Instant payouts stop being a single-network bet: FedNow joins RTP, with eligibility checked when a bank account is linked and the network picked automatically. It lands with fee-plan disclosure inside the onboarding Drop, continuing the pattern of Moov pushing more of the merchant relationship into the embedded flow.

  2. 29d ago

    Onboarding Drop editing, customizable Dashboard roles, invoice URL sharing & API v2026.07.00

    Onboarding can now be resumed and corrected by passing an accountID into the Drop, which matters most for businesses with several beneficial owners to verify. Custom Dashboard roles and shareable invoice URLs round out the same theme: the platform's customers getting finer control over what their own users see and do.

  3. 1mo ago

    Surcharging in test mode & bug fixes

    Test cards for surcharge fees, a month after surcharging shipped. Unglamorous, but a regulated fee feature nobody can exercise in test mode is a feature most teams will not turn on.

  4. 1mo ago

    User defined amounts for payment links

    Payment links can now let the payer choose the amount, within a set range and with up to five suggested values. It also makes amount optional in the API for this link type — a small schema change that widens payment links from checkout into donations, deposits and open invoices.

  5. 2mo ago

    Surcharge fees, taxAmount deprecation & more

    Credit card surcharging arrives across transfers, payment links and invoices, gated behind registration and brand and state caps. The taxAmount deprecation alongside it folds tax into amountDetails, consolidating how money is broken down in a request.

  6. 2mo ago

    Account connections, client-side TypeScript SDK & more

    Account connections let a platform share scopes down to merchants while merchants see only their own customers — the primitive that makes a multi-tier payments platform work. The client-side TypeScript SDK with OAuth pairs with it, moving more of the integration into the browser.