#deckberg-paymentmethods
fossil bluff
thanks for checking. that's a little surprising. must just be the way the data is stored I guess. is there a get customer and expand their payment methods that would include both? there should be an easy way to list all of the customer's attached payment types.
plain field
not really a technical limitation, it's just how that API was designed. The idea is we expect a flow of asking the customer how they'd like to do the payment and then you list their available methods for doing that
there's no trick or workaround no
also the advantage is you don't have to handle a polymorphic list in the response
and that if we add new payment method types, your code doesn't break since you'd start getting those in your list calls
those are the main reasons it was designed this way
but there's lot of feedback raised about this so I'd be fairly certain we'll eventually add some types[] parameter to it
fossil bluff
yea I would think it should at least allow an array for the type so I can decide which types to pull and I can handle a predictable reponse