Enforce a unique constraint for crypto deposits

Without a foreign key on amount and id, what would prevent having an id where the deposits table has one value for amount and the deposits_crypto table has a different value for amount? This shouldn't happen if the functions are coded properly but I'd rather have an integrity constraint so that it's impossible to have that happen.