Moov Drops

If you need to limit which card brands you accept, you can now toggle which brands you support using the allowCardBrands option in the Card link, payment methods, and onboarding Moov Drops.

Cards

• To improve fraud detection and prevention, we integrated with Mastercard’s MATCH service.
• transactionSource for transfers using a card is now supported on all card brands.

Improvements

• Improvements and bug fixes relating to missing account requirements and locking down fields after verification.
• For clarity, we renamed the “Profile” navigation link within an Account to “Settings”.
• We now show all fields under your account’s Business details section.
• Improved our tracking of when a customer has moved to production to prevent multiple employees from having to fill out the same form.

Bug fixes

• We resolved an error where previous transfers in a transfer group wouldn’t show if they had been refunded.
• We fixed an issue where some users weren’t able to advance past the initial loading screen.
• We fixed an issue where the markup fee set on a transfer could be incorrectly calculated.

Onboarding

We rebuilt our entire sign-up and onboarding process to remove as much friction as possible before folks start building. Specifically, we: - Rebuilt our test environment and removed all of the hoops customers previously had to jump through before building. This includes filling out a test business profile, adding test business representatives, and even creating connected accounts and payment methods. All you have to do after signing up is generate test mode API keys and start building. More to come! - Streamlined how we collect required information about your business to get you to production. This historically cumbersome process of inputting data is now seamless. Ensuring that we have all of the necessary information to verify your business up front can shave days off the onboarding timeline.

Dashboard

We improved how we communicate with our clients through their Moov Dashboard by clarifying action items and statuses for your accounts. This includes showing when an account has been verified and therefore can no longer be updated, as well as communicating any verification issues with your accounts and what needs to be corrected to proceed.

API authentication

You can now use basic authentication to authenticate with the Moov API! It's important that you only use this for server-to-server communication and not in a browser.

Once you've created an API key, within your server-side app set the Authorization header to Basic <credentials> where credentials is the Base64 encoding of public key and private key joined by a single colon :. When using this authentication method you don't need to set scopes, but keep in mind that your API key will have read and write access to every Moov endpoint within your account.

OAuth 2.0 based authentication with scopes remains the most secure way to communicate with the Moov API from a browser and can still be used to create restricted access tokens for server-to-server communication.

Account capabilities

You no longer need to request the transfers capability after creating an account because it will automatically be requested and enabled upon account creation. This change simplifies the process of creating accounts that will be charged or sent a payout that don't require verification.

Improvements

• We made it quicker and easier to request capabilities for new accounts by allowing you to create an account and request capabilities in the same API call.
• In an effort to reduce confusion and accidental overwrites of existing data, we have added PATCH methods and have removed the PUT methods for updating Accounts and Representatives. PUT updates to Accounts and Representatives will no longer be supported.

Account locking

Once a Moov account has been verified, you will be unable to edit most of the business or individual identity details as additional verification may need to take place. If you need to update verified information, requests should be sent to our support team.

Dashboard

We made a handful of dashboard improvements to improve how we communicate the status of your account.

• Transfer groups are now visible in the Moov Dashboard so you know exactly where your funds are at all times.
• We made it easier to find and fix capability errors so you know exactly what needs to be fixed before a transfer can be processed.
• After creating a new account or payment method in the Dashboard, you’ll see sample code snippets that give context on how you can perform those same actions more efficiently using our API.

Transfers

• We have introduced the X-Wait-For header for use when making a transfer. When you make a transfer today you get an immediate response containing only the transferID to indicate the transfer instructions have been received. With the new X-Wait-For header, you can pass a value of rail-response to tell the service that you want the full transfer payload back after the request has gone out to the payment rail and back. This is useful for handling client-side errors and retries for card transactions that communicate with the card networks in real time.

Test mode

Things don’t always go according to plan—we’ve added a new test card in test mode to help you simulate what happens when a card payment is declined.

Dashboard

• We streamlined our onboarding process to help prospects start learning what Moov can do for them as quickly as possible.
• We edited test mode so that there is no need to spend any time adding business data or creating accounts and payment methods before you’ve decided to use Moov. Test mode now pre-populates sample business information so you can focus on exploring the platform.

Transfers

• You can now monetize your transfers with facilitator fees. When you set a facilitator fee on a transfer the amount of the fee will be moved to your Moov wallet.
• Transfer groups can now include wallet-to-bank transfers to end the chain.

Transfer groups

Transfer groups are now available via the Moov API. Transfer groups provide a way to associate multiple transfers together by a shared ID of the parent transfer. Use the transferID of a to-wallet transfer as the source of a transfer to group them. The subsequent transfer will be queued until its parent completes, and you can choose to make it visible to the recipient. Support for transfer groups will be coming soon to the Moov Dashboard.

Bug fixes

• We fixed an issue with Dashboard metrics being incorrectly calculated.
• We have consolidated the Moov Onboarding Drop to further streamline the client experience.

Improvements

• For all new accounts, we will auto-populate your test account data so you can start exploring and learning right away.
• We clarified business requirements in our docs and the Moov Dashboard.
• We updated our SSN requirements to toggle between requiring only the last four of a client’s SSN or requiring their full SSN.

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.

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.