I have few missing spots of information when it comes to storing card on file.
Here is my usage of it.
When user fills a form he is required to enter his card information using web payments sdk, the token (nonce) is generated and is sent to the backend. We will not make a payment in the first 30 days (or even 60 days) of when the user has entered his information on his card, or there is a possibility that we won’t make payment at all based on customers action. The customer is notified about this and it’s very clear if he will get charged, when entering his card information on UI.
I have found that only Card on File has a possibility to make a payment latter than 7 days.
My questions are:
- How long will the card on file be valid for, does it expiry date (different one from the expiration date on the card)?
- Since we are generating one-time-use payment token, does that mean that the card will be valid for only one payment and then will be inactive? And if the card becomes inactive does that mean the card is removed from the customer, when will it be removed?
- Since the charging of the card will be in ~30 days and we have the amount that needed to be charged, is there a way to display that information on our frontend using square (open a some square pop up that is security compliant and on FE make the payment and complete or decline the payment when the appropriate time comes).
- And what’s the workflow here, if the payment is created and 7 days are passed from the cration and the payment becomes inactive (ref: https://developer.squareup.com/docs/payments-api/take-payments/card-payments/delayed-capture?preview=true) how to reactivate it?
- Is there a possibility to first create payment and after x days (x > 30) to complete the payment.
Thank you for your time, looking forward to hearing from you!