--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-xanadu-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ax bundleId : - delta3ax --- # Combined Financial Services Card Operations release notes for upgrades from Xanadu to Australia # Combined Financial Services Card Operations release notes for upgrades from Xanadu to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 16 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 Xanadu to Australia This consolidated release note summary covers the Financial Services Card Operations (FSCO) upgrades from the Xanadu release through to the Australia release. It provides ServiceNow customers with important upgrade guidance, new features, changes, removals, and activation information to help ensure a smooth transition and enhanced dispute management capabilities within their financial services operations. Show full answer Show less ## Important Upgrade Information * The Yokohama upgrade reparents the Card Disputes Transaction table to the Financial Task table in Financial Services Operations Core, improving functionality and leveraging core enhancements. Customers with large data volumes in this table may experience longer upgrade times. * No updates or changes were noted for the Xanadu, Zurich, and Australia release upgrades. ## Key Features Introduced Across Releases * **Dispute Playbook Enhancements (Xanadu):** Cardholders can initiate disputes directly via a user-friendly portal, attach documents, complete detailed questionnaires, and track dispute status in real time. Agents can review and modify disputes before investigation. * **Card Disputes Enhancements:** Introduction of a common dispute questionnaire table applicable across card networks and relocation of the reason code to the card dispute transaction table for improved data handling. * **Friendly Fraud Detection (Yokohama):** Automated rules to detect and resolve friendly fraud in Visa disputes, allowing agents to decline, credit, or proceed with chargebacks. * **Visa Disputes Playbook Updates:** Expanded workflow supports multiple transactions, pre-arbitration, arbitration, and appeals with integrated Visa Resolve Online (VROL) subflows. * **ACH Disputes Workflow (Zurich):** A guided, unified workflow accelerates ACH dispute resolution with regulatory checks and next-best-action guidance, supporting non-card transactions. * **Mastercard Dispute Management:** End-to-end workspace and integration with Mastercard Mastercom APIs streamline all lifecycle stages, including arbitration. * **Australia-Specific Enhancements:** New questionnaire items capture dates related to withdrawn facilities and hotel checkouts for chargeback eligibility, plus a read-back field for compelling evidence in Visa disputes. * **Unified Dispute Intake Experience:** A streamlined, single interface for cardholders and agents to raise disputes for both card and non-card transactions, reducing manual effort and speeding resolution. * **Coral Theme:** New default, brand-neutral theme with dark mode for portal, web, and mobile interfaces, improving usability and accessibility. * **Visa Dispute Workspace:** A single-page workspace consolidates Visa dispute tasks and related transactions replacing the previous playbook format, enhancing task management efficiency. * **Automated Document Submission (Australia):** Document attachments for Mastercard disputes are automatically validated for file type and size, minimizing manual rework and rejection risks. * **Internal Policy Rule Evaluation Update:** Rules now evaluate based on the dispute amount rather than the original transaction amount, ensuring accurate policy enforcement after amount modifications during intake. ## Changes and Removals * Updated data model including new tables for dispute intake and cardholder dispute intake to support questionnaire processing. * Removed fields from the Card disputes case table to streamline data management. * Removal of the isparcelado column and updates to Visa Resolve Online domain values aligning with latest VROL releases. * Some dispute questionnaire options and labels were updated to reflect Mastercard chargeback rules and improve clarity. * Reason code adjustments, such as moving late presentment reason code from processing error to authorization category. * Deprecated older AI models in the Now LLM Service starting September 2026, focusing on newer Gemma 4 and open-weight models for AI skills and workflows. ## Activation Information Financial Services Card Operations is available via the ServiceNow Store for all releases. Customers can request installation through the store and refer to the version history for cumulative release information. ## Accessibility and Localization * The Coral theme introduces a dark mode option for improved readability and reduced eye strain in web and mobile experiences. * No specific localization changes were introduced across the releases. ## Practical Benefits for ServiceNow Customers * Improved dispute intake and management workflows reduce manual effort and accelerate resolution for card and ACH disputes. * Enhanced data model and questionnaire updates ensure compliance with evolving card network rules and regulatory requirements. * Unified workspace and portal enhancements improve user experience for cardholders and agents, promoting transparency and efficiency. * Automated document validation minimizes processing errors and speeds up chargeback workflows. * Integration with Visa and Mastercard systems provides seamless dispute lifecycle management within ServiceNow. * Theme and accessibility improvements support better usability for diverse user groups. Consolidated page of all release notes for Financial Services Card Operations from Xanadu to Australia. ## 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 Xanadu to Australia. 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 Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-financialservicescardoperations-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | 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. | [ ] ## New features Between your current release family and Australia, new features were introduced for Financial Services Card Operations. {#dfrn3-financialservicescardoperations-summary__entry__12} | Release | Release notes | |-|-| | Xanadu | [Playbook enhancements for dispute](https://www.servicenow.com/docs/access?context=dispute-playbook-for-portal&family=xanadu&ft:locale=en-US) : These enhancements enable the cardholders to do the following: * Initiate disputes directly through the portal by selecting your financial account and the transactions that you want to dispute. * Simplify the process of initiating and tracking disputes with the user-friendly dispute portal interface. * Collect detailed information about the dispute through a questionnaire on the portal. * Enable cardholders to attach relevant documents to their dispute cases. * Receive real-time updates on your case through the dispute tracker on the portal. * Submit the dispute through the portal to land on a review page, where the agent can review and modify the details for the case as required before submitting it for investigation. [Card disputes enhancements](https://www.servicenow.com/docs/access?context=dispute-management&family=xanadu&ft:locale=en-US) : * Added a common dispute questionnaire table with questions relevant to various card networks for both agents and cardholders. * Moved the reason code field to the card dispute transaction table. * Updated the logic to determine the reason code from the case to the card dispute transaction table. | | 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. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing Financial Services Card Operations features. {#dfrn3-financialservicescardoperations-summary__entry__22} | Release | Release notes | |-|-| | Xanadu | [Updated data model](https://www.servicenow.com/docs/access?context=installed-with-card-operations&family=xanadu&ft:locale=en-US) : Introduced the following two new tables for questionnaire intake: * Dispute Intake \[sn_bom_credit_card_dispute_intake\] * Cardholder Dispute Intake \[sn_bom_credit_card_cardholder_dispute_intake\] [Updated Card disputes transaction table](https://www.servicenow.com/docs/access?context=installed-with-card-operations&family=xanadu&ft:locale=en-US) : Removed the following fields from the Card disputes case table: * Account status as of transaction date * Dispute amount modification reason * Reason code * Reason code message * Suggested reason code [Visa Resolve Online (VROL) version 25.1 updates](https://www.servicenow.com/docs/access?context=card-operations-reference&family=xanadu&ft:locale=en-US) : 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. | | 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 | [ ] ## Removed Between your current release family and Australia, some Financial Services Card Operations features or functionality were removed. {#dfrn3-financialservicescardoperations-summary__entry__32} | Release | Release notes | |-|-| | Xanadu | * Moved the reason code for Late Presentment from the processing error decision question to the authorization category. * Updated the 12.1 chargeback rules to 11.3, aligning with VROL's latest release revision 24.2. * Removed the is_parcelado column from the dispute intake table, in alignment with VROL's latest release revision 24.2. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some Financial Services Card Operations features or functionality were deprecated. {#dfrn3-financialservicescardoperations-summary__entry__42} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | 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. | [ ] ## Activation information Review information on how to activate Financial Services Card Operations. {#dfrn3-financialservicescardoperations-summary__entry__52} | Release | Release notes | |-|-| | Xanadu | 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) 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=xanadu&ft:locale=en-US). | | 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. | [ ] ## 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 | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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 | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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 | |-|-| | Xanadu | No updates for this release. | | 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. | [ ] ## 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 | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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 | |-|-| | Xanadu | * Enable cardholders to create and track disputes with a dispute playbook experience on the portal. * Enhance navigation with intuitive transitions between different role-based landing pages. * Permit scoped admins to modify landing pages with extensive capabilities, confirming that content aligns with the specific needs and preferences of their user base. See [Financial Services Card Operations](https://www.servicenow.com/docs/access?context=card-ops-landing-page&family=xanadu&ft:locale=en-US) for more information. | | 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. | [ ]