Kriya website screenshot

Kriya

Kriya (Kriya Finance Limited, London) is a UK B2B embedded-finance and working-capital provider that lets merchants offer trade credit to their business buyers. Its products span Embedded PayLater (B2B buy-now-pay-later terms at checkout), Invoice Finance, working capital loans, buyer authentication, offline payments and a Kriya-on-Stripe integration. Kriya publishes two partner-facing REST APIs — the Payments API for buyer registration, risk decisioning, order lifecycle and payment deductions, and the Onboarding API for automating company and KYC checks — alongside a hosted Payments Journey and Onboarding Journey web flow, HMAC-signed webhooks, a dedicated test environment with scenario simulators, and e-commerce plugins for BigCommerce, Magento, nopCommerce, PrestaShop and Salesforce. Kriya was acquired by Allica Bank in October 2025.

Kriya publishes 6 APIs on the APIs.io network, including Buyers API, Onboarding API API, OnboardingJourney API, and 3 more. Tagged areas include Company, Fintech, Payments, Embedded Finance, and Buy Now Pay Later.

The Kriya catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Kriya’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, sandbox, and 20 more developer resources.

39.7/100 developing ▬ flat Agent 26/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
2 APIs
CompanyFintechPaymentsEmbedded FinanceBuy Now Pay LaterB2B PaymentsInvoice FinanceLendingWorking CapitalOnboardingKYCUnited Kingdom

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.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/kriya: 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 6

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

Kriya Buyers API

The Buyers API from Kriya — 6 operation(s) for buyers.

Kriya Onboarding API API

The Onboarding API API from Kriya — 2 operation(s) for onboarding api.

Kriya OnboardingJourney API

The OnboardingJourney API from Kriya — 1 operation(s) for onboardingjourney.

Kriya Orders API

The Orders API from Kriya — 7 operation(s) for orders.

Kriya Payments API

The Payments API from Kriya — 3 operation(s) for payments.

Kriya Scenario API

The Scenario API from Kriya — 1 operation(s) for scenario.

Open Collections 7

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

API Collection

OPEN COLLECTION

Scroll for all 7

Event Specifications 1

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

Security Posture 3

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

Kriya Authentication

apiKey · 1 scheme

SECURITY

Kriya Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Kriya Vulnerability Disclosure

contact published

SECURITY

Resources

Get Started 4

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 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 4

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 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: kriya
name: Kriya
description: Kriya (Kriya Finance Limited, London) is a UK B2B embedded-finance and working-capital provider that lets merchants
  offer trade credit to their business buyers. Its products span Embedded PayLater (B2B buy-now-pay-later terms at checkout),
  Invoice Finance, working capital loans, buyer authentication, offline payments and a Kriya-on-Stripe integration. Kriya
  publishes two partner-facing REST APIs — the Payments API for buyer registration, risk decisioning, order lifecycle and
  payment deductions, and the Onboarding API for automating company and KYC checks — alongside a hosted Payments Journey and
  Onboarding Journey web flow, HMAC-signed webhooks, a dedicated test environment with scenario simulators, and e-commerce
  plugins for BigCommerce, Magento, nopCommerce, PrestaShop and Salesforce. Kriya was acquired by Allica Bank in October 2025.
url: https://raw.githubusercontent.com/api-evangelist/kriya/refs/heads/main/apis.yml
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
image: https://cdn.kriya.co/images/KriyaPaymentsAPI-API-Integration-Sequence-Flow.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- northzone
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Fintech
- Payments
- Embedded Finance
- Buy Now Pay Later
- B2B Payments
- Invoice Finance
- Lending
- Working Capital
- Onboarding
- KYC
- United Kingdom
apis:
- aid: kriya:kriya-buyers-api
  name: Kriya Buyers API
  description: The Buyers API from Kriya — 6 operation(s) for buyers.
  humanURL: https://docs.kriya.co/payments
  baseURL: https://api.kriya.co/payments/
  tags:
  - Buyers
  properties:
  - type: OpenAPI
    url: openapi/kriya-buyers-api-openapi.yml
  - type: Documentation
    url: https://docs.kriya.co/payments
  - type: Documentation
    url: https://docs.kriya.co/onboarding
- aid: kriya:kriya-onboarding-api-api
  name: Kriya Onboarding API API
  description: The Onboarding API API from Kriya — 2 operation(s) for onboarding api.
  humanURL: https://docs.kriya.co/payments
  baseURL: https://api.kriya.co/payments/
  tags:
  - Onboarding API
  properties:
  - type: OpenAPI
    url: openapi/kriya-onboarding-api-api-openapi.yml
  - type: Documentation
    url: https://docs.kriya.co/payments
  - type: Documentation
    url: https://docs.kriya.co/onboarding
- aid: kriya:kriya-onboardingjourney-api
  name: Kriya OnboardingJourney API
  description: The OnboardingJourney API from Kriya — 1 operation(s) for onboardingjourney.
  humanURL: https://docs.kriya.co/payments
  baseURL: https://api.kriya.co/payments/
  tags:
  - OnboardingJourney
  properties:
  - type: OpenAPI
    url: openapi/kriya-onboardingjourney-api-openapi.yml
  - type: Documentation
    url: https://docs.kriya.co/payments
  - type: Documentation
    url: https://docs.kriya.co/onboarding
- aid: kriya:kriya-orders-api
  name: Kriya Orders API
  description: The Orders API from Kriya — 7 operation(s) for orders.
  humanURL: https://docs.kriya.co/payments
  baseURL: https://api.kriya.co/payments/
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/kriya-orders-api-openapi.yml
  - type: Documentation
    url: https://docs.kriya.co/payments
  - type: Documentation
    url: https://docs.kriya.co/onboarding
- aid: kriya:kriya-payments-api
  name: Kriya Payments API
  description: The Payments API from Kriya — 3 operation(s) for payments.
  humanURL: https://docs.kriya.co/payments
  baseURL: https://api.kriya.co/payments/
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/kriya-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.kriya.co/payments
  - type: Documentation
    url: https://docs.kriya.co/onboarding
- aid: kriya:kriya-scenario-api
  name: Kriya Scenario API
  description: The Scenario API from Kriya — 1 operation(s) for scenario.
  humanURL: https://docs.kriya.co/payments
  baseURL: https://api.kriya.co/payments/
  tags:
  - Scenario
  properties:
  - type: OpenAPI
    url: openapi/kriya-scenario-api-openapi.yml
  - type: Documentation
    url: https://docs.kriya.co/payments
  - type: Documentation
    url: https://docs.kriya.co/onboarding
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/kriya-onboarding-overlay.yaml
- type: Website
  url: https://www.kriya.co
- type: DeveloperPortal
  url: https://docs.kriya.co/
- type: Documentation
  url: https://docs.kriya.co/payments
- type: APIReference
  url: https://docs.kriya.co/payments#section/API-Endpoints
- type: GettingStarted
  url: https://docs.kriya.co/payments#section/Integration-Scenarios
- type: Support
  url: https://www.kriya.co/contact-us
- type: Blog
  url: https://www.kriya.co/blog
- type: Login
  url: https://merchant.kriya.co/
- type: TermsOfService
  url: https://www.kriya.co/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.kriya.co/privacy-policy
- type: Security
  url: https://www.kriya.co/responsible-disclosure
- type: Authentication
  url: authentication/kriya-authentication.yml
- type: Conventions
  url: conventions/kriya-conventions.yml
- type: ErrorCatalog
  url: errors/kriya-problem-types.yml
- type: DeclineCodes
  url: errors/kriya-decline-codes.yml
- type: Lifecycle
  url: lifecycle/kriya-lifecycle.yml
- type: Conformance
  url: conformance/kriya-conformance.yml
- type: Webhooks
  url: asyncapi/kriya-payments-webhooks.yml
- type: Sandbox
  url: sandbox/kriya-sandbox.yml
- type: DataModel
  url: data-model/kriya-data-model.yml
- type: Components
  url: components/kriya-components.yml
- type: X-MCPServerCandidate
  url: mcp/kriya-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: LLMsTxt
  url: llms/kriya-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: VulnerabilityDisclosure
  url: security/kriya-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/kriya-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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/kriya"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/kriya/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/kriya/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.