Payout fees in the Dashboard

Payout fee support has been added to the Moov Dashboard. Accounts have the ability to pass on payout fees to recipients. Payout fee options provide customers a way to offer no or low cost standard ACH payouts alongside faster payout methods with higher fees. Recipients can choose their preferred payout method and associated fee to receive funds.

By default, merchants pay the fee, which is charged to the source's Moov wallet. If a recipient fee is added, the fee is deducted from the destination before the funds are delivered.

See the Dashboard payment link and transfers guides for more information.

Streamlined partner onboarding in the Dashboard

Partner accounts now provide more business information up-front during onboarding. This streamlines the communication process between partner accounts and Moov support to enable production accounts.

Bug fixes

• Fixes an issue in the Dashboard in which declined invites were still appearing

Payout fees

Starting with Moov API v2026.07.00, Moov accounts now have the ability to pass on payout fees to recipients. Payout fee options provide customers a way to offer no or low cost standard ACH payouts alongside faster payout methods with higher fees. Recipients can choose their preferred payout method and associated fee to receive funds.

By default, merchants pay the fee, which is charged to the source's Moov wallet. If a recipient fee is added, the fee is deducted from the destination before the funds are delivered.

See the payout fees guide for more information.

Update fee plan agreements

Starting with API v2026.10.00 (in-development), you can update an account's fee plan agreement using the create fee plan agreement endpoint.

When sending the request, the planID is the new fee agreement and priorAgreementID is the fee agreement being replaced.

See the fee plans guide for more information.

Bug fixes

• Fixed an issue where payment methods were not being attached to the corresponding capabilities
• Fixed a Dashboard issue where a new onboarding link was only appearing upon refresh
• Fixed a Dashboard issue where merchant category restriction declines were not appearing
• Fixed a Dashboard issue in which not all active wallets were appearing on the balances view

Duplicate images in the library

Starting with API v2026.10.00 (currently the in-development API version), the upload images endpoint has an updated 409 (conflict) response model, which now returns the following image metadata if a duplicate image exists:

• imageID
• publicID
• url / link
• altText
• createdOn, updatedOn, disabledOn

This allows you to identify duplicate images so you can reference or use existing resources rather than re-uploading the same image.

Bug fixes

• Fixed an issue with the sign-in screen being blurry in Firefox
• Fixed an issue where users were redirected to the previous step when uploading documents in hosted onboarding
• Fixed an issue where funding transactions were not aligned with the interchange program
• Fixed an issue where updating a card was not updating card type
• Fixed an issue where VoidApproved and/or VoidDeclined events for an already billed authorization produced usage events
• Fixed an issue where some card account updater events were being handled out-of-order
• Fixed an issue with Apple Pay 409 conflict on reattempts after changes, which blocked onboarding new domains for Apple Pay
• Fixed an issue where webhook URLs were not updating and in-flight retries hit the old URL
• Fixed an issue which allowed invalid wallet status updates

General update

• Removed the requirement for an email or mobile number for the transfers capability

FedNow support

FedNow instant payments are now supported with the instant-bank-credit payment method. Eligibility is automatically checked when linking a bank account and eligible accounts will be able to receive payments on both the FedNow and RTP networks. Depending on the bank's support, Moov will automatically select either the RTP or FedNow network.

See our instant payment guide for more information.

feePlanID

An optional feePlanID has been added to the onboarding Drop. When set, the feePlanID shows the pricing disclosure on the onboarding review step. This allows merchants to review and agree to the fee plan before finishing the onboarding process.

See the onboarding Drop guide for more information.

API v2026.10.00 preview

The preview of API v2026.10.00 is available. The API is considered in-development and should be used with caution as breaking changes may occur without notice.

Bug fixes

• Fixed a bug with brand colors not appearing correctly on payment link buttons
• Fixed a bug where the website field was accepting email addresses, which caused display issues
• Fixed a bug in which not uploading a document when "no processing statements" is selected caused a redirect to the previous step during hosted onboarding
• Fixed a validation error with resolution links
• Fixed an issue where an individual account couldn't be enabled unless an email address or mobile number was submitted

Resume account creation & edit Drop

You can now pass an optional accountID prop in the onboarding Drop when embedding the component.

This allows users to continue where they left off in the onboarding process and fix any verification errors, which is especially useful for onboarding business with multiple beneficial owners. Ensure the generated token is scoped to the same accountID that's passed to the Drop.

See the onboarding Drop guide for more information.

Customizable Dashboard roles

Dashboard users can now create and update their own custom roles in addition to Moov-created roles. This change provides more granularity in what team members can see and do in the Dashboard.

See the managing teams guide for more information.

Invoice URL sharing

You can now copy a payment link invoice URL from the Dashboard, or fetch the URL from the invoicing API.

Invoices are still delivered by email, but you now have the option to copy the link to share via another method (such as SMS). Users that open the shared link will be prompted for a one-time, time-based passcode sent to their email. Look for the Payment link field under Invoice details in the Dashboard.

API v2026.07.00

API v2026.07.00 is now officially released - the version is stable and no breaking changes will be made. Use SDK version 26.7.x with API v2026.07.00.

Bug fixes

• Fixed an issue where billing statement totals were not reflecting residuals during the statement period
• Fixed an issue in which default wallet creation was lagging, which caused wallets to not be found in production

Surcharging in test mode

We've added test credit cards so you can test surcharge fees in test mode. When testing surcharge fees, use the following cards and accompanying requirements:

The test credit cards above can be used for testing any features in test mode. Additionally, we've added two new test debit cards:

See our test mode guide for more information.

Bug fixes

• Fixed a bug where card verification was showing the incorrect status
• Fixed a bug where push to card and pull from card transaction data was not appearing for accounts
• Fixed a bug with sales tax amount in PATCH invoice requests
• Removed the deprecated salesTaxAmount field from newer API versions
• Updated nullable/clearable PATCH fields to include | null

User defined amounts

Allow buyers and payees to choose their own payment amounts when they receive a payment link. You can set a minimum and maximum range, as well as select up to five suggested amounts.

User defined amounts in payment links is supported starting with API v2026.07.00 and in Moov's Dashboard. A payment link can either be a standard payment or payout, or a user defined amount.

In the payment links API (v2026.07.00 and higher), amount is no longer a required field for payment links. amount is required for payment and payout links, but must be omitted for customAmountPayment links.

See the following guides for more information:

• Payment links API guide
• Payment links in the Dashboard

Bug fixes

• Fixed a bug in which financial institutions were being asked to verify a bank account when linking a settlement account via hosted onboarding.
• Fixed a bug with payment links on Safari in which the email field didn't display a cursor and didn't support text selection.
• Fixed an issue where uploading a file was not possible
• Fixed an issue in which push and pull card acquiring transactions were not appearing in the transaction history.

Surcharge fees

Surcharge fees on credit card transactions are now available with Moov API v2026.07.00. Surcharge fees are optionally enabled, and must follow card brand caps and state and federal regulations. Surcharges can be added to:

• General transfers
• Payment links
• Invoices

When creating a transaction, a surcharge fee can be added to the request in amountDetails. See the main surcharge guide or any of the API links above for more details. You must contact Moov to enable surcharging and start the registration process.

Tax amount

The taxAmount field is being deprecated in Moov API v2026.07.00 onwards. Taxes can now be added to amountDetails. This affects general transfers, payment links, and invoices.

1{
2  "amountDetails": {
3    "tax": {
4      "currency": "USD",
5      "valueDecimal": "8.25"
6    }
7  }
8{

Drop payment method theme updates

The payment method Drops theme has been updated. The new theming better supports verification and more closely matches Moov Dashboard flows.

Legacy capability reminder

Note that the following capabilities are legacy capabilities and will be fully deprecated in a future API version:

• wallet
• send-funds
• collect-funds

Update capabilities as needed, to the following:

• wallet.balance
• send-funds.ach
• send-funds.instant-bank
• send-funds.push-to-card
• collect-funds.ach
• collect-funds.card-payments
• money-transfer.pull-from-card
• money-transfer.push-to-card

See the capabilities guide for more information.

Bug fixes

• Fixed an issue where ACH addenda was missing from the originated entry on child transfers
• Fixed an issue with corrected monthly minimums on statements
• Fixed an issue with Amex card account updater enrollment

Account connections

You can now share your scopes with connected accounts. Sharing scopes connects you to other Moov accounts you've created, like a merchant who accepts payments. Sharing scopes also connects that merchant to their own customers.

During the hosted onboarding process for each Moov account, you can now select which scopes to share. Additionally, you can use the API to share an account connection.

Moov maintains strict access controls when you share scopes with a merchant. While you gain visibility across every connected account, merchants can only access their own customers.

See the main connected accounts documentation for more information.

Client-side TypeScript SDK

Moov's TypeScript SDK is now available as a client-side SDK with OAuth. Client-side authentication is supported through the accessToken. See our authentication guide for more information.

Enhanced AI functionality in documentation

Our documentation site has some new, enhanced AI functionality. You can now get more detailed answers when you ask about specific pages and code blocks. You can ask more specific questions and the AI responses will include associated code samples. For example, you can now ask how to use a feature with a specific SDK.

Your AI chats with Moov are also now saved to your browser.

Bug fixes

• Fixed a bug with authorization in sandbox mode