PayEngine

PayEngine is an embedded-payments and payment-facilitation platform for vertical market SaaS companies, operated by Platform Factory, Inc. It lets a software company offer payments to its own customers without building an acquiring stack: PayEngine handles merchant onboarding and underwriting, PCI-scoped card and bank-account capture through hosted SecureFields and a web-component library, card and ACH processing with 3-D Secure, AVS and Level 2/Level 3 interchange data, network tokenization, Tap to Pay and cloud-connected terminals, hosted payment links, subscriptions, disputes, settlement and payouts. A gateway-orchestration layer routes across multiple processors. The platform is a PCI DSS Level 1 certified Service Provider, listed in Visa's Global Registry under Platform Factory, Inc. Integration is REST plus a signed webhook surface of 37 documented events; the REST reference itself requires a partner login.

PayEngine is listed with 1 API on the APIs.io network. Tagged areas include Payments, Embedded Payments, Payment Facilitation, Merchant Onboarding, and Payment Gateway.

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

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

🌐 Visit website 📡 Profile data on GitHub

45.3/100 developing ▬ flat Agent 25/100 agent aware Front door AI 1/6 silent Heartbeat 12/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

1 API

Payments Embedded Payments Payment Facilitation Merchant Onboarding Payment Gateway Financial Services ACH Tokenization Webhook Fintech Company

Kin Score

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

Composite quality — 45.3/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 10.9 / 17

Access Clarity 6.7 / 17

Operational Transparency 4.1 / 11

Contract Governance 0.0 / 10

Discoverability 6.2 / 9

Regulatory Posture 5.6 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 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 0 / 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 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/.

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/payengine/"><img src="https://apis.io/badge/payengine/card.svg" alt="PayEngine 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 39.5 — up to +12.1 composite points
Contract Governance scores 0.0 — up to +12.0 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/payengine/apis.yml: open an issue on github.com/api-evangelist/payengine 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 →

Standards implemented 1

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

APIs 1

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

PayEngine Platform API

REST API for merchant onboarding, card and ACH transaction processing (auth, sale, capture, void, refund, offline and device sale), card and bank-account tokenization, gateway o...

PayEngine API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Payengine Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Payengine Rate Limits

0 limits

RATE LIMITS

FinOps 1

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

Payengine Finops

FINOPS

Event Specifications 1

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

Payengine Webhooks

ASYNCAPI

Security Posture 3

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

Payengine Authentication

4 schemes

SECURITY

Payengine Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Payengine Vulnerability Disclosure

Hackerone · contact published

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

ErrorCatalog

Lifecycle

Components

DataModel

Webhooks

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

DeclineCodes

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Compliance

Compliance

Authentication

Authentication

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: payengine
name: PayEngine
description: 'PayEngine is an embedded-payments and payment-facilitation platform for vertical market SaaS companies, operated
  by Platform Factory, Inc. It lets a software company offer payments to its own customers without building an acquiring stack:
  PayEngine handles merchant onboarding and underwriting, PCI-scoped card and bank-account capture through hosted SecureFields
  and a <pay-engine> web-component library, card and ACH processing with 3-D Secure, AVS and Level 2/Level 3 interchange data,
  network tokenization, Tap to Pay and cloud-connected terminals, hosted payment links, subscriptions, disputes, settlement
  and payouts. A gateway-orchestration layer routes across multiple processors. The platform is a PCI DSS Level 1 certified
  Service Provider, listed in Visa''s Global Registry under Platform Factory, Inc. Integration is REST plus a signed webhook
  surface of 37 documented events; the REST reference itself requires a partner login.'
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
  probe_state: covered
  source:
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://cdn.prod.website-files.com/64cc25b62ffdab8b077809ed/64f2c783505aa955d658014b_payengine-opengrpah.jpg
url: https://raw.githubusercontent.com/api-evangelist/payengine/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 18
  pass: local-v1
x-coverage:
  state: covered
  detail: Public developer docs, llms.txt, webhook catalog, AVS code table, PCI evidence, packages and status page were all
    readable and captured. The one wall hit was the REST API reference itself, which is behind a partner login at docs-api.payengine.co
    - so no OpenAPI, no operationIds, no test-card table and no per-operation error catalog could be read, and skills/, overlays/
    and scopes/ are correspondingly absent.
  evidence:
  - url: https://docs.payengine.co/developer-docs
    status: 200
  - url: https://docs.payengine.co/llms.txt
    status: 200
  - url: https://docs-api.payengine.co/openapi.json
    status: 200
  - url: https://api.payengine.co/openapi.json
    status: 400
  checked: '2026-08-26'
tags:
- Payments
- Embedded Payments
- Payment Facilitation
- Merchant Onboarding
- Payment Gateway
- Financial Services
- ACH
- Tokenization
- Webhook
- Fintech
- Company
tags_raw:
- Payments
- Embedded Payments
- Payment Facilitation
- Merchant Onboarding
- Payment Gateway
- Financial Services
- ACH
- Tokenization
- Webhooks
- Fintech
- Company
- Financial-Services
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: PayEngine Platform API
  description: REST API for merchant onboarding, card and ACH transaction processing (auth, sale, capture, void, refund, offline
    and device sale), card and bank-account tokenization, gateway orchestration, hosted payment links, subscriptions, disputes
    and reporting. Authenticated server-to-server with an HTTP Basic partner private key; embedded UI is authorized with a
    short-lived merchant session token. The full reference is gated behind a partner login.
  humanURL: https://docs.payengine.co/developer-docs
  baseURL: https://api.payengine.co
  tags:
  - Payments
  - Merchant Onboarding
  - Transaction
  tags_raw:
  - Payments
  - Merchant Onboarding
  - Transactions
  properties:
  - type: Documentation
    url: https://docs.payengine.co/developer-docs
  - type: APIReference
    url: https://docs-api.payengine.co/
  - type: GettingStarted
    url: https://docs.payengine.co/developer-docs/getting-started-1/getting-started
  - type: Authentication
    url: authentication/payengine-authentication.yml
  - type: Conventions
    url: conventions/payengine-conventions.yml
  - type: ErrorCatalog
    url: errors/payengine-problem-types.yml
  - type: DeclineCodes
    url: errors/payengine-decline-codes.yml
  - type: DataModel
    url: data-model/payengine-data-model.yml
  - type: Webhooks
    url: asyncapi/payengine-webhooks.yml
  - type: RateLimits
    url: rate-limits/payengine-rate-limits.yml
common:
- type: DomainSecurity
  url: security/payengine-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/payengine-vulnerability-disclosure.yml
- type: Website
  url: https://www.payengine.co/
- type: DeveloperPortal
  url: https://docs.payengine.co/developer-docs
- type: Documentation
  url: https://docs.payengine.co/developer-docs
- type: APIReference
  url: https://docs-api.payengine.co/
- type: GettingStarted
  url: https://docs.payengine.co/developer-docs/getting-started-1/getting-started
- type: Support
  url: https://www.payengine.co/contact-us
- type: Blog
  url: https://www.payengine.co/blog
- type: GitHubOrganization
  url: https://github.com/payengine
- type: Pricing
  url: https://www.payengine.co/pricing
- type: SignUp
  url: https://console.payengine.co/signin
- type: TermsOfService
  url: https://www.payengine.co/terms-of-service
- type: PrivacyPolicy
  url: https://www.payengine.co/privacy-policy
- type: StatusPage
  url: https://status.payengine.co/
- type: Security
  url: https://www.payengine.co/security
- type: Compliance
  url: conformance/payengine-conformance.yml
- type: Conformance
  url: conformance/payengine-conformance.yml
- type: Packages
  url: packages/payengine-packages.yml
- type: SDKs
  url: packages/payengine-packages.yml
- type: LLMsTxt
  url: llms/payengine-llms.txt
- type: Authentication
  url: authentication/payengine-authentication.yml
- type: Conventions
  url: conventions/payengine-conventions.yml
- type: ErrorCatalog
  url: errors/payengine-problem-types.yml
- type: DeclineCodes
  url: errors/payengine-decline-codes.yml
- type: Lifecycle
  url: lifecycle/payengine-lifecycle.yml
- type: Sandbox
  url: sandbox/payengine-sandbox.yml
- type: Components
  url: components/payengine-components.yml
- type: DataModel
  url: data-model/payengine-data-model.yml
- type: Webhooks
  url: asyncapi/payengine-webhooks.yml
- type: Plans
  url: plans/payengine-plans-pricing.yml
- type: RateLimits
  url: rate-limits/payengine-rate-limits.yml

PayEngine API — frequently asked questions

Does PayEngine have an API?

Yes. APIs.io lists 1 API from PayEngine, including PayEngine Platform API.

How do I authenticate with the PayEngine API?

PayEngine uses bearer-token authentication (4 schemes). The details are profiled on APIs.io as Payengine Authentication.

Is the PayEngine API ready for AI agents?

PayEngine has a Kin Score of 45.3 out of 100 (developing) and an Agent Readiness score of 25.2 (agent-aware), 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/payengine"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/payengine/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.