Corrections

PaymentBrief corrects factual errors identified by readers or during editorial review. This page contains selected material historical corrections reconstructed from the publication record and, going forward, notes about consequential corrections. It is not a complete log of every change or an assertion that all earlier corrections were publicly logged when made.

How to report an error

If you find a factual error, an outdated figure, or a claim that is unsupported by its cited source, email contact@paymentbrief.com with:

• The URL of the page containing the error
• The specific claim you believe is incorrect
• The source or evidence you believe is correct

We review reports and prioritise errors that could change an operational decision. Please include the source and affected passage so we can check them. We cannot promise a fixed response or correction time.

Severity classification

Material

A wrong factual claim that could change an operational or commercial decision — for example, a rate, deadline or misattributed regulation. We prioritise correction and document the consequential change.

Minor

Typographical errors, formatting issues, outdated but not misleading figures, or broken links. These are fixed on a rolling basis and are not individually logged unless the underlying data changed materially.

Clarification

Content that is technically accurate but has caused reader confusion. We may revise the wording or add context while preserving the underlying evidence.

Corrections log

The October entries record current editorial corrections. Historical entries below it were assembled on 7 October 2026 from the 27 August publication changes. The dates shown are correction dates, not the dates the historical entries first appeared on this log. This is a selected log, not a claim that every past correction is listed.

• 28 October 2026 — Card on file, tokenization and network tokens: corrected wording about retained card data: card verification codes must not be stored after authorization, even encrypted. Tokenization does not automatically remove PCI DSS obligations, and moving stored credentials depends on the providers and token arrangements rather than always requiring customer re-entry.
• 28 October 2026 — Stored-value operations: replaced the Kenya draft-regulation reference with the enacted 2014 rules and removed the assertion that trust-fund income belongs freely to the operator. Trust balances and permitted uses of income are governed by the applicable safeguarding requirements.
• 28 October 2026 — Cross-border FX and payment orchestration: removed universal refund-conversion and build-versus-buy thresholds. Refund exchange-rate treatment is product-specific; orchestration costs and credential portability depend on the actual integration and contract.
• 28 October 2026 — Japan, Mexico and Philippines: removed unsupported payment-share charts and conflicting wallet-user figures. Corrected Mexico's DiMo launch year and distinguished Philippine payment-system operators from scheme management. Japan's konbini estimate is now attributed and limited to online purchases.
• 14 October 2026 — CE 3.0 and linked dispute guides: corrected the prior-transaction timing anchor to dispute submission/processing, recorded the original-credit exception, and removed wording that treated qualification as a guaranteed merchant win. Unsourced manual-versus-automation win-rate comparisons were removed from the main representment guides.
• 14 October 2026 — EU AI Act payment-system guide: corrected the Annex III high-risk commencement date to 2 December 2027 and limited the financial-fraud exclusion to the creditworthiness category rather than all payment AI uses.
• 14 October 2026 — Authorization rate, rolling reserve and decline code 05: removed universal benchmark/retry/term assumptions and distinguished issuer requests, merchant attempts and contract-specific reserve terms.
• 14 October 2026 — Dispute reason codes and linked representment references: removed fixed merchant response allowances that confused network stages with merchant deadlines. Use the exact deadline in the PSP or acquirer case notice.
• 14 October 2026 — Norway and Bangladesh: corrected product-pricing and merchant-eligibility generalisations, removed unsupported checkout-share estimates, and separated rail availability from contracted acceptance. Bangladesh interoperability guidance distinguishes the instructed start date from provider availability.
• 14 October 2026 — AI fraud detection: removed unsupported performance and loss statistics and replaced them with a sourced evaluation framework and explicitly hypothetical economics. Clarified the EU AI Act creditworthiness exception for fraud detection; this does not exempt every payment AI use case.
• 13 October 2026 — SEPA R-transaction reference, SCT Inst runbook and code lookup: AM02 had been described as a current SCT Inst inter-PSP amount-limit reject. The 2025 implementation guidelines removed it from the negative-confirmation lists. The current EPC guidance lists AM23 for an inter-PSP settlement-limit reject, which concerns the originator PSP's settlement guarantees, not the payer's own transfer limit. The historical AM02 lookup remains available but no longer claims current scheme applicability.
• 13 October 2026 — SEPA operator guide, SEPA glossary and linked references: outdated 36-country and 20-euro-member figures were replaced with the EPC's current 41-country-and-territory scope and Bulgaria's 2026 euro adoption. The guide also removed a table that incorrectly treated €100,000 as an SCT Inst scheme limit. The glossary corrected its statement that SDD B2B banks need not check mandates and qualified absolute no-recovery claims for credit transfers.
• 13 October 2026 — e-mandate glossary: the old ₹15,000 no-AFA threshold had been presented without the RBI's ₹1 lakh exception for specified recurring categories. The issuer's pre-debit notification duty is now distinguished from the merchant's integration responsibility.
• 13 October 2026 — Ghana guide and operator companion: unsupported provider-share and checkout-mix figures were removed. Bank of Ghana network totals were added with their scope stated. The market guide also corrected its virtual-asset framework status after the 2025 Act. The companion narrowed foreign-ownership language that had treated the absence of an explicit restriction as approval.
• 27 August 2026 — United Kingdom guide: an FAQ retained an earlier proposed APP fraud reimbursement maximum of £415,000. The operative maximum cited in the corrected guide is £85,000. The page had already stated the lower figure elsewhere.
• 27 August 2026 — United Kingdom guide: wording treated £100 as a mandatory contactless cap. The mandatory cap had been removed; issuers may still choose that limit.
• 27 August 2026 — Malaysia guide: the guide referred to a Malaysian “Payment Services Act 2019”. That statute is Singapore's, and the Malaysian references were corrected.
• 27 August 2026 — Philippines guide: PESONet was described as having two settlement windows per business day. The corrected guide describes three published windows.
• 27 August 2026 — Philippines guide: the guide said there was no recall route for a transfer. The categorical statement was removed and the relevant fraud-response and urgent-recall mechanisms were distinguished from a guaranteed recovery.