Corpay (formerly FLEETCOR)
Corpay is a global S&P 500 corporate payments company (NYSE: CPAY) that resulted from the March 2024 rebrand of FLEETCOR Technologies. The company serves more than 800,000 business clients across 200+ countries in 140+ currencies and processed approximately $400 billion in payments in 2024 with reported revenue of about $4.0B. Corpay operates across five product lines built largely through acquisition — Commercial Cards (including Corpay Mastercard), AP Automation (extended by the 2024 acquisition of Paymerang), Cross-Border Payments (built on the 2017 acquisition of Cambridge Global Payments and the 2025 acquisition of Alpha Group International), Fuel & Fleet Cards (the original FLEETCOR business plus the 2014 acquisition of Comdata), and Workforce Lodging & Travel. Despite this scale, Corpay does not operate a public developer portal — there is no developer.corpay.com, no public OpenAPI catalog, no public GitHub presence, and no self-service API key issuance. All integration surfaces (ERP connectors for NetSuite, Sage, Microsoft Dynamics, QuickBooks, Acumatica, CMiC, Deltek, Trimble; the former Cambridge cross-border payments API; AP-automation API hooks) are sales-led and gated behind enterprise contracts.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Corpay (formerly FLEETCOR) the way a machine reads it — 6 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Corpay (formerly FLEETCOR) scores 12.4/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Corpay (formerly FLEETCOR)'s current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fleetcor/"
title="Corpay (formerly FLEETCOR) on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fleetcor.svg"
alt="Corpay (formerly FLEETCOR) Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fleetcor/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fleetcor/"
title="Corpay (formerly FLEETCOR) on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fleetcor/card.svg"
alt="Corpay (formerly FLEETCOR) Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Corpay (formerly FLEETCOR)
Each block below is one kind of artifact we hold for Corpay (formerly FLEETCOR). For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Corpay Commercial Cards
Corpay's commercial card portfolio covers the Corpay Mastercard, Corpay World Elite Mastercard, virtual / ghost cards, and supplier-direct payment cards. Integration with ERP an...
Corpay AP Automation
Corpay's AP automation platform covers invoice capture and approval routing, payments automation across virtual card / ACH / check, purchase order automation with PO-to-invoice ...
Corpay Cross-Border Payments
Corpay Cross-Border (formerly Cambridge Global Payments, acquired in 2017 for $690M, and further expanded by the 2025 $2.2B acquisition of Alpha Group International) processes 4...
Corpay Fuel & Fleet Cards
The original FLEETCOR business line, covering fuel cards, fleet cards, and trucking-focused payments — including the Comdata brand (acquired 2014 for $3.45B) for the over-the-ro...
Corpay Workforce Lodging & Travel
Corpay's lodging and corporate travel offering for workforces with project, crew, and contractor lodging needs — booking, management, and consolidated billing. No public develop...
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Corpay (formerly FLEETCOR) — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fleetcor · machine-readable index on apis.io
This is an independent, third-party profile of Corpay (formerly FLEETCOR), published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.