Digital Receipts & Deflections

Overview

Digital Receipts and Deflections work together to prevent chargebacks before they’re filed. Unlike alerts (which intercept disputes in progress), these services stop disputes from starting.

Digital Receipts

When cardholders check their bank statement and don’t recognize a charge, they see enriched transaction details — merchant name, logo, purchase description, and contact information. This reduces “What is this charge?” confusion that leads to friendly fraud.

Deflections

Deflections automatically block chargebacks using Visa’s pre-dispute programs:

Compelling Evidence 3.0 (CE3.0)

When a cardholder disputes a transaction, Visa checks if the same device, IP address, or email was used for previous undisputed purchases. If compelling evidence exists, the chargeback is blocked automatically.

First Party Trust (FPT)

Similar to CE3.0, but also uses billing/shipping address matching for even stronger fraud prevention.

Digital Receipts and Deflections share the same implementation process. The difference is which qualifying fields you provide — if certain fields are present, transactions become eligible for CE3.0/FPT deflection.

Qualifying Fields for Deflection

To enable deflections, you must provide certain data fields with your transactions:

Field	CE3.0	FPT	Description
Merchant Contact Phone	✓	✓	Customer service phone number
IP Address	✓	✓	Customer’s IP at time of purchase
Customer Email	✓	✓	Email address used for the order
Billing or Shipping Address	—	✓	Full address for FPT matching

The more fields you provide, the higher your deflection rate. FPT requires all fields including address; CE3.0 requires phone, IP, and email.

Choose Your Integration Path

Push Data (Recommended)
Pull Data

How It Works

Send enriched transaction data via one of two methods:
- Supported payment processor with receipt data
- Upload Orders endpoint with the receipt object
- Tracker Snippet for IP capture on web
Chargeblast handles all lookups — when Visa queries for transaction data or compelling evidence, we respond automatically using your uploaded data.
Monitor deflection logs via the Deflection Logs endpoint to see blocked chargebacks.

Implementation Steps

Connect Transaction Data with Receipt Info

Upload transactions via the Upload Orders endpoint, including the receipt object with qualifying fields:

{
  "orders": [{
    "id": "order_123",
    "amount": 1999,
    "currency": "usd",
    "transactionDate": "2024-01-15T10:30:00Z",
    "bin": "424242",
    "last4": "4242",
    "ip": "192.168.1.1",
    "receipt": {
      "customerEmail": "customer@example.com",
      "customerPhone": "+1234567890",
      "billingAddress": {
        "line1": "123 Main St",
        "city": "San Francisco",
        "state": "CA",
        "postalCode": "94102",
        "country": "US"
      },
      "description": "Premium Subscription - Annual",
      "merchantName": "Acme Inc",
      "merchantUrl": "https://acme.com"
    }
  }]
}

(Optional) Add Tracker Snippet

For automatic IP capture on web transactions, add the Tracker Snippet to your checkout page:

<script defer 
  src="https://cdn.cgb.la/v1/scripts.js" 
  data-account="YOUR_ACCOUNT_ID" 
  id="chargeblast-script">
</script>

Then identify the user:

Chargeblast.identify("customer@example.com")

Monitor Deflections

Use the Deflection Logs endpoint to track blocked chargebacks.

With push data integration, Chargeblast automatically responds to Visa queries — no real-time endpoint required.

How It Works

Chargeblast forwards lookup queries to your endpoint in real-time when Visa requests transaction data or compelling evidence.
You perform matching and return the enriched transaction data.
You must respond within 1.5 seconds — this is a hard SLA requirement from Visa.

Implementation Steps

Expose a Lookup Endpoint

Create an endpoint that accepts POST requests with transaction lookup queries. Chargeblast will call this endpoint with card and transaction details.Your endpoint must:

Accept transaction identifiers (BIN, last4, amount, date)
Return enriched receipt data within 1.5 seconds
Handle matching logic on your side

Configure Endpoint in Dashboard

Set your lookup endpoint URL in the Chargeblast dashboard under developer settings.

Return Qualifying Data

Your response must include a receipt object with the qualifying fields for deflection eligibility:

{
  "matched": true,
  "orderId": "order_123",
  "ip": "73.162.214.93",
  "receipt": {
    "merchantInfo": {
      "merchantReceiptContact": {
        "phoneForReceipt": "+1-888-555-1234",
        "emailForReceipt": "support@acmeinc.com",
        "websiteForReceipt": "https://acmeinc.com",
        "receiptAddress": {
          "line1": "100 Market Street",
          "line2": "Suite 400",
          "city": "San Francisco",
          "countrySubdivision": "CA",
          "postalCode": "94105",
          "country": "US"
        }
      },
      "name": "Acme Inc",
      "description": "Premium software subscriptions",
      "refundPolicyLink": "https://acmeinc.com/refunds",
      "cancellationPolicyLink": "https://acmeinc.com/cancel",
      "termsAndConditionsLink": "https://acmeinc.com/terms",
      "logoUrl": "https://acmeinc.com/logo.png"
    },
    "lineItems": [
      {
        "productName": "Premium Plan - Annual",
        "productDescription": "12-month subscription to Premium features",
        "currency": "USD",
        "quantity": 1,
        "price": 9999
      }
    ],
    "customerEmail": "john.smith@gmail.com",
    "customerPhone": "+1-415-555-7890",
    "shippingAddress": {
      "line1": "456 Oak Avenue",
      "line2": "Apt 2B",
      "city": "San Francisco",
      "countrySubdivision": "CA",
      "postalCode": "94102",
      "country": "US"
    },
    "billingAddress": {
      "line1": "456 Oak Avenue",
      "line2": "Apt 2B",
      "city": "San Francisco",
      "countrySubdivision": "CA",
      "postalCode": "94102",
      "country": "US"
    },
    "name": {
      "givenName": "John",
      "familyName": "Smith"
    }
  }
}

1.5 Second SLA — If your endpoint doesn’t respond in time, the lookup fails and the transaction won’t be eligible for deflection or digital receipt display. Ensure your matching logic is optimized for speed.

Handling Deflected Transactions

When a transaction is deflected, Visa has already blocked the chargeback using compelling evidence. You should not refund deflected transactions — the cardholder’s dispute has been resolved in your favor.

Poll Deflection Logs

Regularly poll the Deflection Logs endpoint to get a list of deflected transactions:

GET /api/v3/deflections/logs

This returns transactions where chargebacks were successfully blocked via CE3.0 or FPT.

Guard Against Refunds

Before processing any refund (whether from an alert, customer request, or internal process), check if the transaction has been deflected:

Store deflected transaction IDs — Maintain a local cache of deflected order IDs from the deflection logs
Check before refunding — Before issuing any refund, verify the transaction ID is not in your deflected list
Skip refunds for deflected transactions — If a transaction was deflected, the dispute is already resolved; issuing a refund would be unnecessary

Refunding a deflected transaction means you lose the sale unnecessarily. The deflection already prevented the chargeback — there’s no reason to refund.

API Reference

Endpoint	Description
Upload Orders	Push transaction data with receipt info
Track	Push IP/session data
Deflection Logs	View blocked chargebacks
Get Orders	Retrieve uploaded orders

Tracker Snippet Guide — Automatic IP capture for web transactions
Implementation Overview — Compare all services and integration paths
Alerts Implementation — Handle disputes that weren’t deflected

Welcome

Guides

Platform

Alerts

Digital Receipts & Deflections

RDR

Enrollment

Digital Receipts & Deflections

Overview