Delete saved card

Deletes a saved card of pg_user_id: the token can no longer be used for payments and payouts.

Works for all saved cards, including cards saved by Save card for payouts.

Request flow

Result

Response	Meaning	Next step
`card` with `pg_status = deleted`	The card is deleted.	—
`pg_status = error`	The request is rejected.	See «Errors» below.

Errors

The error is returned in pg_error_code and pg_error_description; the HTTP status depends on the error. Error responses are not signed.

HTTP	`pg_error_code`	When	What to do
`200`	`0`	A parameter is missing or invalid: `pg_error_description` names it.	Fix the request.
`401`	`1100`	The signature is missing or invalid.	Check the signature: see Merchant API Overview.
`404`	`1804`	The client has no saved card with this token, or the card is already deleted.	Check `pg_card_token` and `pg_user_id` with Get saved cards.

Request example

Required fields only. pg_sig is calculated with the secret key test_secret_key.
Line breaks in the body are added for readability: send the body as one line.

Responses

🟢200Success

application/xml

Bodyapplication/xml

Example

<?xml version="1.0" encoding="utf-8"?>
<response>
    <card>
        <pg_status>deleted</pg_status>
        <pg_merchant_id>13991</pg_merchant_id>
        <pg_card_id></pg_card_id>
        <pg_card_hash></pg_card_hash>
        <deleted_at>2026-10-25 15:58:33</deleted_at>
    </card>
    <pg_salt>65Wt4EXE</pg_salt>
    <pg_sig>543e6710ec78ef5a717af565d1aa6873</pg_sig>
</response>

🟢200Error

🟠401Unauthorized

🟠404Not Found

Request flow#

Result#

Errors#

Request example#

Request

Responses

Request flow

Result

Errors

Request example