# Card-on-file for terminal chip/nfc cards **URL:** \ **Category:** Feature Requests\ **Tags:** terminal-api\ **Created:** [August 4, 2022, 2:09am UTC](https://developer.squareup.com/forums/t/card-on-file-for-terminal-chip-nfc-cards/6685 "2022-08-04T02:09:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![martini](https://avatars.discourse-cdn.com/v4/letter/m/bc79bd/32.png) [@martini](https://developer.squareup.com/forums/u/martini)\ **Post date:** [August 4, 2022, 2:09am UTC](https://developer.squareup.com/forums/t/card-on-file-for-terminal-chip-nfc-cards/6685/1 "2022-08-04T02:09:14Z")
If I read the Terminal API correctly, it’s currently not possible to do a checkout with the following scenario: 1. Accept a payment with the terminal 2. Later charge the card again (e.g. for damages). This is a very common scenario for a lot of rental companies. Instead, the user will have to: 1. Accept a payment with the terminal 2. Make an authorization for damages. The issue with this approach is there is a ceiling for the damages and this ceiling may be higher than some customers card limit. A slightly better approach is allow the application to re-use the card in step 1 (assuming it’s not a wallet) as a card on file, so additional charges (requested by the customer) or damage charges (according to damage charge agreement) can be charged to the same card. ---
**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\ **Post date:** [August 4, 2022, 4:06pm UTC](https://developer.squareup.com/forums/t/card-on-file-for-terminal-chip-nfc-cards/6685/2 "2022-08-04T16:06:56Z")
This use case is possible today. You can accept a payment with the Terminal and with the Cards API you can [save the card on file with the `payment_id`](https://developer.squareup.com/docs/cards-api/walkthrough-seller-card) to later charge the card on file if needed. 🙂