Org Web Adapter

pages/mmpy_163_prevent_payouts_from_being_added_to_transfers_after_processing_fees_have_been_attached.org

ID
9b145580-ab2c-4282-a605-57e7f80923a4

MMPY-163 Prevent Payouts from being added to transfers after processing fees have been attached

- source :: https://multimediallc.atlassian.net/browse/MMPY-163

- epic :: MMPY-198 Compliance Holds, Fraud Holds, and Banned Payees

- tags :: Falcon Nest Project Story Falcon Nest Project

- status :: Status - Complete

Tasks

DONE Look into best way to add new transfer status

researchmmpy163transfers
ID
585e00e3-c91f-edb7-c814-ccd871d4780b

- Note taken on

This seems like the simplest flow would just be to add a `_transition` call in

the `send` method of a Transfer to push the transfer into the "processing"

status. Beyond that, we also need to add some checks for transfers in

processing when adding new payouts so that the transfer can no longer be

changed once it's in the processing status.

I wonder if what we really want is some sort of:

TransferStatus.locked_statuses()

method so that anything in the processing, canceled or sent statuses don't

allow changing.

DONE Add new transfer status "Processing"

featuremmpy163transfers
ID
89fe5b8d-0d19-b775-99b9-2828356724a3

TODO Add check for processing transfer when payouts are attached

featuremmpy163transfers

TODO Add tests for putting transfers into "processing" status after pickup :tests:mmpy163:transfers

Requirements [3/3]

[X] GIVEN

A transfer exists and has user has no holds and the account is valid.

[X] WHEN

A transfer is picked up for processing.

[X] THEN

Move the transfer to a status of “Processing”.

Additional requirements [0/3]

[ ] GIVEN

A transfer exists for a user with no holds and a valid account with a status of "Processing".

[ ] WHEN

The transfer send process has begun.

[ ] THEN

No payouts can be attached to the transfer.

AND

Transfer may still be cancelled.