question

ben-m avatar image
ben-m asked David Marginian answered

Qualifying Transactions - Iframe vs API

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.

e-commerce api
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
David Marginian avatar image
David Marginian answered

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?

Yes

Does this still apply if we use a multi-pay token as the source instead of the customer ID?

Yes

10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community