Limepay website screenshot

Limepay

Limepay was a Melbourne-based Australian embedded-payments and white-label buy-now-pay-later (BNPL) company that let merchants and platforms accept card payments and offer pay-in-instalments through a single drop-in checkout and a REST API. Its developer surface covered an embeddable Checkout, a Payments API (orders, order-pay, transaction capture/void, refunds, 3-D Secure and wallet payments such as Apple Pay and Google Pay), and a Platform API for marketplaces to onboard and manage sub-merchants, run KYC/identification, and pull settlement reports. Authentication used a Publishable API key for frontend/checkout calls, a Secret API key for server-to-server calls, and a platform API key for administrative onboarding, all passed as Bearer tokens. After a failed 2021 IPO, Limepay was acquired by ASX-listed Spenda in 2024 and its product line was continued under the April Solutions brand; the primary domain limepay.com.au now redirects to meetapril.com and the docs.limepay.com.au developer portal is gated behind a Redocly login. This profile documents Limepay's real, historically public API family honestly; no machine-readable OpenAPI is currently downloadable.

Limepay publishes 3 APIs on the APIs.io network. Tagged areas include Payments, Australia, BNPL, Payment Gateway, and Checkout.

Limepay’s developer surface includes authentication, documentation, API reference, and 10 more developer resources.

11.7/100 emerging ▬ flat Agent 3/100 human only library Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
3 APIs
PaymentsAustraliaBNPLPayment GatewayCheckoutEmbedded PaymentsWhite LabelCard PaymentsMarketplaceInstalments

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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/limepay: 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.

Limepay Payments API

REST API for accepting and managing card and BNPL payments — create and pay orders, capture or void authorised (pre-auth) transactions, issue refunds, save cards as payment sour...

Limepay Platform API

REST API for platform and marketplace integrations to onboard and manage sub-merchants: create platform merchants, merchant bank accounts and merchant persons, run KYC/identific...

Limepay Checkout

Embeddable, customisable checkout that merchants drop into a web store (with plugins for WooCommerce, Magento, PrestaShop and Salesforce Commerce Cloud) to accept card payments ...

Security Posture 2

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

Limepay Authentication

3 schemes

SECURITY

Limepay Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: limepay
url: https://raw.githubusercontent.com/api-evangelist/limepay/refs/heads/main/apis.yml
name: Limepay
kind: company
description: Limepay was a Melbourne-based Australian embedded-payments and white-label buy-now-pay-later (BNPL) company that
  let merchants and platforms accept card payments and offer pay-in-instalments through a single drop-in checkout and a REST
  API. Its developer surface covered an embeddable Checkout, a Payments API (orders, order-pay, transaction capture/void,
  refunds, 3-D Secure and wallet payments such as Apple Pay and Google Pay), and a Platform API for marketplaces to onboard
  and manage sub-merchants, run KYC/identification, and pull settlement reports. Authentication used a Publishable API key
  for frontend/checkout calls, a Secret API key for server-to-server calls, and a platform API key for administrative onboarding,
  all passed as Bearer tokens. After a failed 2021 IPO, Limepay was acquired by ASX-listed Spenda in 2024 and its product
  line was continued under the April Solutions brand; the primary domain limepay.com.au now redirects to meetapril.com and
  the docs.limepay.com.au developer portal is gated behind a Redocly login. This profile documents Limepay's real, historically
  public API family honestly; no machine-readable OpenAPI is currently downloadable.
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  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
  - url: https://www.limepay.com.au/
    status: 301
    note: declared website redirects to https://meetapril.com/ — a different registrable domain (limepay.com.au -> meetapril.com),
      possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- Australia
- BNPL
- Payment Gateway
- Checkout
- Embedded Payments
- White Label
- Card Payments
- Marketplace
- Instalments
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: limepay:limepay-payments-api
  name: Limepay Payments API
  description: REST API for accepting and managing card and BNPL payments — create and pay orders, capture or void authorised
    (pre-auth) transactions, issue refunds, save cards as payment sources, and run 3-D Secure and wallet payments (Apple Pay
    / Google Pay). Documented operations include CreateOrder, PayOrder, GetOrder, CancelOrder, CreateOrderInvoice, CaptureTransaction,
    CancelUncapturedTransaction, GetTransaction, GetTransactionByOrderId, CreateRefund, CreateSavedPayCard and GetPayPlanEligibilityMaxAmount.
    Authenticated with Publishable (frontend) and Secret (server-side) API keys sent as Bearer tokens.
  humanURL: https://docs.limepay.com.au/developer-portal/payments/
  baseURL: https://api.limepay.com.au
  tags:
  - Payments
  - Order
  - Refunds
  - Transaction
  - BNPL
  tags_raw:
  - Payments
  - Orders
  - Refunds
  - Transactions
  - BNPL
  properties:
  - type: Documentation
    url: https://docs.limepay.com.au/developer-portal/payments/
  - type: APIReference
    url: https://docs.limepay.com.au/developer-portal/api-reference
- aid: limepay:limepay-platform-api
  name: Limepay Platform API
  description: 'REST API for platform and marketplace integrations to onboard and manage sub-merchants: create platform merchants,
    merchant bank accounts and merchant persons, run KYC/identification, retrieve merchant tokens and settlement reports,
    issue platform refunds, and look up supported industries. Documented operations include CreatePlatformMerchant, CreatePlatformMerchantBankAccount,
    CreatePlatformMerchantPerson, GetPlatformMerchant, ListPlatformMerchantPerson, GetPlatformSettlementReport, GetPlatformSupportedIndustry
    and CreatePlatformRefund. Authenticated with a platform API key passed as a Bearer token.'
  humanURL: https://docs.limepay.com.au/developer-portal/platform/
  baseURL: https://api.limepay.com.au
  tags:
  - Platform
  - Marketplace
  - Onboarding
  - KYC
  - Settlement
  properties:
  - type: Documentation
    url: https://docs.limepay.com.au/developer-portal/platform/
  - type: APIReference
    url: https://docs.limepay.com.au/developer-portal/api-reference
- aid: limepay:limepay-checkout
  name: Limepay Checkout
  description: Embeddable, customisable checkout that merchants drop into a web store (with plugins for WooCommerce, Magento,
    PrestaShop and Salesforce Commerce Cloud) to accept card payments and present the pay-in-instalments (BNPL) option, controllable
    via parameters such as hidePayLaterOption. Backed by the Payments API for order creation and payment capture.
  humanURL: https://docs.limepay.com.au/developer-portal/checkout-integration/
  tags:
  - Checkout
  - BNPL
  - Embedded Payments
  properties:
  - type: Documentation
    url: https://docs.limepay.com.au/developer-portal/checkout-integration/
common:
- type: DomainSecurity
  url: security/limepay-domain-security.yml
- type: Packages
  url: packages/limepay-packages.yml
- type: SDKs
  url: packages/limepay-packages.yml
- type: Components
  url: components/limepay-components.yml
- type: Authentication
  url: authentication/limepay-authentication.yml
- type: DataModel
  url: data-model/limepay-data-model.yml
- type: Conformance
  url: conformance/limepay-conformance.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/limepay-llms.txt
- type: Website
  url: https://www.limepay.com.au/
- type: DeveloperPortal
  url: https://docs.limepay.com.au/developer-portal/
- type: Documentation
  url: https://docs.limepay.com.au/developer-portal/
- type: APIReference
  url: https://docs.limepay.com.au/developer-portal/api-reference
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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