5D Library › Cross-Border Payment Routing, Chargeback Defense Games and Treasury Ruin Bounds · 中文

Chapter 1. Multi-Acquirer Routing and the Chargeback Red Line

First, correct where the red line comes from and what it is

It is often said that “the issuers’ chargeback red line is 0.9%”. Three corrections are needed. First, monitoring thresholds are set by the card networks and enforced through acquirers, not set by issuers. Second, 0.9% was the “standard” threshold of Visa’s old Dispute Monitoring Program (VDMP), which also required at least 100 disputes in the month; VDMP was retired on 31 March 2025. Third, the Visa Acquirer Monitoring Program (VAMP) that replaced it on 1 April 2025 counts fraud reports (TC40) plus disputes (TC15) over settled card-not-present transactions; for Asia Pacific merchants the “excessive” threshold is 1.5% from 1 April 2026, and a merchant enters monitoring only with at least 1,500 such events in a month (Visa 2025). Acquirers and payment gateways often keep stricter internal risk lines of their own. This book uses 0.9% as the merchant’s own operating alert line, and 0.65% as a more conservative buffer.

Steering high-risk orders to instant QR payment

Besides cards, Malaysian buyers can pay by instant transfer through DuitNow QR or e-wallets (Bank Negara Malaysia 2018). These transfers have no card-style chargeback procedure, so steering the riskiest orders to QR payment lowers the event rate on the card channel. The cost is that some buyers who are shown only the QR option abandon the payment.

Calculation

# Chapter 1. p01: Routing orders between cards and instant QR payment.
# Orders fall into five risk segments (shares 0.40/0.25/0.15/0.12/0.08,
# ticket RM 150). On the card route 90% of attempts succeed, the fee is
# 2.9% + RM 1, and a share r of settled card sales later brings a fraud
# report or dispute (0.2%, 0.4%, 0.8%, 2%, 5%); each costs RM 150 + RM 60
# with probability 0.7. A buyer offered only DuitNow/e-wallet QR (fee 1%,
# no chargebacks) completes with probability 0.85/0.82/0.78/0.70/0.60.
# Choose for each segment the share x offered cards (0, 0.25, ... 1) to
# maximise margin with the card event ratio at or below a target.
from itertools import product

SHARE = (0.40, 0.25, 0.15, 0.12, 0.08)
RATE = (0.002, 0.004, 0.008, 0.02, 0.05)
QR = (0.85, 0.82, 0.78, 0.70, 0.60)
TICKET, CARD_OK = 150.0, 0.90
GRID = (0.0, 0.25, 0.5, 0.75, 1.0)

def margins(i):
    card = CARD_OK * (TICKET - 0.029 * TICKET - 1.0 -
                      RATE[i] * 0.7 * (TICKET + 60))
    qr = QR[i] * (TICKET - 0.01 * TICKET)
    return card, qr

def evaluate(x):
    card_sales = sum(SHARE[i] * x[i] * CARD_OK for i in range(5))
    events = sum(SHARE[i] * x[i] * CARD_OK * RATE[i] for i in range(5))
    paid = card_sales + sum(SHARE[i] * (1 - x[i]) * QR[i] for i in range(5))
    m = sum(SHARE[i] * (x[i] * margins(i)[0] + (1 - x[i]) * margins(i)[1])
            for i in range(5))
    return events / card_sales, paid, m

def best(target):
    ok = [(evaluate(x)[2], x) for x in product(GRID, repeat=5)
          if sum(x) > 0 and evaluate(x)[0] <= target]
    return max(ok)[1]

if __name__ == "__main__":
    allc = (1.0,) * 5
    r, paid, m = evaluate(allc)
    print("   all on cards: event ratio {:.2%}, paid {:.3f}".format(r, paid))
    print("     RM {:,.0f} per 10,000 orders".format(1e4 * m))
    for target in (0.015, 0.009, 0.0065):
        x = best(target)
        r, paid, m = evaluate(x)
        print("   target {:.2%}: card shares {}".format(
            target, " ".join("{:.2f}".format(v) for v in x)))
        print("     ratio {:.2%}, paid {:.3f}, RM {:,.0f} per 10,000"
              " orders".format(r, paid, 1e4 * m))
#    all on cards: event ratio 0.94%, paid 0.900
#      RM 1,289,414 per 10,000 orders
#    target 1.50%: card shares 1.00 1.00 1.00 1.00 1.00
#      ratio 0.94%, paid 0.900, RM 1,289,414 per 10,000 orders
#    target 0.90%: card shares 1.00 1.00 1.00 1.00 0.75
#      ratio 0.86%, paid 0.894, RM 1,282,520 per 10,000 orders
#    target 0.65%: card shares 1.00 1.00 1.00 1.00 0.00
#      ratio 0.59%, paid 0.876, RM 1,261,838 per 10,000 orders

With illustrative parameters, orders fall into five risk segments with event rates from 0.2% to 5%. With everything on cards, the card event ratio is 0.94% and gross margin RM 1,289,414 per 10,000 orders. With 0.9% as the alert line, the best routing sends three quarters of the riskiest segment to cards, lowering the ratio to 0.86% at a margin of RM 1,282,520. With the 0.65% buffer, the riskiest segment goes entirely to QR: the ratio falls to 0.59%, the payment completion rate from 0.900 to 0.876, and margin to RM 1,261,838, about 2% less.

Note

Routing does not change refund obligations. Steering to QR payment targets stolen cards and fraud; refunds owed to buyers by law or by the shop’s own policy must still be paid. Splitting orders or creating small transactions to dilute the denominator usually breaches the acquiring agreement, and this book does not discuss such practices.

Chargebacks arrive late

The monitored ratio divides the events received in a month by the transactions settled in it, and the events a month’s sales bring arrive over the following months. In the illustrative model, 45% arrive the same month, 40% the next and 15% the month after. In months 4 and 5 a fraud ring adds 1,500 orders a month, all scoring in the riskiest segment.

Calculation

# Chapter 1. p02: Disputes arrive late. Of the fraud reports and disputes
# that a month's card sales will bring, 45% are reported that month, 40%
# the next and 15% the month after; the monitored ratio divides the
# events REPORTED in a month by the card sales SETTLED in it. 12,000
# orders a month in the segments of p01; in months 4 and 5 a fraud ring
# adds 1,500 orders a month that score in the riskiest segment, with an
# event rate of 15% if they reach cards (QR completion 5%). Routings:
# loose = the 0.90% routing of p01, strict = segments 4 and 5 half and
# none on cards. Controllers: always loose; react to LAST month's
# observed ratio (> 0.90% -> strict next month); score orders at checkout
# and go strict in any month whose expected ratio exceeds 0.90%.
# 300 simulated years each, seed 85 (counts drawn from normal or
# Poisson approximations to the binomial).
import random
from math import exp

SHARE = (0.40, 0.25, 0.15, 0.12, 0.08)
RATE = (0.002, 0.004, 0.008, 0.02, 0.05)
LOOSE = (1.0, 1.0, 1.0, 1.0, 0.75)
STRICT = (1.0, 1.0, 1.0, 0.5, 0.0)
LAG = (0.45, 0.40, 0.15)

def binom(rng, n, p):
    """Binomial draw: normal for large counts, Poisson for rare events."""
    v = n * p * (1 - p)
    if v > 30:
        return min(n, max(0, round(n * p + v ** 0.5 * rng.gauss(0, 1))))
    lam, k, u = n * p, 0, rng.random()
    term = exp(-lam)
    cum = term
    while u > cum and k < n:
        k += 1
        term *= lam / k
        cum += term
    return k

def month_orders(m):
    rows = [(12000 * s, r) for s, r in zip(SHARE, RATE)]
    attack = 1500 if m in (4, 5) else 0
    return rows, attack

def expected_ratio(m, x):
    rows, attack = month_orders(m)
    sales = sum(n * x[i] * 0.9 for i, (n, r) in enumerate(rows))
    ev = sum(n * x[i] * 0.9 * r for i, (n, r) in enumerate(rows))
    sales += attack * x[4] * 0.9
    ev += attack * x[4] * 0.9 * 0.15
    return ev / sales

def year(rng, rule):
    pipe = [0.0] * 15
    obs, prev = [], 0.0
    for m in range(1, 13):
        if rule == "loose":
            x = LOOSE
        elif rule == "react":
            x = STRICT if prev > 0.009 else LOOSE
        else:
            x = STRICT if expected_ratio(m, LOOSE) > 0.009 else LOOSE
        rows, attack = month_orders(m)
        sales = 0
        for i, (n, r) in enumerate(rows):
            k = binom(rng, int(n * x[i]), 0.9)
            sales += k
            ev = binom(rng, k, r)
            for j, w in enumerate(LAG):
                pipe[m + j] += ev * w
        k = binom(rng, int(attack * x[4]), 0.9)
        sales += k
        ev = binom(rng, k, 0.15)
        for j, w in enumerate(LAG):
            pipe[m + j] += ev * w
        prev = pipe[m] / sales
        obs.append(prev)
    return obs

if __name__ == "__main__":
    rng = random.Random(85)
    print("   controller     month: 3     4     5     6     7"
          "   months > 0.90%")
    for rule in ("loose", "react", "checkout"):
        runs = [year(rng, rule) for _ in range(300)]
        mean = [sum(r[m] for r in runs) / 300 for m in range(12)]
        over = sum(sum(1 for v in r if v > 0.009) for r in runs) / 300
        print("   {:<10} {}   {:.2f}".format(rule, " ".join(
            "{:5.2%}".format(mean[m]) for m in range(2, 7)), over))
#    controller     month: 3     4     5     6     7   months > 0.90%
#    loose      0.85% 1.37% 1.90% 1.64% 1.07%   5.32
#    react      0.86% 1.21% 1.35% 0.94% 0.67%   2.74
#    checkout   0.86% 0.76% 0.56% 0.62% 0.79%   1.33

Routing at 0.9% throughout (no adjustment), the observed ratios in months 4 to 7 are 1.37%, 1.90%, 1.64% and 1.07%, and on average 5.32 months a year are above 0.9%. Reacting to last month’s ratio, the attack is pushed down only in months 5 and 6 (1.35%, 0.94%), with 2.74 months a year above the line. Predicting this month’s event rate from order scores at checkout and adjusting at once brings month 4 down to 0.76%, with only 1.33 months a year above the line, and those mostly from random variation in ordinary months.

Observed card event ratio each month under three ways of control (p02, mean of 300 years). Dotted lines at 0.9% and 1.5%.

Summary

0.9% is the threshold of the retired VDMP standard level; the current VAMP counts fraud reports and disputes together, with an Asia Pacific threshold of 1.5%. Steering the riskiest orders to QR lowers the event ratio from 0.94% to 0.59% at a cost of about 2% of margin. Chargebacks arrive late, so reacting to last month’s ratio is always a step behind; predicting from scores at checkout controls an attack in the month it happens.

References

Bank Negara Malaysia. 2018. Interoperable Credit Transfer Framework. Policy document.
Visa. 2025. Visa Acquirer Monitoring Program (VAMP): Program Overview and Merchant Thresholds. Visa Inc.

Fan, Y. (2026). Cross-Border Payment Routing, Chargeback Defense Games and Treasury Ruin Bounds: Multi-Acquirer Success Optimization, Dispute Evidence Scoring and Cramér-Lundberg Cash Reserves [跨境支付智能路由、拒付抗辩博弈与资金池破产边界] (Version 1.0.0). 5D Library. https://doi.org/10.5281/zenodo.24090225 · Licensed under Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0).