Guides Use cases
SDKs & UIs
Frontend
Drops Pre-built, drop-in UIs for complicated flows Moov.js Client-side SDK for secure data collection All client SDKs Web, iOS, and Android SDKs
Backend
Backend SDKs Server-side libraries for interacting with Moov
Hosted UIs
Hosted onboarding Co-branded onboarding forms Resolution links Secure links for resolving verification issues Payment links Shareable links and QR codes for payments
API Changelog
  • Guides
  • Use cases
  • For developers
  • API reference
  • SDKs
  • Moov.js
  • Moov Drops
  • Developer tools
  • Changelog
<- Full menu

API reference

  • Getting started
  • Rate limits
  • Errors
  • Version reference
  • Authentication
    • Options
    • Access tokens
    • End-to-end encryption
    • Scopes
  • Moov accounts
    • Accounts
    • Billing
    • Capabilities
    • Files
    • Onboarding links
    • Resolution links
    • Partner billing
    • Representatives
    • Underwriting
  • Sources
    • Bank accounts
    • Cards
    • Apple Pay
    • Google Pay
    • Payment methods
    • Terminal applications
    • Wallets
  • Money movement
    • Transfers
    • Sweeps
    • Refunds
    • Disputes
    • Card issuing
    • Invoices
    • Payment links
    • Receipts
    • Scheduling
  • Account tools
    • Image library
    • Product catalog
    • Support tickets
  • Enrichment
    • Branding
    • Form shortening
    • Institutions
  1. API reference

Authentication

View as Markdown

Articles in this section

Options

With a server-side integration, you are responsible for directly handling and storing sensitive user information. With a client-side integration, you can use Moov.js and server-generated access tokens to transmit data from your user directly to Moov.

Access tokens

End-to-end encryption

Scopes

Moov follows the OAuth2 protocol authentication flow. This guide provides the complete list of scopes and guidance for using them.

If you're using Moov.js or any client-side integration, you'll need to set scopes. Scopes specify what actions an account can take. When generating an OAuth2 access token, you'll include the name of the scope that covers the type of access needed. You will then use a generated token for each API call you make.

Was this helpful?

Moov logo
Follow us
Product
Pricing Moov Platform Accept Store Send Spend
Payment links Invoicing New Tap to Pay New Onboarding Dashboard Drops Data Sync All features Roadmap
Developers
Guides Quick start API Moov.js Drops Server-side SDKs Tap to Pay Android SDK Tap to Pay iOS SDK LLMs.txt Changelog Status
Industries
Construction Digital banking Fundraising Loan servicing Small business Transport
Resources
Blog Support center Community Fintech glossary Bug bounty Security portal Prohibited & restricted businesses
Company
Who we are Careers Newsroom Media resources Contact
© Moov Financial, Inc. 2026 All rights reserved
Privacy policy Terms of use Cookies