Card network rule changes and mandates from Visa, Mastercard and other schemes that issuers, acquirers, processors and merchants must build, test and certify, with the opportunity each one opens up.
Updated monthly · Last updated: · Items leave the tracker once their month has passed.
Who sets card network rules
| Network or body | Rules | Payments angle | Who it applies to |
|---|---|---|---|
| Visa | Visa Core Rules and Product and Service Rules; spring and fall releases | Authorization, disputes, tokens, authentication, fees | Issuers, acquirers, processors, merchants |
| Mastercard | Transaction Processing Rules, Security Rules and Procedures, bulletins | Data fields, authentication, address checks, offline chip | Issuers, acquirers, processors, merchants |
| EMVCo | EMV chip, 3-D Secure and tokenization specifications | The technical standards the networks build on | Schemes, vendors, testers |
| PCI Security Standards Council | PCI DSS and PTS (see the Cloud tracker) | Card data security and device approvals | Anyone handling card data |
What changed this month
A short log of new and changed items, updated every month.
Week of Nov 16, 2026
- Tracker launched with 6 card network mandates from Visa and Mastercard.
- Next deadline: Mastercard Transaction Link ID on recurring and card-on-file charges, Dec 1, 2026.
- Moved here from the Payment Rules tracker: Mastercard TLID and offline chip payments, so each item appears on one tracker only.
Card network mandate tracker
Soonest first. Tap a network or a status to filter; tap again to clear.
FILTER BY NETWORK
FILTER BY STATUS
| Network | Rule or change | What it means | Opportunity | Key date |
|---|---|---|---|---|
| Mastercard | Mastercard Transaction Link ID (TLID) Global Our guide → · Source: Stripe docs (summary) | Send the original TLID on recurring and card-on-file charges. | Fewer disputes, no fees; demand for TLID fixes and testing. | Dec 1, 2026 Deadline soon |
| Visa | Enhanced merchant data in issuer apps Europe · issuers Our guide → · Source: Tapix (summary) | Issuers must show merchant name, address, phone and website in digital banking. | Merchant data enrichment to cut unknown-charge disputes. | Jan 23, 2027 Upcoming |
| Mastercard | Mastercard offline chip payments across Europe European Union Our guide → · Source: Mastercard | New cards from Feb 2027, new terminals by May, must work offline. | Plan chip offline limits, terminal updates and outage fallback testing. | Feb–May 2027 Upcoming |
| Mastercard | Issuers must support address verification (AVS) Brazil, Mexico, Puerto Rico, US Virgin Islands Our guide → · Source: Mastercard Rules | Issuers in these markets must take part in AVS for most cards. | Address checks in authorization and card-not-present fraud rules. | Apr 21, 2027 Upcoming |
| Visa | Rules for biometric payments at the point of sale Global Our guide → · Source: Visa Rules | A rules framework for tokenized biometric authentication in stores. | Biometric checkout pilots for issuers, acquirers and terminal makers. | Apr 24, 2027 Upcoming |
| Visa | Issuer subscription management deadline moved Global · issuers Our guide → · Source: Visa Rules | Issuers now have until Oct 23, 2027 to let cardholders manage subscriptions. | Subscription view and cancel features in banking apps. | Oct 23, 2027 Delayed |
WHO OWNS THIS
Card network mandates: roles and sign-off
Each mandate needs a named owner. The cards product manager owns the change; scheme relations tracks bulletins and books certification; engineering and QA build and certify; disputes and fraud adjust their processes; the head of cards signs off.
1. Roles and responsibilities
- Writes the impact assessment for each bulletin
- Plans build, certification and launch
- Runs go/no-go
- Reports status weekly
- Reads bulletins and spring and fall releases
- Books certification windows
- Gets waivers and confirmations
- Escalates scheme questions
- Builds message and data changes
- Works with the processor or vendor
- Supports network testing
- Fixes defects before go-live
- Traces each rule clause to tests
- Runs network certification scripts
- Reports pass, fail and open defects
- Signs test completion
- Updates dispute procedures and reason codes
- Trains the team
- Monitors dispute ratios
- Confirms operations are ready
- Tunes fraud rules for new data fields
- Watches network monitoring thresholds
- Owns authentication strategy
- Signs fraud readiness
- Reviews the impact assessment
- Checks customer notices and terms
- Keeps the evidence pack
- Certifies the rule is met
- Sets priorities and funding
- Accepts remaining risk in writing
- Gives the go-live sign-off
- Reports to leadership
2. Who is accountable for what (RACI)
| Activity | Cards PM | Scheme relations | Engineering | QA lead | Disputes | Fraud risk | Head of cards |
|---|---|---|---|---|---|---|---|
| Read the bulletin and log the mandate | C | A | I | I | I | I | I |
| Impact assessment | A | R | C | C | C | C | I |
| Build message and data changes | C | C | A | C | I | I | I |
| Network certification testing | C | R | R | A | I | I | I |
| Dispute and chargeback changes | C | I | C | C | A | C | I |
| Fraud rules and authentication changes | C | I | C | C | C | A | I |
| Go-live sign-off | R | R | R | R | R | R | A |
A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed. The compliance lead reviews impact assessments and certifies the rule is met; not shown as a column.
3. From review to sign-off
4. Sign-off record
One line per mandate. No signed line, no go-live.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| Mastercard TLID on card-on-file charges | Cards product manager | QA lead, Compliance lead | Head of cards | Before Dec 1, 2026 | Test results, scheme confirmation |
| Visa enhanced merchant data (Europe) | Cards product manager | Disputes lead | Head of cards | Before Jan 23, 2027 | App screenshots, data mapping |
| Mastercard AVS for issuers | Card processing engineering lead | QA lead | Head of cards | Before Apr 21, 2027 | Certification results |
Titles differ by firm; small teams may combine roles, but the person who builds should not be the only one who signs off. General guidance, not legal advice.
Runbook: from a card network mandate to sign-off
How to handle a Visa, Mastercard or other network mandate from this tracker. Use one runbook per mandate. Each phase says when, why, what, who and how, and the evidence to keep.
▸1. Plan · Decide if the item applies to you, how big the change is, and who owns it.
When: As soon as an item appears on the tracker. Target: at least 90 days before the key date (T-90). For proposed rules, inside the comment window.
Why: Late discovery is the main reason teams miss deadlines, pay fines or ship rushed changes. Early planning turns a rule into a normal roadmap item.
What: Decide if the item applies to you, how big the change is, and who owns it.
Who: Owner: Cards product manager. With: Scheme relations manager (reads the bulletin), Card processing engineering lead (sizes the work), Fraud risk and Disputes leads (process impact).
Example: a new Visa or Mastercard bulletin. Confirm scope by card type, region and channel.
How
- Open the official source linked in the tracker and read the actual text, not only the summary.
- Map it to your products, rails, systems, vendors and customers in scope.
- Run a short gap analysis: what we do today versus what the rule needs.
- Size the work (small, medium, large) and add it to the roadmap with a target date.
- Log risks, assumptions, issues and dependencies in the RAID log.
Evidence to keep
- Impact assessment (applies / does not apply, with reason)
- Gap analysis
- Epic or change request with owner and target date
- RAID log entry
▸2. Prepare · Turn the rule into requirements, a design, a test plan and a rollout plan.
When: T-90 to T-60 days.
Why: Clear requirements and a test plan stop rework and give auditors a straight line from the rule to the change.
What: Turn the rule into requirements, a design, a test plan and a rollout plan.
Who: Owner: Cards product manager. With: Card processing engineering lead, QA and certification lead (test plan), Scheme relations manager (certification window).
Example: map each new data field to the message spec and a test case.
How
- Write requirements that quote the rule clause they come from.
- Agree the design and any vendor or partner changes, with dates.
- Build a traceability matrix: rule clause, requirement, test case, evidence.
- Plan test data, environments and a rollback.
- Book change windows and tell support and operations teams.
Evidence to keep
- Requirements with rule references
- Design or configuration decision
- Traceability matrix (draft)
- Test plan and rollback plan
▸3. Execute · Build or configure, test, and release the change safely.
When: T-60 days to go-live.
Why: This is where the change is built and proven. Testing against the rule, not just the feature, is what protects you.
What: Build or configure, test, and release the change safely.
Who: Owner: Card processing engineering lead. With: QA and certification lead, processor or vendor.
Example: build Transaction Link ID handling for recurring charges with the processor.
How
- Build or configure the change behind a flag where possible.
- Run unit, system, regression and negative tests, plus UAT with the business.
- Fix defects and re-test; keep the defect log current.
- Hold a go/no-go meeting with clear criteria.
- Release, watch live metrics and keep the rollback ready.
Evidence to keep
- Test results and defect log
- UAT sign-off
- Go/no-go record
- Change ticket and release notes
▸4. Evidence · One evidence pack that shows the rule was understood, built, tested and approved.
When: Collected all the way through; packaged by T-7 days.
Why: If it is not written down, it did not happen. Good evidence makes audits short and calm.
What: One evidence pack that shows the rule was understood, built, tested and approved.
Who: Owner: QA and certification lead. With: Cards product manager, Disputes and chargebacks lead (procedures).
Example: keep network certification results and test logs.
How
- Create one folder per tracker item with a simple index.
- Store each document with date, version and owner.
- Complete the traceability matrix with links to every test and approval.
- Add screenshots or exports of live configuration where relevant.
- Record training or communications sent to staff and customers.
Evidence to keep
- Evidence index
- Final traceability matrix
- Configuration proof
- Training and communication records
▸5. Audit · Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
When: From T-7 days to 30 days after go-live.
Why: An independent check finds gaps before a regulator, scheme or customer does.
What: Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
Who: Owner: Compliance lead (control check). Independent check: Internal audit.
Example: sample five transactions to check the field is present.
How
- Walk through the evidence pack against the rule text.
- Re-perform a sample of key tests or checks.
- Raise findings with a rating, owner and due date.
- Track findings to closure and re-test the fix.
Evidence to keep
- Control test results
- Findings log with owners and dates
- Closure evidence for each finding
▸6. Review · Post-implementation review: did it work, what broke, what we learned.
When: About 30 days after go-live.
Why: A short look back confirms the change works in real life and makes the next rule easier.
What: Post-implementation review: did it work, what broke, what we learned.
Who: Owner: Cards product manager. With: Fraud risk lead, Disputes and chargebacks lead (post-live review at T+30).
Example: check dispute and fraud rates after launch.
How
- Check live metrics: errors, rejects, exceptions, complaints, incidents.
- Confirm all findings and defects are closed or accepted.
- Note lessons learned and update this runbook if needed.
- Update the tracker status and any related guides.
Evidence to keep
- Post-implementation review notes
- Metrics snapshot
- Lessons learned
▸7. Sign-off · Named people confirm the item is done and the evidence is complete.
When: After the review, and before closing the item.
Why: Formal sign-off shows clear ownership and closes the loop for auditors.
What: Named people confirm the item is done and the evidence is complete.
Who: Owner: Head of cards (approves). Signers in order: Cards product manager, Scheme relations manager, Card processing engineering lead, QA and certification lead, Disputes and chargebacks lead, Fraud risk lead, Compliance lead.
Example: close the item when every signer has signed.
How
- Share the evidence pack and review notes with the approvers.
- Each approver confirms their part in writing, with date.
- Archive the pack in your GRC tool or records system.
- Close the epic and the RAID entries.
Evidence to keep
- Signed approvals (name, role, date)
- Archived evidence pack
- Closed epic and RAID items
Sign-off
Sign in this order: Prepared, then Reviewed, then Certified, then Approved. Each signer checks the evidence of the lines above. Close the item only when every line has a name, date and evidence link. The person who prepares cannot approve.
| # | Role | Stage | Confirms | Evidence | Name and date |
|---|---|---|---|---|---|
| 1 | Cards product manager | Prepared | Impact assessment done; scope and acceptance met | Impact assessment, requirements | ________________ |
| 2 | Scheme relations manager | Reviewed | Bulletin read correctly; certification booked | Bulletin reference, booking | ________________ |
| 3 | Card processing engineering lead | Reviewed | Change built, released and stable | Change ticket, release notes | ________________ |
| 4 | QA and certification lead | Certified | Every rule clause tested; network certification passed | Certification results | ________________ |
| 5 | Disputes and chargebacks lead | Certified | Dispute procedures updated; team trained | Procedures, training records | ________________ |
| 6 | Fraud risk lead | Certified | Fraud rules tuned and monitored | Rule change log | ________________ |
| 7 | Compliance lead | Certified | Mandate met; evidence filed | Control test, evidence pack | ________________ |
| 8 | Head of cards | Approved | Accepts remaining risk and closes the item | Signed approval | ________________ |
Tip: copy this runbook into your own tracker or GRC tool, one copy per rule. Dates are relative to the key date shown in the tracker (T-90 means 90 days before).
Risk and control self-assessment (RCSA): Card network mandates
The main risks for this area, the controls that reduce them, and the risk left after those controls. 4 risks are specific to this area and 6 are shared by every tracker (C1 to C6). Owners match the roles in the Who owns this section above. Reviewed every quarter and checked by the second line. Preventive controls lower likelihood; detective and corrective controls lower impact. Read more in our RCSA guide.
10 risks assessed for this area. Controls bring every high inherent risk down to medium or low.
How to read the heat map: each dot is a risk. It starts at its inherent rating (no controls) and moves to its residual rating (after controls). Score = likelihood x impact: 1 to 6 Low, 8 to 12 Medium, 15 to 25 High. Mid-blue dots are this area; navy dots are shared risks.
QUARTERLY RCSA CYCLE
RISK AND CONTROL REGISTER
| ID | Type | Risk and cause | Control | Owner | Inherent | Residual |
|---|---|---|---|---|---|---|
| CN-R1 | This area | A network deadline is missed and fines apply Cause: Bulletins not read; owner not named | Bulletin log with an owner within 5 days; deadline calendar Preventive · Weekly | Scheme relations manager | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| CN-R2 | This area | Network certification fails close to go-live Cause: Test slots booked late; specs misread | Certification booked at T-90; dry run before the window Preventive · Per item | QA and certification lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| CN-R3 | This area | Fraud or dispute ratios break network thresholds Cause: Rules not tuned for new fields | Monthly ratio monitoring with early-warning alerts Preventive and detective · Monthly | Fraud risk lead | High 15 L3 x I5 | Medium 8 L2 x I4 Control: Partly effective |
| CN-R4 | This area | A network fee change is not priced or passed on Cause: Fee bulletins not shared with finance | Fee bulletin review with finance each release Preventive · Per release | Cards product manager | Medium 9 L3 x I3 | Low 3 L1 x I3 Control: Effective |
| C1 | Shared | A rule change is missed Cause: No owner watches the sources; news arrives late | Weekly tracker review; every new item gets a named owner within 5 days Preventive and detective · Weekly | Scheme relations manager | High 20 L4 x I5 | Medium 8 L2 x I4 Control: Effective |
| C2 | Shared | A rule is read the wrong way Cause: Summaries used instead of the rule text; no expert review | The impact assessment is signed against the source text Preventive · Per item | Compliance lead | High 15 L3 x I5 | Medium 10 L2 x I5 Control: Effective |
| C3 | Shared | A deadline is missed Cause: Work starts too late; dependencies not tracked | Planning starts at T-90; RAID log and go/no-go before release Preventive and detective · Per item | Cards product manager | High 16 L4 x I4 | Low 6 L2 x I3 Control: Effective |
| C4 | Shared | Testing does not cover the rule Cause: Tests check features, not rule clauses | Traceability from each rule clause to a test, with sign-off Preventive · Per release | QA and certification lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| C5 | Shared | Evidence is missing at audit time Cause: Documents spread across tools; no index | Evidence pack with an index, checked at T-7 Preventive · Per item | Compliance lead | Medium 9 L3 x I3 | Low 3 L1 x I3 Control: Effective |
| C6 | Shared | Audit findings stay open Cause: No due dates or follow-up | Findings log with owner and due date; monthly review Preventive and detective · Monthly | Compliance lead | Medium 9 L3 x I3 | Low 4 L2 x I2 Control: Partly effective |
Open actions
- CN-R3: add alerts for network monitoring thresholds. Owner: Fraud risk lead.
- CN-R2: book certification windows for all 2027 mandates. Owner: QA and certification lead.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Compliance lead.
Quarterly attestation
Cards product manager (first line): confirm risks, controls and ratings are current. ________________
Compliance lead (second line review): confirms the review and challenge. ________________
Head of cards: accepts residual risk. ________________
This is a sample RCSA for planning and training. Adjust risks, ratings and owners to your own organisation before use. The full cross-area register is in the monthly portfolio status report.
This tracker is a summary for planning, not legal advice. Dates can change, so always check the official source before acting. The Opportunity column is our own view. Summaries are written in our own words; linked pages remain the property of their publishers. Corrections: sp@paymentconsultant.top.
© 2026 SP Sankar · paymentconsultant.top. This tracker, its summaries, diagrams and layout are original work and are protected. Please do not copy, republish or scrape this page without written permission. You are welcome to link to it. See also Payment Rules Tracker and Payment Tech News.