API reference
Payments
Every successful charge — from a payment link, invoice, subscription, or widget — lands as a Payment row. The list endpoint is the canonical way to reconcile your books against the dashboard. Creating new payments goes through the hosted-checkout flow rather than a direct POST (PCI compliance).
List payments
GET
/v1/paymentsscope: payments:readCursor-paginated, newest first. Filter by status / method / customer; search by partial provider reference, payment id, or description.
Query parameters
statusstring | Filter by status. One of: |
methodstring | Filter by payment method. One of: |
customerIdstring | Filter to payments attached to a single customer. |
qstring | Search across id, providerRef, description. |
cursorstring | Pagination cursor (bare UUID from the previous response's nextCursor). |
limitnumber | 1–100, default 20. |
curl "https://baynoy.com/api/v1/payments?status=succeeded&limit=20" \ -H "Authorization: Bearer sk_test_…"
Response
{
"ok": true,
"data": {
"items": [
{
"id": "8f7e6d5c-4b3a-2918-7654-3210fedcba98",
"amount": "2000",
"currency": "CHF",
"feeAmount": "228",
"netAmount": "1772",
"status": "succeeded",
"method": "card",
"cardBrand": "visa",
"cardLast4": "4242",
"description": "Consulting fee",
"customer": {
"id": "a1b2c3d4-5e6f-7890-abcd-ef1234567890",
"name": "Acme Industries",
"email": "[email protected]"
},
"availableOn": "2026-05-29T00:00:00.000Z",
"createdAt": "2026-05-27T12:34:56.789Z"
}
],
"nextCursor": null,
"hasMore": false
}
}