On this page
Disputes do not all have the same cause
A purchase may be disputed because the customer does not recognize it, delivery differs from expectations or a commercial problem occurred. Identifying who participates in an order adds context but does not solve every situation by itself.
For higher-risk operations, KYC can introduce identity verification before an order proceeds. Its purpose is to support assessment with organized identification rather than relying only on self-declared account details.
Identity and payment need different controls
Verifying a person does not automatically establish that they own the card used. KYC does not replace payment-provider controls, transaction authentication, fraud assessment or the acquirer’s and card network’s dispute rules.
Do not request a complete card number or CVV in an identity workflow to try to establish that relationship. Design the process with payment, risk and data-protection teams, using appropriate channels for each type of information.
Position verification without indiscriminate friction
Choose cases where the step adds value: selected orders under assessment, sensitive changes or situations defined by operational policy. Explain the purpose and plan for pending cases, rejection and review.
Associate the result with the correct order and keep records under controlled access. If a dispute occurs, those records can support assessment without a promise of success, reimbursement or elimination of chargebacks.
Explore KYC and request a KYC demonstration to discuss your ecommerce operation’s design. Payment outcomes remain dependent on the complete transaction context and the applicable dispute process.