Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Zelle fraud case workflow when the result is not as expected

Updated on June 20, 2022

Use the Not as Expected process when the customer indicates that they sent money to another individual for an item, but the recipient received not what they expected to receive. Because Zelle is not a means to pay for merchandise or services, the activity suggests that the customer might have been the victim of a scam, and these cases are managed by the CSR as potential fraud or scam activity.

Pega Smart Dispute for Issuers
  1. In the Collect supplemental information view, in the How can we assist you today? dro-down list, the customer selects I think I am the victim of fraud or scam.

  2. In Describe the complaint in detail box, the customer enters a detailed description of the issue, and then clicks Submit.

  3. In the Customer interview view, the customer answers a series of questions to identify a possible fraud and determine the next action.

    The list of questions can be extended based on your organization's policy.
  4. In the Which of these best describes your issue? list, the customer/CSR selects I received what I paid for, but it was not as described/expected, which starts the Not as Expected scenario.

  5. The customer answers a series of questions that describe the case and help determine the resolution of the issue.

  6. In the Did you attempt to resolve this with the receiver of the funds? question, the customer/CSR selects an option that describes any previous resolution attempts:

    • To attempt to work with the receiver of the funds and resolve the case as Resolved-No Action, the customer selects No.
    • To route the case from the CSR worklist to the Zelle_Scam workbasket, the customer selects Yes.

      The customer then specifies the item they expected to receive, selects whether the issue is with merchandise or service, and enters the email of the party to whom funds to send the funds.

    The following figure shows an example of the Customer interview view:

    Customer interview view example
    The customer interview view on which the customer selects the not as expected scenario and specify answers to the questions that help resolve the case.

  7. The assignment in the back office has a service level agreement (SLA) of ten business days. After this period, the fraud investigator or appropriate back office personnel have the option to to review the case and attempt to contact the receiver for resolution. They capture their results based in their answer to the question Did the receiver respond and agree to resolve the issue?

  8. In the Capture resolution details view, the fraud investigator or back office worker selects, and then selects a resolution:

    Capture resolution details view options

    SelectionResolution options
    The receiver did not respond
    Courtesy Write-off
    The customer receives a courtesy write-off from the bank (Resolved-Courtesy Write-off).
    Sender liable
    The bank holds the sender liable (Resolve-Sender Liable).
    The receiver refused to take any action
    Courtesy Write-off
    The customer receives a courtesy write-off from the bank (Resolved-Courtesy Write-off).
    Sender liable
    The bank holds the sender liable (Resolve-Sender Liable).
    The receiver agreed to resolve the issue
    • The recipient refunds the sender through Zelle (Resolved-Refunded).
    • The recipient delivers merchandise or service to the customer (Resolved-Corrected).
    The following figure shows a sample configuration of the Capture resolution details view:
    Capture resolution details view example
    The Capture resolution details view where the user selects the resolution option to give the customer a courtesy write-off or hold the sender liable.
  9. Click Submit.

  • Previous topic Rules for Zelle fraud case when customers did not receive merchandise or service
  • Next topic Rules for the Zelle fraud case when the result is not as expected

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us