Invoice updates

Available in API version v2026.04.00 and later, you can now create a notification for invoices which are unpaid or overdue. A notification resends an invoice email to a customer. Note that only email notifications are supported at this time.

Also supported with API v2026.04.00 and later, you can provide an optional customerEmail and invoiceNumber when creating an invoice.

• customerEmail overrides the invoice destination during OTP verification
• invoiceNumber overrides the auto-assigned invoice number

See the invoice API for more information.

We've also updated invoicing in the Dashboard:

• Invoice details now include the payment link URL, customer name, and customer email
• Error messages and validation feedback are clearer and more helpful

Card issuing updates

Three new simulation endpoints have been added to API v2026.10.00 to facilitate testing card issuing in test mode.

• Create a simulated authorization
• Create a simulated clearing
• Create a simulated reversal

Bug fixes

• Fixed and improved pagination for large transfer histories
• Fixed an issue in which auto-enroll was re-enrolling purposely disabled merchants
• Fixed race conditions in which transfer webhooks were being dropped
• Fixed an issue in which invoices failed to send if a merchant had a default wallet under more than one partner account
• Fixed an issue in which holderName updates were not being sent to CardUpdated with Moov Drops

Get spending card activity

A new spending card activity endpoint has been added to Moov's API, starting with v2026.10.00.

The endpoint returns a list of spending card activity associated with a Moov account, such as authorizations and settlements. The following query parameters are available:

• skip
• count
• issuedCardID
• authorizedUserAccountID
• statuses
• startDateTime
• endDateTime

See the card issuing API for more information on spending cards.

Query transfers by invoiceID

The list transfers endpoint now includes the invoiceIDs query parameter:

/accounts/{accountID}/transfers?invoiceIDs=1,2,3

Webhook updates

The bankAccount.updated webhook event has been updated to trigger with the verification-expired status reason.

The dispute.updated webhook event now has additional status triggers:

• When submitted evidence changes the dispute to under-review
• When a refund changes the dispute to resolved

Bug fixes

• Updated partner statements to reflect accurate residuals
• Fixed an issue with settlement timing for partner-paid billing fees
• Fixed an issue where webhook URLs were receiving a 500 error if they were more than 250 characters. Webhook URL limits are now 2048 characters. Webhook URLs over 2048 characters will now receive a 422 error.

Self-serve ACH returns

Approved accounts can self-serve ACH bank account errors (R29) with Moov's API or Dashboard. An R29 error may occur if a bank account fails verification or if a debit attempt fails. Resolve the error through a reset, attesting the end user has reauthorized debits.

Each bank account can attempt one new authorization attestation in a rolling 365-day period. If an account receives an ACH return error a second time within that timeframe, you must contact Moov support.

See the Self-serve ACH error guide and Dashboard guide for more information.

Product catalog isTaxable

Starting in API v2026.10.00, the product catalog now includes an isTaxable boolean field, which denotes whether applicable tax rules may be applied to the product.

The value can be used to determine how to populate the tax amount on a transfer (Moov does not compute or assess tax). true means a tax amount can be included; false means it should not. Omitted values default to true on creation and preserve the existing setting on update.

UI updates in the API

Large sections of Moov's API reference have been organized with new endpoint groupings. The additional groups are a UI feature intended to help you easily find endpoints. For example, the Transfers API is now broken up into three sections on the page: Transfers, Transfer lifecycle, and Transfer options and configuration.

Bug fixes

• Fixed a bug with duplicate destination-paid fees on self-to-self transfers
• Fixed a bug in which a CapabilityDisabled event on a merchant was not triggering a subsequent CapabilityEnabled event
• Fixed a bug handling failed transfer creation for confirmed captures
• Fixed a bug in which invoice amounts exceed supported limits
• Fixed a bug in which the evidence endpoint was returning filename for text evidence in the response

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