Paying.co Documentation

Documentation that gets you to the first call quickly.

Quick-starts, API guides, SDK links, authentication patterns and product references for AskPay, Landed and Puny — organized around the work developers actually need to complete.

Start with a quick-start → Browse APIs →

AskPay · Landed · Puny · SDKs · MCP · Status · Changelog

docs.paying.co

// every product starts the same way
Authorization: Bearer $PAYING_KEY
Content-Type: application/json

sandbox → test end to end
live → switch credentials when ready

01 · Quick starts

Choose the thing you want to build.

Create a payment link

Authenticate, create a hosted link, choose QR/email/SMS delivery and handle a paid webhook.

Generate a website

Send a prompt or template ID, receive a site, modify it and publish when ready.

Create a secure share

Create an expiring or password-protected link, or use a one-time capsule for sensitive content.

02 · API guides

Guides before reference tables.

Each API section explains the workflow first, then links into endpoint-level reference.

AUTH

Authentication

Bearer keys, sandbox/live separation and safe credential handling.

WEBHOOKS

Event handling

Signature verification, retries, idempotency and reconciliation patterns.

ERRORS

Error model

Consistent status codes, request IDs and retry guidance.

03 · SDKs

Use REST directly or install a maintained library.

Official SDKs live under the PayingCo GitHub organization with install instructions and first-request examples.

ASKPAYaskpay-sdks LANDEDlanded-sdks PUNYpuny-sdks

LANGSNode.js · Python · PHP · Go · Ruby

04 · Developer resources

Reference when you need it. Status when something breaks.

API Reference

Complete endpoint and field-level documentation.

MCP

MCP Servers

Use Landed, Puny and Ask from compatible AI clients.

System Status

Live uptime and incident history.

What shipped

Versioned product updates and breaking changes.