What data is shared with payment processors (Stripe, Paddle, CoinPayments)?

When you buy credits on Valid Email Checker, the data we share with our payment processors is narrow and predictable. We send the purchase amount, your billing email, and whichever address fields the processor needs for tax. The card number, expiry, and CVC are typed directly into the processor (Stripe, Paddle, or CoinPayments) on a hosted field — VEC never holds the values, which is what keeps us out of PCI scope. The processor returns a token, an invoice ID, and webhook events when payment status changes, and that is what we store on our side.

Stripe (card payments)

For card purchases we route to Stripe. The data we send Stripe is your email, the dollar amount of the purchase, and the credit-pack metadata (which pack you bought). The card details go to Stripe via a hosted Stripe Elements field embedded in our checkout — those keystrokes never touch our servers. Stripe returns a customer ID, a payment intent ID, and webhook events when the payment succeeds or fails. We store the customer ID and intent IDs against your account so we can issue refunds and look up disputes later. Card numbers, full CVC values, and expiry are never stored on our side.

Paddle (merchant-of-record card payments)

Some regions route to Paddle instead of Stripe, because Paddle acts as the merchant of record and handles VAT/sales-tax collection for us. The data picture is the same — amount, email, and credit-pack metadata are sent to Paddle, card details go directly into Paddle-hosted fields, and Paddle returns a transaction ID we store. Because Paddle is the merchant of record, your bank statement shows Paddle (or "Paddle.net*VEC") rather than Valid Email Checker directly. Receipts come from Paddle and include the Paddle-collected tax detail.

CoinPayments (cryptocurrency)

For crypto purchases we route to CoinPayments. The data we send is the fiat amount you want to spend and the chosen coin. CoinPayments generates a payment address on its side, the user sends the crypto, and CoinPayments fires a webhook back to us with the transaction state. We do not see private keys, wallet seed phrases, or any identifying detail beyond the on-chain transaction ID and the customer email. Refunds work differently in crypto — see the refund policy page for the mechanics.

What we keep on our side after the payment

• Processor customer ID and transaction/intent ID — so we can issue refunds and reconcile disputes.
• Amount, currency, and credit pack purchased — for our Credits History and your receipts.
• Last 4 digits of the card and brand (Visa/Mastercard/etc.) for card payments — surfaced in your billing UI for recognition. Never the full number.
• Billing email — usually the same as your account email, sometimes different if you specified a separate billing contact.