Phone Psychic Reading Payment: How to Take Cards Safely Before the Call
Set up phone psychic reading payment safely: payment links, virtual terminals, 3D Secure and prepay rules that cut disputes and PCI scope.

Photo: Pixabay
On this page 8 sections
- Why a Card Number Read Aloud Becomes Your Problem
- Phone Psychic Reading Payment Tools: Link or Virtual Terminal
- What 3D Secure Protects, and What It Doesn't
- Keyed Sales Cost More on Most Cards: A Worked Example
- Prepay the Block and Sell Overtime Separately
- Checks Before You Read for a First-Time Caller
- What You May Never Write Down or Store
- Make the Receipt Match the Name on the Statement
The safest way to take a phone psychic reading payment is to collect it before the call. Send a payment link that the client opens on their own phone or computer and pays themselves. You never hear the card number, and it never ends up in your notes or recordings. The checkout also leaves a timestamped record, plus the card issuer's authentication result when the page runs 3D Secure. If a client can't use a link, key the card into a virtual terminal while they're on the line and save nothing.
Readers need this discipline more than most small businesses. Processors often put psychic services through high-risk underwriting. Every phone reading is also a card-not-present sale, and that's the kind of sale where "I didn't authorize this" disputes usually cost the merchant.
Why a Card Number Read Aloud Becomes Your Problem
A card number read out over the phone ends up wherever the call ends up. If you record sessions for clients to replay, the card now sits in an audio file on a laptop or in cloud storage. A number jotted on a pad "just for a second" now exists on paper. A texted photo of the card lives in your message history and its backups.
Each copy pulls more of your business into scope for PCI DSS, the card industry's data security standard. PCI DSS is a card network requirement that reaches you through your merchant agreement. It isn't a federal law, although state data-breach laws can apply if card data leaks.
Disputes happen more often than breaches. Visa's Dispute Management Guidelines for merchants say that when a cardholder tells their bank they never made a phone or online purchase, the claim is filed as dispute condition 10.4, "Other Fraud – Card-Absent Environment." A keyed phone sale leaves you little to answer with, because nothing shows who was on the line. Readers with older clients see this when relatives review statements, which is why we cover elderly clients and family disputes separately.
If you record calls, check the consent rules first. They differ by state, and a call between two states can bring both states' rules into play. Confirm with an attorney; this is general information, not legal advice.
Phone Psychic Reading Payment Tools: Link or Virtual Terminal
A payment link is a secure checkout page you send by text or email. The client enters their own card and pays. Most gateways can create one link per booking with an amount and a plain description, such as "45-minute phone tarot reading, Nov. 18, 7 p.m. ET." When the checkout supports 3D Secure authentication, the client's bank can confirm who they are with a code or an app prompt.
A virtual terminal is a browser screen where you type the card in yourself. It suits the client who is already on the phone, doesn't text, or keeps getting stuck on checkout pages. The cost is that you hear and type the number, the sale is keyed, and 3D Secure can't run because the cardholder isn't the one at the screen.
| Payment link | Virtual terminal | |
|---|---|---|
| Who enters the card | The client | You |
| You see the full card number | No | Yes |
| 3D Secure possible | Often, depending on the checkout | No |
| Payment record | Checkout timestamp, device details, any 3D Secure result | Your booking notes and AVS/CVV results |
| Best fit | Booked readings, new callers, repeat clients | Clients who can't use a link |
Make the link your default and keep a virtual terminal for keyed phone orders as the backup. Both have to run on a merchant account approved for psychic services in your own business's name. Running readings through a friend's salon account or a generic "consulting" account misrepresents what you sell. If it's discovered, you can lose the account and end up on the industry's list of terminated merchants. If you've been turned down before, read why readers get declined and how to apply and look at providers of high-risk merchant accounts.
What 3D Secure Protects, and What It Doesn't
Under network rules, a properly authenticated online sale moves liability for card-absent fraud disputes (Visa 10.4, Mastercard 4837) from you to the card issuer. As payment security firm Evervault notes, that shift covers fraud-coded disputes only. A client who admits paying but says the reading wasn't what they bought files a consumer dispute, and 3D Secure does nothing for you there. In that case your terms, booking record and receipt are your evidence. That fight is the subject of winning "the reading was wrong" chargebacks.
Visa's rules add two more limits, summarized in TabaPay's liability shift documentation. An "attempted" authentication doesn't guarantee the shift, and merchants flagged in Visa's fraud monitoring program lose it. For repeat clients, Visa's Compelling Evidence 3.0 rule lets merchants answer 10.4 claims with the customer's earlier purchase history, as Chargeflow explains. The criteria are specific, so ask your processor what customer data your checkout captures. A hosted link usually records more than a number you type in yourself.
Keyed Sales Cost More on Most Cards: A Worked Example
Interchange is the base fee the card-issuing bank gets on each sale. The card networks set it, and your processor adds its markup on top. Visa's U.S. interchange reimbursement fee schedule shows how much that base fee changes depending on how the card is taken.
Illustrative case: a $90 reading paid with a Visa debit card. Assumptions: the sale qualifies for the program shown (that depends on your merchant category and the data sent with the sale), and the figures are interchange only, before network fees and processor markup.
| How the card is taken | Visa debit program and rate | Interchange on $90 |
|---|---|---|
| Phone or online, exempt debit | CPS/Card Not Present: 1.65% + $0.15 | $1.64 |
| Tapped or dipped in person, exempt debit | CPS/Retail: 0.80% + $0.15 | $0.87 |
| Keyed in person, exempt debit | CPS/Retail Key Entry: 1.65% + $0.15 | $1.64 |
| Any method, regulated debit | 0.05% + $0.21 | $0.26 |
The math: 1.65% of $90 is $1.485, plus $0.15, which rounds to $1.64. For the in-person tap, 0.80% of $90 is $0.72, plus $0.15, which is $0.87. Exempt debit cards come from smaller banks. Regulated debit cards come from large banks whose debit interchange is capped by federal rule, so that row stays the same no matter how the card is taken.
Two decisions follow from the table. If you also read in person at a shop or a fair, tap or dip the card. Keying it while the client is standing there costs as much as a phone sale and gives up chip protection. Over the phone, the interchange difference between a link and a virtual terminal is small. Visa lists 1.60% + $0.15 for its e-commerce preferred retail debit program, where that program applies. So choose between the two tools on fraud and PCI grounds, not price. The rest of the bill is covered in our guide to psychic credit card processing fees, reserves and holds.
Prepay the Block and Sell Overtime Separately
With prepayment, the money clears before you dial. No-shows cost you nothing, and you have a paid record from before the reading. The price is a little friction for the client and a duty to refund promptly if the call drops on your end. Billing afterward lets you charge for the exact minutes used, but you deliver first and collect second. Charging later also means keeping the card on file, and that belongs only in your gateway's vault, with the client's agreement.
Here's an illustrative example; the numbers are for the math, not suggested prices. You charge $3 per minute, and a new client prepays a 30-minute block by link (30 × $3 = $90). The reading runs to 42 minutes, so the extra 12 minutes come to 12 × $3 = $36. You have three options:
- Warn the client a few minutes before the block ends and stop on time unless they buy more.
- Send a second link for an add-on block that the client pays themselves.
- Charge the card saved in your gateway's vault. Do this only if the client agreed in writing, before the call, to the per-minute rate and to overage charges.
With a first-time caller, option 3 invites a dispute even with that written agreement. Options 1 and 2 mean the cardholder completes a checkout for every billed minute. For established clients with signed terms, charging a saved card afterward can work. Prepaid minutes versus metered billing covers that model.
Checks Before You Read for a First-Time Caller
The Address Verification Service (AVS) checks the billing address a client gives against the card issuer's records. The card verification value (CVV) is the security code printed on the card. Your gateway returns a match or no-match result for each and can decline mismatches automatically. A full match proves less than many readers think, because a thief with a stolen card number usually has those details too. It screens out sloppy fraud, but it won't win a dispute where the real cardholder says the charge wasn't theirs.
So use several checks together for a new caller:
- Send a payment link, with 3D Secure where your checkout offers it.
- Turn on AVS and CVV filters so mismatches decline before the reading starts.
- Get an email and phone number, and confirm the name on the booking matches the name on the card.
- Hold off when you see red flags: several cards declining in a row, a new caller pushing for an unusually long session, or a payer who isn't the person being read.
- Keep a booking record with the date, time, phone number, session length, and the client's written acceptance of your price and refund policy that holds up in disputes.
When a daughter pays for her mother's reading, send the link to the daughter so the cardholder approves her own charge.
What You May Never Write Down or Store
The PCI Security Standards Council's FAQ on card verification codes says Requirement 3.2 bans storing the security code after the payment is authorized. Encrypting it doesn't make storage acceptable, and neither does the customer's permission. The rest follows from there:
- Keep full card numbers out of notes, spreadsheets, email, texts, client-management fields and recordings.
- Save cards only in the gateway's vault, where you see just the last four digits.
- Pause the recording before a client reads card details aloud.
- Delete card photos a client texts you, then send a link instead.
- Give everyone who uses your virtual terminal their own login.
Your processor will ask you to complete a PCI self-assessment questionnaire (SAQ) every year and will tell you which version applies. Merchants that send customers to a hosted payment page by link or redirect use SAQ A, the shortest form. According to Top Floor Security's reading of PCI SSC FAQ 1588, a 2025 eligibility change aimed at checkout forms embedded in a merchant's own web page (iframes) doesn't apply to them. Keying cards yourself brings your own computer into scope, and a longer questionnaire with it.
Make the Receipt Match the Name on the Statement
The billing descriptor is the business name that shows on the client's card statement. A client who booked "Luna Readings" and sees "LMV Holdings LLC" three weeks later may dispute a charge they don't recognize. Ask your processor for a descriptor your clients will recognize, with a phone number or website if your setup allows it. Then send a receipt right away that includes:
- The business name exactly as it appears in the descriptor
- The date, time and length of the reading, and the reader's name
- The amount and what it covered
- A link to your refund policy
Before your next booked reading, send a test payment link to yourself. Check the checkout description, the receipt, and how the charge shows up on your own statement. If any of them shows a name your clients wouldn't recognize, fix it with your processor before a client finds it. If you're reviewing your setup, request a free quote from MannyPay to talk through high-risk processing and whether your business qualifies. A specialist will reply within one business day.
Sources
- Visa Dispute Management Guidelines for Merchants
- Visa USA Interchange Reimbursement Fees
- Visa USA Interchange Reimbursement Fees (regional edition)
- PCI SSC FAQ: Can card verification codes/values be stored for card-on-file or recurring transactions?
- Evervault: Mastering 3D-Secure, chargebacks and the liability shift
- TabaPay: 3D Secure (3DS) Liability Shift
- Chargeflow: Winning Unauthorized Transaction Chargebacks
- Top Floor Security: SAQ A Eligibility Changed
- TrustedSec: The Hidden Trap in the PCI DSS SAQ A Changes
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.


