--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3ba bundleId : - delta3ba --- # Combined Financial Services Operations Integration with Visa release notes for upgrades from Australia to Brazil # Combined Financial Services Operations Integration with Visa release notes for upgrades from Australia to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 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 Operations Integration with Visa release notes for upgrades from Australia to Brazil This consolidated release notes document assists ServiceNow customers preparing to upgrade the Financial Services Operations Integration with Visa from the Australia release family to Brazil. It summarizes new features, changes, removals, deprecations, and activation information relevant for this upgrade. The document also highlights important pre- and post-upgrade tasks to ensure a smooth transition. Show full answer Show less ## New Features * **Visa allocation batch queue support (Brazil)** : A new subflow, *Process Incoming Acceptance Batch Queue*, processes updates from the INCOMINGBQACCEPTANCESRECEIVED batch queue for Visa disputes involving acquirer full liability acceptance. This polling is separate from existing batch queue adapters, reducing missed acceptance processing in fraud and authorization workflows. ## Changes * **Processing code field updates (Australia and Brazil)** : The *processingcode* field in the Financial transaction table has updated choice values and refined labels aligning with current Visa data specifications. These changes cover transaction types such as purchases, cash disbursements, adjustments, account funding, fee collections, returns, activations, and inquiries. Existing transactions require no action. * **Questionnaire field updates (Australia and Brazil)**: Key questionnaire fields have been renamed for clarity, including changing "Explain why credit presented does not apply" to request transaction identifiers and dates, and shortening certification question labels. The Name field is no longer mandatory, and the Key Factors field now accepts up to 200 characters. * **Spoke action enhancements (Australia and Brazil)**: Added new fields "Date facilities were withdrawn" and "Date cardholder checked out from hotel" to dispute-related spoke actions. Also added CE Transaction Details as a read-back field to improve dispute questionnaire processing. * **Updated subflows (Australia)**: Several dispute-related subflows were enhanced to support integration with the Card data security application, improving compliance and data handling. ## Removals and Deprecations There are no removals or deprecations for Financial Services Operations Integration with Visa between Australia and Brazil releases. ## Activation and Installation Financial Services Operations Integration with Visa can be installed by requesting it from the ServiceNow Store. Customers should follow standard procedures for app requests and review cumulative release notes available in the store's version history. ## Additional Information * No updates to browser requirements, accessibility, localization, or additional technical requirements were introduced between Australia and Brazil releases. * **Highlight for Australia release**: Updated subflows aim to help prevent storage or transmission of Payment Card Industry (PCI) data for card disputes within ServiceNow instances. * **Highlight for Brazil release**: Provides a framework supporting dispute resolution use cases requiring integration with Visa Resolve Online (VROL). Predefined subflows enable primary integrations such as dispute case creation, fraud reporting, and dispute questionnaire submission. Consolidated page of all release notes for Financial Services Operations Integration with Visa from Australia to Brazil. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Financial Services Operations Integration with Visa release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Australia 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 Operations Integration with Visa to Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__2} | Release | Release notes | |-|-| | 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 Operations Integration with Visa. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__8} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | Visa allocation batch queue support : The Process Incoming Acceptance Batch Queue subflow captures and processes updates from the `INCOMING_BQ_ACCEPTANCES_RECEIVED` batch queue for Visa disputes in the Fraud and Authorization allocation workflow: cases where an acquirer accepts full liability on an issuer's chargeback, or on a pre-arbitration response filed or submitted by the issuer. The system polls this subflow separately from the existing Batch Queues Flows Adapter, so these acceptances are less likely to be missed during allocation processing. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Financial Services Operations Integration with Visa features. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__14} | Release | Release notes | |-|-| | Australia | Updated questionnaire field labels and validation : Renamed the question "Explain why credit presented does not apply" to "Provide the Transaction Identifier(s) or Acquirer Reference Number(s) and the Transaction Date that the credit(s) was applied to and why the credit(s) does not resolve the Dispute," and renamed "Certification that the merchant facilities were withdrawn" to "Certification that the facilities were withdrawn." The Name field is no longer required, and Key Factors now accepts up to 200 characters. Updated Spoke action wiring for new questionnaire fields : Added the Date facilities were withdrawn and Date cardholder checked out from hotel fields to the Submit Dispute Questionnaire and Look up Dispute Details Response Parser spoke actions, and added CE Transaction Details as a read-back field on Look up Dispute Details Response Parser. See [Financial Services Card Operations 2026 September Monthly release notes](https://www.servicenow.com/docs/access?context=financial-services-card-operations-rn-2026-09&family=australia&ft:locale=en-US) for the corresponding questionnaire questions. Processing code field values updated for Visa compliance : The `processing_code` field choice values in the Financial transaction table have been updated to align with current Visa data field specifications. Existing choice values have been updated with refined labels and descriptions; new choice values have been added to support additional transaction types. The updated choice values include: * `00` --- Goods/Service Purchase - Debit * `01` --- Cash Disbursement (for example, withdrawal or cash advance) - Debit * `02` --- Adjustment - Debit * `10` --- Account Funding or Card Absent Account Funding * `11` --- Quasi-Cash Transaction - Debit or Internet Gambling Transaction * `19` --- Fee Collection - Debit * `20` --- Return of Goods - Credit, Credit Transaction, Credit Voucher * `22` --- Adjustment - Credit * `26` --- Original Credit * `28` --- Activation and Load / Load * `29` --- Funds Disbursement - Credit * `30` --- Available Funds Inquiry * `39` --- Eligibility Inquiry * `50` --- Bill Payment (U.S. only) * `53` --- Payment (U.S. only) * `72` --- Activation (POS) Dispute agents and administrators see these updated labels and descriptions in transaction UI drop-down lists and data entry forms. Existing transactions require no action. Existing choice values not listed here remain unchanged. [Updated subflows](https://www.servicenow.com/docs/access?context=components-installed-with-the-financial-services-operations-integration-with-visa&family=australia&ft:locale=en-US) : The following subflows have been updated to support integration with the Card data security application: * Look up Associated Transactions * Look up Dispute Pre Arbitration Details * Look up Dispute Filing Details * Look up Dispute Response Details * Look up Dispute Pre Arbitration Response Details | | Brazil | Processing code field values updated for Visa compliance : Updated `processing_code` field choice values in the Financial transaction table align with current Visa data field specifications. Existing choice values have been updated with refined labels and descriptions; new choice values have been added to support additional transaction types. The updated choice values include: * `00` --- Goods/Service Purchase - Debit * `01` --- Cash Disbursement (for example, withdrawal or cash advance) - Debit * `02` --- Adjustment - Debit * `10` --- Account Funding / Card Absent Account Funding * `11` --- Quasi-Cash Transaction - Debit or Internet Gambling Transaction * `19` --- Fee Collection - Debit * `20` --- Return of Goods - Credit, Credit Transaction, Credit Voucher * `22` --- Adjustment - Credit * `26` --- Original Credit * `28` --- Activation and Load / Load * `29` --- Funds Disbursement - Credit * `30` --- Available Funds Inquiry * `39` --- Eligibility Inquiry * `50` --- Bill Payment (U.S. only) * `53` --- Payment (U.S. only) * `72` --- Activation (POS) Dispute agents and administrators see these updated labels and descriptions in transaction UI drop-down lists and data entry forms. No action is required on existing transactions. Existing choice values not listed here remain unchanged. Updated questionnaire field labels and validation : Renamed the question "Explain why credit presented does not apply" to "Provide the Transaction Identifier(s) or Acquirer Reference Number(s) and the Transaction Date that the credit(s) was applied to and why the credit(s) does not resolve the Dispute," and renamed "Certification that the merchant facilities were withdrawn" to "Certification that the facilities were withdrawn." The Name field is no longer required, and Key Factors now accepts up to 200 characters. Updated Spoke action wiring for new questionnaire fields : Added the Date facilities were withdrawn and Date cardholder checked out from hotel fields to the Submit Dispute Questionnaire and Look up Dispute Details Response Parser spoke actions, and added CE Transaction Details as a read-back field on Look up Dispute Details Response Parser. See [Financial Services Card Operations 2026 September Monthly release notes](https://www.servicenow.com/docs/access?context=financial-services-card-operations-rn-2026-09&family=brazil&ft:locale=en-US) for the corresponding questionnaire questions. | [ ] ## Removed Between your current release family and Brazil, some Financial Services Operations Integration with Visa features or functionality were removed. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__20} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Financial Services Operations Integration with Visa features or functionality were deprecated. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__26} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Activation information Review information on how to activate Financial Services Operations Integration with Visa. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__32} | Release | Release notes | |-|-| | Australia | Activation information : Install Financial Services Operations Integration with Visa 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 Operations Integration with Visa is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Brazil | Activation information : Install Financial Services Operations Integration with Visa 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 Operations Integration with Visa we have noted them here. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__38} | Release | Release notes | |-|-| | 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 Operations Integration with Visa we have noted them here. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__44} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Financial Services Operations Integration with Visa, such as specific requirements or compliance levels. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__50} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Financial Services Operations Integration with Visa we have noted them here. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__56} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Financial Services Operations Integration with Visa we have noted them here. {#dfrn3-financialservicesoperationsintegrationwithvisa-summary__entry__62} | Release | Release notes | |-|-| | Australia | Use updated subflows to help prevent storage or transmission of Payment Card Industry (PCI) data for card disputes within your ServiceNow instance. See [Visa](https://www.servicenow.com/docs/access?context=financial-services-operations-integration-with-visa-landing-page&family=australia&ft:locale=en-US) for more information. | | Brazil | * Provides the framework for supporting dispute resolution use cases on ServiceNow which requires integration with VROL. * Use predefined subflows to address primary integrations such as creating a dispute case, reporting fraud, and submitting a dispute questionnaire. See [Visa](https://www.servicenow.com/docs/access?context=financial-services-operations-integration-with-visa-landing-page&family=brazil&ft:locale=en-US) for more information. | [ ]