Capture Payment Details
The customer enters an eligible payment method through the configured payment flow.
Build repeat-payment experiences around secure payment references instead of asking returning customers to enter their payment details every time.
Support recurring billing, saved payment methods, faster checkout and centralized customer payment profiles through a vault architecture connected to your approved payment environment.
2 saved payment methods
Token: tok_••••8A21
Token: bank_••••29B4
A customer vault allows an approved payment environment to associate a reusable payment reference with a customer profile.
Your application can work with that payment reference for future eligible transactions instead of requiring the merchant system to retain the complete payment credential.
The customer enters an eligible payment method through the configured payment flow.
The payment environment returns a reusable token or other supported payment reference.
Future eligible payments can reference the stored payment method without requiring the customer to enter all details again.
Payment information submitted.
Reusable payment reference generated.
Payment reference associated with customer.
Stored payment reference reused.
Use reusable payment references and customer payment profiles to support the billing models that require customers to pay more than once.
Work with supported payment tokens or references instead of storing complete payment credentials directly within merchant applications.
TOKENIZATIONAssociate supported card or bank-payment references with a customer profile for eligible future transactions.
PAYMENT METHODSUse eligible vaulted payment methods for subscriptions, memberships, installment plans and other repeat-payment workflows.
REPEAT BILLINGOrganize multiple supported payment methods around one customer account and maintain a preferred payment method when available.
PROFILE MANAGEMENTReturning customers can select an existing eligible payment method rather than entering all payment information again.
CUSTOMER EXPERIENCEWhere supported, payment-method lifecycle services can help maintain stored card references as credentials change.
ACCOUNT UPDATESReturning customer
Default payment method
Saved payment method
Saved bank reference
A customer may use more than one eligible payment method across the relationship with your business.
A vault can associate those reusable references with one customer profile, making it easier to support preferred payment methods, future purchases and repeat billing.
Saved payment methods can support many customer journeys where payment credentials need to be reused after the initial transaction.
Let returning customers select an eligible saved payment method rather than entering complete payment details again.
Reference an eligible stored payment method for scheduled subscription or membership transactions.
Use approved stored payment references across installment or scheduled-payment arrangements.
Give eligible customers a consistent payment profile across future purchases or service interactions.
Tokenization can help separate the payment credential from the reference used by your business application.
The exact impact on PCI responsibilities and security scope depends on how your checkout, gateway and vault are implemented, so the architecture should be reviewed as part of your payment setup.
Stored-card relationships can be affected when a customer's underlying card expires or is replaced.
Where supported by the configured provider, account-updater or network-token services may help maintain usable payment references without forcing the customer to manually re-enter card information every time a card changes.
Monitor payment-method lifecycle where supported by your provider.
Supported updater services may help maintain recurring-payment continuity.
Keep merchant workflows built around a reusable payment reference.
Continue using eligible stored methods across approved future transactions.
Vault functionality can sit behind checkout, subscriptions, customer accounts and billing workflows depending on your payment-provider and integration architecture.
Save eligible payment methods as part of an approved online checkout flow.
Associate payment references with customer-management workflows.
Use eligible stored methods for recurring-payment workflows.
Connect supported vault functions through your payment integration layer.
Vaulting can support industries where customers purchase repeatedly, maintain ongoing accounts or use subscription and membership models.
Saved payment methods for eligible returning online customers.
Reusable payment references for eligible gaming payment environments.
Payment profiles for eligible memberships and repeat treatments.
Saved payment references for eligible repeat patient-payment workflows.
Payment profiles for eligible repeat pharmacy transactions.
Stored-payment workflows for eligible recurring virtual-care relationships.
Start by identifying how customers pay today, where repeat payments occur and how your existing checkout or billing system should interact with the vault.
Identify checkout, recurring billing, memberships and other repeat-payment use cases.
Determine how supported payment references should connect to your customer accounts.
Connect eligible gateway, API, checkout or billing workflows to supported vault functions.
Begin creating eligible payment references and using them within approved customer flows.
Learn more about payment references, stored payment methods, recurring billing and customer profiles.
Ask Our TeamA customer vault is payment infrastructure that can store supported payment credentials within the configured payment environment and provide a reusable reference for future eligible transactions.
Tokenization replaces or references sensitive payment information using a non-sensitive identifier that can be used by supported payment workflows instead of directly using the complete credential.
Where supported, eligible vaulted payment methods can be referenced for subscriptions, memberships, installment arrangements and other repeat-payment models.
Depending on the vault and integration, a customer profile can support multiple payment references and may allow one method to be treated as the preferred option.
Saved payment references can support faster checkout experiences by allowing eligible returning customers to select an existing payment method rather than entering complete payment details again.
No. Tokenization and hosted payment infrastructure may help reduce direct handling of sensitive payment data, but a merchant's PCI responsibilities depend on the complete payment architecture and implementation.
Some payment environments support account-updater or network-token lifecycle services. Availability depends on the card networks, providers and payment configuration being used.
Integration depends on your payment provider. Supported vault functions may be accessed through a gateway, API, hosted checkout or other approved integration method.
Talk to Zenith Transact about payment tokenization, customer profiles, recurring billing and saved-payment workflows built around your existing payment infrastructure.