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 is listed with 3 APIs on the APIs.io network. Tagged areas include Payments, Australia, Buy Now Pay Later, Payment Gateway, and Checkout.
Limepay’s developer surface includes authentication, documentation, API reference, and 10 more developer resources.
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/.
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/limepay/"><img src="https://apis.io/badge/limepay/card.svg" alt="Limepay 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):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
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.
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...
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...
Embeddable, customisable checkout that merchants drop into a web store (with plugins for WooCommerce, Magento, PrestaShop and Salesforce Commerce Cloud) to accept card payments ...
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-11-06'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
x-docs-platform: redocly
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Payments
- Australia
- Buy Now Pay Later
- Payment Gateway
- Checkout
- Embedded Payments
- White Label
- Card Payments
- Marketplace
- Instalments
tags_raw:
- 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
- Buy Now Pay Later
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
- Buy Now Pay Later
- Embedded Payments
tags_raw:
- 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
Limepay API — frequently asked questions
Does Limepay have an API?
Yes. APIs.io lists 3 APIs from Limepay, including Limepay Payments API, Limepay Platform API and Limepay Checkout.
How do I authenticate with the Limepay API?
Limepay uses bearer-token authentication (3 schemes). The details are profiled on APIs.io as Limepay Authentication.
Is the Limepay API ready for AI agents?
Limepay has a Kin Score of 11.1 out of 100 (emerging) and an Agent Readiness score of 3.4 (human-only), scored by API Evangelist on 2026-11-06.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: