---
sourceDocument: Brazil Release Notes
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/release-notes

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Release Notes

ft:clusterId :

    - rn

bundleId :

    - rn


---

# Financial Services Operations Integration with Visa release notes

# Financial Services Operations Integration with Visa release notes {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
The ServiceNow®
Financial Services Operations Integration with Visa application enables integration with workflow applications, such as the card operations dispute management playbook with Visa Resolve Online (VROL) subflows. See the following sections for release notes by version.

## About Financial Services Operations Integration with Visa {#financial-services-operations-integration-with-visa-rn__financial-services-operations-integration-with-visa-rn-static-about}

* 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.
{#financial-services-operations-integration-with-visa-rn__ul_whv_vmn_dkc}

See [Financial Services Operations Integration with Visa](https://www.servicenow.com/docs/access?context=financial-services-operations-integration-with-visa-landing-page&version=brazil&pubname=brazil-financial-services-operations&ft:locale=en-US) for more information.{#financial-services-operations-integration-with-visa-rn__financial-services-operations-integration-with-visa-rn-static-about-2}

## Activation and other requirements {#financial-services-operations-integration-with-visa-rn__financial-services-operations-integration-with-visa-rn-static-requirements-activation}

Activation information{#financial-services-operations-integration-with-visa-rn__financial-services-operations-integration-with-visa-rn-static-activation-info}
:   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/r/store-release-notes/sn-store-release-notes.html).{#financial-services-operations-integration-with-visa-rn__financial-services-operations-integration-with-visa-rn-static-requirements-info-1}
{#financial-services-operations-integration-with-visa-rn__financial-services-operations-integration-with-visa-rn-static-requirements-info-1}{#financial-services-operations-integration-with-visa-rn__financial-services-operations-integration-with-visa-rn-static-activation-details}

## Version 5.2.2 {#ariaid-title2}

Capture dispute updates from the Visa allocation workflow for Fraud and Authorization cases without gaps in queue polling.

### What's new {#financial-services-operations-integration-with-visa-rn-2026-10__financial-services-operations-integration-with-visa-rn-2026-10-new}

Visa allocation batch queue support{#financial-services-operations-integration-with-visa-rn-2026-10__financial-services-operations-integration-with-visa-rn-2026-10-new-feature-1}

:   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.

{#financial-services-operations-integration-with-visa-rn-2026-10__financial-services-operations-integration-with-visa-rn-2026-10-new-list}

### What's changed {#financial-services-operations-integration-with-visa-rn-2026-10__financial-services-operations-integration-with-visa-rn-2026-10-changed}

Processing code field values updated for Visa compliance{#financial-services-operations-integration-with-visa-rn-2026-10__financial-services-operations-integration-with-visa-rn-2026-10-changed-feature-1}

:   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.
{#financial-services-operations-integration-with-visa-rn-2026-10__financial-services-operations-integration-with-visa-rn-2026-10-changed-list}

## Version 5.1.1 {#ariaid-title3}

Align the Visa dispute questionnaire subflows with Visa IES release 26.2, revisions 1 and 2. Dispute agents see accurate field labels, validation, and Spoke action wiring.

### What's changed {#financial-services-operations-integration-with-visa-rn-2026-09__financial-services-operations-integration-with-visa-rn-2026-09-changed}

Updated questionnaire field labels and validation{#financial-services-operations-integration-with-visa-rn-2026-09__financial-services-operations-integration-with-visa-rn-2026-09-changed-feature-1}
:   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://servicenow-prod.fluidtopics.net/ph1IGzHcfuFSLA~5FLUBIA#financial-services-card-operations-rn-2026-09 "Add new dispute intake questions for Visa hotel and facilities-withdrawal disputes, and provide read-back visibility into compelling-evidence transaction details.") for the corresponding questionnaire
    questions.
{#financial-services-operations-integration-with-visa-rn-2026-09__financial-services-operations-integration-with-visa-rn-2026-09-changed-list}