Open
Description
For many projects, the 'CreditCard' object is used for just customerData. We could split it up, but what would be the best way to do this, without BC breaks?
Gateways use getCard
and users use setCard
, so we can't just add a Customer object by default.
The most that bugs me is the name of the object, and the validation of the object. So could we just use the same object but allow both card and customer as objects? And change the validation a bit?
eg. passing customer
would behave the same as card
, by setting card
internally
And validate()
could behave different when parameters are passed.
See also #80
Metadata
Metadata
Assignees
Labels
No labels