Update Payment Transmission Configuration during P2T

Following P2T, we must manually update the payment file transmission configuration to prevent the transfer of payment files to the bank. There is a gap between the completion of the refresh and the completion of post-refresh activities; during this interval, payment files may be transmitted if someone conducts testing. Is there an automated method to restrict payment file exchanges after P2T, rather than handling this manually?

Either inactivate the transmission configuration, remove the username/password, is there anything Oracle can do to make the transmission configuration invalid?