Skip to main content
Documentation

Domain

Payments capabilities

8 capabilities, all acting on a payment. A reference to one from another domain is spelled payment_id — never a bare id — and every one of those fields names the capability that produces it, so a model can chain calls without guessing.
CapabilityWhat it doesEffect
payments.listPOST /api/v1/payments/listList payments the shop has taken, by invoice, customer or dateread-only
payments.getPOST /api/v1/payments/getGet one payment record and what is left of itread-only
payments.deposit_statusPOST /api/v1/payments/deposit_statusCheck which booked jobs still owe their deposit paymentread-only
payments.accepted_methodsPOST /api/v1/payments/accepted_methodsCheck which payment methods this shop accepts from a customerread-only
payments.payout_summaryPOST /api/v1/payments/payout_summaryCheck the shop's card balance and its recent payments outread-only
payments.tips_collectedPOST /api/v1/payments/tips_collectedTotal the gratuities the shop's payments carried in a periodread-only
payments.disputesPOST /api/v1/payments/disputesList the chargebacks disputing payments this shop tookread-only
payments.disputePOST /api/v1/payments/disputeGet the chargeback on one payment and its evidence deadlineread-only

← Every domain