Home Providers Bancomat
Bancomat
BANCOMAT S.p.A. is Italy's leading payment network operator managing the PagoBancomat debit card scheme, ATM network, and BANCOMAT Pay mobile payment service. Launched in 1983 for ATM withdrawals and expanded in 1986 with PagoBancomat for PIN-based POS payments, the network underpins Italian electronic payment infrastructure. BANCOMAT Pay, introduced in 2019, enables mobile e-commerce and P2P payments linked to bank accounts via phone number and IBAN. Since the 2025-07-22 acquisition of FlowPay S.r.l., a Bank of Italy-authorised payment institution (AISP/PISP), the group also publishes a public open-banking REST API — account information, payment initiation, invoicing, pagoPA notices and webhooks — with OpenAPI contracts on docs.flowpay.it and GitHub.
Bancomat publishes 30 API contracts indexed on the APIs.io network, including Accounts API, AIS Service API, Authentication API, and 27 more. Tagged areas include ATM, Banking, Financial Services, Italy, and Mobile Payments.
The Bancomat catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 2 Spectral governance rulesets.
Bancomat’s developer surface includes engineering blog, support, FAQ, CLI, authentication, and 43 more developer resources.
6 published contracts1 MCP Servers6 Features5 Use Cases
On this page
Kin Score
APIs 30
MCP Servers 1
Pricing Plans 1
Rate Limits 1
FinOps 1
Features 6
Event Specs 1
Vocabularies 1
Spectral Rules 2
Overlays 2
JSON Schema 60
Security Posture 2
Scopes 1
Agentic Access 1
Use Cases 5
Integrations 7
Resources 48
apis.yml
Business capabilities this provider's published APIs can perform, derived from its own
contracts. Browse all capabilities →
40 Operational Transparency
0 Create-or-Update Ergonomics
Composite quality — 57.8/100 · strong
Agent readiness — 44/100 · agent ready
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Market Position Depth Registered MCP server Declares compatibility
Open Banking list
9.0
-
-
Registered MCP server and declares compatibility are report only — not weighted .
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Individual APIs this provider publishes, each with its own machine-readable definition.
Scroll for all 30
Model Context Protocol servers that expose these APIs to AI agents.
Published pricing tiers and plan structures.
Documented rate limits and quota policies.
Cost, billing, and metering signals for API financial operations.
Notable capabilities this provider offers.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral governance rulesets for linting and validating these APIs.
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Standalone JSON Schema definitions for this provider's data models.
Scroll for all 60
Authentication, domain security, vulnerability disclosure, and trust-center signals.
OAuth scopes governing access to this provider's APIs.
Recommended x-agentic-access execution contracts for AI agents.
What developers build with this provider.
Pre-built integrations with other platforms and tools.
Scroll for all 7
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll for all 11
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 6
Properties that don't map to a standard resource type
Source (apis.yml)
aid: bancomat
name: Bancomat
description: BANCOMAT S.p.A. is Italy's leading payment network operator managing the PagoBancomat debit card scheme, ATM
network, and BANCOMAT Pay mobile payment service. Launched in 1983 for ATM withdrawals and expanded in 1986 with PagoBancomat
for PIN-based POS payments, the network underpins Italian electronic payment infrastructure. BANCOMAT Pay, introduced in
2019, enables mobile e-commerce and P2P payments linked to bank accounts via phone number and IBAN. Since the 2025-07-22
acquisition of FlowPay S.r.l., a Bank of Italy-authorised payment institution (AISP/PISP), the group also publishes a public
open-banking REST API — account information, payment initiation, invoicing, pagoPA notices and webhooks — with OpenAPI contracts
on docs.flowpay.it and GitHub.
type: Index
deliveryModel:
model: saas
license_evidence:
not_product:
- flowpay/client-openapi
open_source: unknown
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: low
source:
- openapi
- pricing
- repository-not-product
generated: '2026-09-25'
method: derived
accessModel:
pricing: freemium
onboarding: unknown
trial: false
try_now: false
public: false
label: Freemium
confidence: medium
source:
- plans
generated: '2026-07-22'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/bancomat.png
tags:
- ATM
- Banking
- Financial Services
- Italy
- Mobile Payments
- Payments
- Debit Cards
- Open Banking
- PSD2
- Account Information
- Payment Initiation
- Invoicing
- pagoPA
tags_raw:
- ATM
- Banking
- Financial Services
- Italy
- Mobile Payments
- Payments
- Debit Cards
- Open Banking
- PSD2
- Account Information
- Payment Initiation
- Invoicing
- pagoPA
- Financial-Services
url: https://raw.githubusercontent.com/api-evangelist/bancomat/refs/heads/main/apis.yml
created: '2024-01-15'
modified: '2026-09-17'
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
common:
- type: IntegrationEdges
url: integrations/bancomat-integration-edges.yml
- type: AgenticAccess
url: agentic-access/bancomat-agentic-access.yml
- type: Spectral
url: rules/bancomat-spectral-rules.yml
- type: Spectral
url: rules/bancomat-rules.yml
- type: Vocabulary
url: vocabulary/bancomat-vocabulary.yml
- type: Deprecation
url: lifecycle/bancomat-lifecycle.yml
- type: Hosts
url: hosts/bancomat-hosts.yml
- type: Vendors
url: vendors/bancomat-vendors.yml
- type: Leadership
url: https://flowpay.it/who-we-are/team
- type: FinOps
url: finops/bancomat-finops.yml
- type: CapabilityMap
url: capabilities/bancomat-capability-edges.yml
name: Bancomat Business Capability Map
- type: Overlay
url: overlays/bancomat-flowpay-api-v1-overlay.yaml
- type: AgentSkill
url: skills/_index.yml
- type: Overlay
url: overlays/bancomat-flowpay-api-v2-overlay.yaml
- type: MCPServer
url: mcp/bancomat-mcp.yml
- type: Website
url: https://flowpay.it/
name: FlowPay (a Bancomat company)
- type: GitHubOrganization
url: https://github.com/FlowPay
- type: Blog
url: https://blog.flowpay.it/
- type: BlogRSS
url: https://blog.flowpay.it/feed/
- type: Support
url: https://youtrack.flowpay.it/
name: FlowPay API support ticket portal (YouTrack)
- type: Support
url: https://bancomat.it/en/contact-us
name: BANCOMAT contact
- type: FAQ
url: https://bancomat.it/en/faq
- type: PrivacyPolicy
url: https://bancomat.it/en/privacy-policy
- type: TermsOfService
url: https://bancomat.it/en/terms-and-conditions
- type: PressReleases
url: https://bancomat.it/en/press-releases
- type: Login
url: https://insight.bancomat.it/
name: BANCOMAT Insight (member-only portal, OTP login)
- type: Packages
url: packages/bancomat-packages.yml
- type: SDKs
url: packages/bancomat-packages.yml
- type: CLI
url: cli/bancomat-cli.yml
- type: WellKnown
url: well-known/bancomat-well-known.yml
- type: Authentication
url: authentication/bancomat-authentication.yml
- type: OAuthScopes
url: scopes/bancomat-scopes.yml
- type: ErrorCatalog
url: errors/bancomat-problem-types.yml
- type: Conventions
url: conventions/bancomat-conventions.yml
- type: Lifecycle
url: lifecycle/bancomat-lifecycle.yml
- type: Conformance
url: conformance/bancomat-conformance.yml
- type: Compliance
url: conformance/bancomat-conformance.yml
- type: DataModel
url: data-model/bancomat-data-model.yml
- type: LLMsTxt
url: llms/bancomat-llms.txt
- type: Plans
url: plans/bancomat-plans-pricing.yml
- type: RateLimits
url: rate-limits/bancomat-rate-limits.yml
- type: DomainSecurity
url: security/bancomat-domain-security.yml
- type: LinkedIn
url: https://www.linkedin.com/company/bancomatofficial
- type: Website
url: https://bancomat.it/en
name: BANCOMAT S.p.A.
- type: Website
url: https://bancomat.it/en/the-company
name: About BANCOMAT S.p.A.
- type: SpectralRules
url: rules/bancomat-spectral-rules.yml
- type: Vocabulary
url: vocabulary/bancomat-vocabulary.yaml
- type: JSONLD
url: json-ld/bancomat-context.jsonld
- name: Features
type: Features
data:
- name: ATM Network
description: Italy's largest ATM cash withdrawal network operational since 1983.
- name: PagoBancomat Debit
description: PIN-based POS debit card payments accepted at millions of Italian merchants.
- name: BANCOMAT Pay Mobile
description: Mobile app payment service for e-commerce and P2P transfers linked to bank accounts.
- name: QR Code Payments
description: QR code-based checkout integration for online and in-store merchants.
- name: Bank Integration
description: Deep integration with Italian banks enabling account-linked payment authorization.
- name: P2P Transfers
description: Person-to-person money transfers between Italian bank accounts via mobile app.
- name: UseCases
type: UseCases
data:
- name: ATM Cash Withdrawals
description: Debit card ATM withdrawals across Italy's national banking network.
- name: POS Debit Payments
description: PIN-based debit card payments at retail point-of-sale terminals.
- name: E-Commerce Payments
description: Online checkout integration via BANCOMAT Pay mobile app.
- name: P2P Money Transfer
description: Person-to-person payments between bank accounts via mobile app.
- name: Merchant Acceptance
description: Enable BANCOMAT Pay as a local Italian payment method for online stores.
- name: Integrations
type: Integrations
data:
- name: Nexi
description: Integration via Nexi XPay Global payment gateway for merchant acceptance.
- name: Axerve (Fabrick)
description: Integration via Axerve/Fabrick for Italian e-commerce BANCOMAT Pay acceptance.
- name: PPRO
description: Integration via PPRO for international PSP access to BANCOMAT Pay.
- name: HiPay
description: Integration via HiPay payment platform.
- name: Viva.com
description: Integration via Viva.com payment services.
- name: PayPal Braintree
description: Integration via PayPal Braintree payment gateway.
- name: Nuvei
description: Integration via Nuvei payment technology platform.
apis:
- aid: bancomat:bancomat-pay
name: BANCOMAT Pay
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/bancomat.png
description: BANCOMAT Pay is a mobile payment service enabling Italian consumers to make e-commerce purchases and P2P transfers
through a smartphone app linked to their bank account by phone number and IBAN. Merchant integration is typically handled
through PSPs such as Nexi, Axerve, PPRO, and HiPay rather than a direct public API. Scheme-level technical documentation
and certification material for issuers, acquirers and certified operators is distributed only through BANCOMAT Insight
(insight.bancomat.it), an OTP-gated member portal; api.bancomat.it answers every unauthenticated path with a JSON 404.
humanURL: https://bancomat.it/en/bancomat-pay
tags:
- Mobile Payments
- P2P
- Payments
- Italy
properties:
- type: Documentation
url: https://bancomat.it/en/bancomat-pay
- type: Documentation
url: https://developer.nexigroup.com/xpayglobal/en-EU/docs/bancomat-pay/
name: Nexi Integration Guide
- aid: bancomat:bancomat-accounts-api
name: Bancomat Accounts API
description: Manage accounts
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Account
tags_raw:
- Accounts
properties:
- type: OpenAPI
url: openapi/bancomat-accounts-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-bank-account-schema.json
- type: JSONSchema
url: json-schema/bancomat-paginated-result-schema.json
- aid: bancomat:bancomat-ais-service-api
name: Bancomat AIS Service API
description: Endpoint per il servizio di AIS in cui è possbile ottenere informazioni di un account o semplicemente un check
iban
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- AIS Service
properties:
- type: OpenAPI
url: openapi/bancomat-ais-service-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-create-ais-session-request-schema.json
- type: JSONSchema
url: json-schema/bancomat-ais-session-schema.json
- type: JSONSchema
url: json-schema/bancomat-check-iban-schema.json
- aid: bancomat:bancomat-authentication-api
name: Bancomat Authentication API
description: Manage authentication
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Authentication
properties:
- type: OpenAPI
url: openapi/bancomat-authentication-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- aid: bancomat:bancomat-banche-api
name: Bancomat Banche API
description: Banche conformi allo standard PSD2
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Banche
properties:
- type: OpenAPI
url: openapi/bancomat-banche-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-bank-schema.json
- type: JSONSchema
url: json-schema/bancomat-banks-schema.json
- aid: bancomat:bancomat-banks-api
name: Bancomat Banks API
description: Banks informations
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Banks
properties:
- type: OpenAPI
url: openapi/bancomat-banks-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-bank-schema.json
- aid: bancomat:bancomat-bulk-api
name: Bancomat Bulk API
description: 'Questo endpoint consente di effettuare pagamenti bulk di documenti di diversi tipi. <br> Nota: l''API di questo
endpoint non richiede scope specifici, il token di autorizzazione utilizzato deve avere accesso ai documenti che desidera
pagare.
<p align="center">
<img src="https://mermaid.ink/svg/pako:eNqFkl9rwjAUxb9KyB58qWCryOjDwO4PCGOIle2lL7fNrQs2iUtT0YnffYmtGjdhebo553dPEm72tFAMaUxrAwafOCw1iEwSuxjXWBiuJHmdt8pUbhQvMExQhv3-A0maanXlRM4hNy3XFP2yZrBUs4kTL5qrjthsmnbUND0Ki0m7Xxw7yIe9njvulhjRgArUAjizT9s7JKPmEwVmNLZlDrWtAk9_B80hr7B2wL7NzGippHkBwatd29ebq1wZ1QvIBjUDCQFxfVWXdWpJ-Xd3UDhebz1zrbkAvXtUldItcMcYDsviL5MozVD75Gg8LMrSI8FOZwNuQslq6ZNlVN5fZXrk_7HdBRa4NT4XDoaDEXpcjV8NygLfGpFfR57e5MhDJg92GtAYle5kQWOjGwxos2aX_0bjEqr6rD4zbpTuxMMPPNfQrg"
width="50%">
</p>
Il diagramma sopra mostra come funziona bulk.
Supponiamo il caso in cui un utente abbia due fatture per il beneficiario 1 (Ben1), una fattura per il beneficiario 2
(Ben2) e un pagamento PagoPA
L''utente desidera pagare tutti in un''unica operazione.
Il client dell''utente, che ha accesso a tutti i documenti, chiama l''endpoint in blocco con l''elenco dei documenti da
pagare, l''endpoint restituisce un nuovo documento (Bulk) collegato a tutti i documenti da pagare.
Il client fornisce il documento bulk all''utente, che ora può pagarlo con un''unica operazione di Payment Initiation (PIS).
Il bonifico bancario consentito con PIS sul documento in blocco è indirizzato al conto tecnico FlowPay (TA). Quando il
TA riceve il pagamento, divide l''importo tra i beneficiari e invia loro i pagamenti tramite bonifico bancario.
In caso di pagamento bulk allo stesso beneficiario, il beneficiario effettivo di avvio del pagamento è il beneficiario
stesso, quindi il pagatore può riconoscere facilmente la transazione. In caso contrario, il beneficiario effettivo di
avvio del pagamento è FlowPay.
I bonifici bancari ai beneficiari vengono inviati con lo stesso pagatore originale, quindi i beneficiari possono identificare
facilmente il pagatore.
Nota: il destinatario dei pagamenti pagoPA è FlowPay stesso, quindi i pagamenti correlati non vengono conteggiati nelle
operazioni di suddivisione.'
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Bulk
properties:
- type: OpenAPI
url: openapi/bancomat-bulk-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-bulk-2-schema.json
- type: JSONSchema
url: json-schema/bancomat-bulk-schema.json
- type: JSONSchema
url: json-schema/bancomat-paginated-result-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-kind-enum-2-schema.json
- type: JSONSchema
url: json-schema/bancomat-fingerprint-2-schema.json
- type: JSONSchema
url: json-schema/bancomat-fingerprint-schema.json
- aid: bancomat:bancomat-chain-api
name: Bancomat Chain API
description: 'Questo endpoint consente di concatenare i pagamenti tra diversi documenti, automatizzando il pagamento di
una fattura utilizzando l''importo ricevuto da un''altra fattura attiva. <br> Nota: L''API per questo endpoint non richiede
scopi specifici; il token di autorizzazione utilizzato deve avere accesso ai documenti da pagare.
Il processo della catena di pagamento funziona collegando un documento "ring" che collega un documento di attivazione
a un documento di destinazione. Una volta creato il documento ring, esso stabilisce una connessione tra il documento di
attivazione, che avvia la catena di pagamento, e il documento di destinazione, che riceverà il pagamento una volta che
il documento di attivazione è stato pagato tramite FlowPay.
Ad esempio, supponiamo che ci siano due documenti. Il primo documento riguarda un pagamento che l''azienda A deve effettuare
all''azienda B, mentre il secondo documento riguarda un pagamento che l''azienda B deve effettuare all''azienda C. Per
automatizzare questi pagamenti, l''azienda B crea un "anello" utilizzando il suo token di autorizzazione. Questo anello
collega il primo documento come "trigger" (documento di attivazione) e il secondo documento come "target" (documento di
destinazione).
Una volta creato l''anello, è possibile generare sessioni di checkout per ciascun documento. Il checkout per il documento
di attivazione procede come un processo di pagamento standard, mentre il checkout per il documento di destinazione viene
creato con un tipo di catena. Questo tipo di checkout a catena per il documento di destinazione non richiede un pagamento
immediato, ma attende il pagamento del documento di attivazione.
Quando l''azienda B accede e completa il checkout per il documento di destinazione, non viene effettuato alcun pagamento.
Tuttavia, quando il documento di attivazione viene pagato, si attiva automaticamente il pagamento del documento di destinazione.
Se c''è un importo residuo dopo il pagamento del documento di destinazione, l''azienda B lo riceverà.
In questo modo, l''automazione dei pagamenti assicura che tutti i documenti coinvolti siano regolati in modo sequenziale,
utilizzando i fondi ricevuti da un documento attivo per pagare un altro documento in sospeso, riducendo al minimo l''intervento
manuale e semplificando la gestione dei flussi di cassa tra le aziende coinvolte.
### Utilizzo della catena di pagamento per il pagamento frazionato
In uno scenario di pagamento frazionato, la catena di pagamento può essere utilizzata per distribuire automaticamente
i fondi tra più parti, anche trattenendo una parte del pagamento per il partner prima di inoltrare l''importo rimanente
al creditore. Ad esempio, supponiamo che l''azienda A debba pagare l''azienda B, ma che una parte del pagamento sia trattenuta
dall''azienda C (che agisce come partner o intermediario). L''azienda A crea un documento di attivazione che rappresenta
il pagamento che deve all''azienda B. Viene quindi creato un documento ring che collega questo documento di attivazione
a due documenti di destinazione: uno per l''azienda B e uno per l''azienda C.
Quando l''azienda A effettua il pagamento, la catena di pagamento assicura che i fondi vengano prima instradati attraverso
l''azienda C. La parte a cui l''azienda C ha diritto (come concordato) viene trattenuta, mentre il resto del pagamento
viene automaticamente inoltrato all''azienda B. Questa configurazione assicura che il pagamento frazionato venga gestito
senza problemi, con un intervento manuale minimo, e che tutte le parti ricevano gli importi dovuti secondo le regole predefinite
della catena di pagamento.'
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Chain
properties:
- type: OpenAPI
url: openapi/bancomat-chain-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-chain-schema.json
- type: JSONSchema
url: json-schema/bancomat-paginated-result-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-kind-enum-2-schema.json
- type: JSONSchema
url: json-schema/bancomat-fingerprint-2-schema.json
- type: JSONSchema
url: json-schema/bancomat-fingerprint-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-kind-enum-schema.json
- aid: bancomat:bancomat-checkout-api
name: Bancomat Checkout API
description: This endpoint allows managing checkout sessions any document client has access to
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Checkout
properties:
- type: OpenAPI
url: openapi/bancomat-checkout-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-checkout-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-kind-enum-schema.json
- type: JSONSchema
url: json-schema/bancomat-fingerprint-schema.json
- aid: bancomat:bancomat-consent-api
name: Bancomat Consent API
description: Gestione del consenso per l'accesso ai dati bancari
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Consent
properties:
- type: OpenAPI
url: openapi/bancomat-consent-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-consent-dto-schema.json
- aid: bancomat:bancomat-construction-api
name: Bancomat Construction API
description: Manage construction sites and related entities lifecycle
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Construction
properties:
- type: OpenAPI
url: openapi/bancomat-construction-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-site-quote-schema.json
- type: JSONSchema
url: json-schema/bancomat-construction-progress-schema.json
- type: JSONSchema
url: json-schema/bancomat-site-worker-contract-schema.json
- type: JSONSchema
url: json-schema/bancomat-construction-site-schema.json
- type: JSONSchema
url: json-schema/bancomat-site-worker-contract-creation-schema.json
- type: JSONSchema
url: json-schema/bancomat-paginated-result-schema.json
- aid: bancomat:bancomat-constructions-api
name: Bancomat Constructions API
description: The Constructions API from Bancomat — 1 operation(s) for constructions.
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Constructions
properties:
- type: OpenAPI
url: openapi/bancomat-constructions-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-fingerprint-schema.json
- aid: bancomat:bancomat-conti-api
name: Bancomat Conti API
description: The Conti API from Bancomat — 1 operation(s) for conti.
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Conti
properties:
- type: OpenAPI
url: openapi/bancomat-conti-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-accounts-schema.json
- aid: bancomat:bancomat-documents-api
name: Bancomat Documents API
description: CRUD operations on documents
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Documents
properties:
- type: OpenAPI
url: openapi/bancomat-documents-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-invoice-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-term-schema.json
- type: JSONSchema
url: json-schema/bancomat-transfer-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-item-schema.json
- type: JSONSchema
url: json-schema/bancomat-pago-pa-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-attachment-schema.json
- aid: bancomat:bancomat-fatture-api
name: Bancomat Fatture API
description: The Fatture API from Bancomat — 3 operation(s) for fatture.
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Fatture
properties:
- type: OpenAPI
url: openapi/bancomat-fatture-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-invoice-schema.json
- type: JSONSchema
url: json-schema/bancomat-new-invoice-schema.json
- type: JSONSchema
url: json-schema/bancomat-invoice-preference-schema.json
- type: JSONSchema
url: json-schema/bancomat-edit-invoice-request-schema.json
- type: JSONSchema
url: json-schema/bancomat-xml-schema.json
- type: JSONSchema
url: json-schema/bancomat-paid-outside-flow-pay-term-list-schema.json
- aid: bancomat:bancomat-fee-api
name: Bancomat Fee API
description: '{''$ref'': ''docs/fee_description.md''}'
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Fee
properties:
- type: OpenAPI
url: openapi/bancomat-fee-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-fee-rule-schema.json
- type: JSONSchema
url: json-schema/bancomat-fee-schema.json
- type: JSONSchema
url: json-schema/bancomat-paginated-result-schema.json
- type: JSONSchema
url: json-schema/bancomat-fee-rule-map-schema.json
- type: JSONSchema
url: json-schema/bancomat-fee-rule-amount-map-schema.json
- aid: bancomat:bancomat-invoices-api
name: Bancomat Invoices API
description: '{''$ref'': ''docs/invoice_lifecycle.md''}'
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Invoices
properties:
- type: OpenAPI
url: openapi/bancomat-invoices-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-invoice-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-term-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-item-schema.json
- type: JSONSchema
url: json-schema/bancomat-document-attachment-schema.json
- type: JSONSchema
url: json-schema/bancomat-company-vatnumber-schema.json
- type: JSONSchema
url: json-schema/bancomat-paginated-result-schema.json
- aid: bancomat:bancomat-kyc-api
name: Bancomat KYC API
description: '{''$ref'': ''docs/kyc_description.md''}'
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- KYC
properties:
- type: OpenAPI
url: openapi/bancomat-kyc-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
- type: Sandbox
url: sandbox/bancomat-sandbox.yml
- type: Documentation
url: https://github.com/FlowPay/client-openapi/tree/main/docs
- type: SourceCode
url: https://github.com/FlowPay/client-openapi
- type: JSONSchema
url: json-schema/bancomat-kycdossier-schema.json
- type: JSONSchema
url: json-schema/bancomat-company-vatnumber-schema.json
- type: JSONSchema
url: json-schema/bancomat-consumer-national-id-schema.json
- aid: bancomat:bancomat-pagamenti-api
name: Bancomat Pagamenti API
description: I pagamenti generati dall'approvazione di uno o più termini di pagamento relativi a una fattura
humanURL: https://bancomat.it/en/bancomat-pay
baseURL: https://app.flowpay.it/api
tags:
- Pagamenti
properties:
- type: OpenAPI
url: openapi/bancomat-pagamenti-api-openapi.yml
- type: Documentation
url: https://docs.flowpay.it/
- type: APIReference
url: https://docs.flowpay.it/
- type: DeveloperPortal
url: https://developer.flowpay.it/
- type: Webhooks
url: asyncapi/bancomat-flowpay-webhooks.yml
# --- truncated at 32 KB (45 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/bancomat/refs/heads/main/apis.yml
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/bancomat"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/bancomat/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/bancomat/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 .
A second provider on the same verified email joins the account you already have.
Kin Score
How this is scored →