You don't need an association here, only a dependency between those classes.
Association comes in the action, when you need a permanent, long-term link between the corresponding objects. In code is this situation often reflected through data members. Here we speak about a short-term limited contact that should even not be persisted (a simple method parameter instead of a data member).
CardVerificator should of course "know" the "Card" concept in order to be able to verify it, but this is nicely explained with a simple generic dependency: