PayLioDocs

API Reference

API Overview

A small REST API: one endpoint creates a checkout, one checks its status, and a webhook tells you when it is paid.

Base URL#

https://paylio.org/api/v1

All requests use HTTPS. Request and response bodies are JSON.

Authentication#

Create an API key in Dashboard › API Keys. Keys start with plio_live_. Send the key in one of these headers:

HTTP headers
Authorization: Bearer plio_live_YOUR_KEY
# or
X-API-Key: plio_live_YOUR_KEY
  • The full key is shown only once, when you create it. PayLio stores only a hash.
  • You can have up to 10 active keys. Use one per integration so you can revoke them separately.
  • Every key inherits the fees, wallet and providers of your account.

Keep keys on your server

Never put an API key in browser JavaScript, a mobile app or a public repository. If a key leaks, revoke it in the dashboard and create a new one.

Endpoints#

MethodPathPurpose
POST/api/v1/walletCreate a card checkout
GET/api/v1/payment-statusGet a payment's status

Integration flow#

StepWhat you do
1. CreateCall POST /wallet and store payment_id and ipn_token on your order.
2. RedirectSend the customer to checkout_url.
3. ReceiveVerify the payment.paid webhook signature with the stored ipn_token.
4. ConfirmCall GET /payment-status and fulfil the order only if status is paid.

Rate limits#

EndpointLimit
POST /wallet60 requests per minute per API key
GET /payment-status120 requests per minute per API key

When you exceed a limit you get 429 with a Retry-After header. See Errors & Rate Limits.

Reference#

Create CheckoutParameters, response and examples in four languages.Payment StatusVerify payments server-to-server.WebhooksEvents, payload and signature verification.ProvidersProvider IDs, minimums and direct links.Errors & Rate LimitsStatus codes, error codes and retry advice.