Scalapay

Scalapay is an Italian buy-now-pay-later (BNPL) payment provider that lets shoppers split a purchase into instalments — pay in 3, pay in 4, or pay later — while the merchant is settled by Scalapay. Its REST API is a compact, order-centric surface: create an instalment order, redirect the shopper to Scalapay Checkout, then capture, delay, void or refund against the order token, with a parallel in-store and offline pay-by-link family authenticated by a device-scoped key, plus reporting endpoints for reconciling orders, refunds, payouts and disputes against Scalapay's bank transfers. Merchants integrate through a CDN-loaded web component (the Scalapay Suite Widget) on the product, cart and checkout pages, or through prebuilt modules for Magento, WooCommerce, PrestaShop, Shopify, Shopware, BigCommerce, VTEX, Salesforce and others. Scalapay operates in EUR across 14 authorised European territories.

Scalapay publishes 3 API contracts indexed on the APIs.io network: Instore API, Orders API, and Reporting API. Tagged areas include Payments, Buy Now Pay Later, Instalments, E-Commerce, and Checkout.

The Scalapay catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Scalapay’s developer surface includes pricing, documentation, API reference, getting-started guide, support, signup flow, authentication, and 29 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

54.2/100 developing ▬ flat Agent 39/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract 4 Agent Skills

Payments Buy Now Pay Later Instalments E-Commerce Checkout Financial Services Point-of-Sale Reconciliation Europe Company

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Payments & Card Management

BC-1340

InstoreOrders

POST /v2/payments/capture POST /v2/payments/{token}/refund POST /v2/payments/{token}/void POST /v1/instore/orders

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 54.2/100 · developing

Contract Quality 10.9 / 19

Developer Ergonomics 9.4 / 15

Access Clarity 9.6 / 15

Operational Transparency 3.9 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.2 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 39/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/scalapay/"><img src="https://apis.io/badge/scalapay/card.svg" alt="Scalapay 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 Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →

5 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 58.2 — up to +10.5 composite points Ask about this →
Contract Governance scores 18.2 — up to +9.8 composite points Ask about this →
Operational Transparency scores 40.5 — up to +7.7 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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/scalapay/apis.yml: open an issue on github.com/api-evangelist/scalapay 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 →

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
Consumer Lending Licensing (UK, US, Canada credit licence registers)	distribution	9.6 (thin)	-	-
Official SDKs on Packagist, pub.dev and Hex	distribution	9.6 (thin)	-	-

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.

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 3

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

Scalapay Instore API

The Instore API from Scalapay — 6 operation(s) for instore.

Scalapay Orders API

The Orders API from Scalapay — 8 operation(s) for orders.

Scalapay Reporting API

The Reporting API from Scalapay — 6 operation(s) for reporting.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scalapay Instore API

OPEN COLLECTION

Scalapay Orders API

OPEN COLLECTION

Scalapay Reporting API

OPEN COLLECTION

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Create and capture a Scalapay order

AGENT SKILL

Run a Scalapay delayed-capture order

AGENT SKILL

Take a Scalapay in-store or pay-by-link order

AGENT SKILL

Refund a Scalapay order and reconcile the payout

AGENT SKILL

Scalapay API pricing

Prices published by Scalapay, read 2026-09-20 from universe.development.scalapay.com/pricing-table-shortcode/.

Plan	Price
Personal	$0 Includes: WPBakery Page Builder, Advanced Custom Fileds Pro, Slider Revolution, Custom Design & Features, Enha
Premium	$5 Includes: WPBakery Page Builder, Advanced Custom Fileds Pro, Slider Revolution, Custom Design & Features, Enha
Business	$26 Includes: WPBakery Page Builder, Advanced Custom Fileds Pro, Slider Revolution, Custom Design & Features, Enha

Plan details, limits and sources →

Billed by: subscription · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Scalapay Plans Pricing

3 plans

PLANS

Scalapay Price Estimates

0 plans

PLANS

FinOps 1

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

Scalapay Finops

FINOPS

Event Specifications 1

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

Scalapay Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Scalapay API Rules

66 rules · 59 error-severity 3 warn-severity 4 info-severity

SPECTRAL

OpenAPI Overlays 1

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.

Scalapay Overlay

22 actions · documentation · scalapay-openapi-original.yml

DERIVED

Security Posture 2

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

Scalapay Authentication

apiKey · 2 schemes

SECURITY

Scalapay Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Components

ErrorCatalog

ErrorCodes

Lifecycle

Conformance

DataModel

Webhooks

Scroll for all 9

Build 3

SDKs, sample code, and the tooling you integrate with

SourceCode

SourceCode

Packages

Packages

SDKs

SDKs

Access & Security 3

Authentication, authorization, and security posture

Compliance

Compliance

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

Support

HelpCenter

StatusPage

ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

Plans

TermsOfService

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: scalapay
name: Scalapay
description: 'Scalapay is an Italian buy-now-pay-later (BNPL) payment provider that lets shoppers split a purchase into instalments
  — pay in 3, pay in 4, or pay later — while the merchant is settled by Scalapay. Its REST API is a compact, order-centric
  surface: create an instalment order, redirect the shopper to Scalapay Checkout, then capture, delay, void or refund against
  the order token, with a parallel in-store and offline pay-by-link family authenticated by a device-scoped key, plus reporting
  endpoints for reconciling orders, refunds, payouts and disputes against Scalapay''s bank transfers. Merchants integrate
  through a CDN-loaded web component (the Scalapay Suite Widget) on the product, cart and checkout pages, or through prebuilt
  modules for Magento, WooCommerce, PrestaShop, Shopify, Shopware, BigCommerce, VTEX, Salesforce and others. Scalapay operates
  in EUR across 14 authorised European territories.'
url: https://raw.githubusercontent.com/api-evangelist/scalapay/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.23'
created: '2026-08-02'
modified: '2026-08-02'
image: https://cdn.prod.website-files.com/614b9948e0cc06785c60efe7/67c9cc48ae95dd9c93be62c3_favicon-256.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Payments
- Buy Now Pay Later
- Instalments
- E-Commerce
- Checkout
- Financial Services
- Point-of-Sale
- Reconciliation
- Europe
- Company
tags_raw:
- Payments
- Buy Now Pay Later
- BNPL
- Instalments
- E-Commerce
- Checkout
- Financial Services
- Point of Sale
- Reconciliation
- Europe
- Company
- Financial-Services
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: scalapay:scalapay-instore-api
  name: Scalapay Instore API
  description: The Instore API from Scalapay — 6 operation(s) for instore.
  humanURL: https://developers.scalapay.com/reference/api-architecture
  baseURL: https://api.scalapay.com
  tags:
  - In-Store
  tags_raw:
  - Instore
  properties:
  - type: OpenAPI
    url: openapi/scalapay-instore-api-openapi.yml
  - type: Documentation
    url: https://developers.scalapay.com/docs/get-started-with-scalapay
  - type: APIReference
    url: https://developers.scalapay.com/reference/api-architecture
  - type: Sandbox
    url: sandbox/scalapay-sandbox.yml
- aid: scalapay:scalapay-orders-api
  name: Scalapay Orders API
  description: The Orders API from Scalapay — 8 operation(s) for orders.
  humanURL: https://developers.scalapay.com/reference/api-architecture
  baseURL: https://api.scalapay.com
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/scalapay-orders-api-openapi.yml
  - type: Documentation
    url: https://developers.scalapay.com/docs/get-started-with-scalapay
  - type: APIReference
    url: https://developers.scalapay.com/reference/api-architecture
  - type: Sandbox
    url: sandbox/scalapay-sandbox.yml
- aid: scalapay:scalapay-reporting-api
  name: Scalapay Reporting API
  description: The Reporting API from Scalapay — 6 operation(s) for reporting.
  humanURL: https://developers.scalapay.com/reference/api-architecture
  baseURL: https://api.scalapay.com
  tags:
  - Reporting
  properties:
  - type: OpenAPI
    url: openapi/scalapay-reporting-api-openapi.yml
  - type: Documentation
    url: https://developers.scalapay.com/docs/get-started-with-scalapay
  - type: APIReference
    url: https://developers.scalapay.com/reference/api-architecture
  - type: Sandbox
    url: sandbox/scalapay-sandbox.yml
common:
- type: Pricing
  url: https://universe.development.scalapay.com/pricing-table-shortcode/
- type: Plans
  url: plans/scalapay-plans-pricing.yml
- type: CapabilityMap
  url: capabilities/scalapay-capability-edges.yml
  name: Scalapay Business Capability Map
- type: X-MCPServerCandidate
  url: mcp/scalapay-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/scalapay-overlay.yaml
- type: Website
  url: https://www.scalapay.com/
- type: DeveloperPortal
  url: https://developers.scalapay.com/
- type: Documentation
  url: https://developers.scalapay.com/docs/get-started-with-scalapay
- type: APIReference
  url: https://developers.scalapay.com/reference/api-architecture
- type: GettingStarted
  url: https://developers.scalapay.com/docs/get-started-with-scalapay
- type: Support
  url: https://help.scalapay.com/
- type: HelpCenter
  url: https://merchant-help.scalapay.com/
- type: SignUp
  url: https://portal.scalapay.com/signup
- type: Login
  url: https://partner.scalapay.com/login
- type: TermsOfService
  url: https://www.scalapay.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.scalapay.com/privacy
- type: Compliance
  url: https://www.scalapay.com/legals
- type: StatusPage
  url: https://status.scalapay.com/
- type: SourceCode
  url: https://bitbucket.org/scalapay
- type: Authentication
  url: authentication/scalapay-authentication.yml
- type: Conventions
  url: conventions/scalapay-conventions.yml
- type: Idempotency
  url: conventions/scalapay-conventions.yml
- type: Packages
  url: packages/scalapay-packages.yml
- type: SDKs
  url: packages/scalapay-packages.yml
- type: Sandbox
  url: sandbox/scalapay-sandbox.yml
- type: Components
  url: components/scalapay-components.yml
- type: ErrorCatalog
  url: errors/scalapay-problem-types.yml
- type: ErrorCodes
  url: errors/scalapay-error-codes.yml
- type: Lifecycle
  url: lifecycle/scalapay-lifecycle.yml
- type: ChangeLog
  url: changelog/scalapay-changelog.yml
- type: Conformance
  url: conformance/scalapay-conformance.yml
- type: DataModel
  url: data-model/scalapay-data-model.yml
- type: Webhooks
  url: asyncapi/scalapay-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/scalapay-llms.txt
- type: DomainSecurity
  url: security/scalapay-domain-security.yml
x-enrichment:
  date: '2026-08-02'
  status: enriched
  artifacts_added: 23
  pass: local-v1

Scalapay API — frequently asked questions

Does Scalapay have an API?

Yes. APIs.io lists 3 APIs from Scalapay, including Scalapay Instore API, Scalapay Orders API and Scalapay Reporting API.

Is there an OpenAPI specification for the Scalapay API?

Yes. APIs.io indexes 3 OpenAPI specifications for Scalapay, each linked for download from this page.

How do I authenticate with the Scalapay API?

Scalapay uses bearer-token authentication (apiKey · 2 schemes). The details are profiled on APIs.io as Scalapay Authentication.

How much does the Scalapay API cost?

Scalapay publishes its prices; its Personal plan is $0 as of 2026-09-20. APIs.io lists 3 pricing plans for Scalapay, with each plan's price, limits and inclusions under Pricing on this page.

Is the Scalapay API ready for AI agents?

Scalapay has a Kin Score of 54.2 out of 100 (developing) and an Agent Readiness score of 38.5 (agent-ready), scored by API Evangelist on 2026-11-13.

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

All providers

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

Every operation they expose

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

How their score was established

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