Ask Moov Beta
Generative AI is experimental and can make mistakes.
Guides Use cases API Changelog
  1. Overview
  2. Get started

Integration & onboarding

Explore integration and onboarding options depending on your use case and money movement workflow.

You can tailor the components of your integration to your particular needs. For example, you may use a Moov Drop for one portion of your workflow and connect directly to the API for another portion of your workflow.

There are a variety of both technical and business-related factors that may influence how you choose to integrate, including:

  • The structure of your integration with your previous provider
  • The level of customization your integration requires to maintain the look and feel of your user flow
  • The nature of transfers on your platform (e.g., repeat versus one time customers, what payment rails your customers tend to use)
  • How your business handles reporting and billing based on payment data
  • Whether or not your business is equipped to handle sensitive data

For specific guidance on setting up an integration that fits your business, contact our sales team.

Note that our authentication protocol is different depending on how you are integrating. We require API keys for server side integrations, while client-side integrations like Moov.js and Moov Drops use OAuth2 access tokens.

Moov.js

If you choose not to use Moov’s hosted onboarding process for merchant accounts, note that Moov.js is required to use our terms of service Drop.
PCI compliance Customization Development scope
Not required Low to medium Employ a frontend library with the option to use pre-built UI Drop components.

View the Moov.js documentation.

Drops

PCI compliance Customization Development scope
Not required Low Pre-built, but customizable, UI components. Requires Moov.js.

View the Drops documentation.

API

PCI compliance Customization Development scope
Required High Write integration code from scratch, or use our Go or Node SDKs.

View the API reference.

Go SDK

PCI compliance Customization Development scope
Required Medium to high Server-side environment for the Moov API.

View the Go SDK documentation.

Node SDK

PCI compliance Customization Development scope
Required Medium to high Server-side environment for the Moov API.

View the Node SDK documentation.

Onboard merchant options

While there are multiple options to onboard merchant accounts, we suggest you send merchants a secure link to create their account through Moov’s hosted onboarding process. You select the capabilities, pre-fill existing data, choose a pricing plan, and send them a link to finish the application and agree to the terms. See our accounts documentation for more details on business and individual requirements.

To onboard merchants outside of our hosted onboarding process, you must use the terms of service Drop to collect terms of service acceptance for accounts. To use the terms of service Drop, you will need to install Moov.js. View the create accounts POST endpoint for more information on creating accounts through our API.

Method Requirements Customization
Hosted onboarding A Moov account Low
Moov Drops A Moov account, Moov.js, terms of service Drop Low to medium
API A Moov account, Moov.js, terms of service Drop High
Summary Beta