Payment security is one of those things that should be invisible when it works. Here's what's running under the hood.

What happens when a caller enters their card

  1. The card data is encrypted in the caller's browser and transmitted directly to our certified payment partner — never through PaidLine's servers.
  2. The payment partner vaults the raw card data in their PCI-certified system.
  3. PaidLine receives only a secure token — a string that represents the card for future charges but contains no card data itself.
  4. Future calls use the token — the caller doesn't re-enter their card, and their real card details remain only at the payment partner.

What this means in practice

  • PaidLine engineers can't see card numbers. Neither can support, neither can the database.
  • A breach of PaidLine's servers would not expose card data — the data isn't on PaidLine's servers to expose.
  • Repeat callers get the convenience of saved payment without trading off security.

How charges work on a call

Each call is pre-authorized before connecting — the payment partner verifies the card can cover the expected charge. If anything fails (card declined, insufficient funds, expired), the call doesn't connect and the caller is notified. After the call ends, the caller is charged only for actual call time. No mystery charges, no estimates billed in advance.

How payouts work

Earnings move from the payment partner's hold account to your linked U.S. bank account through regulated payment networks with KYC verification (identity check on the receiving account) and ongoing fraud monitoring. Standard ACH timing, audited transaction logs, full reconciliation on every transfer.