Download:
pdf |
pdfIMain Direct Deposit Fraud Prevention: Screen Package
Table of Contents
1. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen ......................................................................................................................................... 2
2. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for query .................................................................................................................. 3
3. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for SSN not found .................................................................................................... 4
4. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for SSN exist ............................................................................................................. 5
5. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for start block ......................................................................................................... 6
6. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for start block (fraud) .............................................................................................. 7
7. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for start block (preventive) ...................................................................................... 8
8. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for stop block ........................................................................................................... 9
9. Direct Deposit (Auto-Enrollment) Fraud Prevention Screen edit for transaction complete ...................................................................................... 10
Scenario 1: The screen below is used to query to see whether a previous request for a block of
an electronic Direct Deposit auto-enrollment exists. The user must enter a 9 digit Social
Security No. and click on the Search button in the upper right hand corner.
Scenario 1, continued. The following message is displayed when the SSN entered does not exist
on SSA’s NUMIDENT database. The NUMIDENT is the database in which SSA houses
information on each SSN that we have assigned.
Scenario 2: The screen below is used for query purposes of the DD Auto-Enrollment Fraud Block
database. This scenario illustrates where a valid assigned SSN exists on SSA’s NUMIDENT. The
user must click on the Search button to get results returned from the Fraud Block Table.
Scenario 2a. (No Block History). This example displays the message on the screen that will be
returned if there is no previous request for a DD Fraud Prevention block. The user can request
to add a block by clicking on the Start Block button at the bottom right corner (see Scenario 3).
If the user only wanted to query to see if a block exists on the record and the
recipient/beneficiary is not requesting to add a block the user will exit the application by closing
the window.
Scenario 3. This scenario illustrates a request to add a DD auto-enrollment fraud prevention
block. This scenario reflects a situation where a prior occurrence(s) of a block request(s) exists
on the record. To add a new block, the user must click the Start Block button at the bottom
right corner of the page and select one of two Reasons For Block buttons. Since a Stop date
exists in the latest occurrence, the only option for the user in this scenario is to add a new
block. If the individual is not requesting a new block, the user will exit the application by closing
the window.
Scenario 3a. The screen below displays the results when the user clicked on the ‘Start Block’
button and selected “Fraud Alleged” on the screen on page 6.
Scenario 3b. The screen below displays the results when the user clicked on the ‘Start Block’
button and selected “Preventive Measure” on the screen on page 6.
Scenario 4 is an example of a request to remove a DD Auto-Enrollment Fraud Prevention Block.
The user must click on the Stop Block at the bottom of the page to remove the block. This is
the only option available since you cannot request a block if the latest occurrence has a Start
and no Stop date. If the individual is not requesting to remove the block, the user will exit the
application by closing the window.
Scenario 4a. The screen below displays the results when the user clicked on the ‘Stop Block’
button.
File Type | application/pdf |
Author | Payne, Aaron |
File Modified | 2012-08-02 |
File Created | 2012-08-02 |