A solution that was exposed to me makes of:
-> PAYMENT an abstract class,
-> and PAYMENT_BY_CREDIT_CARD and PAYMENT_BY_CHEQUE
two subclasses of the PAYMENT class.
For PAYMENT, in ArgoUML, a class was created with no attributes and a stereotype <>.
For PAYMENT_BY_CREDIT_CARD was created a class with two attributes: number and date.
For PAYMENT_BY_CHEQUE was created a class with one attribute: number.
You should consider using superclass of Payment with attributes od Date, Amount etc, and 2 subclasses of CredtCardPayment and ChequingAccountPayment with their own specific attributes that are not in the superclass.