3. Delete Card

It is recommended to perform the process of deleting a saved card only through your servers (Back-End). Direct access from your applications (End User) is not advised.

Delete Saved Card

DELETE {{Base Adres}}/paywall/card/insurance

Important: Card transactions are high-security operations. Therefore, you must send the 'apikeyprivate' and 'apiclientprivate' parameters in the 'Header' section.

CardWallAPI Address

The parameters to be sent to the service (HEADERS) are as follows:

Parameter	Type	Compulsory	Description
apikeyprivate	string	Yes	The Private Key obtained from the merchant's admin panel.
apiclientprivate	string	Yes	The Private Client obtained from the merchant's admin panel.

The parameters to be sent to the service (BODY) are as follows:

Parameter	Type	Compulsory	Description
RelationalId1	string	Yes	The unique information associated with the card.
RelationalId2	string	No	The second unique information associated with the card.
RelationalId3	string	No	The third unique information associated with the card.
UniqueCode	string	Yes	The unique information (identity) of the saved card.

JSON

{
    "RelationalId1": "1000923",
    "RelationalId2": "",
    "RelationalId3": "",
    "UniqueCode": "921245xQN85D0+Zuf7oAJv5@@@@@G86eN7RA4cX8L4hHo7Ma3hg7AW7Bq232yPyw2iVPkrt1qEw=="
}

The parameters returned by the service are as follows:

Parameter	Type	Description
ErrorCode	int	Error code. If the transaction is successful, it returns the value '0'.
Result	bool	It returns a true or false value. If the transaction is successful, it returns the value 'true'.
Message	string	If the transaction is erroneous, this is the message related to the error, and it provides language support based on the locale parameter.
Body	object	If the transaction is erroneous, this is the detailed object related to the error.

JSON

{
    "ErrorCode": 0,
    "Result": true,
    "Message": "",
    "Body": null
}