Discover new features and improvements to Moov.
CapabilityDisabled event on a merchant was not triggering a subsequent CapabilityEnabled eventfilename for text evidence in the response
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.
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.
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.
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.
v2026.10.00 is in-development and should be used with caution as breaking changes may occur.
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:
imageIDpublicIDurl / linkaltTextcreatedOn, updatedOn, disabledOnThis allows you to identify duplicate images so you can reference or use existing resources rather than re-uploading the same image.
VoidApproved and/or VoidDeclined events for an already billed authorization produced usage events409 conflict on reattempts after changes, which blocked onboarding new domains for Apple Pay
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.
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.
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.
website field was accepting email addresses, which caused display issues
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.
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.
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 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.
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:
| Card brand | Test card number | CVV | Postal code | Expiration date |
|---|---|---|---|---|
| Visa | 4111300030003000 |
Any 3 numbers | Any 5 numbers | Any future date |
| Mastercard | 5200900090009000 |
Any 3 numbers | Any 5 numbers | Any future date |
| Discover | 6011111111111117 |
Any 3 numbers | Any 5 numbers | Any future date |
| American Express | 371111111111114 |
Any 4 numbers | Any 5 numbers | Any future date |
The test credit cards above can be used for testing any features in test mode. Additionally, we've added two new test debit cards:
| Card brand | Test card number | CVV | Postal code | Expiration date |
|---|---|---|---|---|
| Discover | 6011233333330000 |
Any 3 numbers | Any 5 numbers | Any future date |
| American Express | 372021002000199 |
Any 4 numbers | Any 5 numbers | Any future date |
See our test mode guide for more information.
PATCH invoice requestssalesTaxAmount field from newer API versionsPATCH fields to include | null
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:
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:
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.
v2026.07.00 is considered in-development until the final release in July.
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{
v2026.07.00.
The payment method Drops theme has been updated. The new theming better supports verification and more closely matches Moov Dashboard flows.
Note that the following capabilities are legacy capabilities and will be fully deprecated in a future API version:
walletsend-fundscollect-fundsUpdate capabilities as needed, to the following:
wallet.balancesend-funds.achsend-funds.instant-banksend-funds.push-to-cardcollect-funds.achcollect-funds.card-paymentsmoney-transfer.pull-from-cardmoney-transfer.push-to-cardSee the capabilities guide for more information.