Can customers save a card during an application and manage it later?

Yes. Use embedCardForm() to collect a card during onboarding or a custom application, and embedPaymentMethods() for an account-page manager. Both packages support them; the DOM Package requires 1.12.0 or newer. Hosted Package containers can use data-tiquo-embed="card-form" or data-tiquo-embed="payment-methods".

To keep the saved card on the customer completing your application, verify the email from your form through sendOTP() and verifyOTP() before opening the embed, then use that signed-in session for profile updates and the card step. The embed reuses the website session. A visitor without a session gets an email-code sign-in inside the embed.

Card details stay inside Tiquo's secure Stripe iframe. Your page receives display details such as brand, last four digits, expiry, and the payment method ID. You do not need a separate card-entry integration. Saving a card does not itself assign a membership or charge it.

Use getPaymentMethods(), setDefaultPaymentMethod(), and removePaymentMethod() for a custom list. The last saved method cannot be removed. Removing a card used by an active membership requires another saved method to replace it; changing the default alone preserves existing memberships' payment methods.

See DOM saved cards and Hosted saved cards.