Descubre el código de motivo de devolución UA02: Fraude: transacción sin presencia física de la tarjeta
Discover UA02 is a card-not-present fraud label in older processor records. The cardholder denies approving or taking part in the purchase. Confirm the provider's current code mapping, then build evidence linking the buyer to the disputed sale. Bank approval alone does not prove who made the purchase.
How Does UA02 Relate to 4868?
Braintree's evidence guide explains the April 2026 change. It keeps older labels for the relevant cases too. Both old and new fraud codes require compelling evidence in this process. These are Braintree's instructions. Confirm the rules for the provider handling the case.
Separate Card Checks From Buyer Participation
Bank approval, address checks and security-code results show different things. They may support a response. Alone, they do not prove who made the purchase. Keep the results from the processor. Do not ask for or store the raw security code to build a case file.
Choose Evidence for the Order Channel
Goods Delivered to an Address
Link the order, address checks and proof of delivery. Show the full address and date. Explain any gap between the billing and shipping address. A carrier record for another order does not answer this charge.
Goods Collected in Person
Keep the handoff record and proof linking the collector to the buyer. A notice that goods were ready does not prove pickup. Ask which allowed evidence category fits the record. Do not describe pickup as a carrier delivery.
Digital Goods or App Access
Link access, download and device logs to the purchase. Braintree's digital download category requires a date and time. It also needs at least two of its listed supporting items. Check the guide for the allowed items and file types. One IP address is not enough.
A Booking or Service
Show who took part in the service or used it. A booking alone does not prove use. Link the records to the payer or named user and state what each one shows. A bill for a service does not prove the cardholder made the purchase.
Use a Short Evidence Index
- Name the claim. Identify the exact transaction and denial.
- State the supported response. Explain the link to the buyer or any matching credit.
- Index the records. Give each file a date and a clear purpose.
- Check the submission category. Follow the provider's required format and deadline.
Hypothetical Device Example
A log shows access from a shared device. That fact alone does not prove who used it. Add the records required for the evidence route and explain any gaps. A device match does not mean fraud could not occur.
Follow the Merchant Reply Date
Use the date on the case notice. The bank has a separate filing limit. If a refund was completed, show the record or check if the provider added it. A refund promise does not prove that credit was paid.
{{COMPONENT_IDENTIFIER}}
Keep Fraud Checks and Fulfillment Records Connected
- Use supported authentication and risk checks.
- Retain permitted results, not raw security codes.
- Link delivery or access records to each payment.
- Make billing descriptors clear and respond promptly to buyer questions.
Source checked November 16, 2026: Braintree's evidence requirements, including its April 17, 2026 Discover notice. Apply the categories, formats and case instructions for the actual provider and transaction.

















