If a recovery is successful, whether at chargeback, pre-arb, or Arb, QFD will automatically send the Paid letter.

For Visa/PLUS network transactions, any documentation included with the dispute response is automatically uploaded to the claim.

The docs are visible within the Attachments section of the Case Assets (far right side of the screen), as well as within the dispute assignments to make it easier to navigate on multi-dispute claims.

Card number, date, and ARN if provided

Once enriched, we just use Case Number

In QFD, yes

Some APIs will not support this.

JackHenry Symitar will not support this function

This is a configuration setting we can support; this will only occur after the initial accounting call has failed.

All of our accounting is done via real-time API call.  Depending on how the accounting was triggered, it can sometimes take a few minutes to kick off.

Not always. Foreign Exchange Feed are almost 100% automated.
Other fees not tied to a transaction 1:1 can be automated but are usually manual.

Any dispute covered by Reg E would be sent through the interest adjustment flow if the account is interest-bearing.

When applicable, the interest-bearing accounts are identified from the Silverlake response, using the “IntBearAcct” field.

By default, once daily at the end of the day

In the Administrator portal, there is a report called "Operators By Access Group" which will identify who has made changes to a user. We do not have a report for what was changed. 

Those over the Visa network, including PLUS.

Paper letters are sent via SFTP.  Each file export will include a metadata file with a list of letters included, which should be used as reconciliation.

We also have a report in QFD, called Outbound Correspondence, that shows all communication sent, regardless of Channel.

We strongly recommend using the out-of-the-box letter package that are customized to your firm's branding but are not altered further. 

For more information on QFD's standard letter package vs. customized letters, see this .

How is information tracked with ACH disputes since they're posted to Jack Henry - how does QFD support ACH disputes?

The transaction information is passed to QFD via Silverlake

Aside from the standard transaction information, QFD is currently set to map the below ACH-specific details:

• • Company ID
  • SEC Code
  • Company Name

Manual enrichment is required to complete Trace Number (not provided by JH Silv response)

We use US East N Virgina as our primary and US West Oregon as our secondary zone

ACH claims are always given Reg E protection in QFD, regardless of transaction age or the span of transactions.  Under § 1005.6(b)(3), consumers are protected for the first statement, plus 60 days, and can be held liable for any subsequent transactions.  Even still, § 1005.6(b)(4) requires that timeframe be extended for "extenuating circumstances", though no definition is provided.  Since QFD is unable to determine a cause for delay, all transactions are considered protected.  There are configuration settings that can be modified to ensure some automation is stopped on aged transactions, however if a user fails to take action by Reg45, QFD will resolve the claim and send a Paid letter to the accountholder.