PCI Compliance for Timeshare Sales Floors and Owner Services
PCI compliance for timeshare operators: remove card numbers from contracts, closing-room copies and owner-services calls, and replace them with tokens.

Photo: Pixabay
On this page 6 sections
- PCI Compliance for Timeshare Starts With Where Card Data Leaks
- Card Numbers on Timeshare Contracts and Worksheets
- Timeshare Call Center PCI: Owner Services Phone Lines and Call Recordings
- Storing Card Data for Timeshare Maintenance Fee Autopay
- Your PCI Compliance SAQ Across Sales, Billing and Online Portals
- Resort Sales PCI Compliance Training for Reps and Closers
Key takeaways
- In timeshare operations, card data often sits on paper and in call recordings, outside the payment system. A clean scan doesn't mean a clean operation.
- Contracts and deal jackets should hold only the last four digits, card brand, authorization code and token reference. The security code should never be written down.
- On owner-services lines, keypad entry with tone masking or a hosted payment page keeps card numbers away from agents and recordings. Pausing the recording depends on agents remembering every time.
- The closing table, the phone line and the owner portal can each fall under a different self-assessment questionnaire. Ask your acquirer which applies to each before you redesign anything.
PCI compliance for a timeshare operation depends on one habit change: card numbers should never be written, photocopied, typed into notes or recorded anywhere in your sales or owner-services process. The card goes into a terminal or a hosted payment page, the processor returns a token, and your paperwork keeps only that token, the last four digits and the authorization code. In timeshare, much of the exposure sits outside the payment system, in deal jackets, closing-room copiers and call recordings. That is how a resort can pass its quarterly scan and still have thousands of full card numbers in a storage room.
PCI DSS, the Payment Card Industry Data Security Standard, is maintained by the PCI Security Standards Council, which the major card brands founded. It is not federal law. It applies to you through card network rules and your merchant agreement, which is why your acquirer asks you to validate compliance and a government agency does not. State data-breach notification laws are separate and are law. Take legal questions about either to a qualified attorney. This article is general information.
PCI Compliance for Timeshare Starts With Where Card Data Leaks
A timeshare sale passes through more hands than almost any other retail transaction. An off-premise contact books the tour. A front-line rep presents. A closer or turnover manager handles the second pitch. A verification officer walks the buyer through the contract, and then the deal jacket (the folder holding the signed agreement, worksheets and copies) goes to the contracts department. Every handoff is a chance for someone to write a card number down "just in case."
Owner services adds a second set of exposure points: maintenance fee calls, reservation and exchange fees, points purchases and loan payments. Most of these are taken by phone, and the calls are often recorded.
| Touchpoint | How card data gets captured | Tokenized replacement |
|---|---|---|
| Tour desk deposit | Card number written on a deposit slip | Authorization hold on a handheld terminal; slip records the auth code |
| Sales worksheet | Closer jots the card for the down payment | No card on the worksheet; payment runs at the closing table |
| Purchase agreement | Payment section asks for full number, expiration and security code | Last four, brand, auth code and token reference only |
| Deal jacket copies | Front and back of the card copied with the buyer's ID | Copy the ID if your process needs it; never the card |
| Owner services calls | Owner reads the number aloud while the call is recorded | Keypad entry with tone masking, or a hosted payment page |
| CRM and owner billing notes | Rep pastes the number into a notes field | Token stored in the gateway vault; notes fields block card-length digit strings |
| Email and text | Owners email cards; staff text photos of cards to contracts | Refuse, purge and send a hosted payment page instead |
An illustrative calculation shows how fast this adds up. Assume a resort closes 40 deals a week for 50 weeks a year, and each jacket carries the card number in three places: the worksheet, the agreement and a photocopy. That comes to 2,000 jackets and 6,000 written card numbers a year, before counting a single phone call. Jackets are usually kept for years, so the archive grows every season.
Card Numbers on Timeshare Contracts and Worksheets
Card numbers ended up on timeshare contracts because the old workflow needed them there. The contracts department charged the down payment after the paperwork cleared, or set up loan billing later from the written authorization. Neither step needs a written card number anymore.
The fix is to charge the card where the buyer signs. A verification officer with a handheld terminal for the closing table can take a chip or tap payment for the down payment in front of the buyer. For help choosing one, see our guide to card terminals for timeshare sales tables and closing rooms. If the card will also be used for future payments, the gateway can tokenize it in the same transaction.
The agreement's payment section then records the card brand, last four digits, authorization code and token ID. That is enough for the contracts team to find the transaction, process a refund during the rescission period and answer a dispute. Where the down payment goes after it's charged is a separate question, and timeshare escrow rules for card down payments vary by state.
Two practices need to stop. First, never write the security code on anything. The code exists to verify the card at the moment of payment, and the PCI standard treats keeping it afterward as off-limits, on paper as much as in a database. Your acquirer can point you to the exact requirement. Second, stop photocopying the back of the card. Some closing rooms copy both sides as fraud protection, but the back shows the security code, so the copy creates the very record you shouldn't keep. A chip or tap transaction gives you better evidence than a photocopy.
The old jackets need a plan too. You probably have good reasons to keep signed contracts for years, but the card number doesn't need to stay legible in them. Work with counsel on how to redact card data without affecting the contract's validity. Until that's done, keep the archive in a locked room with an access log.
Timeshare Call Center PCI: Owner Services Phone Lines and Call Recordings
Owner services is where timeshare call center PCI work usually stalls, because recordings serve real purposes: quality assurance, training and evidence when an owner later disputes a charge. The trouble is what the recording captures. If an owner reads a card number aloud, the recording platform, its storage and everyone who can play it back come into PCI scope. If the security code is spoken, the recording now holds the same data you've just taken off your contracts.
These are the options, from strongest to weakest:
- Keypad entry with tone masking (DTMF masking). The owner types the card number on the phone keypad. The tones are suppressed so neither the agent nor the recording hears them, and the digits go straight to the payment processor. The agent stays on the line and sees only whether the payment was approved or declined.
- Transfer to an IVR. An automated system takes the payment and then returns the caller to the agent.
- A hosted payment page sent during the call. The agent texts or emails a link to the gateway's hosted page, and the owner pays on their phone while still on the call.
- Pause-and-resume recording. The agent stops the recording before the card details are read. This is the weakest option because it depends on people remembering every time, and the agent still hears and types the number.
The agent's workstation matters as well. If reps key cards into a browser-based virtual terminal for phone payments, that computer and the network it uses are in scope. A dedicated, locked-down machine is far easier to secure than a shared desk PC that also handles email.
If you outsource owner services or tour booking to a call center, ask for written proof of its PCI validation, typically an Attestation of Compliance, and make sure your contract assigns responsibility for it. Outbound tour calls may also fall under federal telemarketing rules, which our guide to TSR rules that affect timeshare tour payments covers.
Storing Card Data for Timeshare Maintenance Fee Autopay
Storing card data for timeshare billing is necessary for maintenance fee autopay, club dues and in-house loan payments. Done properly, though, you never hold the card number yourself. The gateway keeps it in a secure vault and gives your owner billing system a token, a reference that is useless outside your merchant relationship. Your software charges the token on schedule, and your database never contains a card number worth stealing.
Card networks also have their own stored-credential rules, separate from PCI DSS. They govern how you get the owner's agreement to keep a card on file and how the transactions that use it are flagged. Ask your processor what consent language and transaction flags they require before you store the first card. The detailed setup, including notices and retry timing, is covered in setting up maintenance fee autopay for owners. Loan billing works the same way and is covered in collecting in-house timeshare financing payments.
One operational detail is easy to miss. Tokens are usually tied to the gateway or processor that issued them. If the HOA and the developer use different merchant accounts, or if you change processors, you can't simply carry the tokens over. The underlying card data has to be moved securely between providers, and not every provider makes that easy. Ask about token portability before you sign. Also ask whether your processor offers an account updater service, which refreshes expired or reissued cards so annual maintenance fee charges don't fail.
Your PCI Compliance SAQ Across Sales, Billing and Online Portals
Many timeshare merchants validate PCI compliance with a Self-Assessment Questionnaire (SAQ). Your acquirer decides which questionnaire and validation level apply, based on how you accept cards and your annual transaction volume on each network. High-volume developers may need an on-site assessment by an outside assessor instead. Because one operation can run several channels, each channel may land on a different questionnaire:
- An owner portal that sends card entry to the gateway's hosted page or a fully hosted payment field usually qualifies for the shortest questionnaire. If your own web page collects the card details before passing them on, expect a longer one.
- Standalone terminals at the closing table and tour desk fall under a terminal-specific questionnaire. Some terminal and processor setups encrypt card data from the moment it's entered in a way the standard recognizes, which can shorten the questionnaire further. Ask your acquirer whether yours qualifies.
- A virtual terminal on a dedicated computer has its own questionnaire, with strict conditions on how that machine is used.
- Card numbers stored in your own systems, or a mix of channels that don't fit the narrower types, usually means the longest questionnaire.
Paper isn't exempt. Stored paper records bring physical security and destruction requirements into play no matter which questionnaire you file. Some operators run separate merchant IDs for the sales floor, owner billing and the online portal so each stays narrowly scoped. Ask your acquirer whether that makes sense for you. Underwriters for high-risk processing often ask timeshare applicants how card data is handled, and a tokenized setup through a payment gateway with hosted checkout is a good answer to have ready. It complements, but doesn't replace, the other approval factors covered in why timeshare merchant accounts get declined.
Resort Sales PCI Compliance Training for Reps and Closers
Resort sales PCI compliance tends to break down late in the day. It's 9 p.m., the buyer's card has declined, and the closer wants to "take the number and try again in the morning." Training has to address that moment directly. Card numbers do not leave the terminal. The closer can retry on the terminal, try a different card or send a hosted payment link. Writing the number down is not an option.
Training should cover everyone who could touch a card: off-premise contacts, front-line reps, turnover managers, verification officers, contracts clerks, owner services agents and the QA staff who listen to recordings. Keep the rules to one page, written in the language of the sales floor:
- Never write, copy, photograph or text a card number.
- Collect the security code only through the terminal or payment page.
- Owners who email card details get a payment link in reply, and the email is deleted.
- Report any card number you find, with no penalty for reporting.
Audits make the rules stick. Each month, pull a random set of deal jackets and owner-services recordings and look for card numbers. A finding traced to one closer calls for a coaching conversation. Findings across the floor mean the process still needs a card number somewhere, and that process is what needs fixing.
This week, pull ten deal jackets and ten call recordings from last month and count every full card number you find. That count is your project list. If fixing it means new closing-table terminals or a different gateway setup, MannyPay can review your current configuration: request a free quote, and a specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


