Introduction
Take payments from customers around the world with a few API calls. Lollipay hosts the checkout, handles tax and fraud, and pays you out.
Lollipay is the merchant of record for software companies. Your server asks Lollipay for a checkout session, your customer pays on a page we host, and we send them back to your site. Cards, local payment methods, sales tax, VAT, fraud screening and disputes are handled on our side.
How a payment flows
Your server creates a checkout session with the line items and the URL to return to.
POST /v1/stores/{storeId}/checkouts answers with a checkout_url.
You redirect the customer to checkout_url. The page shows your store name, the items and the total, and takes
the payment.
The customer lands on your return_url with ?checkout_id=cs_… added. Your server retrieves the session and
fulfils the order once status is complete.
What you need
- A Lollipay account. Sign up and finish onboarding to get a store.
- An API key from Dashboard → Developers → API keys. Start with a test key: test sessions are paid with test cards and never move money.
- Your store ID, shown on the same page. It goes in every API path.
Quickstart
Create and pay your first test checkout in five minutes.
Authentication
Bearer keys, or HMAC-signed requests that never send the secret.
Accept a payment
Line items, return URLs and confirming payment on your server.
API reference
Every endpoint, with a playground to send real test requests.
Basics
| Base URL | https://api.lollipay.cc/v1 |
| Format | JSON in, JSON out. Send Content-Type: application/json. |
| Amounts | Integers in minor units: 4900 is $49.00, 1500 is ¥1,500. |
| Modes | The key decides: lp_test_sk_… keys work in test mode, lp_live_sk_… keys in live mode. |
| Responses | Successes are { "ok": true, "data": … }, failures are { "ok": false, "error": … }. |
Lollipay's API is versioned in the path. Additive changes, like new fields in a response, ship to v1 without notice,
so ignore fields you don't recognise. Breaking changes get a new version.