DailyAPI Documentationv1
Resources

Payments

Retrieve recorded payments without sensitive card, bank, or provider transaction data.

View OpenAPI

Permission: תשלומים (payments:read)

OperationPath
ListGET /payments
RetrieveGET /payments/{id}

The list supports limit, cursor, created_after, updated_after, and only status=recorded. Search is not supported. Results sort by updated_at descending and then ID descending.

set -euo pipefail
: "${DAILY_API_KEY:?DAILY_API_KEY is required}"
curl --fail-with-body --silent --show-error \
  --header "Authorization: Bearer ${DAILY_API_KEY}" \
  --header 'Accept: application/json' \
  'https://api.godaily.co.il/v1/payments?status=recorded&limit=100'
{
  "id": "9eaf89fa-dc55-4130-ac85-598f8a5430c5",
  "object": "payment",
  "document_id": "813d0b3f-ab6c-43d4-9173-8f224566ba2f",
  "customer_id": "44f34dad-a427-4c65-ae26-b0a43f8f65f7",
  "amount_minor": 218300,
  "currency": "ILS",
  "payment_method": "bank_transfer",
  "payment_date": "2026-07-20",
  "status": "recorded",
  "created_at": "2026-07-20T09:15:00.000Z",
  "updated_at": "2026-07-20T09:15:00.000Z"
}

Payment methods normalize to card, cash, bank_transfer, check, paypal, or other. The API deliberately omits provider transaction IDs, card digits or tokens, CVV, and bank account details. customer_id can be null if the safe business relationship cannot be established.

Direct browser request

API playground

Memory only

Your key stays only in this React page’s memory and is sent directly to Daily API. It is not persisted, placed in a URL, logged, or sent to analytics. Refreshing or closing this page clears it.

GEThttps://api.godaily.co.il/v1/payments

Record and correct payments

Receipt payments are recorded through POST /documents with receipt_payments and documents:write. The CreateReceiptPaymentDto schema covers supported payment methods. Payments stay linked to the document that created them; corrections use a linked document according to its lifecycle.

Supplier payments and expense refunds are managed separately under /expense-payments with expenses:read and expenses:write. You can create a payment, allocate it to expenses, and record a reversal event. A recorded financial event cannot be edited or physically deleted. See expenses and payments.

All request and response fields · Write and deletion rules

On this page