--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-yokohama-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3by bundleId : - delta3by --- # Combined Financial Services Card Operations release notes for upgrades from Yokohama to Brazil # Combined Financial Services Card Operations release notes for upgrades from Yokohama to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 17 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Financial Services Card Operations Release Notes for Upgrades from Yokohama to Brazil This consolidated release information guides ServiceNow customers through upgrading Financial Services Card Operations from the Yokohama release to Brazil. It includes new features, important changes, deprecations, activation instructions, and highlights across multiple release families. The information enables financial services customers to efficiently manage card and ACH dispute lifecycles, improve fraud detection, streamline workflows, and enhance user experience. Show full answer Show less ## Pre-Upgrade Considerations During the Yokohama upgrade, the Card Disputes Transaction table was reparented to the Financial Task table in Financial Services Operations Core. This structural change leverages platform improvements while maintaining existing functionality. Customers with large dispute transaction data should anticipate longer upgrade times. ## New Features * **Yokohama:** Introduction of friendly fraud detection for Visa disputes with rule-based resolution options (credit, decline, chargeback). Enhanced Visa disputes playbook supports associated transactions, multiple dispute management, and escalation stages (pre-arbitration, arbitration, appeal). * **Zurich:** Guided ACH dispute workflow unifying intake, investigation, and resolution, supporting regulatory compliance and reducing manual effort. Enhanced Mastercard dispute workspace and integration with Mastercom APIs for streamlined dispute lifecycle management. * **Australia \& Brazil:** New questions added to capture key details such as facility withdrawal dates and hotel checkout dates to support chargeback eligibility for specific Visa reason codes. Introduction of a compelling-evidence transaction details read-back field in Visa dispute reviews. ## Changes to Existing Features * **Visa Resolve Online Updates:** Alignment with version 25.1 including removal and update of columns for dispute intake data. * **Mastercard Questionnaire Enhancements:** Additional mandatory questions to support chargeback eligibility and updated dispute intake questions reflecting new Mastercard rule assessments. * **Unified Dispute Intake:** Streamlined experience for card and non-card (ACH) transaction disputes enabling faster resolution and less manual effort. * **Coral Theme:** New default theme with brand-neutral illustrations and optional dark mode for portal, web, and mobile interfaces, improving usability and accessibility. * **Internal Policy Rules:** Now evaluate dispute amounts rather than original transaction amounts, ensuring accurate policy application when amount modifications occur during intake. * **Automated Document Submission:** Mastercard dispute workflows now include automatic validation of attached documents against Mastercard requirements, reducing manual rework and rejection risks. * **Dispute Summarization:** The Now Assist context menu replaces the AI Summary Card component, allowing agents to generate and edit AI-driven dispute summaries directly from dispute records. * **Visa Consumer Disputes:** Repurposed price discrepancy question to correctly mark disputes as ineligible for reason code 13.3 when applicable. ## Deprecations Starting September 2026, the Now LLM Service incorporates Gemma 4 model, with older AI models deprecated for new development and configuration but retained for existing workflows. This ensures access to advanced AI capabilities while maintaining data sovereignty and security. ## Activation and Installation Financial Services Card Operations is available for installation through the ServiceNow Store. Customers should request the application via the store and review cumulative release notes there for all app versions. Activation instructions remain consistent across Yokohama, Zurich, Australia, and Brazil releases. ## Accessibility and User Experience The new Coral theme includes a dark mode option for web and mobile, enhancing readability and reducing eye strain. Guided workflows provide real-time visibility into dispute investigation stages---Investigate, Chargeback, and Closure---improving dispute management efficiency. ## Key Benefits for ServiceNow Customers * Streamlined and unified dispute intake and management for card and ACH transactions across multiple payment networks. * Improved fraud detection and resolution capabilities, including friendly fraud for Visa and enhanced Mastercard dispute lifecycle support. * Automated compliance and document validation to reduce manual effort and accelerate dispute resolution. * Enhanced user interfaces and workflows increase agent productivity and improve customer experience. * Ongoing support for AI-driven dispute summarization and advanced analytics through updated LLM services. * Consistent activation and upgrade paths with clear pre- and post-upgrade tasks to minimize disruptions. Consolidated page of all release notes for Financial Services Card Operations from Yokohama to Brazil. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Financial Services Card Operations release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Brazil. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Financial Services Card Operations to Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-financialservicescardoperations-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | Upgrade information : During the upgrade to Yokohama, the Financial Services Card Operations plugin reparents the Card Disputes Transaction table \[sn_bom_credit_card_disputes_transaction\] to the Financial Task table \[sn_bom_task\] in Financial Services Operations Core. Reparenting leverages the benefits and advancements of ServiceNow® Financial Services Operations Core while preserving the functionality of existing applications. Note: If your instance uses the Card Disputes Transaction table \[sn_bom_credit_card_disputes_transaction\] and it contains a large amount of data, you may experience increased upgrade times. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for Financial Services Card Operations. {#dfrn3-financialservicescardoperations-summary__entry__12} | Release | Release notes | |-|-| | Yokohama | [Detect friendly fraud](https://www.servicenow.com/docs/access?context=resolve-friendly-fraud&family=yokohama&ft:locale=en-US) : Resolve friendly fraud disputes with predefined rules to ensure consistent and precise detection of friendly fraud in Visa disputed transactions. Agents can decline requests, issue credits, or proceed with chargebacks, allowing for tailored responses based on the situation. [Enhanced Visa disputes playbook](https://www.servicenow.com/docs/access?context=managing-card-disputes&family=yokohama&ft:locale=en-US) : Leverage an updated card disputes processing flow to associate additional transactions, manage multiple transaction disputes, and handle pre-arbitration, arbitration, and appeal requests to Visa for allocation and collaboration chargeback workflows. | | Zurich | [ACH disputes workflow](https://www.servicenow.com/docs/access?context=work-dispute-ach&family=zurich&ft:locale=en-US) : Resolve ACH disputes faster with a guided, end-to-end workflow that unifies intake, investigation, and resolution---built on a framework ready for any non-card transaction. The unified intake now features a new dispute reason framework for accurate regulatory mapping and embedded WSUD signature collection for seamless authorization capture. The overall workflow centralizes data, applies real-time regulatory checks, and surfaces next best actions to reduce manual effort and speed decisioning, all on a modular design that can scale to additional non-card dispute types. [Workflow](https://www.servicenow.com/docs/access?context=dispute-management-workflows&family=zurich&ft:locale=en-US) : Resolve Mastercard disputes quickly with an enhanced end-to-end workspace that supports all stages of the dispute life cycle, including pre-arbitration and arbitration. Use comprehensive tools to simplify and accelerate the dispute management process. | | Australia | Date facilities were withdrawn : Dispute agents and cardholders can now record the date facilities were withdrawn by answering the question "Date of the facilities were withdrawn." This question displays only after answering Yes to "Certification that the facilities were withdrawn," and supports chargeback eligibility evaluation for reason code 13.2 (Cancelled Recurring Transaction). Date cardholder checked out from hotel : Dispute agents and cardholders can now record the date a cardholder checked out from a hotel by answering the question "Date cardholder checked out from hotel." This question displays only for disputes filed as Not as Described (reason code 13.3) or for a services dispute, where the merchant is categorized under a hotel or lodging merchant category code (MCC 7011, or the 3501-3856 hotel-chain range). CE Transaction Details : View compelling-evidence transaction details as a read-back field when reviewing Visa dispute details. | | Brazil | Date facilities were withdrawn : Dispute agents and cardholders can now record the date facilities were withdrawn by answering the question "Date of the facilities were withdrawn." This question displays only after answering Yes to "Certification that the facilities were withdrawn," and supports chargeback eligibility evaluation for reason code 13.2 (Cancelled Recurring Transaction). Date cardholder checked out from hotel : Dispute agents and cardholders can now record the date a cardholder checked out from a hotel by answering the question "Date cardholder checked out from hotel." This question displays only for disputes filed as Not as Described (reason code 13.3) or for a services dispute, where the merchant is categorized under a hotel or lodging merchant category code (MCC 7011, or the 3501-3856 hotel-chain range). CE Transaction Details : View compelling-evidence transaction details as a read-back field when reviewing Visa dispute details. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Financial Services Card Operations features. {#dfrn3-financialservicescardoperations-summary__entry__22} | Release | Release notes | |-|-| | Yokohama | [Visa Resolve Online (VROL) version 25.1 updates](https://www.servicenow.com/docs/access?context=card-operations-reference&family=yokohama&ft:locale=en-US) : Updated the following columns to align with release 25.1 revision changes: * The is_parcelado column has been removed from the dispute intake table. * The domain value description for the DisputeResponseReason column has been updated from Copy of ATM Cash Disbursement or Load Transaction to Copy of ATM Cash Disbursement. | | Zurich | [Updated dispute intake questionnaire for July Store release](https://www.servicenow.com/docs/access?context=dispute-rules-content-pack-for-mastercard-landing-page&family=zurich&ft:locale=en-US) : New questions have been added to the dispute intake questionnaire to support updated Mastercard chargeback ineligibility rule assessment. * For Goods or Services Not Provided disputes (RC 4853): Dispute agents must select the applicable waiver and insurance status for merchandise delivery. Options are: a liability waiver was signed by the buyer; shipment insurance was declined by the buyer; both a liability waiver was signed and shipment insurance was declined; or neither applied. This question is mandatory for dispute agents and is also displayed to cardholders. * For Authorization disputes (RC 4808): Dispute agents must identify the current account status. Options include: account closed; suspended or restricted; fraud or compromise; credit-related issue; or account active and in good standing. This question is specific to Mastercard and is not displayed to cardholders. The following additional changes have been made to existing questionnaire questions in this release: * The What is the dispute about? question choice list has been updated: the Multiple Authorization Requests option has been removed from the RC 4808 Authorization list, and Late Presentment has been removed from the RC 4834 Processing Errors list. The following labels have been updated: CAT 3 Devices (formerly Cardholder-Activated Terminal); Transit First Ride Risk (FRR) and Transit First Ride Issuer Liability (FRIL) claims; Installment Billing Dispute-Participating Countries; Cardholder Dispute-Not Elsewhere Classified-United States Domestic (new). * Display conditions have been updated for several existing RC 4853 Cardholder Disputes questions --- including merchandise return date, date the cardholder first notified the issuer, and whether previous negotiation with the merchant occurred --- to reflect the addition of the Cardholder Dispute-Not Elsewhere Classified- United States Domestic sub-category. * For Refund Not Processed disputes (RC 4853): The question asking for the date the cardholder first notified the issuer of the dispute is displayed when the credit voucher or transaction receipt is not dated. This question applies to dispute agents only. [Updated chargeback eligibility questionnaire for May Store release](https://www.servicenow.com/docs/access?context=dispute-rules-content-pack-for-mastercard-landing-page&family=zurich&ft:locale=en-US) : New Mastercard-specific questions have been added to the chargeback eligibility questionnaire. For Authorization disputes (all RC 4808 sub-categories): A new mandatory certification statement appears in the dispute information section. It displays after the dispute amount modification reason field. Dispute agents must confirm that authorization was required for the transaction but was not properly obtained before an Authorization chargeback can proceed. For Consumer Dispute RC 4853 Failed Travel Merchant: Two new questions support the bond or insurance scheme reimbursement requirement: * When a bond or insurance scheme exists, agents are asked what response was received from the bonding authority or insurance scheme when reimbursement was requested. * When no response has been received, agents are asked to provide the date on which the reimbursement request was submitted. Questionnaire questions were updated including RC 4853 Failed Travel Merchant -- Intra-EEA and Domestic European Transactions Only as an additional display condition. [Resolving disputes with Mastercard](https://www.servicenow.com/docs/access?context=work-on-disputes-integrated-with-mc&family=zurich&ft:locale=en-US) : Integrate the Dispute Management workflow with subflows that communicate with Mastercom, supporting an end-to-end dispute life-cycle from raising an initial dispute to final resolution. [Unified dispute intake experience](https://www.servicenow.com/docs/access?context=dispute-intake-overview&family=zurich&ft:locale=en-US) : The dispute intake process has been streamlined to provide a clear, intuitive experience for customers and dispute agents, resulting in faster resolution and reduced manual effort. A unified interface now allows cardholders, account holders, and agents to raise disputes for both card and non-card (ACH) transactions seamlessly. Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Workflow](https://www.servicenow.com/docs/access?context=dispute-management-workflows&family=zurich&ft:locale=en-US) : Track the progress of the investigation workflow intuitively with a redesigned user interface that presents each transaction within a dispute case using a clear, process-based layout. This new layout visualizes the distinct stages of the investigation workflow, Investigate, Chargeback, and Closure, which enhances visibility and dispute management efficiency. | | Australia | Price-discrepancy question for Visa consumer disputes : An existing question, originally used under the Processing Errors dispute category, has been repurposed for consumer disputes filed under reason code 13.3 (Not as Described or Defective Merchandise/Services). Dispute agents are asked "Is the dispute due to the difference between the quoted price and the actual charges made by the merchant?" and cardholders are asked "Is the dispute related to a discrepancy between the quoted price and the actual charges made by the merchant?" A Yes answer marks the dispute ineligible for reason code 13.3, since a price discrepancy is not a valid basis for that reason code under the Visa Chargeback Guide. [Visa dispute management on the one-pager workspace](https://www.servicenow.com/docs/access?context=work-on-a-dispute-case-integrated-with-visa&family=australia&ft:locale=en-US) : All Visa dispute tasks across the investigation, collaboration, and allocation stages are available in a single-page workspace, replacing the previous playbook-based experience. Dispute agents can view associated transactions from the Visa network directly on the task form and access the pre-arbitration questionnaire inline, with status tracking. [Updated dispute intake questionnaire for July Store release](https://www.servicenow.com/docs/access?context=installed-with-card-operations&family=australia&ft:locale=en-US) : New questions have been added to the dispute intake questionnaire to support updated Mastercard chargeback ineligibility rule assessment. * For Goods or Services Not Provided disputes (RC 4853): Dispute agents must select the applicable waiver and insurance status for merchandise delivery. Options are: a liability waiver was signed by the buyer; shipment insurance was declined by the buyer; both a liability waiver was signed and shipment insurance was declined; or neither applied. This question is mandatory for dispute agents and is also displayed to cardholders. * For Authorization disputes (RC 4808): Dispute agents must identify the current account status. Options include: account closed; suspended or restricted; fraud or compromise; credit-related issue; or account active and in good standing. This question is specific to Mastercard and is not displayed to cardholders. The following additional changes have been made to existing questionnaire questions in this release: * The What is the dispute about? question choice list has been updated: the Multiple Authorization Requests option has been removed from the RC 4808 Authorization list, and Late Presentment has been removed from the RC 4834 Processing Errors list. The following labels have been updated: CAT 3 Devices (formerly Cardholder-Activated Terminal); Transit First Ride Risk (FRR) and Transit First Ride Issuer Liability (FRIL) claims; Installment Billing Dispute-Participating Countries; Cardholder Dispute-Not Elsewhere Classified-United States Domestic (new). * Display conditions have been updated for several existing RC 4853 Cardholder Disputes questions --- including merchandise return date, date the cardholder first notified the issuer, and whether previous negotiation with the merchant occurred --- to reflect the addition of the Cardholder Dispute-Not Elsewhere Classified- United States Domestic sub-category. * For Refund Not Processed disputes (RC 4853): The question asking for the date the cardholder first notified the issuer of the dispute is displayed when the credit voucher or transaction receipt is not dated. This question applies to dispute agents only. [Internal policy rule evaluation using dispute amount](https://www.servicenow.com/docs/access?context=dispute-decision-tables&family=australia&ft:locale=en-US) : Internal policy rules in the Card dispute rules for internal policy decision table now evaluate using the dispute amount instead of the original transaction amount. Previously, if a cardholder or agent modified the disputed amount while answering additional transactional questions during intake, policy rules still evaluated against the original transaction value. Rules now use the dispute amount field (sn_bom_credit_card_disputes_transaction.dispute_amount), so any amount adjustments made during intake are correctly reflected in rule outcomes. [Updated chargeback eligibility questionnaire for May Store release](https://www.servicenow.com/docs/access?context=installed-with-card-operations&family=australia&ft:locale=en-US) : New Mastercard-specific questions have been added to the chargeback eligibility questionnaire. For Authorization disputes (all RC 4808 sub-categories): A new mandatory certification statement appears in the dispute information section. It displays after the dispute amount modification reason field. Dispute agents must confirm that authorization was required for the transaction but was not properly obtained before an Authorization chargeback can proceed. For Consumer Dispute RC 4853 Failed Travel Merchant: Two new questions support the bond or insurance scheme reimbursement requirement: * When a bond or insurance scheme exists, agents are asked what response was received from the bonding authority or insurance scheme when reimbursement was requested. * When no response has been received, agents are asked to provide the date on which the reimbursement request was submitted. Questionnaire questions were updated including RC 4853 Failed Travel Merchant -- Intra-EEA and Domestic European Transactions Only as an additional display condition. [Automated document submission in Mastercard transaction dispute process](https://www.servicenow.com/docs/access?context=chargeback-stage-mastercard&family=australia&ft:locale=en-US) : Streamline the submission of supporting documents to Mastercard in the Mastercard Dispute Management workflow through document attachment and validation. Attached files are automatically checked against Mastercard requirements for file type and size. This update reduces the need for manual intervention, minimizes rework, and helps avoid rejection risk. [New subflow and action to support Card data security](https://www.servicenow.com/docs/access?context=card-data-security&family=australia&ft:locale=en-US) : Support attaching documents to a specified table record using the following subflow and action in Card data security: * Attach Document to Table Record * Attach Tokenized Document to Table Record | | Brazil | Dispute Summarization component update : The Now Assist context menu (NACM) component replaces the AI Summary Card component that generated Dispute Summarization on the dispute record page. Dispute agents can generate an AI-generated summary of a dispute from the dispute record page. Dispute agents can share a generated summary to the claim's work notes from the summary component. Selecting Share opens an editable work notes dialog, where agents can edit the summary text before selecting Save to work notes. Activate the Dispute Summarization skill configuration for the summary component to appear. If the skill configuration isn't active, the component doesn't display on the dispute record page. Price-discrepancy question for Visa consumer disputes : An existing question, originally used under the Processing Errors dispute category, has been repurposed for consumer disputes filed under reason code 13.3 (Not as Described or Defective Merchandise/Services). Dispute agents are asked "Is the dispute due to the difference between the quoted price and the actual charges made by the merchant?" and cardholders are asked "Is the dispute related to a discrepancy between the quoted price and the actual charges made by the merchant?" A Yes answer marks the dispute ineligible for reason code 13.3, since a price discrepancy is not a valid basis for that reason code under the Visa Chargeback Guide. | [ ] ## Removed Between your current release family and Brazil, some Financial Services Card Operations features or functionality were removed. {#dfrn3-financialservicescardoperations-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Financial Services Card Operations features or functionality were deprecated. {#dfrn3-financialservicescardoperations-summary__entry__42} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | Now LLM Service deprecation notice : Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. We're committed to bringing you the latest industry advancements while maintaining sovereignty-focused options, all hosted and governed by ServiceNow with the infrastructure and data protections you rely on today. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the [KB3066214: ServiceNow Otto Model Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3066214) article in the Now Support Knowledge Base. | | Brazil | Now LLM Service deprecation notice : Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. The latest industry advancements are available alongside sovereignty-focused options. All models are hosted and governed by ServiceNow with the same infrastructure and data protections. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the [KB3066214: ServiceNow Otto Model Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3066214) article in the Now Support Knowledge Base. | [ ] ## Activation information Review information on how to activate Financial Services Card Operations. {#dfrn3-financialservicescardoperations-summary__entry__52} | Release | Release notes | |-|-| | Yokohama | Activation information : Install Financial Services Card Operations by requesting it from ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US). Important: Financial Services Card Operations is available in ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Important: Financial Services Card Operations is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Australia | Activation information : Install Financial Services Card Operations by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=australia&ft:locale=en-US). Important: Financial Services Card Operations is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Brazil | Activation information : Install Financial Services Card Operations by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=brazil&ft:locale=en-US). | [ ] ## Additional requirements If any additional requirements were introduced or changed for Financial Services Card Operations we have noted them here. {#dfrn3-financialservicescardoperations-summary__entry__62} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Financial Services Card Operations we have noted them here. {#dfrn3-financialservicescardoperations-summary__entry__72} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Financial Services Card Operations, such as specific requirements or compliance levels. {#dfrn3-financialservicescardoperations-summary__entry__82} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Financial Services Card Operations we have noted them here. {#dfrn3-financialservicescardoperations-summary__entry__92} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Financial Services Card Operations we have noted them here. {#dfrn3-financialservicescardoperations-summary__entry__102} | Release | Release notes | |-|-| | Yokohama | * Resolve friendly fraud disputes by incorporating friendly fraud detection and resolution in the existing dispute flow for Visa transactions. You can take actions such as crediting the customer, denying the dispute, or initiating an exception process. * The Financial Services Card Operations data model is updated in this release with reparented tables to align the data and manage the dispute transactions more effectively. See [Card Operations](https://www.servicenow.com/docs/access?context=card-ops-landing-page&family=yokohama&ft:locale=en-US) for more information. * Enhance the card disputes process with an updated end-to-end Visa disputes playbook that now includes support for reviewing associated transactions and handling pre-arbitration, arbitration, and appeals. * Manage and work on multiple disputed transactions for a case with individual playbooks for each disputed transaction. * Integrate new VROL subflows into the enhanced Visa card disputes playbook. | | Zurich | * Resolve disputes with a new dispute life cycle for Mastercard dispute transactions. * Leverage a new workspace page in Financial Services Card Operations to resolve Mastercard disputes. * Integrate Mastercard's Mastercom APIs into the Dispute Management workflow to resolve card disputes faster and more efficiently. * Resolve ACH disputes faster with a guided, end-to-end workflow that unifies intake, investigation, and resolution---built on a framework ready for any non-card transaction. * Streamline operations with a single, consistent intake process that applies across all dispute workflows. See [Workflow](https://www.servicenow.com/docs/access?context=dispute-management-workflows&family=zurich&ft:locale=en-US) for more information. | | Australia | * Work on Visa dispute transactions and associated transactions from a unified Dispute Workspace for all active transactions. * Streamline dispute document submission to Mastercard with the document attachment and validation enhancement. * Improve dispute resolution accuracy with updated internal policy rules that evaluate the dispute amount rather than the original transaction amount. See [Card Operations](https://www.servicenow.com/docs/access?context=card-ops-landing-page&family=australia&ft:locale=en-US) for more information. | | Brazil | * Manage credit card openings and closings on one platform. * Simplify credit card blocking and credit limit processes. * Enable agents to create and manage dispute cases for both personal and business, debit and credit card accounts, and ACH dispute cases. * Enhanced user experience through guided workflows and real-time visibility. See [Card Operations](https://www.servicenow.com/docs/access?context=card-ops-landing-page&family=brazil&ft:locale=en-US) for more information. | [ ]