Card Storage
Card storage feature provides a secure and convenient solution for managing payment card information, allowing users to securely save and manage card details for future transactions.
You can create a user and a card linked to that user in iyzico without creating a payment. Or, using the same endpoint, you can add a new card to an existing user. Request parameters differ between the two variants. Both request bodies and JSON examples are provided below.
Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.
Media type of the request body.
application/jsonSuccessful response
Invalid request / validation error
Sample Codes
You can list the cards that belong to a user in iyzico.
Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.
Media type of the request body.
application/jsonRequest to list stored cards.
Response language. Default tr.
enPossible values: Correlation ID sent for request/response matching.
23233333User key whose cards will be listed.
6abd3f19-8305-d0c9-09e2-0300b5516a38Successful response — Card list
Invalid request / validation error
Sample Codes
Deletes a card that belongs to a user created in iyzico.
Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.
Media type of the request body.
application/jsonRequest to delete a stored card.
Response language. Default tr.
enPossible values: Correlation ID sent for request/response matching.
123456789User key of the stored card.
6abd3f19-8305-d0c9-09e2-0300b5516a38Token of the card to be deleted.
c80ba376-8250-f819-88c9-94984710e72cSuccessful response
Invalid request / validation error
Sample Codes
After card storage, you can send a “NON3D or 3DS” payment request using the returned cardUserKey and cardToken. Unlike a standard payment request, card details are sent via cardUserKey and cardToken. Suitable for one-click payments or subscription cycles. Example below shows NON3D.
Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.
Media type of the request body.
application/jsonRequest to NON3D payment using a stored card.
Language code. Default; tr
enPossible values: Unique ID for request/response correlation.
conversationIdTotal amount to be charged from the customer.
1Basket total amount.
1Installment count. If omitted, single installment (1) is used.
1Possible values: Payment channel.
WEBPossible values: Basket ID.
B67832Payment group. Default; PRODUCT.
PRODUCTPossible values: Currency. Default; TRY.
TRYPossible values: Successful response — payment captured
Invalid request / validation error
Sample Codes
Last updated
