Changelog

Moov Drops

We’ve released three pre-built user interfaces for embedding payments quickly and securely.

• Onboarding: implements a flow for onboarding and verifying customers
• Payment methods: an interface for helping users set up and manage their linked bank accounts and cards
• Card Link: a web component for adding credit card information securely

All Moov Drops:

• Leverage Moov.js, ensuring that sensitive data never hits your servers
• Optimize for a seamless user experience through form-shortening, error handling, and accessibility features
• Are customizable to match your brand (see our theming guide)

Cards

• You can now refund card payments in the Moov Dashboard. You can issue a full refund from a transfer with card-payment as the source.
• We now include card type and issuer information on linked cards in the Dashboard.
• We added a new cardDetails object for setting a dynamic statement descriptor and recurring flag for card payments.
• Fees will be shown in the Dashboard. Fee support in the API will be generally available soon.

Node SDK

• We launched documentation for our Node SDK. You can now quickly generate OAuth tokens with the proper scopes to use in Moov.js, add new accounts from the server, and initiate a new transfer. This reduces the lines of code needed to interact with our platform (compared to making the API call directly), saving time and allowing you to move money faster.

Listing industries

• We added a new endpoint for listing accepted industries, including their name, MCC, NAICS, and SIC codes. Use the API or Moov.js to list industries.

Autocompleting addresses

• We have a new endpoint for auto-completing addresses, creating a better user experience with less timing and better accuracy for KYC verifications.

Improvements

• Plaid customers using the Moov processor token will now receive a canned response when using a Moov test account.
• We improved the display of bank accounts, cards, and their payment methods in the Dashboard.

Dashboard

• We’ve released Dashboard metrics. You can now view new accounts (by type and overall), transfer count (by status and overall), and transfer volume over time on the Moov Dashboard. See our Dashboard overview guide for more information.

Server-side SDK

• We started work on Moov’s first server side library to make interacting with our API even easier.
  • If you have a Node backend you can npm i @moovio/node to install the early version of the API. The first feature is a way to generate OAuth scopes, which you can pass back to the client to initiate Moov.js with. Additional features, and robust documentation are coming soon. View the NPM page for basic documentation.

Collect-funds capability

• In preparation for the release of our card acquiring beta program, we wanted to simplify the onboarding process for our customers that intend to accept card payments. Part of this preparation is to only allow businesses to have the collect-funds capability.

Wallets

• Utilizing a Moov wallet can be a great way to simplify and expedite many payment use cases. Starting now, any Moov account with the send-funds or collect-funds capabilities enabled will automatically get a wallet. This wallet may be used for payment exception use cases.

MX Integration

• Moov has partnered with MX to offer our clients another seamless way to perform instant account verification. Our clients that have an existing MX relationship can now connect their MX account directly to their Moov account so their clients have the ability to link their bank accounts instantly. See our MX integration guide for more information.

Transfer status webhooks

• The transfer.updated webhook event now includes the rail-specific statuses that correspond to each leg of the transfer. The breakdown of statuses can be found here. This provides a more granular level of transparency on a transfer and will notify you (if subscribed) of transaction completion or any rail-specific issues that arise when we hear about them.

Test mode

• We’ve enabled test accounts so you can interact with Moov’s platform without sending real money or waiting on account verification.
  • API key creation for test accounts
  • Simulate micro-deposits by inputting $0.00
  • Simulate successful transfers

Transfers metadata

• We now allow our customers to store free-form data on transfers. As a customer, you can store any type of data that suits your needs, for example: invoice numbers, correlation IDs, SKU data, etc.

Bug fixes

• We resolved a bug that was preventing 2FA codes from being emailed out for a brief period of time.

Improvements

• We made small text updates to improve the consistency of member role names (i.e., “Administrator” instead of “Administrators”).
• We improved internal logging across session refreshes to continue to monitor, track, and prevent fraudulent activity.
• We updated the UX for adding multiple domains on an API key.

Plaid integration

• Moov-managed Plaid integration allows our customers to offer instant account verification and launch the Plaid experience from Moov.js.

Webhooks

• We finished a project this cycle to ensure all the required information is included on all the webhooks so developers can pull the information that is needed. We also updated our documentation to include a list of the schemas for all the webhook events.
• Added the accountID and status to the bankAccount.created, .updated, and .disabled events.
• The transfer.created and transfer.updated now include the accountID for the account facilitating the transfer along with the status of the transfer.
• We are now sending events for the transfer.updated event when a transfer fails or is reversed, since sometimes things don’t go as planned.
• We added the accountID to the balance.updated webhook to allow developers to get additional information about the wallet if needed.
• The paymentMethod webhook events now include the accountID and the sourceID to allow developers to more quickly get information about that payment method.
• The representative.created and representative.updated webhooks now include the accountID for the account the representative belongs to.

Permissions

• For users with “Developer,” “Support,” or “View only” permissions, the dashboard will now reflect what actions they can or cannot perform instead of getting an error message when they attempt to perform that action. If the user isn’t able to perform an action, the button will be disabled, hidden, and in some cases, the entire section won’t be visible.

Dashboard

• We added verification status to the accounts list and account details.
• Improved usability of date of birth, tax ID, and phone number fields.

Bug fixes

• We resolved an issue where a warning banner was being shown when it wasn’t supposed to be when trying to add a new member.
• We resolved a bug that was temporarily preventing you from switching the role of a user in the dashboard.