Disputes and refunds

Liability shift, chargeback handling, and refunds for Apple Pay payments.

View as MarkdownInstall skills

Liability shift and fraud protectionAsk

Apple Pay transactions are always device-authenticated — the customer authenticates with Face ID, Touch ID, or passcode, and Apple generates a one-time cryptogram tied to that specific transaction. This is equivalent to a strongly authenticated card transaction and carries inherent liability shift on fraud chargebacks across all major networks globally.

NetworkLiability shiftNotes
MastercardYes — all regionsAll devices
VisaYes — all regionsDevices running iOS 16.2 and above; for iOS below 16.2, liability shift applies only if the card was issued in Europe
AmexYes — all regionsAll devices
Cartes BancairesYes — EEAAll devices

Liability shift covers fraud chargebacks. It does not remove a dispute from card scheme monitoring programs such as Visa VAMP. All disputes — including liability-shifted ones — count toward scheme dispute activity that VINR monitors on your behalf.

DisputesAsk

Apple Pay users must authenticate every payment with their device, significantly reducing the risk of unauthorized transactions. However, customers can still dispute a charge after it completes — for reasons including non-delivery, a duplicate charge, or a subscription they didn't intend to renew.

When a dispute is opened, VINR creates a dispute object and the standard dispute lifecycle applies — evidence submission, deadlines, outcomes, and fees all work the same as for any card payment. See Disputes for the full lifecycle, how to submit evidence, and how to keep your dispute rate low.

To identify an Apple Pay payment in a dispute:

{
  "payment_method": {
    "type": "card",
    "card": {
      "wallet": {
        "type": "apple_pay"
      }
    }
  }
}

Evidence strategy

Apple Pay's device authentication is strong counter-evidence for "fraudulent" and "unrecognized" disputes. When submitting evidence:

  • Include the fact that the transaction was authenticated via Apple Pay — the customer actively confirmed with biometrics or passcode on their registered device.
  • For "product not received" or "subscription canceled" disputes, provide shipping/delivery confirmation or cancellation records — the dispute reason is unrelated to the authentication method.

Common dispute reasons for Apple Pay

ReasonNotes
unrecognizedMost preventable — set a clear billing descriptor so customers recognize the charge
fraudulentRare with Apple Pay due to device authentication; the cryptogram is strong counter-evidence
product_not_receivedFulfillment issue — unrelated to Apple Pay; provide shipping proof
subscription_canceledCustomer expected cancellation to prevent the charge; make cancellation self-serve
duplicateCheck for double-submission on your server

RefundsAsk

You can partially or fully refund any successful Apple Pay payment. The refund goes to the underlying card associated with the customer's Apple Wallet entry — not to an Apple Wallet balance — and the customer does not need to take any action. The refund process is identical to a standard card refund. See Refund and cancel payments for instructions.

Refunding a payment that is already disputed does not resolve the dispute and can result in the customer being paid twice. Respond to the dispute instead; only issue a refund if you intend to concede.

Preventing disputesAsk

  • Clear billing descriptors — set a recognizable statement descriptor in your VINR account settings. "Unrecognized" disputes are the most common and most preventable.
  • Prompt fulfillment and tracking — keep shipping and delivery confirmation on hand to rebut "product not received" claims quickly.
  • Easy cancellation for subscriptions — cancellation friction is the primary driver of subscription_canceled disputes. Make cancellation self-serve and confirm it immediately to the customer.
  • Respond to early fraud warnings — if you receive a warning_needs_response dispute event, refunding proactively avoids a formal chargeback, the associated fee, and the dispute-rate impact.

See alsoAsk

Was this page helpful?
Edit on GitHub

Last updated on

On this page