In the future, will the card information be able to be stored in a new payment flow compatible with the 3DS?
If so, when do you expect to be able to do this, and will it be ready by March 29, 2025?
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
Additional Documentation
Strong Customer Authentication
Strong Customer Authentication
Supported Payment Methods by Country
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
Yes, the card information can be stored for future use with the 3DS flow using the Cards API. This allows you to save a credit or debit card for a customer, which can then be charged for future purchases. However, it’s important to note that customers must give their permission before their card information is saved.
As for the timeline, the Cards API and 3DS flow are already available and can be implemented right away. There’s no specific date or deadline like March 29, 2025, mentioned in the provided context.
This answer was reviewed by @Bryan-Square.
The following page states that the card cannot be saved to a file. Can it be saved without problems?
Note
Storing a card on file with the new payment flow and the STORE intent isn’t yet supported for the Beta. Instead, continue to use the existing payment flow with verifyBuyer() to store a card on file. For more information, see Store a Card on File with SCA.
We recommend using our Charge and Store a card on file with SCA. This will become the new default once it GAs. 
I want to comply with the 3DS.
The Charge and Store complies with 3DS.
Can that method be used with the new payment flow?
Yes, it can be used with the new payment flow.