4. Update Card
It is recommended to delete the registered card only through your servers (Back-End). It is not recommended to directly access your applications (End User).
Update Card
PUT
{{Base Address}}/paywall/card
Important: Card transactions are highly secure transactions. Therefore, you need to send the 'apikeyprivate' and 'apiclientprivate' parameters in the 'Header' field. CardWallAPI Address
The (HEADERS) parameters that should be sent to the service are as follows:
Parameter | Type | Required | Description |
---|---|---|---|
apikeyprivate | string | Yes | The Private Key you have obtained from the merchant panel |
apiclientprivate | string | Yes | The Private Client you have obtained from the merchant panel |
The (BODY) parameters that should be sent to the service are as follows:
Parameter | Type | Required | Description |
---|---|---|---|
RelationalId1 | string | Yes | Unique information that the card is requested to be associated with |
RelationalId2 | string | No | Unique second information to be associated with the card |
RelationalId3 | string | No | Unique third information to be associated with the card |
UniqueCode | string | Yes | Unique information (identity) of the hidden card |
Month | int | Yes | Expiry date of the stored card to be updated (Month) |
Year | int | Yes | The expiry date of the stored card to be updated (Year) |
Response
Parameter | Type | Description |
---|---|---|
ErrorCode | int | Returns '0' if the operation is successful, '1' if not |
Result | string | Returns 'true' if successful, otherwise 'false' |
Message | string | The operation reports the result message |
Body | object | If the operation is faulty, the detail object about this error |
Last updated