Scalapay website screenshot

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 APIs 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.

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

48.1/100 developing ▬ flat Agent 37/100 agent ready saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
1 APIs
PaymentsBuy Now Pay LaterInstalmentsE-CommerceCheckoutFinancial-ServicesPoint-of-SaleReconciliationEuropeCompany

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
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/.
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 github.com/api-evangelist/scalapay: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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 4

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

API Collection

OPEN COLLECTION

Scalapay Instore API

OPEN COLLECTION

Scalapay Orders API

OPEN COLLECTION

Scalapay Reporting API

OPEN COLLECTION

Event Specifications 1

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

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Scroll for all 9

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  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
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
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: 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

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"

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.