Paymentus

Paymentus (NYSE: PAY) is a Addison, Texas-based cloud billing and payment technology company founded in 2004 that operates one of the largest electronic bill presentment and payment (EBPP) networks in North America. Its Intelligent Payment Platform, Instant Payment Network (IPN), BillWallet, and Profit by Paymentus (AP/AR) products let utilities, government agencies, insurers, telecom, healthcare, higher education, and financial institutions accept and disburse payments across web, mobile, IVR, call center, and agent channels using cards, ACH/eCheck, cash, and digital wallets (PayPal, Venmo, Apple Pay, Google Pay). Its home market is the United States. Paymentus is API-native but its developer surface is access-controlled: the developer portal at developer.paymentus.io is live and public, yet the full API reference, specifications, and testing environment sit behind a request-access / NDA gate. A public Node.js Server SDK (@paymentus/core, @paymentus/auth, @paymentus/xotp) documents the real payment (XOTP) surface, JWT/pre-shared-key authentication, granular OAuth-style scopes, and production base URLs. No downloadable OpenAPI/Swagger specification is published on the public web as of this review.

Paymentus publishes 2 APIs on the APIs.io network. Tagged areas include Payments, United States, Bill Payment, Electronic Bill Presentment, and Payment Processing.

Paymentus’ developer surface includes API reference, engineering blog, support, authentication, and 20 more developer resources.

37.6/100 thin ▬ flat Agent 21/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
2 APIs 1 MCP Servers
PaymentsUnited StatesBill PaymentElectronic Bill PresentmentPayment ProcessingPayment GatewayDisbursementsACHReal-Time PaymentsTokenization

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 37.6/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 9.6 / 20
Commercial Clarity 7.4 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 21/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/paymentus: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

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

Paymentus XOTP API

The XOTP (Paymentus payment) API exposes core Service Commerce operations — make payment (Sale), account inquiry, payment history, void/cancel payment, customer profile create/r...

Paymentus Authentication API

The Authentication API issues short-lived JWT access tokens for the XOTP payment surface. A client signs a request with a pre-shared key (identified by a key id / kid and a thre...

MCP Servers 1

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

paymentus-mcp.yml

MCP SERVER

Security Posture 3

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

Paymentus Authentication

http/oauth2 · 1 scheme

SECURITY

Paymentus Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Paymentus Trust Center

SOC 2, PCI DSS, HIPAA

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Paymentus Scopes

16 scopes

16 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: paymentus
url: https://raw.githubusercontent.com/api-evangelist/paymentus/refs/heads/main/apis.yml
name: Paymentus
kind: company
description: 'Paymentus (NYSE: PAY) is a Addison, Texas-based cloud billing and payment technology company founded in 2004
  that operates one of the largest electronic bill presentment and payment (EBPP) networks in North America. Its Intelligent
  Payment Platform, Instant Payment Network (IPN), BillWallet, and Profit by Paymentus (AP/AR) products let utilities, government
  agencies, insurers, telecom, healthcare, higher education, and financial institutions accept and disburse payments across
  web, mobile, IVR, call center, and agent channels using cards, ACH/eCheck, cash, and digital wallets (PayPal, Venmo, Apple
  Pay, Google Pay). Its home market is the United States. Paymentus is API-native but its developer surface is access-controlled:
  the developer portal at developer.paymentus.io is live and public, yet the full API reference, specifications, and testing
  environment sit behind a request-access / NDA gate. A public Node.js Server SDK (@paymentus/core, @paymentus/auth, @paymentus/xotp)
  documents the real payment (XOTP) surface, JWT/pre-shared-key authentication, granular OAuth-style scopes, and production
  base URLs. No downloadable OpenAPI/Swagger specification is published on the public web as of this review.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- United States
- Bill Payment
- Electronic Bill Presentment
- Payment Processing
- Payment Gateway
- Disbursements
- ACH
- Real-Time Payments
- Tokenization
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.19'
apis:
- aid: paymentus:paymentus-xotp-api
  name: Paymentus XOTP API
  description: The XOTP (Paymentus payment) API exposes core Service Commerce operations — make payment (Sale), account inquiry,
    payment history, void/cancel payment, customer profile create/read/update/delete and list, wallet/payment-method tokenization,
    linked accounts, and AutoPay management. Requests carry a Bearer JWT and are scoped with granular XOTP scopes. Documented
    publicly via the @paymentus/xotp Node.js SDK and the developer portal reference tables; the full interactive reference
    requires portal access.
  humanURL: https://developer.paymentus.io/docs/Reference
  baseURL: https://api.paymentus.com
  tags:
  - Payments
  - Bill Payment
  - Tokenization
  - AutoPay
  - Disbursements
  properties:
  - type: Documentation
    url: https://developer.paymentus.io/
  - type: APIReference
    url: https://developer.paymentus.io/docs/Reference
  - type: SDK
    url: https://www.npmjs.com/package/@paymentus/xotp
- aid: paymentus:paymentus-authentication-api
  name: Paymentus Authentication API
  description: The Authentication API issues short-lived JWT access tokens for the XOTP payment surface. A client signs a
    request with a pre-shared key (identified by a key id / kid and a three-letter application acronym / tla), declares the
    granular scopes it needs (for example xotp, xotp:profile, xotp:payment, xotp:autopay, xotp:accounts) or a pixel that maps
    to those scopes, and receives a Bearer token used on subsequent XOTP calls. Documented publicly via the @paymentus/auth
    Node.js SDK.
  humanURL: https://developer.paymentus.io/
  baseURL: https://api.paymentus.com
  tags:
  - Authentication
  - JWT
  - Scopes
  properties:
  - type: Documentation
    url: https://developer.paymentus.io/
  - type: SDK
    url: https://www.npmjs.com/package/@paymentus/auth
common:
- type: TrustCenter
  url: security/paymentus-trust-center.yml
- type: DomainSecurity
  url: security/paymentus-domain-security.yml
- type: Website
  url: https://www.paymentus.com/
- type: DeveloperPortal
  url: https://developer.paymentus.io/
- type: APIReference
  url: https://developer.paymentus.io/docs/Reference
- type: StatusPage
  url: https://status.paymentus.com/
- type: GitHubOrganization
  url: https://github.com/paymentus
- type: LinkedIn
  url: https://www.linkedin.com/company/paymentus/
- type: TermsOfService
  url: https://www.paymentus.com/customer-terms-privacy/website-condition-of-use/
- type: PrivacyPolicy
  url: https://www.paymentus.com/customer-terms-privacy/website-privacy-notice-united-states/
- type: InvestorRelations
  url: https://ir.paymentus.com/
- type: Blog
  url: https://www.paymentus.com/industry-insights/
- type: Support
  url: https://www.paymentus.com/contact/?form=pay
- type: Packages
  url: packages/paymentus-packages.yml
- type: SDKs
  url: packages/paymentus-packages.yml
- type: Authentication
  url: authentication/paymentus-authentication.yml
- type: OAuthScopes
  url: scopes/paymentus-scopes.yml
- type: Conventions
  url: conventions/paymentus-conventions.yml
- type: MCPServer
  url: mcp/paymentus-mcp.yml
- type: Conformance
  url: conformance/paymentus-conformance.yml
- type: Compliance
  url: https://trust.paymentus.com/
- type: Lifecycle
  url: lifecycle/paymentus-lifecycle.yml
- type: DataModel
  url: data-model/paymentus-data-model.yml
- type: LLMsTxt
  url: llms/paymentus-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com