Delete payments
DELETE https://datafa.st/api/v1/payments
Delete payment and free-trial records by transaction ID, visitor, or time range. Filters are evaluated in priority order: transaction ID first, then visitor, then bulk time range.
For bulk deletes without a transaction or visitor,
start and end are required (this endpoint uses start/end, not startAt/endAt).Related: Revenue attribution
Request
Query parameters
websiteIddft_ account token on Website API routes. Omit with a df_ website key. Example: ?websiteId=665f0b3c4d2e1a0012345678.transaction_id / tx_id"txn_abc123". Re-posting the same ID returns a duplicate message, not a second payment.datafast_visitor_iddatafast_visitor_id cookie or tracking script. Example: "a3ab2331-989f-4cfa-91c6-2461c9e3c6bd". Alias: visitorId on some endpoints.startstart=2026-05-01T00:00:00Z&end=2026-05-19T23:59:59Z. Required together when no other filter (transaction, visitor, or goal name) is provided. Note: uses start/end, not startAt/endAt.endstart for bulk deletes.Example queries
By transaction:
DELETE /api/v1/payments?transaction_id=txn_abc123
Bulk by date range:
DELETE /api/v1/payments?start=2026-05-01T00:00:00Z&end=2026-05-19T23:59:59Z
Response
Returns a JSON object with
status: "success" and endpoint-specific fields in data (and pagination when the endpoint is paginated).Response fields
statussuccess.data[].messagedata[].transaction_iddata[].datafast_visitor_iddata[].timeRange.startdata[].timeRange.endAuthentication
df_website API key: The website is inferred from the key. You do not need awebsiteIdquery parameter.dft_account token: Requirespayments:writepermission and?websiteId=on every request. The token must be allowed to access that website.
Read authentication and scopes for token creation, permission lists, and scoped tokens.
Errors
400 — No filter provided, invalid visitor ID, or missing
start/end for bulk delete.404 — Transaction not found.
See API errors for the standard error envelope, auth failures, validation errors, permission errors, and rate limits.