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.

circle-info

If you want to store the card during the payment process, simply send the registeredCard parameter as 1 in NON3D or 3DS payment requests.

Create User and Card

post

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.

Header parameters
AuthorizationstringRequired

Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.

Content-TypestringRequired

Media type of the request body.

Example: application/json
Body
or
Responses
post
/cardstorage/card

Sample Codes

List Stored Cards

post

You can list the cards that belong to a user in iyzico.

Header parameters
AuthorizationstringRequired

Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.

Content-TypestringRequired

Media type of the request body.

Example: application/json
Body

Request to list stored cards.

localestring · enumOptional

Response language. Default tr.

Example: enPossible values:
conversationIdstringOptional

Correlation ID sent for request/response matching.

Example: 23233333
cardUserKeystringRequired

User key whose cards will be listed.

Example: 6abd3f19-8305-d0c9-09e2-0300b5516a38
Responses
post
/cardstorage/cards

Sample Codes

Delete a Stored Card

delete

Deletes a card that belongs to a user created in iyzico.

Header parameters
AuthorizationstringRequired

Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.

Content-TypestringRequired

Media type of the request body.

Example: application/json
Body

Request to delete a stored card.

localestring · enumOptional

Response language. Default tr.

Example: enPossible values:
conversationIdstringOptional

Correlation ID sent for request/response matching.

Example: 123456789
cardUserKeystringRequired

User key of the stored card.

Example: 6abd3f19-8305-d0c9-09e2-0300b5516a38
cardTokenstringRequired

Token of the card to be deleted.

Example: c80ba376-8250-f819-88c9-94984710e72c
Responses
delete
/cardstorage/card

Sample Codes

Crate Payment with Stored Card (NON3D)

post

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.

Header parameters
AuthorizationstringRequired

Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.

Content-TypestringRequired

Media type of the request body.

Example: application/json
Body

Request to NON3D payment using a stored card.

localestring · enumOptional

Language code. Default; tr

Example: enPossible values:
conversationIdstringOptional

Unique ID for request/response correlation.

Example: conversationId
paidPricedecimalRequired

Total amount to be charged from the customer.

Example: 1
pricedecimalRequired

Basket total amount.

Example: 1
installmentinteger · enumOptional

Installment count. If omitted, single installment (1) is used.

Example: 1Possible values:
paymentChannelstring · enumOptional

Payment channel.

Example: WEBPossible values:
basketIdstringOptional

Basket ID.

Example: B67832
paymentGroupstring · enumOptional

Payment group. Default; PRODUCT.

Example: PRODUCTPossible values:
currencystring · enumOptional

Currency. Default; TRY.

Example: TRYPossible values:
Responses
post
/payment/auth

Sample Codes

Last updated