Acknowledgements & Consents

Acknowledgements let you capture a customer's explicit consent during a purchase or account change — for example agreeing to Terms of Service, a Privacy Policy, Auto-Pay, Payment Terms, or a stored-credential mandate (to meet payment requirements such as 3DS2).

Why it matters

Consents create an auditable record that a customer agreed to your terms at the moment of purchase. That record is both a compliance safeguard (proving terms were presented and accepted) and a payment requirement: card networks and 3DS2 expect an explicit stored-credential acknowledgement before a card can be saved and reused for future charges. Without it, recurring billing and one-click purchases may be declined.

How it works

Consents are presented as part of the buying flow: the customer checks a box to agree before the order completes, and the agreement is recorded against their account. You add and configure consent capture on the relevant pages and journey steps, so each flow shows exactly the acknowledgements it needs.

How to use it

1. Decide which acknowledgements a flow requires (T&C, Auto-Pay, stored-credential, etc.).

2. Add the consent capture to the appropriate page or journey step.

3. Confirm the box must be checked before the order can complete.

Gotchas

• A required acknowledgement should block order completion until accepted — otherwise you lose the auditable record.

• The stored-credential acknowledgement is tied to saving a payment method for reuse; see Stored-Credential Acknowledgement for how it pairs with stored-credential transactions.