Delegated payment
What is delegated payment
in luxury retail?
A governed practice where an authorised operator — a Client Advisor or Store Manager — triggers a card charge on behalf of a VIP client who has given prior consent. The client does not need to be present at the moment of payment.
I.Why the practice exists
In luxury retail, the relationship between a Maison and its most valued clients is built on continuity and trust. A VIP client does not shop in the same way as the general public. They have a dedicated advisor who knows their preferences, anticipates their needs, and acts — sometimes before the client has even seen the item.
Consider a few common scenarios:
- A piece is reserved during a trunk show. The client is travelling. The advisor confirms the purchase on their behalf and arranges delivery.
- A wardrobe selection is sent to a client's home for fitting. The client keeps three pieces. The charge is applied to the agreed items after the return.
- A client calls their advisor to buy a specific item before it sells out. The advisor acts immediately, confirms by message, and the client never visits the boutique.
These are not edge cases. For the most valued clients — often only a few hundred per Maison per country, but with exceptional purchasing power — this is the expected mode of service.
II.Why the infrastructure must catch up
The problem is not the intent. The problem is how it is executed today.
Across many luxury Maisons, delegated payment relies on practices that were designed for a pre-digital world:
- Paper consent forms — The client signs a document authorising future charges, stored in the boutique, sometimes in a safe.
- Card details stored locally — A photo of the client's card, or the card number written by hand, kept in a file or drawer.
- Manual terminal entry — The advisor types the card number into the terminal. The card is not physically present. The client is not present.
Each of these creates exposure: PCI DSS requires card data not be stored in readable form outside secure environments; GDPR requires a documented legal basis for storing personal payment data; internal audit cannot reconstruct who charged what, on whose behalf, and under what authority.
None of this means the practice itself is wrong. It means the infrastructure underneath it has not kept pace with the relationship it supports.
III.What a governed framework changes
A governed delegated payment framework replaces fragile manual practices with a structured digital workflow — without changing the nature of the relationship.
- Digital consent
- The VIP client gives explicit, recorded consent through a secure web journey. Dated, documented, and retrievable for audit or dispute resolution.
- Secure card capture — no staff handling
- Card details are entered by the client directly through the PSP's hosted page. No card number passes through the boutique's operational environment.
- Role-based authorisation
- The Maison defines who can act, for which clients, within which perimeter. Authorisations are enforced by the platform, not by individual discretion.
- Audit-ready evidence
- Every action — onboarding, charge, refund, notification — is logged with operator identity, timestamp, client reference, and operation type.
IV.ButlerPay and delegated payment
ButlerPay is the governance layer for this specific use case.
It is not a payment service provider — payment execution stays with the Maison's existing PSP (Adyen, Stripe, or others). It is not a checkout, a wallet, or a sales system — the sale is always recorded in the POS, the client relationship stays in the CRM.
ButlerPay sits between these systems, adding the one layer they do not provide: a governed, traceable, auditable framework for delegated payment.
For more detail, see the Glossary for key term definitions, the FAQ for common questions, and the Security & Compliance page for the responsibility framework.