Delete a customer

0Gate is the primary public integration path for hosted payment, ramp, and swap experiences. Keep secret-key operations on your server and hand only browser-safe values to the widget.

Soft-delete a customer (identity) record. The record is marked deleted and stops appearing in reads, but its email and external_id stay reserved for your account. The call is idempotent — deleting an already-deleted customer returns the same shape.

Endpoint

The {id} path parameter is a customer id scoped to your account. A customer that belongs to another partner returns 404 — cross-tenant access is never 403.

Use it for

Remove a customer from your active list. After a delete, GET /v1/customers/{id} returns 404 and the record is excluded from GET /v1/customers.

Production rules

• Keep secret keys on your server. This endpoint requires an sk_* key.
• The delete is a soft-delete: the row is retained server-side and its email/external_id remain reserved, so you cannot immediately re-create a customer with the same email or external_id (that returns 409).
• The call is idempotent — a repeat delete returns the same deleted marker, so retries are safe.
• Wrap the path id in your code — the {id} placeholder is a literal customer id at call time.
• Treat examples and placeholder ids as fake data only.

Path parameters

Response

Returns 200 with a compact deleted marker — not the full customer object.

Examples

curl -X DELETE https://gate-api.0bit.app/v1/customers/67a1f3b9e4b0c10001234567 \
  -H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

{
  "id": "67a1f3b9e4b0c10001234567",
  "object": "customer",
  "deleted": true,
  "deleted_at": "2026-01-03T00:00:00Z"
}

Errors

All errors use the unified envelope and carry an X-Request-Id response header. Branch on code/type/statusCode, not on the free-form message.

{
  "type": "not_found",
  "code": "not_found",
  "message": "Customer 67a1f3b9e4b0c10001234567 not found",
  "request_id": "req_test_000000000123",
  "doc_url": null,
  "statusCode": 404
}

Public boundary

This reference covers partner-scoped endpoint behavior, authentication, idempotency, webhook verification, and support-safe records. Internal operations, administrative routes, and unsupported availability claims are outside the public API contract.

Related pages