Mesh Payments website screenshot

Mesh Payments

Mesh Payments is a global travel and expense (T&E) and spend management platform for finance teams, combining corporate virtual and physical card issuing, expense management, accounts payable, procurement (ProcurePay), travel booking and accounting automation in a single system. Mesh exposes a RESTful API on api.meshpayments.com for virtual card lifecycle management, merchant and category controls, metadata tagging, authorization and settlement retrieval and real-time balance queries, authenticated with either HMAC-SHA256 request signing or OAuth 2.0 client credentials. It also publishes an OAuth-protected Model Context Protocol (MCP) server at api.meshpayments.com/mcp and a configurable webhooks surface, plus ERP, HRIS and TMC integrations.

Mesh Payments publishes 2 APIs on the APIs.io network. Tagged areas include Company, Payments, Spend Management, Expense Management, and Corporate Cards.

The Mesh Payments catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Mesh Payments’ developer surface includes documentation, support, engineering blog, pricing, signup flow, changelog, authentication, and 22 more developer resources.

51.5/100 developing ▬ flat Agent 39/100 agent ready saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0
AccessSelf serve
2 APIs 1 MCP Servers
CompanyPaymentsSpend ManagementExpense ManagementCorporate CardsTravelAccounts PayableFintechCard IssuingAccounting Automation

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/mesh-payments: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Mesh Payments API

RESTful API for the Mesh spend management platform. Documented capabilities include connectivity verification, virtual card lifecycle management (issuance, suspension, cancellat...

Mesh Payments MCP Server

OAuth-protected Model Context Protocol (MCP) server operated by Mesh at api.meshpayments.com/mcp. The endpoint advertises RFC 9728 OAuth 2.0 Protected Resource Metadata at /.wel...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Mesh Payments Authentication

http/oauth2/custom-hmac · 3 schemes

SECURITY

Mesh Payments Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Mesh Payments Vulnerability Disclosure

security.txt · contact published

SECURITY

Mesh Payments Trust Center

SOC 1 Type II, SOC 2 Type II, PCI DSS, GDPR, CCPA, Vendor Security Alliance (VSA)

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Mesh Payments Scopes

1 scope · authorizationCode/clientCredentials/deviceCode

1 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: mesh-payments
name: Mesh Payments
description: Mesh Payments is a global travel and expense (T&E) and spend management platform for finance teams, combining
  corporate virtual and physical card issuing, expense management, accounts payable, procurement (ProcurePay), travel booking
  and accounting automation in a single system. Mesh exposes a RESTful API on api.meshpayments.com for virtual card lifecycle
  management, merchant and category controls, metadata tagging, authorization and settlement retrieval and real-time balance
  queries, authenticated with either HMAC-SHA256 request signing or OAuth 2.0 client credentials. It also publishes an OAuth-protected
  Model Context Protocol (MCP) server at api.meshpayments.com/mcp and a configurable webhooks surface, plus ERP, HRIS and
  TMC integrations.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  generated: '2026-09-02'
  method: derived
image: https://meshpayments.com/wp-content/uploads/2026/05/meshpayments.png
url: https://raw.githubusercontent.com/api-evangelist/mesh-payments/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Payments
- Spend Management
- Expense Management
- Corporate Cards
- Travel
- Accounts Payable
- Fintech
- Card Issuing
- Accounting Automation
apis:
- name: Mesh Payments API
  description: RESTful API for the Mesh spend management platform. Documented capabilities include connectivity verification,
    virtual card lifecycle management (issuance, suspension, cancellation), merchant and category limitation configuration,
    metadata tagging for tracking, authorization and settlement data retrieval, and real-time account balance access. Authentication
    is HMAC-SHA256 request signing or OAuth 2.0 client credentials. Full endpoint reference and code samples (Python, Node.js,
    Java, C#, PHP) are published on the Mesh Developers Portal, which is served behind HTTP Basic authentication.
  humanURL: https://developers.meshpayments.com
  baseURL: https://api.meshpayments.com
  tags:
  - Payments
  - Corporate Cards
  - Card Issuing
  - Spend Management
  properties:
  - type: Documentation
    url: https://developers.meshpayments.com
  - type: Authentication
    url: authentication/mesh-payments-authentication.yml
  - type: OAuthScopes
    url: scopes/mesh-payments-scopes.yml
  - type: Webhooks
    url: asyncapi/mesh-payments-webhooks.yml
- name: Mesh Payments MCP Server
  description: OAuth-protected Model Context Protocol (MCP) server operated by Mesh at api.meshpayments.com/mcp. The endpoint
    advertises RFC 9728 OAuth 2.0 Protected Resource Metadata at /.well-known/oauth-protected-resource/mcp and challenges
    unauthenticated JSON-RPC calls with a WWW-Authenticate Bearer header. Mesh describes its orchestration layer as MCP-compatible
    so customers can connect their own AI agents and build workflows on top of Mesh policy governance.
  humanURL: https://meshpayments.com/orchestration/
  baseURL: https://api.meshpayments.com/mcp
  tags:
  - MCP
  - Agents
  - Spend Management
  properties:
  - type: MCPServer
    url: mcp/mesh-payments-mcp.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/mesh-payments-domain-security.yml
- type: Website
  url: https://meshpayments.com/
- type: DeveloperPortal
  url: https://developers.meshpayments.com
- type: Documentation
  url: https://kb.meshpayments.com/support/integrators-corner/
- type: Support
  url: https://kb.meshpayments.com/
- type: HelpCenter
  url: https://kb.meshpayments.com/
- type: Blog
  url: https://meshpayments.com/blog/
- type: GitHubOrganization
  url: https://github.com/mesh-payments
- type: Pricing
  url: https://meshpayments.com/pricing/
- type: SignUp
  url: https://app.meshpayments.com/
- type: Login
  url: https://app.meshpayments.com/
- type: TermsOfService
  url: https://meshpayments.com/legal/
- type: PrivacyPolicy
  url: https://meshpayments.com/privacy/
- type: ChangeLog
  url: https://meshpayments.com/feature-updates/
- type: ChangeLog
  url: changelog/mesh-payments-changelog.yml
- type: Integrations
  url: https://meshpayments.com/partners-and-integrations/
- type: WellKnown
  url: well-known/mesh-payments-well-known.yml
- type: LLMsTxt
  url: llms/mesh-payments-llms.txt
- type: MCPServer
  url: mcp/mesh-payments-mcp.yml
- type: Authentication
  url: authentication/mesh-payments-authentication.yml
- type: OAuthScopes
  url: scopes/mesh-payments-scopes.yml
- type: Conventions
  url: conventions/mesh-payments-conventions.yml
- type: Lifecycle
  url: lifecycle/mesh-payments-lifecycle.yml
- type: Conformance
  url: conformance/mesh-payments-conformance.yml
- type: Compliance
  url: https://meshpayments.com/security-is-our-priority/
- type: Security
  url: https://meshpayments.com/vulnerability-disclosure-policy/
- type: VulnerabilityDisclosure
  url: security/mesh-payments-vulnerability-disclosure.yml
- type: TrustCenter
  url: security/mesh-payments-trust-center.yml
- type: Webhooks
  url: asyncapi/mesh-payments-webhooks.yml
- type: Packages
  url: packages/mesh-payments-packages.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 18
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/mesh-payments"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/mesh-payments/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/mesh-payments/evidence"

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

Get an API key

Free tier, no email required.

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