FedNow Service · Authentication Profile

Fednow Authentication

Authentication

FedNow Service secures its APIs with mutualTLS and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.

PaymentsUnited StatesReal-Time PaymentsInstant PaymentsISO 20022Account-to-AccountScheme OperatorFederal Reserve

Methods: mutualTLS, apiKey Schemes: 3 OAuth flows: API key in: header

Security Schemes

ClientCertificate mutualTLS

ClientID apiKey

· in: header ()

FedLineSecurityToken mfa

Source

Authentication Profile

generated: '2026-07-24'
method: searched
source: https://www.frbservices.org/fedline-solutions/fedline-developer/fednow-apis
docs: https://www.frbservices.org/fedline-solutions/fedline-developer
summary:
  types: [mutualTLS, apiKey]
  api_key_in: [header]
  oauth2_flows: []
  gated: true
  audience: enrolled financial institutions (FedNow / FedLine participants)
schemes:
- name: ClientCertificate
  type: mutualTLS
  description: >-
    Each FedNow / FRFS API call presents a client PKI certificate. A separate
    certificate is required per environment (Test and Production); the same
    certificate may be reused across multiple APIs or a unique certificate may be
    requested per API. Certificates are provisioned through the credential-gated
    FedLine Developer platform.
- name: ClientID
  type: apiKey
  in: header
  description: >-
    A Client ID accompanies the certificate to identify the calling institution
    and its API entitlements.
- name: FedLineSecurityToken
  type: mfa
  description: >-
    FedLine multi-factor authentication security tokens gate access to the FedLine
    Developer platform where API credentials (Client ID + certificate) are managed.
    This layers institution-level MFA on top of the per-request certificate auth.
notes: >-
  FedNow is not a self-serve public API. Authentication is layered: FedLine MFA
  security tokens to reach the developer platform, then Client ID + a
  per-environment PKI client certificate on each API request. No OAuth2/OpenID
  Connect flow and no public API key self-service are published; onboarding is
  restricted to enrolled U.S. financial institutions.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/fednow-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.