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 Payments, Electronic Bill Presentment, and Payment Processing.
Paymentus’ developer surface includes API reference, engineering blog, support, authentication, and 20 more developer resources.
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 could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
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/paymentus: 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 →
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...
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.'
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://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- United States
- Bill Payments
- Electronic Bill Presentment
- Payment Processing
- Payment Gateway
- Disbursements
- ACH
- Real-Time Payments
- Tokenization
tags_raw:
- 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.23'
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 Payments
- Tokenization
- AutoPay
- Disbursements
tags_raw:
- 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: X-MCPServerCandidate
url: mcp/paymentus-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: 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
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.
Kin Score
How this is scored →