Skip to main content
DELETE
/
v1
/
partner
/
card
/
users
/
{serviceId}
curl -X DELETE https://services-staging.getplu.com/api/v1/partner/card/users/acme-user-abc123 \
  -H "Authorization: Bearer sk_staging_your_api_key"

{
  "status": "success",
  "message": "success",
  "data": {
    "deleted": true
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.getplu.com/llms.txt

Use this file to discover all available pages before exploring further.

Deletes a card user. All cards belonging to the user must be terminated before deletion. Users whose KYC was denied or is still pending can also be deleted.
​
Authorization
string
required
Bearer token. Example: Bearer sk_staging_your_api_key
​
serviceId
string
required
The user’s service ID.
curl -X DELETE https://services-staging.getplu.com/api/v1/partner/card/users/acme-user-abc123 \
  -H "Authorization: Bearer sk_staging_your_api_key"

{
  "status": "success",
  "message": "success",
  "data": {
    "deleted": true
  }
}

​
Response Fields

FieldTypeDescription
deletedbooleantrue if the user was successfully deleted

​
Error Codes

CodeStatusDescription
USER_NOT_FOUND404User does not exist or belongs to another partner
ACTIVE_CARDS_EXIST409User has unterminated cards. Response includes activeCards array of card IDs that must be terminated first.

​
Fee Waiver on Re-Creation

If you delete a user and later re-create them with the same email, the KYC fee behavior depends on whether the original user was fully approved:
Original user statusRe-creation fee
approvedCharged normally
pending, pending_kyc, denied, or any other statusWaived — no KYC fee charged
The fee waiver is scoped to your partner account. If a different partner creates a user with the same email, they are always charged the full KYC fee.
When re-creating a deleted user, the new request body (name, contact details, etc.) is used — the old user data is not preserved.