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

Google Pay

You can now use Google Pay to accept card payments and send payouts with Moov and the open standard Google Pay API.

Google Pay is a fast and secure way to move money in a variety of use cases, such as:

• Accept card payments from payers
• Send near real-time disbursements to recipients' cards
• Pull funds from debit or prepaid cards on file for approved use cases

Visit our guides and API documentation for more information. Google Pay is available for Moov API starting with version v2026.04.00.

API v2026.07.00 preview

The preview of API v2026.07.00 is available. This preview includes the following:

• /card-metadata endpoint. Use this endpoint to look up metadata for a card without linking it to a Moov account. This endpoint requires you to provide Moov with a copy of your PCI attestation of compliance before use.
• Removes salesTaxAmount on payment links and transfers
• Adds amountDetails.tax to payment links and transfers

Bug fixes

• Fixed a bug with rail-specific details determining the outcome of a transfer and added rail-specific details to the failure code in the checkout transfer creation response
• Fixed a bug in which unsetting transfer metadata was not working

Tipping

Moov now supports tipping for payment links and transfers. Use Moov's API or Dashboard to create tipping presets for the checkout process. Tipping presets can be fixed amounts, or percentages of the total on a pre or post-tax basis.

Presets must be enabled per Moov account. In the Dashboard, enable tipping and set up presets in your account's business details settings or a merchant's account settings.

The API has three new transfer configuration endpoints which allow you to create, update, and view tip presets for an account.

See the following documentation for more information:

• Enable tipping via API
• Payment link tipping via API
• Payment link tipping via Dashboard

Tipping demo

Healthcare benefit cards

Moov now supports processing HSA, FSA, and HRA cards for Healthcare merchant category codes (MCCs) and 90% rule merchants on the Visa and Mastercard networks.

Visit our documentation for specific information on accepted MCCs and 90% rule merchants, rules, regulations, and registration details.

Create schedules in the Dashboard

You can now create scheduled transfers and recurring transfers in the Dashboard. Select a future date for a single transfer, or create a recurring transfer on a daily, weekly, monthly, or yearly schedule.

Moov's Dashboard also supports viewing and cancelling schedules as well as sending receipts. Visit our documentation for more information.

Bug fixes

• Added a missing Subtotal and Tax row to the hosted checkout flow

Quarterly API - v2026.04.00

Moov API version 2026.04.00 is now stable. This release includes resolution links and instant bank credit, described below.

Visit our reference guide for information on API versions.

SDKs

SDKs have been bumped to a new, stable version. The in development SDK version 26.4.0-dev.x is now 26.4.x.

Resolution links

When a business mis-keys or omits information during account verification, you can now generate a link for them to resolve outstanding data issues. Resolution links are temporary, secure links which allow a business to provide missing information or upload missing documents. Use the Moov Dashboard or API to check for requirement errors and send a resolution link via email or SMS.

Moov sends the business a secure MFA code to access the link, which automatically expires after 30 days.

View our Dashboard and API guides for more information.

Instant bank

RTP transactions are now supported by the instant-bank-credit payment method. In the near future, instant-bank-credit will also support FedNow transactions.

General updates

• Credit cards can now be used for approved pull-from-card (AFT) use cases
• OpenID Connect providers can now be configured in the Dashboard, allowing new members of your team to sign in with your company-provisioned credentials
• Hosted onboarding now shows your brand colors and makes your logo more prominent
• Added imageID validation error field to invoice line item models
• Added a title filter for list products API

Bug fixes

• Fixed a bug in sandbox mode where underwriting was stuck in pending after approval
• Fixed a bug in which query params were not being validated on some card transactions queries
• Added pattern to TerminalApplication.packageName
• Made all fields in rail details models optional
• Fixed an issue where the /accounts/{accountID}/fee-revenue endpoint was not returning merchant fees

Onboarding Drop

Our onboarding Drop has undergone a makeover with a more streamlined look. Additionally, the onboarding Drop now supports granular capabilities and dynamic underwriting.

Visit the onboarding Drop guide for more information.

Docs MCP server

You can now use Moov's MCP server in conjunction with our new docs MCP server. The docs MCP server allows you and your AI agent to parse Moov's documentation and ask questions about how to set up integrations.

Visit our MCP & AI section for more information.

General updates

• Credit cards can now be used for approved pull-from-card (AFT) use cases
• OpenID Connect providers can now be configured in the Dashboard, allowing new members of your team to sign in with your company-provisioned credentials
• Hosted onboarding now shows your brand colors and makes your logo more prominent
• Added imageID validation error field to invoice line item models
• Added a title filter for list products API

Bug fixes

• Fixed a bug in sandbox mode where underwriting was stuck in pending after approval
• Fixed a bug in which query params were not being validated on some card transactions queries
• Added pattern to TerminalApplication.packageName
• Made all fields in rail details models optional

Partner billing

Our new partner billing API provides more insight into fees, residuals, and revenue. You can now retrieve information about your partner costs and merchant-generated revenue to reconcile costs and residuals.

On the first day of each month, Moov will generate a statement for your account. Partner statements will include a summary of the following:

• Merchant fees collected for each fee category
• Partner fees assessed for each fee category
• Net income for each fee category
• Residual payment (for revenue-share partners)
• Monthly partner platform fees (if applicable)
• Interchange report

You can access your statements with the list statements endpoint. View the new billing guides for more information.

Invoicing

Use the invoices API or the Dashboard to send professional, branded invoices to your customers and accept payments without relying on third‑party tools.

When you send an invoice, Moov automatically creates a single-use, secure payment link scoped to that invoice and customer. See our invoices guide for more information.

API & SDK versioning

Moov API v2026.01.00 is officially released. API v2026.04.00 is available as an in development API and should be used with caution as breaking changes may occur without notice.

Visit our API version reference for details on major releases per version.

SDK versioning will follow the following format:

Currently API v2026.04.00 is in development, so the corresponding -dev.x SDK version indicates an in development version of the SDK and should be used with caution.

Bug fixes

• Fixed a webhooks bug when fetching an accounts metadata and foreignID
• Fixed a bug where transfers were getting stuck in sandbox mode
• Fixed a bug in which createTransfer was being duplicated for sweeps