QFPay

QFPay provides payment solutions including credit card and QR code payments, enabling businesses to accept online payments quickly, securely, and efficiently. The company positions itself as a best‑in‑class payment partner helping merchants thrive in the cashless era, with services spanning pay‑in, pay‑out, financing, and developer tools.

QFPay is listed with 1 API on the APIs.io network. Tagged areas include Company, Payment, FinTech, API, and Payments.

QFPay’s developer surface includes engineering blog and 8 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

9.5/100 minimal Agent 7/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 API

CompanyPaymentFinTechAPIPayments

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 9.5/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 0.4 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 5.0 / 9

Regulatory Posture 1.9 / 15

Agent readiness — 7/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 0 / 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

A2A Agent Card 8 / 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

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/qfpay/"><img src="https://apis.io/badge/qfpay/card.svg" alt="QFPay 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

11 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 2.4 — up to +19.5 composite points
Access Clarity scores 21.1 — up to +15.8 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/qfpay/apis.yml: open an issue on github.com/api-evangelist/qfpay 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 →

APIs 1

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

QFPay Developer Centre

Developer portal providing OpenAPI documentation and integration guides for QFPay payment solutions.

Security Posture 1

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

Qfpay Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Newsroom

Newsroom

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

AgentCard

AgentCard

Hosts

Hosts

Source (apis.yml)

aid: qfpay
name: QFPay
image: https://qfpay.global/wp-content/uploads/2023/11/talking-cashier-2.png
description: QFPay provides payment solutions including credit card and QR code payments, enabling businesses to accept online
  payments quickly, securely, and efficiently. The company positions itself as a best‑in‑class payment partner helping merchants
  thrive in the cashless era, with services spanning pay‑in, pay‑out, financing, and developer tools.
url: https://raw.githubusercontent.com/api-evangelist/qfpay/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-27 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-27'
modified: '2026-10-27'
tags:
- Company
- Payment
- FinTech
- API
- Payments
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: LLMsTxt
  url: llms/qfpay-llms.txt
- type: AgentCard
  url: a2a/qfpay-a2a.yml
- type: Hosts
  url: hosts/qfpay-hosts.yml
- type: TermsOfService
  url: https://qfpay.global/terms-and-conditions/
- type: PrivacyPolicy
  url: https://qfpay.global/documents/privacy-policy/
- type: Newsroom
  url: https://qfpay.global/news/
- type: Blog
  url: https://qfpay.global/blog/
- type: DomainSecurity
  url: security/qfpay-domain-security.yml
- type: Website
  url: https://qfpay.global/
apis:
- name: QFPay Developer Centre
  description: Developer portal providing OpenAPI documentation and integration guides for QFPay payment solutions.
  humanURL: https://sdk.qfapi.com/
  baseURL: null
  aid: qfpay:qfpay-developer-centre
x-submission-probe: 200 2026-10-26
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: Developer portal provides an OpenAPI file but it describes a sample plant store, not QFPay's API.
  evidence:
  - url: https://sdk.qfapi.com/openapi.json
    status: 200
  checked: '2026-10-27'
x-enrichment:
  date: '2026-10-27'
  status: enriched
  artifacts_added: 11
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

QFPay API — frequently asked questions

Does QFPay have an API?

Yes. APIs.io lists 1 API from QFPay, including QFPay Developer Centre.

Is the QFPay API ready for AI agents?

QFPay has a Kin Score of 9.5 out of 100 (minimal) and an Agent Readiness score of 6.6 (agent-aware), scored by API Evangelist on 2026-10-31.

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

All providers

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

Every operation they expose

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

How their score was established

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

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.

GitHub Google LinkedIn

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