Merchant API reference
The REST API your servers call to take payments, manage customers and send money from your Paysio account.
The Merchant API is the REST API for running a Paysio business from your own code. Your servers use it to create products and checkout sessions, charge cards, manage customers and subscriptions, send payouts, and read transactions and disputes.
Each API key belongs to one workspace, and every request acts on that workspace. GET /account tells you which one.
Base URL
Every endpoint is relative to this base URL. Live and test keys both use it.
https://paysio.com/api/v1Authentication
Send an API key as a Bearer token in the Authorization header. Create keys in the dashboard under Settings, then API Keys.
curl https://paysio.com/api/v1/products \
-H "Authorization: Bearer sk_test_your_api_key"- Secret keys (
sk_live_,sk_test_) are for your server. Writes need one. Never put a secret key in client code. - Publishable keys (
pk_live_,pk_test_) are read-only and are the ones to use client-side. - Test keys use sandbox data and never move real money.
Read Authentication for the details and Testing data for sandbox cards.
Responses
Every successful response wraps its result in a data key. A list adds has_more and pages with limit and starting_after. Amounts are integers in cents.
// One object
{ "data": { "id": "...", ... } }
// A list
{ "data": [ ... ], "has_more": true }Errors carry a JSON body with error, type and, where one applies, code. Branch on type, not on the wording. See Errors, Pagination and Rate limits.
Resource groups
Getting started
Payments
Checkout
Customers
Billing
Products
Orders
Payouts
Related
- To take card details in a browser or an app, use Paysio.js or the Mobile SDK. Your server still calls this API with a secret key.
- Apps built for the Paysio dashboard sign in with their own access token and have their own App Endpoints. A merchant API key cannot call those.