HiPay
HiPay is a European omnichannel payment platform headquartered in Levallois-Perret, France, offering REST APIs for online payments, in-store terminal management, fraud prevention, 3DS authentication, tokenization, marketplace payments, and payment reporting. Founded in 2011, HiPay is listed on Euronext Growth Paris and processes over €7.5 billion in transactions annually across five European countries.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles HiPay the way a machine reads it — 47 machine-readable artifacts across 9 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 — HiPay scores 36.1/100 (thin), with a separate agent-readiness read of 32/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from HiPay'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/hipay/"
title="HiPay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hipay.svg"
alt="HiPay Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/hipay/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hipay/"
title="HiPay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hipay/card.svg"
alt="HiPay 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 HiPay
Each block below is one kind of artifact we hold for HiPay. 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 20
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.
HiPay balance API
Manage the balance of a HiPay account
HiPay bank-info API
Manage bank informations of a HiPay account
HiPay captcha-generation API
Generate captcha
HiPay Connector API
The Connector API from HiPay — 1 operation(s) for connector.
HiPay constants API
Manage your account with our API tools
HiPay identification API
Manage your identification documents
HiPay invoice API
Manage marketplace invoices
HiPay maintenance API
Perform operations (capture, refund) on transactions
HiPay merchant-group API
Manage merchant groups
HiPay Order API
The Order API from HiPay — 2 operation(s) for order.
HiPay payments API
Everything you need to create orders and transactions
HiPay Routing API
The Routing API from HiPay — 1 operation(s) for routing.
HiPay Sessions API
The Sessions API from HiPay — 1 operation(s) for sessions.
HiPay settlement API
Everything you need to get all settlement details
HiPay tokenization API
Everything you need to tokenize payment cards
HiPay Transaction API
The Transaction API from HiPay — 6 operation(s) for transaction.
HiPay transfer API
Transfer funds between HiPay accounts
HiPay ubo API
Manage your Ultimate Beneficial Ownerships (UBO)
HiPay user-account API
Manage your HiPay account
HiPay withdrawal API
Request a withdrawal from a HiPay account
Scroll within the panel for all 20 ·
Open Collections 21
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONHipay Payment Gateway balance API
OPEN COLLECTIONHipay Payment Gateway balance bank-info API
OPEN COLLECTIONHipay Payment Gateway balance captcha-generation API
OPEN COLLECTIONHipay Payment Gateway balance Connector API
OPEN COLLECTIONHipay Payment Gateway balance constants API
OPEN COLLECTIONHipay Payment Gateway balance identification API
OPEN COLLECTIONHipay Payment Gateway balance invoice API
OPEN COLLECTIONHipay Payment Gateway balance maintenance API
OPEN COLLECTIONHipay Payment Gateway balance merchant-group API
OPEN COLLECTIONHipay Payment Gateway balance Order API
OPEN COLLECTIONHipay Payment Gateway balance payments API
OPEN COLLECTIONHipay Payment Gateway balance Routing API
OPEN COLLECTIONHipay Payment Gateway balance Sessions API
OPEN COLLECTIONHipay Payment Gateway balance settlement API
OPEN COLLECTIONHipay Payment Gateway balance tokenization API
OPEN COLLECTIONHipay Payment Gateway balance Transaction API
OPEN COLLECTIONHipay Payment Gateway balance transfer API
OPEN COLLECTIONHipay Payment Gateway balance ubo API
OPEN COLLECTIONHipay Payment Gateway balance user-account API
OPEN COLLECTIONHipay Payment Gateway balance withdrawal API
OPEN COLLECTIONScroll within the panel for all 21 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Finops
FINOPSSecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for HiPay — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hipay · machine-readable index on apis.io
This is an independent, third-party profile of HiPay, 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.