#Does Dodo Payment support Card tokenization for user dublication verification?

1 messages · Page 1 of 1 (latest)

deep coralBOT
#

Short answer: No, not in the way you’re describing.

What Dodo supports today:

  • Cards are automatically tokenized and stored securely after a successful payment or setup via Checkout.
  • You can reuse the saved payment method for future charges for the same customer.
  • AVS, CVV, 3DS, and fraud checks run automatically during payment.

What’s not supported:

  • Standalone card verification / $0 or $1 auth without charging
  • Access to a stable card fingerprint or token you can use to dedupe accounts
  • Using card tokens as an identity signal across different customers

Important note:

  • Card tokens are scoped to a customer and must not be used for account de-duplication (PCI + compliance reasons).

Recommended approach:

  • Deduplicate creators using email, phone, government ID, or your own KYC flow.
  • If you need stronger guarantees, talk to the Dodo team about custom risk / KYB workflows.

If you want, I can suggest a Dodo-compatible flow that minimizes duplicates without using card data.

#

Hey @lost talon, We have limited availability over weekends, but rest assured we'll get back to you as soon as possible!

lost talon
#

@deep coral Can I store card tokens in my database?

deep coralBOT
# lost talon <@1423708558800846919> Can I store card tokens in my database?

Short answer: No.

Details:

  • You must not store raw card tokens or any card data in your database.
  • Dodo automatically tokenizes cards and stores them securely on its side.
  • What you can store is:
    • customer_id
    • payment_method_id (or equivalent reference returned by Dodo)
  • These IDs are:
    • Scoped to a single customer
    • Only usable via Dodo APIs to charge or reuse the payment method

Important:

  • Card tokens are not stable identifiers
  • They cannot be used for deduplication, identity, or cross-customer matching
  • Storing anything beyond Dodo-issued IDs can create PCI compliance issues

If you explain your exact use case (billing vs fraud vs account linking), I can suggest a Dodo-safe pattern.

#

Hey @lost talon, We have limited availability over weekends, but rest assured we'll get back to you as soon as possible!