Skip to main content
When a merchant customer pays with a card through Payluk’s inline checkout, Payluk tokenizes the card: it stores the card’s reusable payment authorization against that customer. The tokenized card then shows up here, and its id can be passed as depositDetails.cardId to Create payment intent (transactionType: deposit) to top up the wallet without the customer re-entering card details. This group lets you list and remove those saved cards. All routes act on a specific customer, so they need the customer-id header.
Saving cards is a gated feature: it must be enabled on your merchant account. If it isn’t, cards are never tokenized and these routes return 403 (“This feature is not enabled on your merchant account”).

​
Endpoints