Hi David,
I was wondering how I could go about making sure most of my app e-commerce transactions qualify. I'm noticing we cannot add fields to the tokenized card request using the Iframe.
https://docs.clover.com/reference/createtoken
The only values set by the iframe are;
address_zip, brand, exp_month, exp_year, first6, last4
If I save the card to a customer, and use the customer ID in the source, does it use that information ( Address, country, etc ) as part of the transaction qualification like it would if we tokenized it with it using the API?
Does this still apply if we use a multi-pay token as the source instead of the customer ID?
If we don't have 3DS yet, I'd at least like to make sure I can help the transaction qualification process as much as possible.