Skip to main content

Payment-as-verification

Payment-as-verification lets a completed card payment stand in for the parental-consent step. An adult who has already paid for a purchase with a credit card is the same adult signal the credit-card verification method already trusts, so where that method applies, k-ID can accept the payment you already have rather than asking a parent who has just completed a purchase to verify separately.

It's a consent signal rather than a way to see or approve purchases. For visibility and per-purchase approval, see Transactions.

It mirrors credit-card verification, exactly​

The rule that keeps payment-as-verification safe is a single equivalence: it's honored exactly where the credit-card verification method is enabled for the session, and nowhere else.

  • Where credit-card verification is enabled for the session's jurisdiction, a qualifying payment satisfies the parental-consent step on its own.
  • Everywhere credit-card verification is off, the payment is ignored and the parent completes k-ID's standard verified parental consent flow, unchanged.

Normalizing a merchant of record's payment​

Merchants of record each report a payment differently, and k-ID reads one standard shape. You can optionally normalize your provider's raw payment into k-ID's fields through an endpoint k-ID provides for supported providers, which makes every reasonable effort to derive the card's funding type so you don't have to.

See Payment-as-verification in the integration guide for the endpoints, the supported providers, and the attestation shape.

Enabling it​

Payment-as-verification rides on the same Transactions configuration, enabled per product in Compliance Studio.

Next steps​