Required field logic on action

When setting up fields with a true/false value for required, is there a way to designate two fields as required where only one needs to be populated but it doesnt matter which?

for example, if you are creating a payment it could be deposited directly to a bank account or go to undeposited. Depending on the case you will need provide either the bank account or the undeposited funds account. If I have each of these as a field, is there a way to say that either one of these two fields needs to be populated but not both?

You can build the action to do logic testing for the presence of required data when it executes in an automation, but you cannot define that type of complex logic at a field level for validation when doing data mappings.

ok. thats exactly what i was trying to do and catch it on the initiation of the action instead of inside it.