When a client is configured to do fraud card suspense the system has to check the fraud card status to confirm the account balance has been transferred prior to off setting the customer credit issued on the new end of chain card.  When second operation accounting is triggered the accounting will be routed into this flow to check the fraud card status prior to being executed.

When in the flow the system will check for fraud card status for defined number of days which is configurable at the client level.  Once the days have been exhausted the system will move to the Determine Fraud Card Status assignment for review.  From this assignment the user will have the ability to retry the fraud card status check or mark the fraud card as postable or not postable.  When a user marks the card as not postable it will trigger the fraud card suspense accounting to be manual.

Configuration

Enabling Determine Fraud Card Status - This is controlled at a Implmentation level and is not enabled in the product by default.  (IsUsingFraudCardSuspenseExtension)

How many times should the system retry if the integration call fails?  (D_ImplConfig.DetermineFraudCardStatusAttempts)

Clients can configure the check to be automated or manual in the the precondition table.  This is available for client overrides.  The product default is for this to be automated. (DetermineFraudCardStatusPreconditions)

References