Deletion and erasure
Deleting a customer erases their personal data at once. What it removes, what it keeps, and what cannot be undone.
Deletion is not the reversible archive it is on most resources.
https://api.wajub.com/customers/{id}The record is removed from your lists and its personal data is anonymised immediately, in the same
request, to satisfy a right-to-erasure demand without a second step. The anonymised record stays in
the Dashboard's deleted customers until someone on your team deletes it for good. A full copy is
kept in an archive for 120 days, then permanently deleted. Past payments survive, since they are
financial records: their customer details are pseudonymised, and they keep the wallet or account
number they were paid with. The customer.deleted event carries the anonymised record, and the
customer's details are removed from the events and webhook deliveries already recorded. A repeated
call answers the same 200, and finishes an erasure an earlier call left incomplete. With X-Sync
the call answers 403: a platform does not erase a merchant's customers. Deleting a
payer lists everything it removes.
There is no undo through the API
The API has no restore endpoint. The Dashboard can restore the record, but the personal data does not come back with it: it was anonymised in the delete request. Deactivate rather than delete when you simply want a customer out of the way.