Discover new features and improvements to Moov.
You can now update the expiration date and address details for a card, as well as re-verify a card’s CVV, using Moov’s new Update card PATCH endpoint. With the new endpoint, when a CVV is provided, immediate re-verification is initiated. If no CVV is provided, the updated details are saved for the card’s next use.
Visit Moov’s Card payments documentation for more information.
Moov now provides the option to send a card reversal request. A reversal will either cancel a transfer or refund a transfer depending on the settlement status. If a transfer can be canceled, this reduces processing costs for the merchant and returns funds to cardholders quicker. Read more in our Reversals documentation.
Payment methods for Apple Pay now include unique fingerprint detection, expiration date, and dynamic last four of the device-specific card number.
Moov has updated the micro-deposit process. In addition to sending two micro-deposit credits, Moov initiates a debit to re-coup the credit amount. Each micro-deposit now has a range of up to .49¢.
You have the ability to use more characters in account names, for example, characters like ñ are now accepted. The characters are converted before sending them off to certain payment rails with character restrictions. To see all accepted characters, you can view the name object in an individual’s profile in the create an account endpoint.
An issue in the Payment methods Drop was resolved where the onResourceCreated event wasn’t firing when adding a bank account or card.
An issue with the way the foreignID and the created date was displayed in the business accounts’ Dashboard view has been corrected.
Moov can now approve accounts for default faster ACH processing. Faster ACH processing allows you to bypass the standard two-day debit hold period, kicking off the credit process soon after the transfer is initiated. Based on processing cutoff times, bank-to-bank and bank-to-wallet transfers can fully complete in one day. Faster ACH approved accounts will also have the ability to add the two-day hold period to a transfer if desired.
You can now permanently disconnect accounts from your Moov account. This action does not delete the account or any associated data with the account. Disconnected accounts cannot be interacted with, and you will no longer be able to edit the profile, upload documents, or create new transfers or payment methods. Disconnected accounts will also no longer appear in your list views, however, you can still view them using a filter. When disconnecting accounts, please take note this action cannot be undone.
The Capabilities tab in the Moov Dashboard now shows when an account requires a review from Moov. In this scenario, capabilities will show as pending with no requirement errors.
We’ve optimized our account search endpoints to be exceedingly quick. You can search by term, status, account type, or any combination of the three to retrieve your account list in as little as half a second.
With broader search criteria, you will now be able to see more than just exact matches in your search results.
There was a problem in the Dashboard where the “Review” button was not functional. We’ve updated the “Review” button so it should work for accounts with capability errors.
We shipped a pre-built UI component that allows users to upload important documents to their Moov account. With this Moov Drop, your users pass documents directly to Moov and you stay out of the flow of sensitive data collection.
We have optimized the LIST wallet transactions endpoint so that paginated and filtered transactions load faster than ever.
If you’re not already benefiting from wallet transactions, they make it easy to track all the money moving through your platform. You can use them to present detailed transaction history and for real-time reconciliation. See our wallet transactions guide to learn more.
In addition to the Dashboard and Moov API, you can now upload files related to an account using Moov.js. This means you can stay out of the flow of sensitive documents and allow them to be passed directly from your user to Moov. To read more on file upload specifications, see our file uploading guide.
We optimized our verification logic to improve business verification speed and consistency.
We’ve added transfer failure reasons to the Moov Dashboard for greater transparency and understanding for why a transfer did not succeed. See our transfer failures guide for more context on failure reasons.
As a part of our underwriting process, you can now provide underwriting data in the Moov Dashboard. When creating a new account via the Dashboard, you can input the required information depending on the capabilities the account needs. You can also edit these fields when viewing an account’s profile and clicking on transaction details.
We resolved an issue that was causing some ACH transactions initiated during weekends to not complete as scheduled.
The new issued card Moov Drop enables customers to display a previously issued virtual card within a secure, Moov-hosted iframe.
We have added a new underwriting requirement for certain capabilities. See our underwriting guide for more context on when we need to underwrite an account and what we require. A section for underwriting will be added to the Moov Dashboard in the near future.
We resolved an issue that was causing some ACH test mode transfers not to complete as scheduled.
We’ve improved visibility by surfacing reasons for failed bank account validation attempts. For example, when micro-deposits expire, the statusReason will be ErrMicroDepositExpired.
We have updated the status field on disputes objects. Pre-disputes resolved by Visa’s rapid dispute resolution will have the resolved status, while all other disputes have status response-needed status.
We have added the respondBy field added to disputes object. The date in the respondBy field should be must be presented to the merchant as the last day they are able to submit evidence to fight a chargeback. See our disputes guide for more information.
The networkReasonCode field for a dispute in the transfers endpoint will now return an empty string, and will be fully deprecated on January 21, 2023. The network code is still available via the GET dispute endpoint.
When a transfer fails, we will now communicate the reason for the failure through the failureReason field in API response for a GET transfer. The failureReason field provides context so our platform partners can understand why a transfer failure happened and determine what next steps to take. See our failures guide for more information on the reasons and their corresponding descriptions. Please note, card and ACH specific failure codes are still available under the source and destination objects.
The availableBalance field on the balance.updated webhook event is deprecated. If you need to retrieve the available balance for a wallet, you can use the GET wallet endpoint.
We’ve made some updates that allow us to send webhook events faster. However, because we are prioritizing speed, we can no longer guarantee ordering on the walletTransaction.updated webhook event.