PayStand

Paystand is a blockchain-enabled B2B payments and receivables automation platform that lets businesses send, receive, and reconcile payments with zero-fee bank-to-bank (ACH/EFT) transfers, card acceptance, and a Bitcoin-anchored "Assurety" certified audit trail. The Paystand Developer API (v3) exposes payments, refunds, disputes, payers, customer banks, accounts and balances, scheduled payments, transfers, withdrawals (including auto-withdrawal settings), a Checkout / Billing Portal embed surface, an Events resource, and the Assurety blockchain notarization APIs (assurors, chains, contracts, records, schemas, wallets). It integrates with major ERPs and e-commerce platforms (Magento, WooCommerce, BigCommerce) and is used to automate accounts receivable and payable for mid-market and enterprise finance teams.

PayStand publishes 9 API contracts indexed on the APIs.io network, including Balances API, Banks API, OAuth API, and 6 more. Tagged areas include Company, Payments, B2B Payments, Accounts Receivable, and Accounts Payable.

The PayStand catalog on APIs.io includes 1 Spectral governance ruleset.

PayStand’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

50.1/100 developing ▬ flat Agent 39/100 agent ready Front door AI 5/6 prominent Heartbeat 96/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

2 published contracts

Company Payments B2B Payments Accounts Receivable Accounts Payable Fintech Blockchain ACH Billing Checkout

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 50.1/100 · developing

Contract Quality 9.8 / 19

Developer Ergonomics 9.3 / 15

Access Clarity 7.3 / 15

Operational Transparency 1.8 / 10

Contract Governance 2.9 / 9

Discoverability 5.6 / 8

Regulatory Posture 5.0 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 39/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/paystand/"><img src="https://apis.io/badge/paystand/card.svg" alt="PayStand on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 52.0 — up to +12.0 composite points
Operational Transparency scores 18.4 — up to +10.6 composite points
Access Clarity scores 48.7 — up to +10.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/paystand/apis.yml: open an issue on github.com/api-evangelist/paystand to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	19.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

NACHA

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 9

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

Paystand Developer API

Paystand v3 REST API for B2B payments: create and manage payments, refunds, disputes, payers, customer banks, accounts, balances, scheduled payments, transfers and withdrawals, ...

PayStand Balances API

The Balances API from PayStand — 2 operation(s) for balances.

PayStand Banks API

The Banks API from PayStand — 1 operation(s) for banks.

PayStand OAuth API

The Oauth API from PayStand — 1 operation(s) for oauth.

PayStand Payers API

The Payers API from PayStand — 1 operation(s) for payers.

PayStand Payments API

The Payments API from PayStand — 2 operation(s) for payments.

PayStand Refunds API

The Refunds API from PayStand — 1 operation(s) for refunds.

PayStand Transfers API

The Transfers API from PayStand — 1 operation(s) for transfers.

PayStand Withdrawals API

The Withdrawals API from PayStand — 3 operation(s) for withdrawals.

Scroll for all 9

PayStand API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Paystand Plans Pricing

0 plans

PLANS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Paystand Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

PayStand API Rules

12 rules · 10 errors 1 warnings 1 info

SPECTRAL

Security Posture 2

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

Paystand Authentication

oauth2/apiKey/http · 4 schemes

SECURITY

Paystand Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Paystand Scopes

1 scope · clientCredentials/authorizationCode

1 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Paystand Agentic Access

12 operations · 7 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

Components

Components

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

TrustCenter

TrustCenter

Operate 3

Status, limits, changes, and where to get help

Deprecation

Deprecation

Support

Support

StatusPage

StatusPage

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 4

The organization behind the API

Newsroom

BlogRSS

Website

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: paystand
name: PayStand
description: Paystand is a blockchain-enabled B2B payments and receivables automation platform that lets businesses send,
  receive, and reconcile payments with zero-fee bank-to-bank (ACH/EFT) transfers, card acceptance, and a Bitcoin-anchored
  "Assurety" certified audit trail. The Paystand Developer API (v3) exposes payments, refunds, disputes, payers, customer
  banks, accounts and balances, scheduled payments, transfers, withdrawals (including auto-withdrawal settings), a Checkout
  / Billing Portal embed surface, an Events resource, and the Assurety blockchain notarization APIs (assurors, chains, contracts,
  records, schemas, wallets). It integrates with major ERPs and e-commerce platforms (Magento, WooCommerce, BigCommerce) and
  is used to automate accounts receivable and payable for mid-market and enterprise finance teams.
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: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://www.paystand.com/hubfs/paystand-logo.png
url: https://raw.githubusercontent.com/api-evangelist/paystand/refs/heads/main/apis.yml
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 16
  pass: local-v1
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Payments
- B2B Payments
- Accounts Receivable
- Accounts Payable
- Fintech
- Blockchain
- ACH
- Billing
- Checkout
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/paystand-plans-pricing.yml
- type: AgenticAccess
  url: agentic-access/paystand-agentic-access.yml
- type: Spectral
  url: rules/paystand-rules.yml
- type: Deprecation
  url: lifecycle/paystand-lifecycle.yml
- type: Hosts
  url: hosts/paystand-hosts.yml
- type: Vendors
  url: vendors/paystand-vendors.yml
- type: Newsroom
  url: https://www.paystand.com/press
- url: https://www.paystand.com/blog/rss.xml
  type: BlogRSS
- type: DomainSecurity
  url: security/paystand-domain-security.yml
- type: Website
  url: https://www.paystand.com
- type: DeveloperPortal
  url: https://developers.paystand.com
- type: Documentation
  url: https://developers.paystand.com/docs/introduction
- type: APIReference
  url: https://developers.paystand.com/reference
- type: GettingStarted
  url: https://developers.paystand.com/reference/getting-started
- type: Support
  url: https://support.paystand.com/hc/en-us
- type: Blog
  url: https://www.paystand.com/blog
- type: GitHubOrganization
  url: https://github.com/paystand
- type: Pricing
  url: https://www.paystand.com/pricing
- type: SignUp
  url: https://dashboard.paystand.com/v2/signin
- type: TermsOfService
  url: https://www.paystand.com/terms-of-service
- type: PrivacyPolicy
  url: https://privacy.cptn.co/privacy-policy/9e569c48-09ec-4470-9690-5f41a96372a6
- type: StatusPage
  url: https://status.paystand.com
- type: TrustCenter
  url: https://trust.paystand.com
- type: LLMsTxt
  url: llms/paystand-llms.txt
- type: WellKnown
  url: well-known/paystand-well-known.yml
- type: Packages
  url: packages/paystand-packages.yml
- type: SDKs
  url: packages/paystand-packages.yml
- type: Components
  url: components/paystand-components.yml
apis:
- name: Paystand Developer API
  description: 'Paystand v3 REST API for B2B payments: create and manage payments, refunds, disputes, payers, customer banks,
    accounts, balances, scheduled payments, transfers and withdrawals, plus the Assurety blockchain notarization surface and
    Checkout / Billing Portal embed.'
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Payments
  - B2B Payments
  - ACH
  - Blockchain
  properties:
  - type: Authentication
    url: authentication/paystand-authentication.yml
  - type: OAuthScopes
    url: scopes/paystand-scopes.yml
  - type: ErrorCatalog
    url: errors/paystand-problem-types.yml
  - type: DeclineCodes
    url: errors/paystand-decline-codes.yml
  - type: Conventions
    url: conventions/paystand-conventions.yml
  - type: DataModel
    url: data-model/paystand-data-model.yml
  - type: Sandbox
    url: sandbox/paystand-sandbox.yml
  - type: X-MCPServerCandidate
    url: mcp/paystand-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: Lifecycle
    url: lifecycle/paystand-lifecycle.yml
  - type: Conformance
    url: conformance/paystand-conformance.yml
  aid: paystand:paystand-developer-api
- aid: paystand:paystand-balances-api
  name: PayStand Balances API
  description: The Balances API from PayStand — 2 operation(s) for balances.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Balances
  properties:
  - type: OpenAPI
    url: openapi/paystand-balances-api-openapi.yml
- aid: paystand:paystand-banks-api
  name: PayStand Banks API
  description: The Banks API from PayStand — 1 operation(s) for banks.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Banks
  properties:
  - type: OpenAPI
    url: openapi/paystand-banks-api-openapi.yml
- aid: paystand:paystand-oauth-api
  name: PayStand OAuth API
  description: The Oauth API from PayStand — 1 operation(s) for oauth.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - OAuth
  - Authentication
  tags_raw:
  - Oauth
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/paystand-oauth-api-openapi.yml
- aid: paystand:paystand-payers-api
  name: PayStand Payers API
  description: The Payers API from PayStand — 1 operation(s) for payers.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Payers
  properties:
  - type: OpenAPI
    url: openapi/paystand-payers-api-openapi.yml
- aid: paystand:paystand-payments-api
  name: PayStand Payments API
  description: The Payments API from PayStand — 2 operation(s) for payments.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/paystand-payments-api-openapi.yml
- aid: paystand:paystand-refunds-api
  name: PayStand Refunds API
  description: The Refunds API from PayStand — 1 operation(s) for refunds.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Refunds
  properties:
  - type: OpenAPI
    url: openapi/paystand-refunds-api-openapi.yml
- aid: paystand:paystand-transfers-api
  name: PayStand Transfers API
  description: The Transfers API from PayStand — 1 operation(s) for transfers.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Transfers
  properties:
  - type: OpenAPI
    url: openapi/paystand-transfers-api-openapi.yml
- aid: paystand:paystand-withdrawals-api
  name: PayStand Withdrawals API
  description: The Withdrawals API from PayStand — 3 operation(s) for withdrawals.
  humanURL: https://developers.paystand.com/reference
  baseURL: https://api.paystand.com/v3
  tags:
  - Withdrawals
  properties:
  - type: OpenAPI
    url: openapi/paystand-withdrawals-api-openapi.yml
x-readme-harvest:
  date: '2026-10-14'
  ops: 12
  tool: harvest-readme-openapi.py
  portal: https://developers.paystand.com

PayStand API — frequently asked questions

Does PayStand have an API?

Yes. APIs.io lists 9 APIs from PayStand, including Paystand Developer API, PayStand Balances API and PayStand Banks API, and 6 more.

Is there an OpenAPI specification for the PayStand API?

Yes. APIs.io indexes 8 OpenAPI specifications for PayStand, each linked for download from this page.

How do I authenticate with the PayStand API?

PayStand documents its authentication (oauth2/apiKey/http · 4 schemes). The details are profiled on APIs.io as Paystand Authentication.

Is the PayStand API ready for AI agents?

PayStand has a Kin Score of 50.1 out of 100 (developing) and an Agent Readiness score of 38.7 (agent-ready), scored by API Evangelist on 2026-11-06.

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/paystand"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/paystand/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/paystand/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.