Payments and Vault

Payment methods, token coverage, payment orders, recurring agreements, disputes, and settlement

Payment Surfaces

Surface	Primary users	Purpose
Account or Contact Add Payment Method	Sales, finance, support	Save customer payment method and gateway tokens.
Sales Order payment console	Sales, finance	Review saved methods, route readiness, payment orders, and collection actions.
Payment Operations app	Finance, payment admins	Work payment orders, attempts, receipts, transactions, disputes, gateways, and settlement.
Payment Gateway Connections	Payment admins	Manage active/deprecated/removed gateways and successor migrations.

Token Coverage

Payment readiness is route-specific. A customer may have a saved method but still require retokenization if the method does not have a valid token for the order route or gateway.

Do not tell a customer to re-enter a card until the app indicates a new payment method is required. If the state is retokenization required, an admin should resolve the gateway/token migration path.

Payment Orders

Payment Orders group collection intent and lines. They can be created from Sales Orders and worked in Payment Operations. Use Payment Order actions to send payment links and print payment order PDFs.

Recurring Agreements

Recurring plans are managed through Payment Agreement records and Sales Order actions. Supported lifecycle actions include pause, resume, cancel, print agreement PDF, and manage recurring plan.

Disputes, Refunds, Voids, and Settlement

Disputes should be recorded from Payment Order actions. Refunds, voids, fees, settlement batches, processor events, and transaction accounting should stay tied to the Payment Transaction and settlement records so finance reports can reconcile gateway activity.

Admin Safety

Gateway deactivation requires a successor and associated record migration plan. Never edit a gateway identity in place when historical tokens or transactions still point to it.